This might just be one of those revolutionary moments in the history of consumer software engineering.
Yes, its not native to the OS primitives etc. But with a strong core graphics engine, that's just an abstraction away. You can always create WinUI/SwiftUI like look and feel. The ecosystem is what we need to look out for.
Congratulations on the launch and best of luck. A step forward into removing Electron bloat from the world of desktop apps
This. Writing a parser in Zig is so simple. Just allocate once, and then start writing your parser.
One allocator for parser, one for scanner. One for type allocation. Keep them all for semantic analysis. Write the output renderer (binary/language). Deallocate.
In this whole process, it makes it so easy to not think about memory anymore. Just enjoy writing your program.
But I left it because of recursive imports. I had to basically put all my types into one file and use them from various others. For a relatively medium sized project (~10LOC), its a but of a hassle. Refactoring is an issue.
That being said, the language is fantastic. Can anybody with experience suggest me what HTTP library/framework do they prefer for servers?
Go through Zig’s Async. Its a bit like co-routines but low level. You are required to keep track of memory allocations and pointers to function “frames”. For someone coming from a high-level language POV, frames were a new concept. But Zig does it so superb.
Zig just needs some runtime event loop like Tokio or AsyncIO from Rust to get up and running with its fantastic async model.
Welcome to Hackernews. Being sour is part of every user here just to spread negativity in the guise of "user feedback". Just ignore those comments and read the positive ones.
Try logging in programming.dev and check your network tab.
You will see the request being sent as a websocket. The lemmy author implemented lemmy so as to see how fast you can get the site working. Inferno, Rust, WebSockets. He probably didnt have expect the scaling issues that come with it.
Anyways, I am happy the site exists. Kudos! Looking towards better implementation in the next release
The exact problem with SvelteKit, NextJS, NuxtJS etc is the plugin the OP has to create.
Somehow these meta-framework don't make much sense once you go past the basic DB -> REST -> SSR apis. Productivity decline is a guarantee. DX will suck your soul. Svelte is a far enjoyable library/framework than SvelteKit.
They did bring a lot of good things into the world of JavaScript, but I think this architecture will soon be obsolete for regular template (webpages) or simple SPAs (webapps).
That being said, one of the most promising contenders is InertiaJS though. I think something like InertiaJS will come in 2-3 years and make these meta-frameworks obsolete. Why? The DX.