Mais - j'essais comprendre n'étant pas français ... - si les ministres auraient été remplacés par leurs suppléants, le résultat aurait été ± la même, n'est-ce pas ?
benjhm
Thanks, fixed! As you can see parts of the science code are already accessible via the 'cogs', but not yet the structural code - anyway keeps evolving, update soon.
Note that Knesset has 120 seats (not obvious from the article). (also, of course, a large fraction of people between the river and the sea don't get to vote for any of its seats)
Similar - I thought about codeberg for the source of my interactive climate model,
but am not yet ready to give it a pure-foss license - might split in parts with different licenses. Could try self-hosting.
Useful insight, especially country-specific part, thanks for link. Coal is still too high, but maybe we should look at seasonal usage, not assume 'operational' = always on. For example in China, they might be keeping excess coal capacity for occasional use during extra-cold winters ?
Reminds me of time when, during the Beijing olympics, the sky miraculously cleared of smog and turned blue - showed what they can do when it's a priority, but didn't lost long.
Good analysis. Instead of blobs for one year, try also plotting energy use/capita vs income/capita (same axes) changing over time - you see how the curves bend.
I don't buy this. I'm still using SMTP on my own domain and it’s working fine, a bit of spam but not unmanageable, real messages get read. Main challenge is digesting so many potentially-interesting list messages, indicating email's continued dominance for professional topics. Seems this author has another agenda.
Having said that, it's a pity the world never agreed a protocol for micro-payment for emails (and for many other services), which would resolve the spam problem, and not be a burden for honest users.
Point de vue d'un visiteur d'un pays voisin en planifiant voyages en famille, la problème c'est que c'est si complexe, rechercher d'options différentes pour chaque région.
It's good to respect efforts and successes, the curves have bent and we need to explain that as it’s hard to perceive through the inertia, but the world is bigger than US, and stage eight needs a lot more elaboration ...
I'm no fan of geoengineering (see this paper from 1996 ) but these specific proposals seem local, potentially reversible interventions to slow down melting, so could be worth investigating. Even if we get to net zero and stabilise the global surface temperature, it would take much longer (decades-centuries) to stabilise ice- melt, deep-ocean warming and consequent sea-level rise, there is a lot of inertia.
Their second approach focuses on meltwater, but thatt has to flow somewhere, maybe better focus to keep ice solid - e.g. I'm surprised no mention is made of the ice-surface albedo - e.g. minimising soot, algae. Minimising aviation-cirrus from planes passing over greenland might also help.
I use vscode as I develop this model in Scala3, whose language-server 'metals' integrates well with vscode, and when scala3 was new in mid-21 this was the platform they first targeted. But the scala command-line tools do the clever analysis, vscode provides the layout, colours, git integration, search/regex, web-preview etc.. Now considering other options (eg zed) as vscode too dependent on potentially unsafe extensions (of which too much choice), also don't want M$ scraping my code. Long ago when same model was in java I used netbeans, then eclipse. Would prefer a pure-scala toolset.