himujjal

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

I like ZSF and what it stands for.

I don’t like “American” only politics in it. Thats it. In fact I would like zero politics in it. (from anywhere in the world)

Bash the mediocrity in software that we have produced over the years. Slow. Electronbased. Etc.

I can have both the opinions.

Also I will support Andrew Kelley on Mastodon if he says the same.

Separation of Concerns.

You know a better dsl? jquery.

I think this is against HN’s policies. @dang

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.

Neovim user detected!

This is state of the art. It will take time before Tigerbeetle themselves release their state machine as a library.

They have done some incredible job. Implementing things I didnt know existed about software/hardware.

I dont know if you want to monetize this. But I suggest make it open source.

You will receive tons of improvements and updates. I love this idea!

Python doesn't work with circular imports. NodeJS does. After using NodeJS for such a long time, I think it is a feature that is taken for granted.

That being said, the Nim team is working on it as per a few issues: [1] https://github.com/nim-lang/rfcs/issues/6 [2] https://forum.nim-lang.org/t/2114

I love the language, and this is probably the only bottleneck for me.

I loved Nim when I used it first.

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.

Did you check their Wiki? Have a nice set of gifs

So, its not just me!

Yeah. This is what people miss. I have always seen Space missions as an investment into the future.

Waiting for V to hit 1.0. It is going to be a game changer once everything is up and running at its best.

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.

This project is really good. Really really good!

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

Yeah. This is exactly why I think the meta-frameworks wont really matter in a decade’s time or will disappear.

InertiaJS is an idea/implementation I like and its way of mitigating this issue of meta-framework dependence.

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.

A question. Other than basic APIs what do Khan Academy do that is deemed complex from server side POV.

Using GraphQL and all those jargons and all. Would a Rails app (not considering perf) be good enough for the same.

I am asking being curious.

Hi. I am the author of EKON. I realized YAML was doing too many things. EKON was meant to be an extension of JSON5. Although right now I realise its also doing too many stuffs under the hood.

I should rewrite the project again. But be as simple as possible.

That was my first C project ever during my University. :P

Weird there are even negative comments about UPI. That too from people who haven't lived in pre-UPI era.

My father and my uncle both have had history of losing cash to robbery earlier in the past in broad daylight. Snatch and run. Huge amounts of cash. My wallet has not seen any paper-based cash in over 1-2 years now and I live in a Tier-4 town/city.

The habit of not giving the extra 1-2 rupees of extra change has gone. Now, its the exact amount. Plus no one these days have to loan out payments. You can directly pay the amount quick.

The scale and the way UPI has become such an integral part of Indian lives is such so much valuable that the minor inconveniences (Privacy & customer care) are ignorable.

The developer experience is night and day with Svelte(kit)

Svelte has a cool DX. Best I have seen. SvelteKit not so much.

Hey Kevin! First of all. I am a regular listener to your podcast! Love it!

Now, I am not specifically targeting SvelteKit to be fair. But the whole host of meta-frameworks like NextJS, NuxtJS etc which Vercel is pushing.

These frameworks in general are too much complexity added. SSR is hard and the best way to handle all of these is to not have a server layer at all. That is just abstract the rendering/routing part and leave the rest of the server stuffs to the user.

I want to simply write my Fastify/Express/Go-gin/Django app. Then add SvelteKit as my front-end with SSR support.

Right now, I first write SvelteKit and then think how am I going to integrate Express and Fastify to it (for a moment let's leave non-node solutions).

Trust me. If you simply leave the server out of SK and generate a simple API abstraction like `res.send(renderSKPath('/users/:id', { serverData }))`. It would have done the job.

I think its difficult to express what I want to say, but in short, remove the server and keep SK as a rendering layer only.

P.S. I know that there is an express adapter for SK. But that is not the point of this comment at all.

I agree with this comment. SvelteKit is unnecessarily complicated. The `+page.svelte` etc are just the start of it.

Plus I can't use it with Go, PHP, Ruby, Rust etc when it comes to SSR (without running multiple servers and handling deployment nightmares).

Something about this whole Node + SSR Front-end is smelly. (next, nuxt, solidstart) I love Svelte as a framework and a way of writing UI, but SvelteKit. Eh! Not so much.

SvelteKit is too much complexity for no reason. Goes opposite of what Svelte was meant to be: Simple and intuitive.

Squeezing unnecessary performance for no reason is just stupidity and time wasting at best.

When I say turbopack, I was thinking why the hell would someone need this. Vite is fast enough for everybody. Quite fast indeed. Then there is Parcel which is also quite good and reliable.

I never felt with Vite performance was an issue at all. Everything is so dang fast in my company's website. We are unnecessarily optimizing stuff!

Yeah. checked out wasm part. But man. I am not going to go into Nim without cyclic imports.

I was writing a compiler I remember where I hit the 5k LOC mark in Nim. And then the errors and stuff. It was a terrible experience putting all the types into one file, the functions into others etc etc. The DevExp is bad that way.

Other than that, I don't see much issues with Nim to be fair. Its quite a good language that ticks all boxes

This is what I have been saying. Amazon makes people work 8-12 hours a day here in India and its not even talked about.

And this is not actually known before joining. At least bun says that outright.

Some people actually don't mind working hard unlike others if things are interesting. Not everyone is the same. There is certainly more fun working on bun out in the open than solving some random bug in Netflix, Amazon without even being noticed. And with forewarned warning.

I would have used Nim for just about everything, had there been:

1. Support for cyclic imports 2. Official WASM support. I know nlvm exists. But those are two separate runtimes to be managed for long time.

Had to scroll so down to find Lex's name recommended. But he is just awesome.

There is something about Lex. He isn't the most entertaining fluently speaking host, but the guests. Oh my! He has a standard. That's what I love