That is the same curve for almost everything that becomes mainstream. The only real difference is the length of time t takes. But everything starts out small, stays that way for a while, then some critical mass hits and it explodes. For a project to become mainstream it is really all about overcoming "the chasm" of early adopters where most projects die or get stuck in for a long time.

Single upticks mean almost nothing. Next month or two will likely drop again a bit. Things generally regress to the mean. Even their chart shows that. Every major up or down tick quickly move back towards the mean. So the mean is the only bit worth getting excited about and that is showing good steady growth.

Application developers are not being forced to integrating with systemd at all. They are choosing to do that because it helps them. The only developers negatively affected by this are the ones developing other init systems that don't want to provide the same features the application developers want to use.

Both don't sound right as they are ambiguous. "Their name is Trevor," sounds like it is talking about a single person. "Their names are Trevor" feels incomplete. "They are both named Trevor" or "Their names are Trevor and Trevor" solves that ambiguity.

If they claim it is absolutely secure then they don't understand security at all and very likely have some very lax security practices.

I wouldn't expect it to be constantly full of things you have not heard about and are actually interested in. Or else you would be constantly buying games. If it is getting a few new things in front of you then it is doing its job. Better then seeing the same set of hand picked games over and over again.

Three branches and a fifteen-line ceiling sounds generous until you write against it.

I disagree with this. There is a lot of situations where breaking these rules results in more readable code and trying to follow them strictly results in code that is far harder to read overall. Sometimes colocated code is the more readable solution. There is no hard and fast rule that can make code more readable. Only general guidelines that don't always work.

This has Uncle Bob vibes which just takes this to the extreme - thinking you can only have 1 branch and 5 lines in a function. It does not solve the complexity problem. It just spreads it around and thus makes the whole program and logic flow harder to read as you need to make far more jumps through the code to understand it.

That sounds like an awful lot of features to implement.

No, no. You forgot about this:

The announcement post also warns that the vibe-coded Preview is currently “light on features”

So a slightly faster launcher that is light on features!

Restoring from the system tray will save you 0.06seconds!!! How can Valve compete with that.!.

Oh yeah, by being a decent platform for buying games.

It is like some areas are just not being extruded at all.

Because that is what is happening. Wood filament is just PLA mixed with wood particles suspended in it. These particles are very likely getting stuck in the printer nozzle and stopping any more filament from being extruded. This is not the only cause of under extrusion like this but the most likely.

Given it clears its self up it is probably that the blockages are clearing themselves eventually with enough time/pressure/heat behind it. Or it could be a particle moving around inside the head (which I think is less likely).

Best thing is probably to get a larger nozzle that will be less prone to being blocked by larger particles in the wood PLA. You can also clear the nozzle as well with a tiny needle or a cold pull of the filament. This may help for a bit it there is stuff built up inside the nozzle or if it the blockage is self clearing it may not help at all (but wont hurt anything). But the better solution is likely a larger nozzle.

Can we just ban it for everyone? If it is bad for minors it is bad for adults.