Especially in autumn and winter.

The largest "but" is that they only look at electricity generation, not energy in general. There's a lot of heating with natural gas and of course most cars still have internal combustion engines which burn petrol or diesel.

Heating with gas is difficult to phase out since it's a major investment. It would require large-scale build out of remote heating.

Replacing IC engines is a whole different story, and it's not clear whether electric cars are a complete replacement yet.

But that only works if you already know the exact movement and you basically end up playing a film on the background screen walls. You can't change anything of this on set anymore. Using real-time rendering with Unreal or whatever gives you more flexibility in exchange for visual quality.

It's done that way because of pre-visualization or Previs, which has been the norm for over a decade now.

https://www.youtube.com/watch?v=oxTNhNe6Fbc

Carbon tax is not about offsetting emissions, it's about disincentivising fossil fuels.

It is about disincentivizing fossil fuels because there are negative externalities which are not priced-in absent the carbon tax.

Announcements in English aren't done for every station. Usually only for central stations and airports.

> Airbus would have been a terrible idea: no one had built commercial airliners before, and only the US had the know-how.

That's just plain false, Airbus started as a cooperation between a lot of european aerospace companies, which had different a lot of know-how in different fields. For example Sud Aviation (later Aérospatiale, now Airbus) was the French part of the Concorde, they also had the Caravelle.

Plus there was a significant contribution from England - VC10, deHavilland Comet, etc.

England also made what I consider to be the prettiest bomber ever made - the Handley-Page Victor

I would use "sei" instead of "lass" for "let" to be more in line with notation in mathematical proofs.

Imports being slow is annoying, but only matters to short running code.

Many simple scripts at my work that more or less just argparse and fire off an HTTP request spend half a minute importing random stuff because of false deps and uncommon codepaths. For some unit tests it's 45 seconds, substantially longer than the time taken to run the test logic.

In dev cycles most code is short-running.

> Many simple scripts at my work [...] For some unit tests it's 45 seconds

> I spend a lot of time rewriting the python logic in C++, which makes it 100x faster

Nice! Your workplace didn't care to pick a better tool for the job in the past, and it seems to not care what you're doing at present, if you have to spend time rewriting the stuff in C++, instead of picking Nim and calling it a day, in a day.

Even better, in Nim these little CLI tools could use https://github.com/c-blake/cligen and have had terminal colorized, auto-generated help for many years now with much less dev-effort than raw argparse. Start-up time of statically linked Nim programs is like O(100..500 microseconds, just like C programs).

Have you thought about packing that stuff into an executable or precomputing or preloading it? There's techniques for each of those things that help in some scenarios.

It's two different computers with different CPUs, so different runtimes are expected and has nothing to do with the OS.

> Framework laptop running Ubuntu Linux 24.04 (Intel Core i5 CPU)

> Mac laptop running macOS Sequoia (M2 CPU)

Yes, and why? way to not address the question at all.

Are you asking why the M2 is faster than the i5?

Well I was asking whether there is something in the Mac Kernel which makes it faster or is it just the different CPUs/Memory that account for this?

According to general benchmarks Apple Silicon is the highest performing CPU for single-threaded work. It'll be hard to confirm how much of a difference the OS factors in but the hardware difference is most likely why.