If you are going to annoy people, do it properly.

Which is not very noteworthy, don’t you think?

Putting some HTML files on a web server somewhere is not that big of a mystery in 2025 that it might have been in 1995.

Github Pages supports Jekyll as a SSG out of the box.

Any documentation or tutorial – official or otherwise – that simply skips on this is getting people’s hopes up just to waste their time.

Ohh, boohoohoo, what are you gong to do, cancel your lib.rs subscription?

Perhaps, the linked page just does a poor job of selling that.

As someone also working on a minimal programming language, I might share some of the values, but using Go as an implementation language is an immediate turnoff.

Also, not having a single code example on the linked page is super-annoying.

People need to stop that.

Incorrect.

Rust is not a functional, let alone functional-first language.

Surprisingly, the beaten spouse does not plan to abandon their significant other in the foreseeable future. They stated that expertise in receiving a black eye is still valuable in the domestic violence sector.

This you?

Surprisingly, Kaganski does not plan to abandon Windows in the foreseeable future. He stated that expertise with the world’s most popular operating system is still valuable in the IT sector.

In this case, he needs to stop the fucking whining then.

And all of this due to the mistaken design decision to stick with the obsolete readiness-based model instead of going with the superior completion-based model.

(You can build a readiness-based API on top of a completion-based API, but not the other way around.)

git worktree is just so much easier to work with if you want to work on multiple versions or branches of some code.

It allows having multiple IDE instances open, all fully functional and indexed, and handing over commits from one worktree to another without having to fetch constantly in between.

Trying to emulate this with multiple clones feels like trying to do OOP in C – sure one can do it, but it’s pointless hassle compared to a fleshed-out solution that works right out of the box.

Not to mention it’s so much faster and more efficient than git clone.

What a confused post.

There is not much to learn, so just do it? It’s not a relevant investment that would require much thought.

Yeah, avoids pointless debates whether they should be lined up in matches or not. :-)

Many languages’ Option and Result types suffer from an organically-grown and therefore inconsistently named set of functions that operate on them.

We can do better! The article demonstrates how a full set of useful methods with predictable names can be derived from few, simple rules.

Absolutely delusional.

code that is readable, auditable, and easy to port

Yeah C is the language that comes to everybody’s mind reading that. /s

C’s simplicity …

Is that simplicity currently in the room with us?

… and widespread adoption make it the best choice for this philosophy.

Ah, the asbestos argument.

If people want to run the latest kernels on hardware that isn’t maintained anymore, they need to toughen up and send patches …

… or they stick to an old kernel for their unmaintained hardware.

Both is fine to me, but that entitled Boomer attitude of “nobody should have nice things, because that would challenge status quo” needs to die.

Studying at a university is not a fancy job training.

Do whatever pays your bills, and learn what interests you. Sometimes the latter will help with the former, but it would be silly to depend on that.

I know it’s a lot to cope for you, but you really need to calm down if you want to be taken seriously.

“apparently it’s a better safer C++, but I’m not going to switch because I can technically do all that stuff in C++”

The main difference between C++ and D was that (for most of the time in the past) D required a garbage collector.

So, D was a language with similar Algol-style syntax targeting a completely different niche from C++.

Trying to correct your quote, it should read something like “I’m not going to switch because I can’t technically do all that stuff in D that I’m doing in C++” for it to make any sense.

I think the article suffers a bit from not being up to date in regard to the work Java has done with virtual threads.

There quite a few assumptions being made in the article that would not have been questioned a few years ago, but now these assumptions feel quite unfounded and all the conclusions based on them stand on shaky ground.