[tgb]

So how embarrassed should I be for using Vue for small, static websites? I made a results page for some data my colleagues and I processed and there’sa bunch of categories. So there’s a selector and you pick one and Vue updates the page to show the data for that. It’s deployed to GitHub pages and the data is static so no server needed. I could have made it server side rendered and done all 500 different pages ahead of time and gotten faster load times and supported JS disabled browsing. But Vue is what I knew so I didn’t. I’m not a web developer, I just wanted to make a site. So have I sold my soul?

[grayrest]

If you solved your problem then it's not a big deal. The web isn't that old and has been in constant churn. The signal for a shift in what's popular starts with articles like this one or the two dozen others I've seen with this same take. Over the next two years or so the zeitgeist will move into competing solutions, one will "win" and that'll propagate to later adopters as the new norm. At least that's how it's worked for *SP, Rails, jQuery, Backbone, and React. The current era has been unusually long/stable so it's likely that younger developers haven't run into the situation.

If you do want to jump on the trend while keeping your Vue knowledge, check out Astro [1]. I'm provisionally in the Marko [2] camp, not so much for the current Marko but because Marko 6 is looking good.

[1] https://astro.build/ [2] https://markojs.com/

[CharlesW]

> So how embarrassed should I be for using Vue for small, static websites?

Not at all, and don't let anyone tell you differently.

[dgb23]

That seems like a fantastic use case for DIHYW (do it however you want).

[MaxBarraclough]

Using Vue is a long way from selling your soul -- if you want to make a bloated monstrosity of a website, you have to do far more than just use Vue.

That said I think it's a pity if a static website doesn't work at all without JavaScript.