rpnx

The C++ environment for builds is kind of awful. It's usable, but extremely complicated, non-uniform, and rarely well implemented.

CMake isn't a good build system, it's just the least bad one we have.

Disagree. There are important things C++ gets "right" that languages like Go, C#, Java, and Rust get "wrong". It's difficult to impress these ideas on people who dislike C++, because they are largely not willing to learn C++.

The C++ build environment is awful, I'll give you that much.

I find people tend to fall into two camps, people who don't understand C++ because it's "too complicated" and people who like C++ (though acknowledge the syntax is a bit odd sometimes).

Extraction of the essence of C++ is ongoing...

> no real language will spent 4 entire years and is still stuck in version 0.0.0-0.

Strongly disagree. I too thought that it would be easy to implement a new language in 1-2 years. I started the current Quxlang codebase (under a different name) on Dec 27, 2022. In 2026, hundreds of commits and hundreds of thousands of lines of code later, I still don't have a feature complete language.

I also rewrote the syntax, mainly because C++ parsing is a nightmare... Although my choice was very different...

Worth noting, Carbon is just an experimental language, I see no evidence it's being used widely or replacing C++.

This is why I'm building Quxlang.

C++ cannot evolve easily without breaking backwards compatibility.

I started Quxlang because I saw the writing on the wall for C++. Doesn't mean C++ isn't good, but it has issues and needs improvement.

Somehow I managed to implement working modules, C++ doesn't seem to have that yet, although the C++ build system is horribly broken.

We'll have to see how it compares when it's more complete and ready to use. I don't have oop/inheritance yet which is also important for a C++ alternative.

Obviously using work equipment is a no-no. I'm also in agreement on point #2 aside that I think it's okay to discuss such topics e.g. during lunch in the same way you may discuss any other random topic at lunch.

No, we should make standard time permanent.

Daylight savings time is bad for our bodies particularly in the winter.

It also makes noon even more out of sync with solar noon.

It is worth noting that if the Air Conditioner is powered by electricity that came from solar panels, the net heat produced compared to letting the sun heat solar panel colored ground is exactly 0.

Air Conditioners do not produce a net heating effect unless you power them by burning fossil fuels.

Good. Reduce population growth until housing buildout can catch up with population. Trying to create more babies and allowing immigration when there aren't enough homes is dumb.

Ran across this while writing the Quxlang compiler frontend. Was wondering how GCC/Clang solved this problem... turns out at least with regard to GCC... they don't!

200-ish line C++ file with no user-defined templates generates around 90k assembly lines with -Os enabled.

GC was removed from the C++ standard in C++23 because all the compilers were like "hell no" and it was an optional feature so they could get away with not adding it. So this optional feature never actually existed and they removed it in later standards.