TIL (Today I learned) that writing websites with simple HTML and CSS is now called "post-framework". Well. I did "post-framework" even before frameworks existed and I never stopped writing that little bit of HTML and CSS needed for static pages myself. I guess I'm so old that it is considered being young again :) (frantically adding "20+ years of experience and practice with post-framework web design" to my CV ;)
1/4
@jwildeboer @neuimneuland at one point in my JavaScript journey frameworks (they weren't called that yet) were getting popular, particularly jQuery. I shied away from them because it seemed like a huge amount of library to load just for relatively simple stuff, and the extra dependency didn't seem worth it. Plus, the idea that I'd sink time into learning something that would perhaps quickly become obsolete wasn't appealing, when using the standardized APIs was not much harder and helped keep me honest about HTML element complexity and design.
document.querySelectorAll is pretty great actually!
So now I guess I'm also a post-framework veteran? Ha.
@tiotasram @jwildeboer @neuimneuland someone I worked with once called me a vanillaJS fangirl 😂 made my day
I feel like "kids these days" dont know just how far vanilla HTML, CSS, and a lil js script can take you.
And that’s true when there’s so little vanilla you can barely see it!
Yeah. I guess that's the main point here. HTML (+CSS+JS) was designed as primary user written language. To be extended whenever new features are needed (like it right at the start by addition of htbin, later CGI).
What developers did was treating it rather like some immutable low level ISA one needs to build on - with explicite forcing of features, not trusting standard implementation or user intend.
A long sad story.
@fay @jwildeboer @neuimneuland
Which makes Frameworks like passports and border controll? Invented during war, never went away afterwards?
Jan Wildeboer 😷
Karma Sahne - R.I.P @natenom
Tiota Sram
Ornella 🍉
clew
Raffzahn
morgan
Stijn van Drongelen