Reminder that Google Maps only exists because of one 100-1000x engineer who rewrote all the code in one weekend
Reminder that Google Maps only exists because of one 100-1000x engineer who rewrote all the code in one weekend https://t.co/kFKGU0y8qr
Not familiar with the ajax/XML heyday of the past, can anyone explain why XML contributed so much bloat?
Bret responded!! Every eng should aspire to be a Bret
Bret responded!! Every eng should aspire to be a Bret
@zack_overflow For extra context: XSL is very complex and powerful tool for almost arbitrary processing of XML documents. It's so heavy, the SPEC2017 CPU benchmark still includes a test that just runs Xalan-C++ which is an XSL processor.
@zack_overflow If love my XSL. If still use it to extract what I need from JUnit XML output. XSL:FO for generating PDF is actually easier to manage and understand than code using iText. If you serve XML and the server has GZIP enabled the results are pretty impressive. Where things start going/
Human readable export and import files are the only way. I spent a career trying to make people understand this. Also the power of diffs. If you tell a roomful of engineers that human readable formats and diffs are useful, they will say "Of course! Duh!" And then completely ignore this advice.
@zack_overflow I was scrolling down to search for bret.
@zack_overflow XML is not the most efficient way of representing data, depending on your model design you can actually come with 10% of the size of JSON. Doing XSLT in the browser with lot of XML hurts.