I still like bootstrap so I'm happy it's being modernized.

The main issue with Bootstrap was that a lot of sites used it with the default theme, but it's highly customizable so you can apply your own styling and brand colours to it to make it unique.

Shadcn has the same issue today - a lot of people just use its default styling, so often you can instantly tell a site is using it.

Nice job!

Please don't ever put this in a page I have to visit

Star wipe

It looks fun.

Glad that the JPEG XL is getting more support. Google already squandered its chance to take a principled stand when it dropped JPEG XL in favor of WebP.

Finally

No idea why game engines hate SVG. Last time I was "manually" parsing svgs and then drawing them with lines through engine functions. I hope SVG2 will be BETTER, not just with even more crazy things C++ standard style.

Thanks. That makes sense and settles pretty much all my concerns.

I'll be using garage then.

I do not think so. You only need to provide the source code if you modify it.

Stop making tool tips, that's the answer.

God I hate things that popup when I didn't ask, just because I let my mouse hang out in one spot 0.002 seconds too long.

Would there be a conflict since my website is meant as for profit and not open source (if using garage)?

the grand unifying architecture of the fronted is either wrapping a 40x inside a 200; or for everything.

^/s^

Edit: But on a serious note, yes that's how I have always simplified webdev for myself. I have been reluctant to enter the js ecosystem only dipping my toes into react frontend as recently as two months ago.

My goto backend is python + flask. Naturally I started with jinja templates for the frontend. I have now gravitated away from fully relying on templates into having a partially REST API with JSON payloads and asynchronous requests. This is nicely fits with the three layering transformation that this blog endorses and is optimal from a manageability perspective.

Ceph and GarageHQ due to redundancy. Use ceph object storage if you already use Ceph. Otherwise Garage is the most versatile.

curl -fsSL https://vite.plus/ | bash

nooo can we stop doing that

Yes. It does also contain the migration prompt, but also information on migrating yourself. Haven't used it myself, so YMMV: https://viteplus.dev/guide/migrate

Laggiest website I have used on my phone.

Can I get linting and formatting on a whole Vue single file component yet?

Is there a migration guide that isn’t “paste this AI prompt”?

Damn, that's so refreshing to see. I have zero use case for it, but damn does that make me wish I did lol

We initially considered a paid license for companies when we announced Vite+. We decided that Vite+ can only achieve our mission of making JavaScript developers more productive than ever before when it is truly free and open source. We got tired of debating which features should be paid and how they should be gated, as this only creates friction in the workflows our open-source users already enjoy and love. Feedback from the community helped us reinforce our conviction. Therefore, we decided to fully open source Vite+ under the MIT license.

Source: https://voidzero.dev/posts/announcing-vite-plus-alpha#mit-license

Wasn't Vite+ supposed to be a paid product or I missed something?

i read the first paragraph

in the age of AI and agentic development

React won

not really worth reading further.

Regarding the interview layout, I do always like it when web design elements are used in articles themselves. We often treat articles just as rich text, even though we have this arsenal of HTML+JS+CSS underneath.

Interactive visualizations can be really valuable for explaining concepts, see e.g.:

• https://meltingasphalt.com/interactive/going-critical/
• https://www.redblobgames.com/pathfinding/tower-defense/

But I've also been really wanting something like <map/>, just less of a pain in the butt.
For example, at some point, I put together this overview of how logging works in your typical application:

It's a fairly self-explanatory picture (assuming some programming experience), but if you're not sure what a 'producer' is, then I'd like you to be able to click on the box to get an explanation.
Instead, I have a bunch of prose underneath the picture, as if I was presenting it at a science fair. 🫠

That's how the old web worked. The old web was accessed on 14.4kbps to 56.6kbps connections, so it made sense to do that.

Today's web is accessed on 200mbps to 1000mbps. Today, it makes more sense for webdevs to just code better and make their sites not suck.

Can we stop with the wired article? Not a lot of quality is coming from them for a long time.