Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My stack is HTML+CSS

blog.steren.fr

Post reply on HN
Print view View original

121–130 of 194 posts

Re: My stack is HTML+CSS

#121

Post by dubcanada »

Ya well my stack is just HTML, who even needs CSS. It has everything yours has with the benefit is having a single file.

Why just HTML you ask? Well all the reasons that they provided plus the fact it's only HTML files.

This whole stack argument is silly, just let people use what ever they want to use. If someone wants to use a giant complex webpack setup, that's perfectly fine. Sure there is obvious downfalls and longer term maintenance can be a hassle, but it's what they enjoy.

If you want to use just HTML and CSS, go for it, but why are we bragging?

Re: My stack is HTML+CSS

#122

Post by forgotmypw17 »

lazyjeff wrote: post #90
411111111111111 wrote: post #71

Earlier quoted context omitted.

To be fair, static site generators are a thing and are very much underused in cooperations. He could have the same scores/performance and still get the full advantages you mentioned. But yes, handcrafting html is pointless at some point, especially if you have to update the contents every so often

A static site generator requires a toolchain, being platform-aware, updating dependencies, etc. Sometimes I think of these things as labor for a new employee (if you need to onboard a new maintainer) on a new system (if you need to switch hosts or upgrade the disk/OS). It's probably about 2-4 hours for an experienced developer to figure out how to setup and maintain a static site generator assuming no unexpected prob…

A static site generator requires the cat command.

I don't see how you can call yourself "lazyjeff" when you've just written this, tbh.

Re: My stack is HTML+CSS

#123

Post by progval »

Evidlo wrote: post #93

Why can't HTML some kind of templating system, or even simple includes? Then I wouldn't need to use a static generator and could just author HTML directly. e.g. (with hypothetical and tags) template.html My Fancy Blog index.html Hello world Maybe this would compromise browser performance or add some kind of vulnerability, but authoring DRY HTML directly is my fantasy

> Why can't HTML some kind of templating system, or even simple includes?

XHTML does, it's XSLT.

For example:

    
    
    
        Page Title
        
            
                
Hello world
With this in stylesheet.xsl:

    
    

        
            
                
                    
                
                
                    My Fancy Blog
And it's supported by all major browsers. Probably even IE6.

Re: My stack is HTML+CSS

#124

Post by forgotmypw17 »

dceddia wrote: post #16

While I really like the idea of serving raw HTML and CSS, I think that on the authoring side, a static site generator that ingests Markdown and generates HTML is a more practical way to go. I think writing raw HTML can work fine for small pages, and arguably it can be better than Markdown for pages with a lot of design elements, like landing pages. But for the typical blog post, or especially if the blog post has cod…

I don't like Markdown, because it too often takes what I meant and changes it to what I think I meant.

I'm OK with ambiguity between implementations, but this one is a deal-breaker for me, and I've not encountered a Markdown implementation which doesn't do it.

I think it's just a faulty idea to begin with.

Re: My stack is HTML+CSS

#125

Post by marc_abonce »

protonimitate wrote: post #12

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"?

Well, this is a motherfucking website without the swearing, so I guess it could be useful to people that would be offended by that? Although, to be fair, the intersection of people that would switch to raw HTML but are offended by swearing is nonexistent as far as I know...

Re: My stack is HTML+CSS

#126

Post by umaar »

leerob wrote: post #28
dceddia wrote: post #27

Earlier quoted context omitted.

Oh boy, YouTube embeds! I went through checking the Lighthouse score on a few of my pages a while back, and the ones that had videos were performing pretty badly. It turned out that embedded YouTube videos were pulling down something like 1mb of JS, just to show the thumbnail , before the user even clicked Play. I ended up making a static thumbnail with a hover-over "play" icon that would replace itself with the real…

Twitter embeds are equally bad. Ended up remaking them to output static HTML + CSS to improve perf ( https://leerob.io/tweets ).

Same, I get ~500 tweets displayed with:

- No JavaScript necessary

- All profile images turned into one massive sprite

- Minimal payload size

Here are what the tweets look like when rendered: https://umaar.com/dev-tips/feedback

Here's the code to achieve that: https://github.com/umaar/better-twitter-embed

Re: My stack is HTML+CSS

#127

Post by pastjean »

tomc1985 wrote: post #67
Rauchg wrote: post #21

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…

Back in the day you sized your image for the web, there was no need for dimensions in img tags > For example, vanilla ` ` will ship the same image to every device, As it should be, for simplicity's sake. Designers trying to assert pixel-perfect control of layout is part of why the web sucks so much today. Let the browser handle layout, that is one of the things it is designed to do!

Well on my low latency nordic cellphone connection, it's always nice to receive a lower resolution image. Especially if I don't have the resolution to display it

Re: My stack is HTML+CSS

#128

Post by deckard1 »

tannhaeuser wrote: post #48
greggturkington wrote: post #25

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…

no one that lived through the SGML/XML days would describe it as anything close to "simple." That's why the world has developed countless ways to get away from it all... JSON, yaml, markdown, etc. etc.

The world prefers ad hoc rather than formal and verified. Worse-is-better strikes again.

Which is ironic now that we have garbage like GraphQL and TypeScript moving us back to formalism, but built on top of dynamic ad hoc structures. Guys... this... this is bloody fucking ridiculous. It's like trying to build a house out of wet tissue paper.

Re: My stack is HTML+CSS

#130

Post by progval »

Wowfunhappy wrote: post #105

The one thing I really feel like I'm missing out on, in my own no-build-system Github Pages site, is an RSS feed. A couple of people have emailed me asking if there's a way to be notified if I make a new post, but I don't see how I can do it without bringing in an external service.

What about your commits' RSS feed; assuming most of your commits are only to add a page?
Post reply on HN