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 This is the way to go.. again!
We have made development so complicated with all kinds of frameworks, libraries, managing tools and other cruft, it's ridiculous. Tools don't guarantee the outcome.
I have been doing webdev for 15+ years now. Simple(r) always wins. I am back to CSS only. Being able to move things between pc's and continue coding. No extra tools, processors etc. It's a great workflow.. 'post-framework'? Sure, name it that.
Is this little thing I made a post-framework too?
I don't know, but it tries to be post-React at least.
@haitchfive @jwildeboer I'm not familiar with Go.
This 'post-framework' (which eq 'pre-framework') idea:
- Write HTML by hand
Done!
Additionally:
- Template parts, sections for ease and maintainability (might need a server something)
So, HTML, a (template) parser. How we use to do it, how we build thing internet-thing, how we will be doing it.
https://www.youtube.com/watch?v=qUiEoFRLlno&pp=ygUTZGhoIGxlc3MgZnJhbWV3b3Jrcw%3D%3D
Sure, some cases excempt.. Point is, we need very little to build the web. Less == better.
Uhhhg...DHH, no thank you...
See, this is how division plays out. Even though I get it, I was point you to the signal, not the container. Life gets easier, and your improvements faster if you mold life your way.
Listening to someone who doesn't hold your views, isn't letting yours go. Again, I am point to signal, not politics. What weighs heavier for you is your decission.
Jan Wildeboer 😷
codebuzz 🐧
@haitchfive