Re:The Eve programming language project is winding down
by rtpg on Thursday January 25, 2018 @05:22AM
(#16229967)
Here's some really silly examples. They all have reasons, and it makes sense in context, but it's part of the deal.
- Java code needs to be in a class. I can't open up a file and start typing immediately
- bool(midnight) being false
- C header ifdef silliness to make sure you don't double include a header
- circular dependency import issues in many languages
- strings and bash as the lowest common denominator meaning that almost everything that glues commands together must first write a parser for the output of `ls`
- our not putting encoding explicitly into files meaning that there have been decades of people getting weird glyphs when sending files to each other.
- implicit str to bytes and back in Py2 causing billions of spurious decode/encode calls. And many more incorrect calls
All this stuff is small , and has reasons. But it's also stuff that's been around for decades and decades and cascades into massive weirdness. Death by a bazillion idiosyncrasies.
- Java code needs to be in a class. I can't open up a file and start typing immediately
- bool(midnight) being false
- C header ifdef silliness to make sure you don't double include a header
- circular dependency import issues in many languages
- strings and bash as the lowest common denominator meaning that almost everything that glues commands together must first write a parser for the output of `ls`
- our not putting encoding explicitly into files meaning that there have been decades of people getting weird glyphs when sending files to each other.
- implicit str to bytes and back in Py2 causing billions of spurious decode/encode calls. And many more incorrect calls
All this stuff is small , and has reasons. But it's also stuff that's been around for decades and decades and cascades into massive weirdness. Death by a bazillion idiosyncrasies.