somishere

... And TBH the bigger smell is eminating from the explicit `null` returns. Next essay please.

And what if `fetchUser` hits an error? At the very least pop your de-maybeifier after the async call. Or use something language standardised (like a promise in JS where you can just throw).

I'm all for a perfy shortcut / early return but this maybe just seems like an abstraction on a non-issue.

Sure! Thank you. There's a few good definitions out there, some more absolute than others, but none of which quite capture the generally subjective nature of it. Personally tend to align more towards the "corrupted utopia", esp. where acceptance is controversial or blurred ... think the matrix or fahrenheit 451.

But the scene I pictured when I read that line, rightly or wrongly, was straight out of pearl jam's do the evolution. It's evolution baby.

think we're probably each focusing on different tropes of the genre here

"I guess that depends on what your definition of the word is is" ;)

> Yet, it is fake, as I am sitting on our top floor, a barely furnished room full of items belonging to a family house with two young kids

Define dystopia.

> LeafletJS’s developer is Ukrainian and can’t advance his project

Not sure what you mean by this?

Are you suggesting you can't support the project of a Ukrainian, or that the Ukrainian developer is unable to support their own project due to the war? Keeping in mind that Leaflet is a well established, open source project with any number of maintainers / contributors and (while no doubt an impossible time for a family from Kyiv) @mourner's contribution graph [1] remains remarkably healthy.

[1] https://github.com/mourner

Great context + points. Thanks!

Definitely not in a position to question the status quo, let alone the OSM community consensus. Other than to say that - even if the focus is currently on internal software / editors alone - it still feels like a massive opportunity. And one that aligns with a number of strategic goals of OSMF[1], specifically around efforts to grow the community, extend the core developer base (and more) ... by fostering a closer relationship between OSM data-derived products / the wider (non-editor) community.

Let it be known I love scope creep.

[1] https://osmfoundation.org/wiki/Strategic_Plan

Appreciate you weighing in directly Brandon! To be clear though, I didn't mean to say that protomaps was potentially a better solution (of course an uncompressed DB makes much more sense), simply that the developing nature of the protocol meant that it's inclusion within the "ecosystem" shouldn't be a closed case :)

Which is to say, distribution of OSM data feels like a large part of the process. Of course there are various bottlenecks / considerations around edits / writes, but in practice surely reads are the bigger vector. I wonder how many OSM-external use cases rely on "minutely" updates or need the full fidelity of the raw data source. Feels like there is a solid case for providing less frequent (hourly, daily?) official updates via official "single-file" formats that could be widely distributed to the benefit of all, and e.g. allow OSM to loosen up their hot-linking policies and ensure continued investment in the chosen protocols.

But mainly I was questioning how a somewhat proven format like SQLite, with its many benefits (interoperability, distribution, etc.), would be so easily dropped from consideration without even a test having been run. Just my thoughts of course!

Not an expert, however (lol) - even if the recommendations here are solid - this doesn't feel like a particularly well-reasoned comparison.

IMHO maintaining a large number of files on disk (be it 16m or 1.5b) should be a non-starter (not to mention that zipping them to slightly reduce the count removes one of the benefits of having them in the first place). A database makes sense - as does SOC between generation and distribution if it brings benefit - but immediately writing off SQLite because of write performance[1]? Similarly the arguments against pmtiles feel outdated and ignorant of the developing nature of the protocol (appreciate it's a 2yo post!).

OSM deciding on a format here has potential to significantly shape things to come. Hopefully Paul has progressed his thinking a bit since this was written.

[1] https://blog.wesleyac.com/posts/consider-sqlite

What a nostalgia hit!

Funny because I only recently found my old collection of Australian Hyper magazines from the early-to-mid 90s ... Looking at the covers makes me feel like I'm 10 again, hiding out in the local newsagent. What an era :))

This is an amazing resource. Thank you.

I mocked up an "infinite" circular menu concept last year. Idea was to use for navigating a non-linear timeline of photos / dates (in limited space on a website / map). Felt like a good use case.

Still think the use case feels solid.

https://codepen.io/theprojectsomething/pen/JjmgXrg

I'd also say keyboard shortcuts can work really well alongside this kind of UI, giving a single mapped key much more depth.

Awesome dream. I've pitched / currently attempting to pull it off for an Australian news org (scoped to their stories). But a radio.garden x gdelt is where it's at!

If you right click on desktop and choose your browser's version of "show controls" it gives a nice sense of the loop points ... some of them are insanely short!

What a mind bend. I picked it up as a foreigner in Glasgow when I found out I was living downstairs from one of AG's friends and also muse / basis for a character in the book. Found myself regularly lost, re-reading large sections of it with different contexts / interpretations each time. Have held onto it the last 16 years and lent it to many. Not too many have finished it!

Seriously amazing piece of tech here - satellite sourced emissions data covering the globe and the majority of industry. As someone who stares at this kind of thing most days, this latest release represents the gold standard for the sustainable development goal-y trinity of emissions data sourcing, wrangling & visualisation.

According to the presser they're looking to begin releasing updates multiple times per year, in the new year. Fairly impressed.

Funnily enough just finished monkey wrench last week. Dark and hard going at times, but enjoyable. As someone who has never lived in Melbourne but spent formative years in Brisbane, Glasgow and Dublin, I would say it's fairly relatable (within that very specific cultural milieux!)

My sentiments and experience completely. Could mostly put up with the DX with the right mix of modules in place, but never got over the UI. Next. Level. Terrible.

Can only access the NYT piece in reader mode, but the Centre for Climate Reporting broke the story a couple of days ago (alongside the BBC). They have the documents embedded in the story. “breathtakingly hypocritical” being the choice quote.

https://climate-reporting.org/cop28-president-oil-climate/

I mean, if you're not shipping the weight of the water then how could there not be? Tho I guess it would come at the expense of local artisan roasteries ...

Honestly though, I think conscientious / well regulated labeling can do a lot of heavy lifting when done correctly. Especially for highlighting what factors you should be considering, rather than those that are being promoted. Let market forces lead to "source-roasting" and other innovative improvements.

Fair point. But this isn't a get out of jail free payment, you're not "offsetting" your cup, just getting charged for it. The social stigma of walking around with a single use coffee cup remains, and may even be amplified. Not to mention that "cafe coffee", at $4-5 / cup (in Australia at least), is already very much a luxury item.

The cup is a product that is currently perceived as gratis / of zero value. Charging for it is intended as a disincentive. In the case of plastic bags (here) it largely worked as such (with prices as low as 10c per bag!) and paved the way for a ban. Though the parallel effect of more resource-intensive bags / cups entering the market / being treated as single use is always a consideration.

But to your broader point, for sure .. bring on a ban.

If we're talking emissions and coffee then another important aspect is the source / growing practices / distance travelled of the beans. Better labelling around these kind of aspects would better balance the current cafe decision matrix of blend / extraction type / roasting characteristics.

A lot of Australian coffee shops give a discount for bringing your own (takeaway) cup. Personally I think they should just charge/tax for single use cups, to the benefit of those sitting in or bringing their own.

Single use plastics, but not bioplastics, are on the way out across Australia, and some more conspicuous forms like bags have recently been phased out. With bags the first step was to start charging for them at the till, which led to many choosing to byo. This was followed by a blanket ban (in my state anyway) in September this year which had suprisingly little fallout.

I also kind of like the idea / various iterations of the Freiberg cup [1], but the fact that they are so easily replaceable makes me wonder how many just end up discarded (esp by those who don't like carrying around a used cup). But I'm sure these questions have answers / solutions.

I was going to comment, but you've done it for me. Your additional advice is spot on. But I actually think, "do whatever you like, the web is designed to be flexible".

The most crucial (half made) point here is that if you want your website to be useable beyond the output, document it ... include comments, make your reasoning explicit and not implied. And yeah, a repo is probably a great place for this. It doesn't even need to be linked on the visible part of your site (I mean, who's the primary audience here), just do the old "we're hiring " trick and print a link to the site's GH in the console. The docs will probably solve a few problems for you too when you need to change things down the line (I constantly read and improve my own comments during refactors, and usually kick myself when I haven't made them).

This is great, thanks for sharing.

as did Bale's Patrick Bateman ...

I was half your age in 89, so don't remember the news item, but I have strong memories of the Netscape and ozemal icons taking up estate on my step mum's compaq in the mid 90s. She was writing her PhD on it, and technically we weren't even allowed into the "office", let alone on the computer. Yet somehow I found time between 3.15 (when the school bus dropped me outside) and 4.30 (when she got home from uni) to work out what it was, connect and turn on the modem, hunt down the ozemail card and access password (after days of trial and error pw prompt denials), connect, explore first the boundaries of the ozemail portal and then beyond, and ultimately build a number of (local) personal websites using tables and hotlinked pictures that I hid in an official looking folder structure. This probably happened over many months, with the help of various co-conspirators (I would have had little idea of what the internet was before starting out, we had computers in our small state primary school, but the best thing they had on them was sim city). I was finally found out (though not red handed) when she came home early one day and picked up the phone in the living room ... at which point I bolted out the back door.

Funnily I didn't really do any elective computer subjects in high school when they were available, but I did spend a lot of time at home on my step mum's computer, chatting on ICQ, making websites and playing with graphics programs like paint and cool 3d. And eventually won my first computer at the end of high school (from channel V the pay tv music channel in Australia, tho truthfully I was a dyed in the wool rage child) with an animation of a frog jumping into a fan, made with a pirated version of Macromedia flash, downloaded in many chunks over 56k ozemail dialup.

The pioneering efforts of the early Australian net scene was lost on me. But it also shaped me. I'd love to see the doco.

Tried to get pouchdb / rxdb working on a number of projects over the years. Hoodie also. Ran into "too hard" problems every time and fell back to something else :/

I think what I liked the least was the complexity introduced to the client (a fun statement considering some of the apps I've worked on recently). Instead of being able to abstract away business logic behind a simple API, it was there in all it's "haute logique" glory - hardwired into my otherwise dead simple todo app.

That said, still love the concept. Keen to try some of the new names. Tho the idea of it living in a worker, where it can be queried / controlled / deployed (or replaced) as if remote, has a nice ring to it?

In Australia 35mm cameras worked out to about this (for decent c41 developed at a decent print shop), even before smartphones / digis went mainstream.