Post

Opening with @neurocy.bsky.social explaining the 'working group' model we're doing for the 3rd PROPL

Programming for the Planet

@propl.dev

15 June

There are clear roles for computer scientists to have a role in managing planetary health, and we can win! #propl26

Programming for the Planet

@propl.dev

15 June

There'll be a split PROPL this year; a morning set of position papers (including climate modeling), and then a working group where we'll put concrete action items together for what the PL/systems community can work on together on!

Programming for the Planet

@propl.dev

15 June

While there are many digital commons out there for scientific data, the future digital commons must also *compute* using FAIR principles, says @neurocy.bsky.social doi.org/10.1145/3759...

Programming for the Planet

@propl.dev

By FAIR, we mean good support for findability, accessibiilty, interoperability, reproducibility, while supporting liveness at scale.

15/6/26, 3:32 pm0 reposts0 likes

Programming for the Planet

@propl.dev

15 June

We need to get out into the wider world and consider the incentive structures for who will actually use these systems. The benefits of this new structure cannot just go towards those regions that don't need it help.

Programming for the Planet

@propl.dev

15 June

Next up, @deepakcherian.bsky.social presents Icechunk, a storage system that scales with the whole planet!

Programming for the Planet

@propl.dev

15 June

Deepak's a great example of someone who wouldn't ordinarily attend @sigplan-pldi.bsky.social; he's a 'professional scientist' who has worked on terabyte scale oceanic models, and now maintains important scientific infrastructure like xarray

Programming for the Planet

@propl.dev

15 June

Oceanography has an inspiring history of open source from the 90s zenodo.org/records/1061... but more sophisticated ideas and services never built a network effect and so we've ended up with 'standard compliant self-describing metadata-rich piles of files'

Programming for the Planet

@propl.dev

15 June

Each of these massive storage arrays is bespoke, and each consumer repeats huge amounts of computation without any sharing or peer verification. Updates and ingest are also invisible, and so users are exposed to raw filenames and how its partitioned. This is happening with data from NASA, JPL etc!