Hacker News new | past | comments | ask | show | jobs | submit login

I don't have solidified idea for reinventing web dev but I'm oscillating between two opposing strategies. One would be to have a micro app server in hardware - think RPi nano or even less, where each http session gets a dedicated "box" thus returning to the model of development that reduces everything to a single user, single process system. Persistence becomes a challenge. Ideally it would be a truly shared hardware component or alternatively it would be a swarm of tiny disks that can be queried independently and in aggregate.

The opposite idea would be to build a single OS on top of distributed hardware that presents resources in a truly unified fashion where the illusion of programming and deploying to a single machine is unbroken and none of the underlying abstractions leak up. Think VMware but in reverse.

The other thing that must be done over is the DOM/JS paradigm. It's so absurdly and ridiculously complex for what it does that it makes most developers laughable unproductive. There is no reason there couldn't be an environment like Delphi or VB but geared to the web developer. Wasm is a ray of hope here as its cutting loose the inane JS/DOM paradigm and finally offering a plain programmable canvas to the browser for the first time since the demise of Flash an Java applets before it.




The idea of single OS sounds great! Sounds like the future of the Cloud.

DOM/JS -> I think it now mostly came down to the paradigm of reactive programming, with React / Vue / Svelte. What about Delphi and VB, what was so good about them?


it was easy to reason about. It was basically a canvas and UI components wired with callbacks. It didn't have the state management stuff of Redux but it was dead simple to reason about anyway despite everyone rolling out their own "state" objects.

But the whole idea of mutating UI by changing the DOM via a script is a pile of needless complexity for 99% of the apps out there. A simple canvas with GUI components that fire callbacks would be way easier for most developers to work with.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: