Live data from Hacker News

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

github.com

31–40 of 58 posts

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

#34

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

nxtfari is a less than half a year old account...

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

#35

[flagged]

Why are you assuming this was AI? It doesn't show any obvious indications of being AI. Maybe this is just someone's random side project. I advise you against jumping to conclusions.

He also built a 3d engine from scratch using only 2d line function, way before ai:

https://github.com/mrconter1/IntuitiveEngine

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

#36
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!"

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 _worst_ qualities of the GPL _and_ pseudo-free-software-licenses (i.e. the EULAs used by mongo and others). It has all the deceptive qualities of the latter (e.g. we are open but not really -- similar to Sun Microsystems [love this company btw, in spite of its blunders], trying to convince people that NeWS is "free" but that the cost of media [the CD-ROM] is $900), with the viral qualities of the former (e.g. the fruit of the poison tree problem -- if you use this in your code, then not only can you not copyright the code, but you might actually be liable for infringement of copyright and/or patents).

I would appreciate it if the contributor, mrconter11, would treat HN as an internet space filled with intelligent thinking people, and not a bunch of shallow and mindless rubes. (Please (1) explicitly disclose both the use and absence of use of LLMs -- people are more likely to use your software this way, and preserves the integrity of the open source ecosystem, and (2) share you prompts and session).

So passes the glory of open source.

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

#37
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!"

Does it matter who the sycophant was or just that there was a sycophant?

My partner does that as well as LLMs at this point; "Sure honey, I remember you've talked a lot about Rust and about Clojure in the past, and you seem excited about this Clojure-To-Rust transpiler you're building, it sounds like a great idea!", is that bad too?

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

#38
post #36
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!"

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.

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

#39

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 -…

This is the first time I've heard the term 'apecode', and I will make sure to use it at every opportunity.

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

#40

Earlier quoted context omitted.

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

Yeah, right? Are we just... talking with bots?

well there is a context to this of people doing ridiculous projects just because they can through LLMs, of which Claude excels at for code-writing, so it makes sense that two users would have a similar reaction to this. also copying jokes from other people is as old as time (just check youtube comments from 2008)
Post reply on HN