> We’re closing coal plants and building wind farms and it all just has to add up in the end. It’s not a one-to-one

And of course this won't cover the loss of energy, so let's pretend we can do that through "energy efficiency"

>You can make up that power by the way you operate the rest of your facilities or having energy efficiency savings so your customers are using less

Tl;Dr for the energy side: Smoke and mirrors.

Or, more generally, don't trust unregulated financial businesses and/or operating in shady offshore countries.

FTX was both unregulated and based in Bahamas.

With a huge process, you have a timeframe between the child is spawned and it executes exec*() where you typically "do stuff" (such as closing a lot of fd)

During this timeframe the parent process has its universe COW'ed, and each write will trigger a page fault.

The performance impact can be concerning in the _parent_ process.

We indeed have a lot of those fancy buildings from famous architects, mostly from the 70s.

They all share a common pattern:

- a repressed artist who became an architect

- a beautiful piece of concrete modern art on the outside and that makes fancy design magazine photos

- an oppressive building and a complete failure in term of comfort/ergonomy

Another example is the "Espaces d'Abraxas". But there are even worse examples when you look at brutalist architecture.

This is why nuclear power plants should be state-sponsored projects. States typically have loans at 0% rate, or even negative interests.

Sure, but basically it means rewriting all structures that rely on a bucket of stuff.

By the way maps often use a large bucket, and rehash in-place can be preferable.

> Which not many do, not unless the allocation is so large as to be in its own dedicated mmap

Do you know a modern operating system that does not have a mremap equivalent ?

On Linux you pretty much use it as soon as you reach large blocks.

I tend to agree, as a C++ developer. There are many core issues in the language that haven't been resolved and that are unacceptable for kernel code.

My personal pet peeve: C++ is unable to reallocate a new[] region. This makes basically all structures (vector, hashmap, trees...) unusable for large data handling.

There is no such thing as storage systems at wide scale unfortunately

> well also run out of fuel within a few generations

Absolutely. But hopefully fusion will be around then.

You can't exit from the oil economy with renewable such as wind or solar due to their non-predictability.

If you want to stop importing Russian gaz, you need nuclear energy.

This. Used Emacs for fifteen years professionally, and I gave up when I had to reinstall my laptop, as having intellisense-like features and easy navigation in Emacs is a complete pain.

I actually did not intent to switch to VSCode, but after a couple of hours of scratching my head with list configuration files, I ended up "trying" VSCode, and after a couple of _minutes_, everything was working (completion, navigation etc.)

After a couple of tweaking, clangd was plugged, and I had direct visual compiler feedback in realtime while typing code in the window.

VSCode is not "better". It's just another world.

The corporate wording for "Fuck you!".

Also knows as "the candidate we can pay less"

Even countries ruled by theocratic leaders who promote hate and obscurity ?

I can't wait to decolonize mathematics, physics, etc. and banish those arbitrary colonialists laws such as the law of gravitation, thermodynamics etc.