There are still absolutely beautiful websites using basic css and html with little or no js. professional web dev has gotten more complex along with specialization, but you can still build personal sites with 20yr old tech. and some new stuff is simpler.

What we've lost, it seems to me, is the broad indie pipeline to both learning and socializing (and socially learning).

partly because we who learned it 20yrs ago have landed in more specialized/complex jobs.

@mia AGREE HEAVILY. Encountered something recently with a FAQ entry so hostile and belligerent toward using raw/native web tech that... I got fucking incandescent.

It was less that one little scrap of text and more knowing that that's likely the prevalent mindset out there.

Nobody needs goddamn webpack just to noodle with web stuff. Hell, technically not even to make an extremely complex and performant site/app.

@joshuaelliott @mia

Webpack sucks and the people who made it deserve to be punished.

@mia I like the (generous) nod towards specialisation, but it's not only that. There's a power dynamic that (superfluous) complexity creates, and it sand-blasts teams and leaders down to their values.

Turns out a lot of the JS community (esp Over Reactors) had pretty shitty values, and saw the chance to talk down to CSS knowers as an opportunity, rather than a problem. Complexity as gate to keep the riffraff out.

@slightlyoff @mia oh Over Reactors, I like that one.
@slightlyoff yeah, that's true. I also don't see specialization as neutral or natural, but as corporate. and also think the constant drive to deliver - the coveted efficiency of speed - tends to encourage complexity (and other broken things).

@mia Having helped more than a hundred teams convalesce with codebases that are in deep, deep JS-ecosystem-dogma-created trouble, I'm well out of patience for the "but speed!" nonsense. Because it's nonsense.

These teams get *beached* by JS dogma. The frameworks and tools become ends unto themselves, and usability declines to the point that for all the churn, no progress is detectable by mgmt; only a knot so Gordian they fear it, rather than manage it. This is anything *but* going faster.

@mia As I keep telling folks, the claims of "but I can move faster in X" are nearly entirely self-reported trajectories of learning. The same thing you'd get if you really bore down and practiced...IDK...Perl, or whatever.

But annecdata is not a controlled study. Extrapolations here, particularly around "DX" have always been statistically flawed to a fatal degree. Unsurvivable doses of marketing radiation everywhere you turn.

@slightlyoff @mia Claude renders the dx/cant-not-hire-react argument moot

@slightlyoff @mia

"Over Reactors"   I am pinching that thank you.

@mia I would use even less JS if browsers had better and more modern XSLT support
@oblomov Or ar all. Isn’t Chrome phasing out XSLT support completely?
@oblomov modern XSLT 🫢

@zopyx compare

https://www.w3.org/TR/xslt-30/

with what the browsers make available.

And of course 4.0 is in the works too.

https://qt4cg.org/specifications/xslt-40/

Just because GAFAM has decided to kill a tech because they can't exploit it for surveillance doesn't mean it hasn't evolved.

XSL Transformations (XSLT) Version 3.0

@oblomov XSLT was never modern, it has never been approachable, it has always been a niche and zero tears for seeing fading away
@zopyx bullshit. XSLT delivered exactly what it was supposed to deliver, doubly more so in later revisions that made it immensely more approachable. And if your problem was ever the syntax, that's what XQuery was designed for. But again, can't do surveillance capitalism with that so not supported in browsers.
@oblomov your opinion…an outdated Technology that has neve been modern. Nothing that we need in our tech stack…never needed, always avoided..not a big loss… in particular irrelevant in the web stack and only used in web context by XML freaks …just for the reason have no ideas about alternatives. The complete XML world is a parallel universe on its own…to some degree academic brainfuck
@zopyx the amount of ignorance you're showing in your responses is almost amusing.
@oblomov thatā€˜s why I created https://github.com/zopyx/XCut/
GitHub - zopyx/XCut: a new XML transformation language

a new XML transformation language . Contribute to zopyx/XCut development by creating an account on GitHub.

GitHub
@zopyx you mean because you didn't know about XQuery?

@mia the personal indie web is still very much there! I suspect it never went away, we collectively just got used to social media feeds and forgot how to surf. There are some large communities, the socialising and social learning is happening too.

Do you mean though, that the learning for these is so far removed from the industrial/professional web practises, that building for yourself doesn't get people up to starter job level any more?

@sarajw oh I phrased that very carefully. :)

I know people studying HTML/CSS purely as an art form, fucking rad! That was intended as The Point of my post, against arguments that the web is toooo complicated for it now.

I think instead, we've lost discoverability. I'm not sure the same pipeline into & through it still exists? Or I expect it's much harder to fall into – less opportunities for play built into the walled gardens. Less chance to 'customize myspace' etc?

@mia aaaahhh. Mmm. True.

Though one reason people were tired of MySpace was some of the garish customisation happening - facebook and twitter seemed so clean and simple - and that was the end of that.

I think the likes of Neocities is great, but people have to discover it exists - by word of mouth I guess.

Back in the day you'd get online with your ISP, and they'd give you a little tutorial to set up your provided email, newsgroup access and little bit of hosted webspace. That's gone too.

@sarajw @mia
2000-2005 for local small businesses in London, UK to control their computer & web destiny, installed windoze NT &
1. set up POP3+SMTP mailbox server+clients
2. setup local, staff restricted intranet webserver
3. FTP+CMS for local intranet & external websites.

Since 2010 ā€œSaaS-opolisā€ mainframe brainwash, computers are no longer ā€œseen or usedā€ as general purpose compute tool. Rather, only opinionated commercial endpoint for extracting money from ā€œconsumerā€ audience.

@sarajw @mia

For real. My first ISP was my college. I got a public web folder with FTP and Telnet access, and a dial-up number. I built my first web site using the editor that was built into my browser (Netscape Composer). It was right there - I didn't have to go looking for it.

But, to be real, even then it was a pretty nerdy thing to do, to have a personal web site :) Most of my friends didn't.

@mia
That's how I still do create we!sites.
I never learned JS, PHP or whatever other programming language.

Unfortunately, it wouldn't earn me a job, nowadays (currently unemployed).

Some days ago, I asked, if there would be interest in creating "web 1.0"-websites for customers today šŸ˜†

See, if curious, they are from around 20 years back (thanks to the wayback machine):

https://fe.disroot.org/notice/B53ecOoKj1nUXhI2nQ
flo (@[email protected])

Sagt mal: Besteht heutzutage noch Bedarf an "einfachen Web-1.0-Websites"? Handgeschriebenes HTML (selbstverstƤndlich ohne den Einsatz von "KI"), garniert mit modernen Styling-Features (CSS)? Hi...