qalmakka
Joined 9 years ago
Joined 9 years ago
I understand the concept but having a feature that's not consistent among compilers, targets, ... all while doing absolutely nothing to solve the _real_ problems with C++. Like that the build model is still the obsolete TU model of C, while adding multiple compile-time features that inevitably end up causing build times to skyrocket considerably. Or that modules are still DOA after 6 years. Or that the syntax is full of bullshit anti-features that could be at least fixed by having a proper build model (like Rust) and editions (like Rust).
Having yet another feature that only works sometimes with quirky semantics is dumb and I understand why many people feel like it should be shelved to prioritise the features people _really_ care about, like meta
I think that we as a society fail to see that the speed we built things was rarely the problem. The real shortage was in the ideas - having them, finding the motivation to act on them, sharing them, and the biggest driver was the desire of showing off, being told you are great and your idea was great.
I am afraid that by removing the ick to fix things, to challenge everything and being rewarded for that, we will end up with less innovation, not more. Why bother? Why do anything if everything is cheap, why start a new project only to be shrugged away as being yet another thing any machine could have done? Why show off when the merits are the machine's?
HN went from being a constant stream of Show HN to AI news after AI news. The most interesting projects AI have enabled are to run old stuff onto other things.
Rehashes of old ideas keep sprouting out of everywhere, keeping new ones at bay. I think we are probably entering a long winter and all that will be left is permutations of what we did before '23
Ah that's the reason why they came up with an instant speedup. Optimising CEF is basically like docking a zero from your speedup loop [1]
That sounds like Subversion with extra steps
> In git, you commit locally and then push to share your work. In Scion, every commit, rebase, or merge happens on the server, so there’s nothing to push,
Yep not beating the allegations with this one
To be fair 90% of the companies I've ever worked for always used git in a way that turned it into Subversion, but with 10x the storage usage (note: I hate Subversion with a passion, I'd rather send patches via email than that)
I'd say that I don't think it's that relevant? Hopefully everyone was aware that you required a VM to run Linux software on Windows and Mac, and then who would really care about what VM docker used to run development containers? The more expendable the better. Hopefully nobody is using a Windows PC with docker desktop in a production scenario - but given how utterly incompetent some people I met was, I'd not be too surprised from that
The only somewhat realistic proposal in this space is Herb Sutter's cpp2, which is arguably a massive improvement and I'm puzzled why nobody in the standard thought to give it a spin, there's just to much cruft they'll never be able to get rid of unless they make an alternate yet backward compatible syntax with C++ that changes the defaults from "random 80s nonsense" to something better