You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, I think a process-per-request approach would be better to keep Novika simple when it comes to serving. Anything more complex will require agents (read: concurrency / parallelism [don't know which one haha]). And agents are for the far far future.
I guess an API which blocks while a connection is alive is the way to go for now.
Another thing is sockets. They're a must: why use SDL if we can use the browser? At the very least I'd like to see live-reloading docs/environment. But that, too, is for the far far future. And an SDL-backed UI wrapper/framework is still an idea, why not. It'd be much more lightweight than the browser approach. Signals as in SolidJS and a UI DSL are a nice little combo, essential for showing the practicality of Novika to the world. E.g. the simplest proposed UI framework usage is app: 'Some text...' which will show something like a message box. I'm still a newb in from-scratch UI dev, so can't tell when this "far far future" will be there.
Should allow to fetch and serve. Should be a simple, very high-level interface.
The text was updated successfully, but these errors were encountered: