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.

Now, DNS is largely used for this purpose.

Um, that does not really make sense.

-mail.microsoft.com -ftp.microsoft.com -irc.microsoft.com -print.microsoft.com

These are all domain names and DNS servers are used to resolve these to different IPs. Always has done that job and still does it today. But microsoft.com is a single domain name and DNS can only resolve it to a single address (or set of addresses). So cannot be used to tell different services apart.

DNS does not know anything about http or https or any other protocal like that. It just resolves the domain name to an IP/set of IPs. The only thing it can do is point www.microsoft.com and microsoft.com to the same location so that you can use either to get to the webservers.

Everything is a tradeoff. At this point there are more valuable things to be spending money on than making chargers that are as fast as possible. Not all cars can charge at 500+kWhs many cannot even do 100kWhs. IMO better to spend money upgrading all the slow 7-50kWh chargers. As well as putting in more slow charging near residents. Kerb charging for people that dont have a driveway in cities or chargers for those living in flats. That would serve people better then spending more money on something very few can actually benefit from.

They need a basic remote API and SKD first. Now we have that anyone can implement these local daemons/translation layers if they want to. This is still early days.

They could at least have implemented a shell

They do have an interactive shells:

You can also run interactive shell. Just type ./proton-drive and then the commands directly.

Though the commands are not the same as Linux equivalents that is IMO not a big concern. Similar things like AWS S3, or even ftp also don't have the exact same commands. It is really a trivial thing to learn how it works.

And again, anyone is free to build on this now if they want to.

I would not be surprised to see a fuse fs popup at somepoint around this.

Where's sftp? s3? smb?

I would highly suspect this is because they don't want to handle encryption and decryption on their servers where ever they can. Yes they need encryption for emails they receive but for every thing else they want to have as end to end protected as they can. Which means client side encryption and decryption for almost every thing. That is the big feature that a lot of people are buying into from them.

All these protocols don't feal with encryption on the client at all. Which means if they supported them they would need to handle encryption and decryption on the server side. Which I doubt they want to do and likely work hard to avoid at all.

Even if you exceed 20W it doesn't matter. The only real thing that matters is the average draw and the total duration of a session. If you spend most of the time drawing 10W and peek at 50W for a minute then you can run off a 20W powersupply forever.

But a faster power supply does offer you more benefits. You can play unplugged until the battery is low, plug it in and continue. It will charge sooner letting you unplug it again sooner. If the wires bother you then that can be a big advantage.

I find that if you don't finish that last 10% now than if you do ever find a use for it you won't bother with that last 10% and will just find a quicker work around to finish the project you were working on instead. Then that last 10% will never get done.