4 ms·
Genuine question, not trying to be dismissive - but why should something like a pretty printer be part of the JVM? It looks like something I'd expect to either
by geokon 4y ago
Genuine question, not trying to be dismissive - but why should something like a pretty printer be part of the JVM?
It looks like something I'd expect to either be an external tool (like VisualVM) or part of an IDE
- jitl 4y agoHow would this work with an IDE? As part of a debugger in the IDE? Isn’t it nice that you could throw an Error with this stuff?? I don’t write Java but I do end up writing pretty printers whenever I work on a project with interesting binary data zooming around between memory, network, and disk, and it’s cool that this framework builds it in. I would love if all languages had a pretty printer this nice for their struct types.
- ohgodplsno 4y agoBecause language usefulness pretty much scales with stdlib features. Tools then get built around that pretty printer, instead of everyone having their bespoke implementation. The Java ecosystem is many things, but you cannot say it isn't homogenous. Dependency injection ? Every single project that has gone on to use annotations will be using the same @Inject. And so on, for many, many featyres.
- marginalia_nu 4y ago> Every single project that has gone on to use annotations will be using the same @Inject Except when they use @Autowired. (Ackshually aside, I do agree with the sentiment of your post. The standard library is arguably one of Java's greatest assets)