Is antjs coded in plain and simple C?
Show HN: Ant – A JavaScript runtime and ecosystem
41–50 of 168 posts
Re: Show HN: Ant – A JavaScript runtime and ecosystem
#42Re: Show HN: Ant – A JavaScript runtime and ecosystem
#43And 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 only getting started...
Re: Show HN: Ant – A JavaScript runtime and ecosystem
#44Re: Show HN: Ant – A JavaScript runtime and ecosystem
#45i was just joking about Anthropic's `ant` CLI not caring about Apache `ant` (maybe one person got it), and now we're talking about Javascript `ant`!
Re: Show HN: Ant – A JavaScript runtime and ecosystem
#46Re: Show HN: Ant – A JavaScript runtime and ecosystem
#47Could you use the JSR package registry instead of setting up a new one?
Implementing, running, maintaining, scaling a module registry is probably not worth the time. Unless there's a clear technical requirement from the runtime. I would think there isn't since npm protocol compatibility is a stated goal/feature.
Re: Show HN: Ant – A JavaScript runtime and ecosystem
#48Re: Show HN: Ant – A JavaScript runtime and ecosystem
#49Lots of frontend devs (and vibe coders) just want a "deploy my code" service.
Re: Show HN: Ant – A JavaScript runtime and ecosystem
#50I code with AI all day, every day. But I do think that it's worth pointing to this issue (from March). The author has said that they've redone it since, but the "from-scratch hand-built" framing specifically – for me – somewhat grates given the original heavy lifting from an existing AGPL codebase. https://github.com/cesanta/elk/issues/75 I want to acknowledge that the original authors don't seem to have minded too m…
isn't the post of someone who just implemented a js engine (it reads like someone who asked an LLM to write a blog post about the git log of a different LLM which was apparently lifting code from a different js engine...)
It's a bit hard to understand what's going on here, but definitely hard to trust the project.