3 ms·
>We do have a choice though. I took the choice: to run from the web with my hair on fire, screaming. Towards embedded, where none of this matters, and where t
by aa-jv 3y ago
>We do have a choice though.
I took the choice: to run from the web with my hair on fire, screaming.
Towards embedded, where none of this matters, and where the crux of the whole thing is really, really important: its the atoms, then the electrons...
We don't need the web if the user holds our interface in their hands. Surprisingly enough, the web holds an iron grip on that face/phone interface, but .. one easy solution to all the cruft, is simply return to the roots.
Yes, this requires hardware production capabilities. Its not for everyone, then.
But I tell you, 40 years into this industry, it was so refreshing to abandon all of the fancy front-end stuff and just get straight down to the embedded realm. Nothing nicer than having the machine - and the user - all to oneself.
Of course, this edge case gets discussed further in the article, but that is just one of a few things this old-timer could say about what went wrong with programming culture... (*cough* *cough*..should never have removed the compiler..*cough* *cough*.. this opened the door for all the weirdos to take over what should've stayed in the OS .. *cough*)
- namaria 3y agoI keep finding myself reading Forth literature and playing with gforth in the evenings, thinking fondly of hardware to escape the atrocities of editing yaml and waiting 10-30 minutes to see results. Maybe I should run in the same direction...
- aa-jv 3y agoYou really should. I encourage you to do so. There is still so much potential in the embedded world to "get it right" - i.e. undo all the cruft and bloat of the desktop/web/etc. But, be careful, its requires just as much rigour as any other market. Perhaps more so, in some ways. Tooling and methodology are a lot more important ..