41–50 of 194 posts
I swear this same exact post gets re-dressed and upvoted weekly. Is there anything worth discussing here? The entire thesis of the post is "my blog is maintenance free". Ok, and? Is blog maintenance really a noteworthy topic? How many times can blogs rephrase "use the right tool for the job"?
This is an inaccurate over-simplification. If you just use HTML and CSS, you can also have really bad Lighthouse scores. For example, vanilla ` ` will ship the same image to every device, regardless of viewport size. Vanilla ` ` doesn't enforce setting `width` and `height`, which makes your layouts shift. Slow-loading images and layout shifts are the very things that will downgrade the "100" score he's currently prou…
https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimed...
Version everything in your Gemfile, use rbenv, and and you're set.
This is an inaccurate over-simplification. If you just use HTML and CSS, you can also have really bad Lighthouse scores. For example, vanilla ` ` will ship the same image to every device, regardless of viewport size. Vanilla ` ` doesn't enforce setting `width` and `height`, which makes your layouts shift. Slow-loading images and layout shifts are the very things that will downgrade the "100" score he's currently prou…
(I'm doing this all the time, also with perfect Lighthouse scores. That is, there's often also a bit of PHP involved for includes and setting some meta tags, and a bit of non-essential JS sprinkled in.)
This is an inaccurate over-simplification. If you just use HTML and CSS, you can also have really bad Lighthouse scores. For example, vanilla ` ` will ship the same image to every device, regardless of viewport size. Vanilla ` ` doesn't enforce setting `width` and `height`, which makes your layouts shift. Slow-loading images and layout shifts are the very things that will downgrade the "100" score he's currently prou…
You can have responsive images with vanilla [0]. You can even lazy load images with just `loading="lazy"` attribute[1]. I'm pretty sure I can optimize more things.
I'm mostly agree with this blog post. Plain HTML+CSS is really good for simple webpages, like landing page or portfolio that requires less update. But for a blog with pagination? I don't think so. Imagine updating each page in plain HTML. SSG can help my life easier.
[0] https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimed...
Very much like saying, “my vehicle will outlive yours. No, it doesn’t have wheels or axles, because my vehicle is the human legs.”
- Werner Herzog
Writing HTML and CSS by hand?! Those are just the output. OOTB Wordpress didn't have a perfect Lighthouse score, so it's worthless? > I didn’t need 99% of its features anyway Oh, then it was already a terrible fit. So why are you advising people on how to replace Wordpress?
You know, HTML is rooted in SGML and digital humanism. The entire point of it is that you use it as a simple means for self-publishing of digital text (and HTML 5 "standards" portray it in that role, in case you've never had a look).
Granted, that isn't quite apparent when looking at the trainwreck that is HTML/CSS/JS. The solution (with SGML at least) is that you use your own custom markup vocabulary, including custom Wiki syntax for markdown and other short form syntax, and then convert that into result markup for delivery. The idea being that nothing can be as lasting for your specific purpose than your own text format.
But the self-proclaimed web heads didn't get it. They made CSS so absurdly powerful and "meta" to cater for the historic shortcomings of HTML, which is just a format for casual academic publishing locked in 1991. Not considering that you can, in fact, define your own elements and meta rules. Or at least, I don't have another explanation for the fact that everything around HTML has to change ad absurdum while HTML has to stay the same while it quite obviously isn't a good fit for the vast majority of content on the web. And that for some reason you absolutely have to send the same HTML to your mobile that you send to your desktop, and that CSS absolutely has to be the place to shift, re-layout and hide content for these different purposes.
This is an inaccurate over-simplification. If you just use HTML and CSS, you can also have really bad Lighthouse scores. For example, vanilla ` ` will ship the same image to every device, regardless of viewport size. Vanilla ` ` doesn't enforce setting `width` and `height`, which makes your layouts shift. Slow-loading images and layout shifts are the very things that will downgrade the "100" score he's currently prou…
> Vanilla ` ` will ship the same image to every device, regardless of viewport size. You can have responsive images with vanilla [0]. You can even lazy load images with just `loading="lazy"` attribute[1]. I'm pretty sure I can optimize more things. I'm mostly agree with this blog post. Plain HTML+CSS is really good for simple webpages, like landing page or portfolio that requires less update. But for a blog with pagi…
This is where frameworks can be really helpful, and I wouldn't dismiss them. It gets quite tedious to keep up with the new attributes, cross-browser and cross-platform differences, image optimization CDNs and so on :)
Writing HTML and CSS by hand?! Those are just the output. OOTB Wordpress didn't have a perfect Lighthouse score, so it's worthless? > I didn’t need 99% of its features anyway Oh, then it was already a terrible fit. So why are you advising people on how to replace Wordpress?
> How could you possibly consider writing HTML and CSS by hand? Those are just the output. You know, HTML is rooted in SGML and digital humanism. The entire point of it is that you use it as a simple means for self-publishing of digital text (and HTML 5 "standards" portray it in that role, in case you've never had a look). Granted, that isn't quite apparent when looking at the trainwreck that is HTML/CSS/JS. The solu…