All of this NPM bruhaha has me wondering, what does a better solution look like? NPM has always been a reason I’m wary of modern JS dev. The whole ecosystem seems contingent on NPM as its central rail — what happens when it is bought, hacked, or just flakes? I pretend that quicklisp does it better, but I am really not sure, tbh. Is a centralized package manager always going to be a or even the central point of failure for a wider ecosystem? I regularly use a bunch of different package managers across a few different languages, is one better than the other? At the end of the day is their a better model to follow?
Follow this tag
In reply to: Caution: Chromebooks
Thanks for sharing these insights! Reading them, I think you are totally right that it is a bit wonky to say (as I did!) that a Raspberry Pi is a better choice than a Chromebook. I also think you are 100% on the nose re: tech elitism. As the father of a young child, I’m heaps intrigued by what you’ve said about iPads and young kids (especially those who cannot read, yet). I’ve played a little bit with some apps meant for kids, and in a past life, before I confused myself with a liberal arts education I was set on becoming a pre-school/kindergarten teacher. If I ever go back to school I’d most certainly be interested in exploring how to design systems (digital, physical, and otherwise) with children in mind, e.g. what does a public transit system for kids look like.