HNHacker News
TopNewBestAskShowJobs

spacechild1

3,562 karma · joined May 28, 2017

submissionscomments
spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
This sounds more complicated overall. Also, I would still need the staging area to only commit the debug statements.

As I said, I like to work on several things in parallel and I don't want to switch branches back and forth. That's just my workflow for my own projects and apparently I'm not alone.

spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
Is there an equivalent to `git stash` in Mercurial?
spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
If I really want to make sure, I do:

1. git stash

2. build + test

3. commit

4. git stash pop

> Some projects might not have a CI at all.

Well, then you have bigger problems. Without CI, how would you even know if your projects compiles on other platforms?

spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
No.
spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
Yes, I pretty much do the same thing with git-gui. You are right that the staging area isn't strictly necessary for this kind of workflow.
spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
That makes sense, thanks for clarifying!
spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
1. CI

2. Why should comments or printf statements affect the build? When it compiles with them, why shouldn't it compile without them?

3. the commits might be temporary and get squashed anyway

spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
> Most people on small projects just want "checkpoint the current code in my directory and put a comment on it".

Interesting, that's definitely not how I use git. My current code is rarely in a shape that can be fully committed. It often contains additional stuff I did on the way (small bug fixes, TODO comments, debug printf statements, etc.) that I don't want in the commit. Very rarely do I type `git add .` Am I the exception?

spacechild1··on I believe there are entire companies right now under AI psychosis
Actually, I have been wondering to which extend the AI craze has reached the DACH region. I don't work for any company and neither do my friends. HN is essentially my only peephole into the world of commercial software development and I'm aware that it's extremely biased towards Big Tech and SV startup culture.
spacechild1··on The old world of tech is dying and the new cannot be born
I have never seen these before. Very interesting!
spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
> It looks better to me than the other macro solution as it is more transparent what is done compared to DEFINE_ENUM.

Fair enough.

spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
Just wait for C++32 :-D. After all, we only got `std::string::starts_with` in C++20 and C++23 finally gave us `std::string::contains`. It's a clown show, you just need to take it with humor.
spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
That doesn't look any better.

Yes, xmacros have the best compile times, but you can't possibly argue that they are elegant to use compared to the alternatives.

spacechild1··on Meta won't let you block its AI account on Threads
I have been barely using FB, but I deactivate my account early 2025 and I never looked back. I never had Instagram or Twitter.

I thought I would miss out on many events, but then I just signed up to a few more newsletters and that's still more events than I have time to vist.

I still wish we had a proper replacement for FB events. At least we have a nice market place platform that everyone uses (willhaben.at). For a long time I didn't even know that FB MarketPlace exists.

spacechild1··on Meta won't let you block its AI account on Threads
I had a similar experience in Osaka. Prettry frustrating. Actually, I didn't know that you can read the posts without an account! That's good to know!
spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
If the implementation really was sufficiently complete, then this is even worse! Why did they choose to vote something into the standard that is very complex and difficult to implement, but does not live up to the promises? Maybe they thought it would improve in the future, but isn't this a huge gamble?

I have heard rumors that certain people in the Visual Studio team have exaggerated the state of their modules implementation to speedrun the standardization process. I have no idea if that is really true, but it would explain a lot of things...

I'm not the only one who is asking these questions:

> I don’t know if they exaggerated their claims at the time, or if they didn’t properly fund the Visual Studio team since or what, but you can’t tell me 8 years wasn’t enough to make syntax highlighting work with modules. And if it is, then maybe there was something deeply wrong in their proposal and the committee should have asked to see the receipts before voting yes.

https://mropert.github.io/2026/04/13/modules_in_2026/

spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
I don't remember because I wasn't there :)

People are not complaining about the fact that C++ has modules, but about their usability and effectiveness. The compile time benefits seem modest and I have seen reports that it breaks Intellisense. (Maybe that's not true anymore?)

As Vittorio said, if it takes compiler vendors so long to implement them properly, maybe the design wasn't that good after all?

My point was: if you add such a big feature, shouldn't the standard require a sufficiently complete implementation? Otherwise, how can they assess whether the proposal actually works in practice and lives up to its promises?

spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
Oh, I didn't know about __VA_OPT__(), thanks for that!

That looks much nicer indeed, but I still vastly prefer the other solutions, simply because I can just declare regular enums.

spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
The implementation doesn't look too bad, but the usage is terrible:

  #define E_LIST(X) \
      X(V0) X(V1) X(V2) X(V3)

  DEFINE_ENUM(E, E_LIST)
That's not how I want to declare my enums...
spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
The downside is, of course, that it's ugly and very awkward to use.

That's the essence of C++: you're basically trading ergonomics for compile times.

spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
> it is fair to question if the problem is with the design/implementability of the feature itself.

The module story is just insane. How was it possible to get such a big feature into the standard without any working reference implementation? Isn't this the requirement for standard proposals to get accepted? If I compare this with how they treated JeanHeyd and his #embed proposal, the difference is staggering. To me it seems like a few powerful comittee members wanted to get modules into C++20 at any cost. This was just irresponsible.

spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
> But if given the choice, I'd choose the C-macro implementation (which is 30+ years old) over this, every time.

Why? The implementation is not pretty, but you only need to write it once and then it works for all enums. The actual usage is trivial, it's just a function call.

The C macro version is horrendous in comparison. Why would I want to declare my enums like that just because I might want to print them?

spacechild1··on Cost of enum-to-string: C++26 reflection vs. the old ways
I find it quite readable. I can understand what it does even though I haven't written reflection code yet myself.
spacechild1··on Linux gaming is faster because Windows APIs are becoming Linux kernel features
> How often does a video game really need a lock that can be shared between processes,

What do you mean? SRWLock (or the older CRITICAL_SECTION) cannot be shared between processes. A (Win32) Mutex does work across processes, but that's its entire purpose. So Windows does have different tools for different jobs.

In fact, it's really the other way round: on Linux, a futex also works across processes, but there is no equivalent in Windows. (Sadly, WaitOnAddress can only be used in a single process.)

spacechild1··on Nullsoft, 1997-2004 (2004)
REAPER is awesome! It has been my DAW of choice for 15 years now. It opens instantly, it's very fast and snappy and it practically never crashes.

I particularly like the concept that everything is just a track. In REAPER, tracks can be arbitrarily nested, they can contain all kinds of items and you can route signals between them.

You need a group? Just make a track and add other tracks to it.

You need a bus? Just a make track and send to it from other tracks.

You need an instrument track? Just add a VSTi to it.

You need a MIDI track? Just add a MIDI item.

In most other DAWs, these are all different things, for no good reason IMO.

spacechild1··on Pinocchio is weirder than you remembered
Wow, thanks for the tip!
spacechild1··on Pinocchio is weirder than you remembered
You mean the versions of Charles Perraults? These are indeed interesting. According to wikipedia, the Grimm brothers did not even use the original sources for "Rotkäppchen" and "Dornröschen" and rather relied on second-hand retellings.

As a side note, there is also a fair share of cannibalism in Grimm's "Schneewittchen" (= "snow white"): the evil queen tells the hunter to kill Schneewittchen and cut out her lungs and liver so that the queen can cook and eat them. The hunter, however, has pity for Schneewittchen and kills a boar instead. The queen proceeds to cook and eat the boar's lungs and liver, thinking it is Schneewittchen's. Only after the meal the magic mirror reveals the truth.

The death of the evil queen is also pretty brutal: at the wedding of Schneewittchen and the prince, the queen is forced to wear shoes filled with glowing coals and dance until she faints and dies.

For some reason, the Disney version decided to omit these parts of the story :-D

spacechild1··on Modern C++ Programming: Busato
I just read through a few chapters. This is actually a very nice and solid resource!
spacechild1··on America's Expanding Domestic Surveillance
Just as much as voting for a narcissistic pathological liar and sex offender is Christian. Turns out people are not very consequent with their supposed values when it gets in the way of their personal interests.
spacechild1··on America's Expanding Domestic Surveillance
The HN community is not a monolithic entity. Yes, there are many libertarian SV folks, but there are also plenty of people (like myself) who despise that culture and push back on a regular basis.
← PreviousPage 7 of 34Next →