3 ms·
So, I literally teach all of this, and I think the biggest thing to get people to understand is that -- the stack you use right now is a product of evolution, n
by jrm4 3y ago
So, I literally teach all of this, and I think the biggest thing to get people to understand is that -- the stack you use right now is a product of evolution, not intelligent design.
It's a minimum of THREE languages to get anything going using the presently most popular programming language; and that includes the stupid fights over whether all three of those are ACKSHUALLY languages.
The environment feels almost hostile to onboarding by design, so you have to STRONGLY distinguish theory from practice.
- paulddraper 3y agoThough that's not unique to the web. Many UI platforms have multiple languages, e.g. XAML.
- jrm4 3y agoSure, but overwhelmingly "the web" is what people are interested in -- in a way, it's more of a default "operating system" than most operating systems.
- paulddraper 3y agoRight, I'm suggesting that using multiple languages is not a mistake or idiosyncracy in the web platform.
- jrm4 3y agoBut it really is in practice? As in, if you could design "programming on the web" from the ground up, I'm going to guess you wouldn't base it on technology designed to make reading on the web a look little more like a newspaper plus hyperlinks, and then yet another language that sort of does the same thing but...more, and visually oriented -- before you even get to, and not strongly integrated with, real programming logic?
- paulddraper 3y agoIf my goal is a platform for both static documents and interactive applications... I would design it very similarly. Yes, there would be a lot of 20/20 hindsight improvements, fewer WTFs, but the overall structure would be similar. And you?