5 ms·
I have a strict NO XML policy in any codebase that I control. It's not because I think that XML necessarily always kills babies, it's because I think that XML
by snprbob86 16y ago
I have a strict NO XML policy in any codebase that I control.
It's not because I think that XML necessarily always kills babies, it's because I think that XML has never once been the best choice. "Does everything well enough, but I don't need to learn or develop a new technology" is not a valid reason to use it and there are plenty of valid reasons not to use it.
That said, XML has killed every baby I've ever exposed to it.
- bpodgursky 16y agoDo you count even things like ant buildfiles? I won't say that editing them is fun, but it's no worse than configuring any other build system.
- beagle3 16y agoWell, Java is worse than most things, but even for Java - djb redo, recently implemented by Avery Pennarun (apenwarr) is better than everything else.
- endtime 16y agoIf you're using Java, you've already given up on not killing babies.
- beagle3 16y agoWell, Java is worse than most things, but even for Java - djb redo, recently implemented by Avery Pennarun (apenwarr) is better than everything else.
- xiongchiamiov 16y agoReally? In my (admittedly limited) experience, ant was much more of a PITA than things like Rake and Scons.
- beej71 16y agoI've exposed it to the "structured document markup" baby, and it has cared for it quite nicely.
- zdw 16y agoDoes this go along with your strict "NO WINDOWS" and "NO FUN" policies as well? Seriously, there are places where XML is the right tool, which the poster does a fine job of bringing up. There are a lot of places where it is not, but was used because something better for those specific use cases hadn't been invented yet - JSON is barely 10 years old, whereas XML's SGML roots go back over 30. Whatever the case, we're better off with ANY structured data format than old delimited and fixed column width formats from the dinosaur days.