Ben Matthews

Sure, China needs more ambitious medium-term climate targets, and this matters as its emissions are such a large fraction of the total, so their projections strongly influence global climate goals. But much changed recently - their capacity for renewables is huge, and road transport electrifies. Meanwhile China is heading downhill now - population is clearly declining, emissions probably are too (awaiting latest data), and maybe even economy depending on which statistics you believe, and whether there’s any soft-landing from the housing stall.
So the peaking target is probably no longer relevant, although they may still have trouble with their gdp intensity targets (due lower gdp than expected) - but there are various ways to re-interpret that.
It doesn’t surprise me that Tsinghua profs try to keep options open to nourish the dreams of the old men in power - just maybe their three-child policy will bear fruit, maybe people want even more highways and bridges to nowhere, or they can keep exporting such projects (including their steel) to africa, south asia etc.
China also occasional gets extra-cold blasts some winters, which may help to explain keeping coal power capacity as a backup, while also keeping regional coal tycoons on-side, but on average this capacity may not get used much.
So when comparing targets, and especially aggregating such targets across countries to project the climate outcome, it’s important to bear in mind that the gap between official ambition and reality - the probability of meeting emissions targets - differs a lot between countries, this partly reflects political systems - and China seems particularly ‘conservative’ in this regard …

Looking forward - eventually - to trying out the wasm option, which might eventually help speed up my interactive climate-scenario model which already runs with scala.js. Although speed is not currently the limiting factor, a wasm option might expand the potential scope - for example to increase regional resolution. However I presume to do this I’d have to refactor the code a lot, to keep all the gui and io in js while pushing the intensive calculations to wasm, and create data interfaces between these (at a rather low level if i understand correctly?), which could get tricky as it’s tightly coupled, code evolved over 24 years …
Puzzled why wasm is promoted for “backend”, which already has other compilation targets (jvm, native), seems to me this is a bigger opportunity to do complex calculations in the browser.

Hmm. I’m still using a 2014 iMac, as its 27" 5k screen still very good for coding (with added memory). Sometimes develops a bunch of thin vertical lines, which come and go maybe dependent on temperature, but hasn’t changed for for ten years and i can live with those. Just wish they’d continue providing security updates for it.

Odd that Estacio de França is now the terminus only of lines from the opposite direction - but it makes sense to run all across the centre.

I’ve been calculating and struggling with climate change for - well, seems a long time now.
As a young man, I didn’t expect that world society would survive as long as it has, I thought climate was existential now - in the 1990s - so I tackled what I could then, rather than planning for my life decades later (which is consequently not easy).
But we’re still here, and actually the range of scenarios looks somewhat better now than projections back then.
Probably emissions in China have just peaked, and as these are such a big chunk of the global total over last 20 years, so that may have peaked too. Global science and civil society has, collectively, helped to influence that. We have bent the curves. Of course there is inertia in the system, it takes time for carbon and heat to penetrate the deep ocean and the ice, so the surface temperature will continue to rise for decades, but not necessarily for centuries - that’s still our choice. Yes, some megacities will drown beneath the sea, and others become uninhabitable due to heatwaves and drought, but there will be plenty of other places to live, we’ll need some redistribution. Many other species will be (and have been) lost, but life on earth has survived worse catastrophes, life will go on.
Especially people who care about such future, who educate themselves about the challenges, yourself included, should be part of that. But it’s a long-term problem, without quick-fixes, so plan accordingly, saving some strength for later, we’ll still need it.

I like some concepts and design of Mbin, something to learn from, but I’d believe more in its growth potential if not written mainly in php.

Interesting observation and analysis, and illustrates the potential of more lemmy-mastodon interaction.
Indeed mdon like-federation seems weird but I presume it was setup this way for efficiency, to reduce the number of small communications? Although Lemmy has a backend in rust - more efficient than mdon’s ruby - still I wonder whether the lemmy system of federating all upvotes would scale well if the number of users grows to that of mastodon and beyond ? Could there be some intermediate compromise solution (e.g. federate batches of 100 likes)?

Indeed to use scala-native you’d need pure-scala libraries, but the core lib re-implements most java lib, and there are now small simple external libs available for common tasks like file management, database, etc. - for example check out the lihaoyi suite.
I mainly use scala-js (to make this) which was formerly a java app - as it compiles to both js and jvm (cross-project) can gradually convert stuff you already wrote. I’ve tried native for stuff like pre-processing data files.

I didn’t discover Lemmy through search, nor did I ever use reddit - I found it from mastodon where a few people promote lemmy posts. Then gradually realised I preferred the community-focus here, compared to the individual-focus of mdon (although combining both could be good). As mdon has many more users, improving this inter-op would help to bring people here.

Scala compiles either to native, js or jvm - obviously the IO / interface options vary between these envs, but the lang is the same. Recently Scala 3.5 incorporates a simple-to-use CLI which makes it easier to compile to native (or just run a small file as a script, or experiment with a repl), native binaries are small and fast, and there are some simple io libraries. Since you can also compile to jvm to interop with java, that might help with transition.