Ben Matthews

  • New here on lemmy, will add more info later …
  • Also on mdon: @benjhm@scicomm.xyz
  • Try my interactive climate / futures model: SWIM
  • 0 Posts
  • 108 Comments
Joined 3 years ago
cake
Cake day: September 15th, 2023

help-circle
  • I find this analysis is a useful starting point for discussion, although there are plenty of details one might adjust.
    Personally I’m using (inter alia) claude to help me refine an interactive climate model (example here - although that’s last year’s version pre-ai-help ). So I care about these things.

    As my own life also has an energy cost - even just sitting at a desk with computers and some heat light and food. I reckoned by my own crude calculations that my ‘human’ energy cost per hour was considerably higher than that of my AI assistant, which certainly helps me progress faster, so the net effect was less energy per ‘task done’, meanwhile we don’t have infinite time to solve such problems. I’m only using claude within the limits of a pro subscription, and achieve that with tough claude_md instructions - not to go digging rabbit holes without consulting me. Sometimes it analyses and fixes autonomously and efficiently, but you have to keep alert - sometimes I interrupt and say no there’s a simpler way, and draft better algorithms / structures myself. Also I use scala whose sophisticated (non-ai) tooling constrains mistakes and its mcp/lsp makes searching and refactoring across a large codebase much more efficient than claude’s normal grok by subagents. Combine tools carefully, not brute force.

    Evidently a big unclarified issue is the energy cost of training these things. But we don’t need so much more training - for my purposes they are already good enough. The frequent new releases are about scary headlines to pump the IPOs. If this race could slow down, we could just learn to use what we’ve got more efficiently. In the general public discussion, I’d also appreciate clarification about how much of ‘AI’ energy-use is going into creating images and videos, rather than text and code, my hunch is it’s much worse for videos most of which are about trivial stuff. Also loads of datacenter energy is wasted transmitting talking-head videos around the world - that’s really inefficient. So well designed code, part-aided by ai, might help find more efficient ways to run needed global dialogue.



  • 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.