Ben Matthews

  • New here on lemmy, will add more info later …
  • Also on mdon: @[email protected]
  • Try my interactive climate / futures model: SWIM
  • 0 Posts
  • 177 Comments
Joined 3 years ago
cake
Cake day: September 15th, 2023

help-circle
  • This article feels to me really out of date. Scala3 was launched nearly five years ago, The tooling and lib-support was indeed dodgy back then but works very smoothly now. Scala3 also broke Scala2 macros, and some people whose business-model was selling support for clever libraries built on those macros made a lot of fuss (bad publicity). Meanwhile Scala3 has new more robust macros which work fine.

    I develop in scala an interactive climate-scenario model web-app . It’s running the model in your browser (500 years x 250 countries x many gases, sectors, feedbacks etc. - so it’s complex)… The scala code compiles to js (or wasm) -which is what runs this web app - but the same code also compiles with scala-native to run fast batch- calculations or tests. It also compiles to the jvm app like my older java code, but I rarely use this now.

    Scala3 code looks more like python than java - minimal brackets, and much nicer to read and higher level than rust.
    As for tools I just use Zed editor with Metals for LS, Mill for build, and other libs from the lihaoyi ecosystem, no web ‘frameworks’. Scala is both robust and flexible. In general - if the code compiles, typically it runs correctly first time, if not the very-intelligent compiler identifies precisely what to fix where (very different from so-called ‘AI’). So instead of reams of junk ‘tests’, it’s usually just enough to check whether my climate system plots look and behave as expected - higher level thinking.

    As for Kotlin it was effectively a russian-led (at the time) fork of Scala, staying closer to Java - so less flexible, but they did much more systematic marketing - and I suspect some of that deliberately pushed blog posts knocking Scala.
    What Scala lacks is promotion, so those following fashions of this hype-driven world won’t find it.
    For those who use it, it’s a great language, to do complex stuff that scales robustly.














  • Seems to me a win-win scenario. Remember that Ukraine is actually remarkably good at railways - especially at manufacturing large numbers of comfortable and good-value sleeper wagons, which the rest of europe lacks, and also at maintaining their system in such adverse circumstances - their punctuality today is still much better than DB. On the other hand the track routes in Ukraine are anything but direct, dating from 19th century when capital cities were Petersburg and Vienna (so they align better N-S than E-W), so there’s a lot of potential to make them straighter. The obstacles maybe rather regional mistrust - whether politicians in Suceava accept the status of Chernivtsi - a similar question as whether hungarians / slovakians accept Uzhhorod, polish Lutsk or Kovel,…? Better passenger transport links could help to build trust.







  • This study is indeed disturbing, drawing on multiple lines of evidence suggesting melting may happen faster than previously assumed, I’ll study more.

    However, there never was any magic safe (global-average-surface-) temperature level, to save polar ice sheets. Melting, and the penetration of heat, is cumulative, so to a first approximation it is the integral of the warming that counts (maybe we could talk about a heating budget, similar to the concept of carbon-budget to avoid a specific temperature).

    Although diplomats may stress that the concept of safe level is baked into Article 2 of the Climate convention, that orginally applied to “concentrations” not temperature. Back in the day (early 2000s) I among others pushed (this wasn’t easy) to adopt temperature as a goal closer to real impacts, pointing out that required peak+decline concentration pathways.
    Nevertheless we always knew that a stable (higher) temperature does not bring a stable sea-level (on a multi-century timescale) . While for some other types of impacts - e.g. ecosystem adaptation, it may be the rate (derivative) rather than the integral that matters more. The ‘level’ concept was a compromise to coalesce policy (within which - round numbers like 2.0 or 1.5 C also arbitrary).

    Maybe it could help motivate the global debate, to specifically (dis)agree goals of sea-level rise we try to avoid ? That’s a more tangible level ( at least until we get into regional sea-level-rise variations…) , but due to the double integral, it’s harder to implement.