this post was submitted on 23 Oct 2023
29 points (100.0% liked)
Programming
423 readers
6 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I develop an interactive climate / future scenario model, now in scala, earlier in java, almost no dependencies. No visualisation frameworks - the diverse plots hand coded in scala (transpiles using scala.js, makes SVGs on demand). The science code from demography through economy emissions, bioegeochemistry, to climate - just scala, no interface to other languages / models, no "solver" tool. Data input just text files -easy to check. Some modules over 20 years old (except converted java -> scala), still work reliably. It's efficient as all client-side, no IO/net between adjustments and results. Seems no big institute would employ me for such model dev because my experience doesn't tick the boxes of all the current fashionable frameworks. But at least I can share a way to explore the future for ourselves ... and yes it’s bleak but not so dire as many people here seem to assume, we still have choices.
One choice I think you've nicely demonstrated: the choice of a solid base and not choosing to add dependencies.
Choosing not to do something can be hard.
Also double points for having a sustainable software project that helps with environmental sustainability. Really walking the walk haha
More like sprinting the sprint!
Hi, thanks for the encouragement, delayed response due focusing on the code, and a related conference, and now trying to keep up with the COP. As it happens, the "ratchet" system of pledges created in Paris (COP21) is an iterative algorithm - start with wild guesses and gradually improve them by feedback - this made sense given the weaknesses of diplomacy, but it’s hard to summarise this mess with neat code in a compact model.