Live data from Hacker News

Show HN: Rust compiler in PHP emitting x86-64 executables

github.com

51–58 of 58 posts

Re: Show HN: Rust compiler in PHP emitting x86-64 executables

#52

You never know what’s going on in someone else’s Claude Max plan =D

Interesting that both you and nxtfari made essentially the same comment within an hour of each other, though yours is slightly modified

Just another glitch in the matrix. Guess whst chances were that this happend by pure coincidence. Dead Internet Theory is real.

Re: Show HN: Rust compiler in PHP emitting x86-64 executables

#55
post #42
post #20

I bet claude was hyping this guy up as he was building it. "Absolutely, a rust compiler written in PHP is a great idea!"

Every compiler in any language for any language has at the very least educational value. On the other hand, demeaning comments without any traces of constructive criticism don't have any value.

[dead]

Re: Show HN: Rust compiler in PHP emitting x86-64 executables

#56
post #36

Earlier quoted context omitted.

There is no comment on whether LLMs/agents have been used. I feel like projects should explicitly say if they were _or_ were not used. There is no license file, and no copyright header either. This feels like "fauxpen-source": imagine getting LEX+YACC to generate a parser, and presenting the generated C code as "open-source". This is just another way to throw binaries over the wire, but much worse. This has the _wors…

According to his Readme he seems to have built a 3D engine completely from scratch 8 years ago without using any library: https://github.com/mrconter1/IntuitiveEngine > A simple 3D engine made only with 2D drawLine functions.

[dead]

Re: Show HN: Rust compiler in PHP emitting x86-64 executables

#57

I think people don't really realise that compilers are "difficult" projects in the same way as an appendicectomy is for a skilled surgeon, i.e. the surgery is "routine" only because the surgeons spent decades honing their skills to do these routinely. The hard part was training someone to be able to do that. Writing a compiler/interpreter is _extremely_ straightforward; a lexer -> parser -> ast -> semantic analysis -…

That’s true for any software project - on average only 5% goes into developing of the first version, while 95% goes into continuous development, support, and maintenance.
Post reply on HN