101–110 of 168 posts
Earlier quoted context omitted.
Tangent but what a horrible website at least on my android. Starts as light mode, suddenly shows three streched columns, turns to dark mode and the title is hidden behind the header. After years of being around how can they end up with something like this
Completely broken on iOS as well. Feels like AI slop.
Seems odd not to acknowledge and differentiate yourself from [apache ant]( https://ant.apache.org ). Failure to do so certainly makes me think the new project isn't very serious.
The author shared their experience building the first version in a month: https://themackabu.dev/blog/js-in-one-month And then the follow up few months later: https://themackabu.dev/blog/ant-part-two I'm not sure what the economics of building a new runtime and ecosystem from scratch are but it seems we're already in a phase where individual developers are creating software which previously took a whole team. And its…
Earlier quoted context omitted.
this was flagging code from all the way back in dec of 2025, back when this project was just some idea and not what it is today. around feb thats when basically deleted the existing codebase and designed a much more reliable system from the ground up. I knew the existing code was basically pure slop, and it was not the biggest issue then, now nothing goes past me unreviewed and untested > To the author: I absolutely…
> now nothing goes past me unreviewed and untested So it's not hand-built?
I, at the very least, need a keyboard.
Why call it "Ant" and not "Antjs" or "Ant.js" when there is already Ant from Apache? https://ant.apache.org
Earlier quoted context omitted.
It's existed for a lot longer than LLM generated code has
It's gotten much worse than I used to remember it, though. It used to be pretty bad before too, but it at least had an ok homepage.
Why call it "Ant" and not "Antjs" or "Ant.js" when there is already Ant from Apache? https://ant.apache.org
I’m not that deep in the JS ecosystem or runtimes, but I’m a little surprised by some of the claims here about being smaller, having fast starts, sandboxing, performance-competitive, etc. Does anyone have a sense of what insights, design choices, big bets, etc, unlock all these advantages against already mature and highly optimised JS stacks?
But okay, it’s not the fastest kid on the block; although “X but faster” isn’t the most compelling argument to adopt a new runtime.
As to the choices this project made: well, Claude or Codex seems to have chosen to copy large parts of the Elk codebase.