atilaneves

Wouldn't it be more useful to build a programming language that LLMs can use better?

> I don't understand how people have that stated as a fact. Coding was never the slow part.

Because, for them (and me!), it was. I never understood why people kept saying that typing speed wasn't a problem since coding was never the bottleneck. It always was for me.

> functions ?

Macros can condense code down a lot more since you're essentially writing a language within the language.

> but in practice it doesnt because llms arent trained to that extent on this.

Right, but it probably works with words instead of symbols.

> You can write DSLs in Rust which gives you static typing, a borrow checker, and clippy.

It also makes your agent wait for the compiler to finish.

How is Go simpler to deploy than the alternatives? C++ has been able to compile to statically linked binary for ages.

I think Go's compile times are great for the AI age, but that "pretty fast runtime" is not.

> You don't need Emacs

Yes, I do.

> and lose access to most things

What "most things" are these?

No, you can just write D. It'll have the same performance as C, if you write C-like code. It might have better performance than C if you use templates (just like in C++).

Yes, that's my point. I'm replying to claims that "if it compiles it probably works". My limited experience with both is "nah".

Because it is also possible to write tests that don't adequately capture real-life requirements.

It was an MQTT server, and the tests basically went "if we have these subscriptions, then...", but no subscriptions ever got actually stored by the server.

Every language with a GC drastically reduces the chance of memory errors.

I hear this about both Haskell and Rust, and yet, when I tried both in the former I wrote a useless program because I didn't handle state (and yet passed all tests!) while in the latter I immediately wrote a deadlock.

So...yeah.

I made the same comment last week upon learning of a redis clone entirely vibe coded in IIRC ~70k lines of Rust. Why Rust? Why does a computer need a memory safe language?

I'm still figuring out why anyone would want to write a shell script in C. That sounds like torture to me.

Wouldn't the instance state here be "was constructed"? That is: you should always be able to call `Read` because the constructor opened the file, and you shouldn't have to call `Close` anyway because the destructor did.

I just posted on the forum about it, I didn't do it before because of surgery (I'm still nowhere near 100%).

What changes would you like to see happen?