jonnyscholes

If you're not worried about black-ish pixels, it's surprisingly reliable.

Gosh it's hard not to enjoy this, even as an artist who is uneasy about the whole GenAI image thing. Having said that, I'm temporarily comforted at how ugly a lot of the abstract paintings are once animated.

Fair point. I'd be the first to admit I have rose tinted glasses about those early years! And also the first to grumble at those who came later...

For me there's 2 things:

Whilst being post-dotcom, where a lot of the internet was worked out technically, culturally platforms were still only just starting out. It was before social network UIs all looked the same and there was a play book for creating a network for X. Small communities were thriving and they all still had control of their ecosystems. Internet "mediums" were still in a state of flux on all fronts.

It was the start of "the masses" coming online and creating profiles - but they came online through things like MSN spaces, MySpace and geocities. Which were a lot less sanitized than today's equivalents. Everyday people experimented with their pages the same way teenages do with their bedroom walls. They looked awful, but the medium was alive.

Both of these made me feel more like making for the sake of making was less linked to ego. And overall every community I was part of was still innovating on the medium as much as their niche (be it art, netsec, photography, local history etc).

The parallels I'm thinking of in particular are both artists rushing to the platforms and trying digital art for the first time (admittedly many driven by $$). Meanwhile community leaders are having to deal with new technical, cultural and governance issues - many of which are novel issues imo.

That's fair, and perhaps for you that true. But 99-05ish are the internet years that I remember as the most creative. It was well before everyones IRL persona was mirrored online, which is when I saw a dramatic shift in what people created online (at least where I lived). Broadly speaking it become less about experimenting with the medium and more about broadcasting what already existed.

The communities I came across were for the most part making for the sake of making. And plenty of them were building new things and experimenting.

Everyone's experience is relative. Perhaps my experiences are rose tinted by nostalgia.

All that is to say, I observe aspects of some NFT (or crypto) communities feel the same to me - new mediums, new challenges and a new excitement around them.

* However I do still think that there is a huge NFT/crypto bubble and there is cataclysmic amounts fud.

This is my experience. Hicentnunc (and the tezos community at large) is the closest I've felt to 00s internet culture/content which got me hooked on programming.

Although perhaps paradoxically, I suspect the barrier to entry is part of this.

Full disclosure: I hold a small amount of tezos.

Product looks great and I look forward to working with it, but they should think about how to solve the drag-trap on mobile for these types of experiences. I literally had to scroll by touching my finger on the top menu and flicking. Google maps eventually move to a two finger drag on mobile to fix this...

This is particularly true on iPads. Instagram has clearly decided it's not worth the engineering effort to adapt Instagram (a multi billion dollar asset) for iPad. No matter - add the PWA to your homescreen!

Can confirm PB&H is a thing in Aus - however peanutbutter and Vegimite is where it's at

This comment is just as applicable to the sibling comment here and many others, I don't mean to pick. Peace.

I've seen this comment and reserved comment a few times but here we go...

Sure, Standard on the face of it seems simple technologically, and compared to many other things it is. But it's value lies in completely removing long winded and often unnecessary conversations within teams about code style.

Standard represents a standard style of writing JS that has gained widespread support (similar to Airbnb's linter config). It's value is that a team can adopt broadly sane conventions then never think about it again - which leaves those dev cycles for shipping features. Without widespread use, Standard would be just another linter config - but large parts of the JS ecosystem (regardless of what people think of JS) have adopted it and as a result it has saved the world a million conversations that "didn't need to happen".

If you care enough about style to not pick their choices, you're free not to use it. But for a lot of us we just want a broadly accepted opinion so we can focus on features.

And as it turns out, maintaining a style guide for how to write JS for the masses takes quite a lot of work. Not writing code necessarily, but considering and replying to all the feedback on that style.

Not for or against the funding project - but within the JS ecosystem Standard has meant many hundreds of hours that might have been spent biked shedding, have been spent shipping features.

Standard has been genuinely useful to myself and pretty much every other JS developer I know. And whilst I'm in no position to speak to weather I'm junior or not I know a lot of the most experienced programmers in the JS ecosystem reach for Standard so they can focus on more important matters.

It's not JS that has such opinions enshrined in law, Python for example has pep8.