SaxonRobber

Yes but it isn’t clojure so I have to downvote this.

(I can’t actually downvote)

That’s just what happens around here when you imply that a Lisp might not be perfect.

Don’t think to hard about it, they don’t either.

No, if companies aren't allowed to fail then the economy is broken. Every time a company is bailed out it just incentives less accountability in the future. Besides, no one is going to bail out the small, or even medium sized companies despite what politicians say.

Programming languages are the biggest tar pit. Too often I get distracted by language features instead of just doing what works. With experience, I grew to appreciate simple languages like C, Scheme, and SML because I could focus on being productive rather than debating which language features to use. More code less abstractions.

Maybe the same reason why others choose to omit light modes, despite that being my preference.

Vector operations are one of the few cases where I think operator overloading is sometimes a good idea.

Eventual deprecation is not a valid justification for making current technology less useful.

Now I would buy your argument if C++ were as conservative as C, but it clearly isn’t. It keeps trying to push itself as a modern general purpose language, while ignoring what it actually takes to be useful as one.

Framing this on my blog

I think it does, I should not require an external dependency for JSON. Having standard JSON support is far far more useful than another micro optimizations.

I mean standardizing libraries that are widely useful for minimizing external dependencies.

Like networking support, serialization for ubiquitous formats like JSON, etc.

It also requires a library outside of the standard.

I’ll never understand the portion of the C++ community that insists on modernizing the language to the detriment of everything else. When is enough enough? Just let the language be and focus on improving the standard library, not changing language features.

I think that is for the best. I prefer less implicit behaviour in my code, even if it means my identifiers get longer.

This is the philosophy that has led to our software becoming slower despite improvements in hardware.

Performance is always important. Especially for consumer applications, where your software will probably need to run alongside many other processes each competing for resources.

Code: The Hidden Language of Computer Hardware and Software

One of my favorite books, it covers everything from braille to microprocessors. A great book for anyone interested in technology.

This is wishful thinking

It was actually motivated by competition from Russia.

More than the west gets from Toronto.

For this reason I went back to C and have been experimenting with Rust.

It’s a shame, because there are some places where C++ is a strict improvement over C, but you have to accept so much more baggage.

It would be better if GIMP ran nowhere tbkh

What planet do you live on? The one I am from is filled with tech companies making money selling ads and user data without scruple. But god forbid someone providing their labor gratis would DARE ask for a piece of it.

Why should an individual contributor not be allowed to partake in that, when the people who are using his work are making money off it?

A social convention, who put you in charge of that? There are plenty of bad conventions in this world, no one should be obligated to follow them.

Then fork it and remove the message yourself. Sitting on your hands and moaning about the size of your logs being “immoral” is peak entitlement. He doesn’t owe you or npm shit.

How does Zig compare with Nim and Rust? (putting aside the differences in adoption)

That's what happens when the Free is removed from FOSS.

I'd add that spending some time to play with the languages that are hard or different will pay dividends down the road.

Learning some Haskell was probably the most worthwhile time I have spent learning a language because it forced me to fundamentally reevaluate how I think about programming. Now I don't use Haskell at work, and likely never will; but, years later, the techniques I learned from it I still apply daily when I write C, Python, JS or whatever. It made my code far cleaner.

Jesus npm is a cancerous dumpster fire. Guy must have been a saint to continue maintaining the project in spite of all of entitled "developers" using his package and scolding him for DARING TO ASK FOR A DIME.

The only improvement C really needs are true constants that don’t rely on macros or enums. How this still isn’t in the language is baffling.

Large commercial projects. The problem is the mid sized projects, especially FOSS ones, there isn’t the time needed to curate every pull request and bikeshed. There is also something to be said for having less abstractions, moderately wet code can be easier to follow and fix than needlessly dry code.

Sounds like you need to raise the bar on hiring if learning static typing is an impediment. I recommend less JS monkeys and looking for actual engineers.

It’s all good, life is too short to care