|
|
|
|
|
by seanmcdirmid
3064 days ago
|
|
You are being a bit harsh. These were ambitious undertakings with high levels of risk going into them, which, I bet, were well known. I've struggled in this field for 10+ years now and there are lots of dark alley ways that end in walls. Then everyone constantly tells you this has already been done when, no, it really hasn't (at best, the technology is there but so piss poor designed that it isn't useful). If you reign in your ambition, well, isn't that why innovation in the programming experience field is so stagnant (basically stuck at the Smalltalk level) in the first place? We should be free from disdain to take risks, possibly lose, with a chance of hitting it big. |
|
It’s not that programming ergonomics are stagnant, it’s that all of the gains have been made by professionals. And the tooling is nearly impossible to leverage for a beginner environment because all of the assumptions of a pro developer are built in to their design.
The innovations are there, Heroku, Git, CSS, Markdown... these are all triumphs of programming ergonomics. They’re just all inevitably coopted by professional “Foundations” and amended to the maximum level a Pro developer can handle. JavaScript is almost useless for beginners now because the tooling is so complex, but full time front end devs can crank out HTTP packets like no ones business.
So you will need to watch those developments and lean on their ideas and some of the low level tooling if you ever hope to build a beginner environment. But you can’t use the tools themselves.
Still, if you start with SmallTalk you will fail. If Chris Granger and Bret Victor started their and failed, you will fail too, because those guys are rockstars.
You need to take the ideas being tested in the Pro tools and use them, without adopting the Pro implementations or even the interfaces. It’s or easy.