Ben Matthews

Scala-js is working on it - as its compiler design may facilitate this.
I haven’t yet tried (on todo list) and am not an expert, but bookmarked in passing:
recent github implementation, some history, following older discussion

Wonder whether the popularity of the president will follow a similar pattern as in France, trying similar idea … ?

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.

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.

I see that says ‘has to be local only, not federated’ (same issue also discussed on github).
‘Local only’ suggests to me front-end, i.e. info stored by browser. In that case people who are often switching devices would have to re-organise on each one, which could be tedious.
So isn’t there something in between local and federated - i.e. saved by the instance as user-settings, but not pushed to other instances?
Maybe there could be some manual copying mechanism, so a user who organises a big set of communities could share with others. (This reminds me of mastodon ‘lists’ and various ways of organising and transferring them).

Nearly 200 upthumbs, more ?!
But the discussion explores broader and narrow variants, need to coalesce.

Hi, excuse me for replying so late, but i’ve been away from lemmy for.a while. Well, to summarise, the model calculates the future trajectories, of population, economy, emissions, atmospheric gases, and climate response etc., according to a set of (hundreds of) diverse options and uncertainties which you can adjust - the key feature is that the change shows rapidly enough to let you follow cause -> effect, to understand how the system responds in a quasi-mechanical way.
Indeed you are right, complexity is beautiful, but hard. A challenge with such tools is to adjust gradually from simple to complex. Although SWIM has four complexity levels, they are no longer systematically implemented - also what seems simple or complex varies depending where each person is coming from, so i think to adapt the complexity filter into a topic-focus filter. Much todo …

I’m using Alexandrite, find it good

Hmm, publishing that will really help those Crimean beach hotels get customers for this summer…

I can relate to this, having developed a coupled socio-emissions-carbon-climate model, which evolved for 20 years in java, until recently converted to scala3. You can have a look here. The problem is that “coupling” in such models of complex systems is a ‘good’ thing, as there are feedbacks - for example atmospheric co2 drives climate warming but the latter also changes the carbon cycle, demography drives economic growth but the latter influences fertility and migration, etc… (some feedbacks are solved by extrapolating from the previous timestep - the delay is anyway realistic). There are also policy feedbacks - between top-down climate-stabilisation goals, and bottom up trends and national policies, the choice affects the logical calculation order. All this has to work fast within the browser (now scala.js - originally java applet), responding interactively to parameter adjustments, only recalculating curves which changed - getting all these interactions right is hard.
If restarting in scala3 I’d structure it differently, but having a lot of legacy science code known to work, it’s hard to pull it apart. Wish I’d known such principles at the beginning, but as it grew gradually, one doesn’t anticipate such complexity.

This is an unprecedented situation - if a guy who’s in prison (speaking via AI) and whose party is not allowed on electoral lists can nevertheless win an election , think which other countries might also be inspired by this … ! (note - although I’m not so keen on Khan (populist), am even less keen on military rule). I suppose now it depends which way PPP and MQM will turn ?

One reason people stick on Lemmy and other fediverse communities, is the choice of quality over quantity (in this case - wrt comments). So quality over quantity could also apply to platforms like Codeberg. Github has so many abandoned student projects or forks going nowhere - maybe making the effort to look beyond the obvious is an indicator of serious (new) projects and contributors ?

Saw same band (±) perform this in Norwich almost 30 yrs later, classic. As students we used to add ‘actions’ to dramatise it.

I began programming java climate model with UK keyboard. When I moved to the continent, switched to swiss then belgian keyboard to better type emails/docs in french, but it was so tedious for code brackets {[()]} and some other punctuation, eventually switched back. Recently converted whole codebase to Scala 3 (here’s the model), now can drop most of those brackets. I speculate whether one motivation for creating scala3 (made in in Lausanne) was swiss/french keyboards.

I like Scala:

• multi-paradigm, you can explore many ways of doing something, within one codebase - arguably the most complex language, if you want, but doesn’t have to be: start simply, later scales robustly
• compiles and interoperates with JS, JVM, native
• Scala3 dropped brackets - easily readable like python
• great tooling (recently) - compiler infers so much -> less puzzles / testing
• developed mainly in europe, not controlled by big-tech

Fwiw, here’s my interactive climate system model running in pure scala.

Too true.
I still remember when java5 came out, many new features, great potential for a massive refactoring of my interactive climate model. Within that, I had an idea called “parallel worlds” for comparing scenarios, whereby for efficiency data was shared for parts of the system, and split across parts that varied as user adjusted parameters. So I pulled apart the whole codebase, and joined it back together again… - about two years later, by which time colleagues had given up interest.
[ story simplified to relate to point of OP - not only task in two years! ].
Now I develop a derivative climate system model in scala, but evidently it’s more interesting to develop some new complex part of the science code, than fix a graphical interface for beginners. But moods vary - some days lacking energy for refactoring, could be satisfied ticking off a few small tasks in a todo list. Yet after some time, brain craving for another big new complex idea…

In defence of the jack-of-all-trades, if everybody is a cog in the machine, nobody sees the overview of how the cogs could connect.
For what it’s worth, here’s an overview of some cogs made by a j-o-a-t, for whom software developer is just a sub-role, within understanding complex climate system.

It’s only 5th December, seems unusually early for -58º. From Wikipedia - Yakutsk, maybe daily min should be about -37º now. I recall crossing Siberia by train in early December, rain in west, fresh snow in east, lakes still water, yet coming back in April you could still walk on Baikal. Seems odd, but they get extra problem of fires in winter, as fire hoses freeze, can’t extinguish them. Anyway polar vortex went wobbly recently, so we get alternating cold and warm waves - always look for both sides of regional anomalies.