Hydrogen is troublesome as an energy storage. The roundtrip efficiency (electricity -> hydrogen -> electricity) is just… very not worthwhile compared to batteries. Then beyond efficiency there is still the question of “how do we store hydrogen safely?”

Storing energy indefinitely is not a problem for electricity storage, since we are pretty much guaranteed to use the stored energy up in a single day.

It is all quite complicated.

1. A renewable producer (e.g. solar panels) cannot produce energy 24/7. And when it produces energy, you are not guaranteed the production is stable.

2. A consumer cannot consume energy 24/7. And when they consume energy, you are not guaranteed the consumption is stable.

3. To make the issue worse, a producer may not be producing energy when the consumer wants it, and vice versa.

4. Currently, energy storage is not widely installed. Hence any produced energy must be consumed at the same time.

The factors above combined means that there will be a mismatch. If the production is too great, your electricity appliances will probably explode and whatnot. If the consumption is too great, you experience blackouts. Neither are desirable.

Now consider there is a middleman. The grid. Producers sell energy to the grid. Consumers buy energy from the grid.

At some point in time, due to the factors above, the grid will need (A) zero to negative prices to encourage consumers to buy & use more energy from it, and to encourage producers to produce & sell less energy to it. Or (B) increased prices to encourage consumers to buy & use less energy and producers to produce & sell more energy. A flat price is not realistic. (Residential users only have a flat rate because our demand patterns are more stable.)

But due to the production patterns of renewable energy and consumption patterns of our society, there is a not-insignificant risk that renewable producers will consistently face scenario (A) above making it difficult to cover back the costs.

There are a lot more ways to store energy other than lithium and hydrogen.

Pumped storage, vanadium redox battery, sodium battery, … I’d even say they are most suited for grid-level energy storage.

[deleted]

Last time I asked around about this question, the answer was surprisingly “probably not much”! When a low-power x86 chip (like those mobile chips) is idling (which is pretty much all the time if all you are doing is hosting a server on it) it consumes very little power, about the same level as an idling Pi. It is when the frequency ramps up that performance-per-watt gets noticeably worse on x86.

Edit: My personal test showed that my x86 laptop fared slightly worse than my Pi 3 in idling power (~2 watts higher it seems), but that laptop is oooooooold.

It’s not just DNS. I have this rule in my firewall:

udp dport 15600 counter drop comment "Block Samsung TV shenanigans"

So far, it has blocked 20575 packets (constituting 1304695 bytes) in 6 days and 20 hours.

Anticheats can be very invasive, they can theoretically scan all the files inside your computer (whether it is practically done, I don’t know but it surely feels like it’s been done), take screenshots regularly, send your hardware information, etc. So yeah, if you are someone who takes security seriously…

[deleted]

If you squint your eyes just enough, insurance is like gambling… You are betting that something is going to happen to you, the insurance company is betting against that. The insurance company can improve their chances by adding conditions to that something.

For many systems out there, /bin and /lib are no longer a thing. Instead, they are just a link to /usr/bin and /usr/lib. And for some systems even /sbin has been merged with /bin (in turn linked to /usr/bin).

Not just Linux… 99% of the time you see something weird in the computing world, the reason is going to be “because history.”

Gen Z’s are well aware of traditional phones. Smartphones were not really that ubiquitous (up until 2010(ish)), and by that time Gen Alphas were already born.

The C developers are the ones with the ageist mindset.

The Rust developers certainly are not the ones raising the point “C has always worked, so why should we use another language?” which ignores the objective advantages of Rust and is solely leaning on C being the older language.

They very rarely have memory and threading issues

It’s always the “rarely” that gets you. A program that doesn’t crash is awesome, a program that crashes consistently is easy to debug (and most likely would be caught during development anyway), but a program that crashes only once a week? Wooo boy.

People vastly underestimate the value Rust brings by ensuring the same class of bugs will never happen.

Ah you got my comment wrong! I didn’t mean to suggest Gecko is closed source. I just wanted another web engine that is also open source.

Servo was an experimental ground for Mozilla in some ways (like testing out a new CSS engine and porting it back to Gecko if it works). So it’s quite normal for people to be unaware of it, it was not meant for the public.

But later on it was abandoned by Mozilla and stuck in a limbo, until it got picked up by the Linux Foundation. Now it’s a standalone project and I wish them well. We really need a new FOSS web engine.

It really depends.

If I know I will never open the file in the terminal or batch process it in someways, I will name it using Common Case: “Cool Filename.odt”.

Anything besides that, snake case. Preferably prefixed with current date: “20240901_cool_filename”

I recall reading somewhere the earlier compilers had a hard limit on the length of function names, due to memory constraints.

People back then just grossly underestimated how big computing was going to be.

The human brain is not built to predict exponential growths!

One of the issues at hand is that X11, the predecessor of Wayland, does not have a standardized way to tell applications what scale they should use. Applications on X11 get the scale from environment variables (completely bypassing X11), or from Xft.dpi, or by providing in-application settings, or they guess it using some unorthodox means, or simply don’t scale at all. It’s a huge mess overall.

It is one of the more-or-less fundamentally unfixable parts of the protocol, since it wants everything to be on the same coordinate space (i.e. 1 pixel is 1 pixel everywhere, which is… quite unsuitable for modern systems.)

Wayland does operate like how you say it and applications supporting Wayland will work properly in HiDPI environments.

However a lot of people and applications are still on X11 due to various reasons.