2 ms·
With the year so prominently in the title, i thought this was going to be about a technology that is obviously not trendy anymore, ie, JAX The Terrible Java XML
by skrebbel 5y ago
With the year so prominently in the title, i thought this was going to be about a technology that is obviously not trendy anymore, ie, JAX The Terrible Java XML Parser. I'm disappointed that it was just blog title spam about some non-controversial modern technology.
- jszymborski 5y agoWait, is the "The Terrible Java XML Parser" moniker tongue-and-cheek or sincere? I remember JAX (the XML parser) really saving my bacon when I was parsing larger-than-memory XML files ages ago.
- skrebbel 5y agoIt was sincere, but I'll readily admit that the opinion was informed by a 15-year-younger me who definitely was not trying to parse larger-than-memory XML files. I bet it was just a matter of the wrong tool for the job, but I (with some weird fondness, I might add), remember finding it extremely overengineered, even for Java standards.
- jszymborski 5y agoIf XML files fit in memory, then it totally feels like an astronomically more annoying way to parse files. Totally sympathize with the sentiment.
- bart_spoon 5y agoIt’s not really spam, because it’s the opposite situation of what you describe: JAX is still in its infancy and doesn’t have high adoption yet, and as such, the user experience is changing rapidly over time. It’s valid to title your article something like “X in YEAR” when a few years ago and a few years from now the experience would be very different.