> It's a very unpopular opinion around here, but I think designers using the next generation of no-code tools will eat front-end and simple app developers' lunches and I think it will happen really soon. I'll bet teams at Wix, Webflow and other no-code authoring tools are working like mad to develop these tools right now, and I'll bet that's a hair's breadth from automatically generating electron apps from whatever users make there.
I'm sure Wix et al are indeed working on that. Looking at their website, they've been at it for 17 years and have a whole bunch of high-level things already available — meaning "blog" and "eCommerce" and "scheduling", not merely "fancy checkbox" or "date widget" — which will cover the needs of a lot of small businesses who neither want nor could afford a single full-time web dev for even just 3 months.
Nevertheless, I disagree with your core claim: I learned how HTML worked partly by reading the output of Dreamweaver[0], followed by teens working with REALbasic (now Xojo) and then VisualBasic. I also spent most of the last decade using Interface Builder in Xcode (with 1.5 years of "why did you do this in C++?" and 1.5 years of "why won't Xcode render this SwiftUI like it's supposed to?").
I don't understand why the visual editors aren't more popular in our profession — they seem like they should be perfect; SwiftUI and React shouldn't need to even exist — and it's that gap between how I think the world ought to work and how I observe it actually working that contains the real problem that means so many of the jobs we do, aren't with the no-code tools we already had 25 years ago.
(Of course, one possibility is that Upton Sinclair quote: “it is difficult to get a man to understand something, when his salary depends on his not understanding it.”, and perhaps we're all just in a bubble of belief that can collapse at any time…)
[0] I think. Something like that anyway, free demo on a Mac[Format|World|User] magazine cover CD.
I'm not totally sure, but you seem to be conflating knowing how to design interfaces and being able to code them? They're not even in the same career trajectory. I could be misreading what you meant.
I'm sure Wix et al are indeed working on that. Looking at their website, they've been at it for 17 years and have a whole bunch of high-level things already available — meaning "blog" and "eCommerce" and "scheduling", not merely "fancy checkbox" or "date widget" — which will cover the needs of a lot of small businesses who neither want nor could afford a single full-time web dev for even just 3 months.
Nevertheless, I disagree with your core claim: I learned how HTML worked partly by reading the output of Dreamweaver[0], followed by teens working with REALbasic (now Xojo) and then VisualBasic. I also spent most of the last decade using Interface Builder in Xcode (with 1.5 years of "why did you do this in C++?" and 1.5 years of "why won't Xcode render this SwiftUI like it's supposed to?").
I don't understand why the visual editors aren't more popular in our profession — they seem like they should be perfect; SwiftUI and React shouldn't need to even exist — and it's that gap between how I think the world ought to work and how I observe it actually working that contains the real problem that means so many of the jobs we do, aren't with the no-code tools we already had 25 years ago.
(Of course, one possibility is that Upton Sinclair quote: “it is difficult to get a man to understand something, when his salary depends on his not understanding it.”, and perhaps we're all just in a bubble of belief that can collapse at any time…)
[0] I think. Something like that anyway, free demo on a Mac[Format|World|User] magazine cover CD.