Notices by molily (molily@mastodon.social)

Hear, hear, citizens of Fedistan! The React Critic has posted another React Critique against the doors of the cathedral!

fedi dude: “they will crawl back to fedi when bsky inevitably runs out of VC money”
No, they will once again organize to migrate to whatever service they find useful, where folks are not alienating and self-righteous

This long thread on Mastodon and Bluesky is on fire. 🔥🔥🔥

Don't agree with everything there but there are many good observations and thoughts.

https://hachyderm.io/@danilo/113382452904993645

Read it backwards up (thread by OP is hidden otherwise 🤡):

https://hachyderm.io/@danilo/113545771142835903

nb. I want safe, open, publicly-owned, community-operated, anti-fascist infrastructure that lasts for decades. The fediverse is the nearest we have, that's why I'm writing here. There are many promising efforts to make this place better. Not complaining about the lack of certain features compared to a site funded by *checks notes* crypto blood money. Complaining about the arrogance and self-righteousness of certain fedi folks.

It's true that in this crucial moment of opportunity, the fediverse failed to attract users (succeeded to repel users). So it might have reached it's peak. I'm confident that it will continue this way or another. And hopefully serve its current users better. Overall, fedi is self-contented and doesn't want to change and grow substantially, so all is right, or not? 🤷

Ask yourself why a community like Vue took an enormous effort to write Elk and later organizes a (hugely successful) eXodus to Bsky (within days)

(fedi reply guy: “i don't care, good riddance, sellouts, class traitors” etc)

BuT wE DoN't WaNt tO Go MaInStReaM1
– every fedi reply guy when someone notes that the protocol or the server software or the UI is confusing or missing something

Hi. You might follow me for web development. Haven't posted often though.
In the future, I'd like to put this account to use by sharing links on water, hydraulic engineering, drinking water, wastewater, freshwater & marine ecology and related fun topics like climate change. Mostly in German, English and Dutch. 😅 💦

Fakt: Mittelaltermarkt heißt auf Niederländisch »extra belegen markt«

#deutsch #niederländisch #übersetzung #duits #nederlands #vertaling

I think noone really has a clue, not me, not you. Last year I wrote that we need to stop with sermons, insults and self-righteousness. We need to convene in respectful and productive ways to make radical changes. These are still my two cents.

Unpopular opinion in these corners of the internet:
The current state of client-side JavaScript usage on the web is so abysmal *also* because the criticism of said state is so abysmal.
As someone who tried to intervene to improve the state, I don't exempt myself from this verdict. If we want to make any progress, we need to start with this confession.

There are so many truisms that crumble when the tire hits the road.
Use the Platform, HTML First, Progressive Enhancement, UX over DX, Vanilla JavaScript, Web Components, Hypertext/Hypermedia, HTML over the Wire, Resumability, Islands, Server Components or whatever the new savior is supposed to be.
Some fundamental principles and certain techniques are useful. Unfortunately they are often sold with the same zeal, marketing and superficiality as the next JS framework.

I think there's much room for debate. So many questions need to be discussed in nuanced ways. Social, organizational, economical questions. Not only technical.
Instead, people present silver bullets and jump to conclusions.

Human brain: Benutzer*innen
Planet brain: Benutzer∗innen
Galaxy brain: Benutzer�innen

This is an interesting series on Progressive Enhancement & JavaScript:
When JavaScript Fails: https://scribe.rip/@jason.godesky/when-javascript-fails-52eef47e90db
A Practical Guide to Progressive Enhancement in 2023: https://blog.bitsrc.io/a-practical-guide-to-progressive-enhancement-in-2023-52c740c3aff3

In total, I think it would help to not discuss the progressive enhancement of non-products and try to infer/generalize the theory, but share what we have learned from enhancing existing products.

This equally affects my writing on progressive enhancement which often focussed on trivial examples or was too theoretical. It often lacked stories about products I was actually working on.

I kinda agree and appreciate that the article addresses this misunderstanding. But I kinda disagree as well? I, for one, am interested in progressive enhancement to get my product's value proposition implemented as robust as possible. IMHO, this is the business benefit of progressive enhancement and also my advantage over competitors with slow/brittle software.

But again, it's hard to discuss such important architectural questions on the basis of simple examples, so I might be overthinking.

More importantly, I find the high-level messages worth discussing.

The crucial point for me is “[Enhancement] doesn’t mean unimportant. Enhancements can be critically important. […] Your primary value proposition might be an enhancement”.

The other point is the rather technical definition of the “core experience” as the “value that you can provide when [everything but the server] breaks”.

I'm glad more people are getting into progressive enhancement. Still, as someone who's deep into it, this leaves me puzzled for several reasons. I think we need realistic, non-trivial examples regarding PE & JS. Here we have a rather contrived example with one button/interaction. Not saying it has no educational value. It addresses many practical questions. Yet it's not particularly convincing. One could question this particular example or its implementation, but this would be pointless.

Conceptually and structurally, this resembles jQuery + Handlebars widgets in 2013 but now based on Custom Elements.

Totally agree with the article saying *nothing has changed*. “[Using Web Components is] not *meaningfully* different than simply passing a node to a constructor and listening for DOM updates.”

That's what we did in 2013. And in 2003. I find it hard to grasp that people accept an outdated development model that produces error-prone sites.