pxeger1
Joined 5 years ago
Joined 5 years ago
If you wanted to implement a package manager in the build system and keep it in the compiler, what abstraction for it would you provide between the compiler and the build system? This probably affects how you design the import system, and some other fundamental parts of your language. Those are important to get right, and probably hard you change. If you start by tightly coupling the package management and the compiler, it could be easier to design that by starting with the programmer experience you want and working backwards. Then you can change the implementation later, affecting fewer users.
I'm thinking specifically of Python here, where the import system is crazily complicated and warty, partly to accommodate all the varied ways package management was done. This compares to Go where there is a comparatively neat and small syntax for imports and the like, because they were designed with package management in mind from the start. (Not that I agree with all its design decisions.)
This is not called double parking. Double parking is something different: https://en.wikipedia.org/wiki/Double_parking
I don't know about you but here in the UK, close parallel parking is normal and expected, and I was taught to avoid trying to cross in the gap between two parked cars, and to be extra careful if I was going to. In this scenario some blame might lie with the driver for going too fast, but I would certainly also blame the child (or their parent) for stepping far into the road without looking.
I think the policy Harris is referring to is based on the _risk_ of something like this - it is easy to imagine wireless devices being vulnerable and enabling this capability - rather than being based on definitive existence of this capability.
[ my public key: https://keybase.io/pxeger; my proof: https://keybase.io/pxeger/sigs/pWFo0gTe2jOWx8j82aJ_hhdt2wU97tpY-l0AzxVfZFw ]