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

Plain Vanilla Web

plainvanillaweb.com

Post reply on HN
Print view View original

51–60 of 715 posts

Re: Plain Vanilla Web

#51

Post by pelagicAustral »

gjsman-1000 wrote: post #35
pelagicAustral wrote: post #32

Earlier quoted context omitted.

We created a generation of developers that AIM to over-engineer requirements... and we also came up with extremely pervasive frameworks to go with it... My firm cannot hire people with no React experience... people REALLY only know how to build cruft these days...

I have no React, Vue, or Angular experience. My websites were built with Livewire, some HTMX (basically Hotwire in the Rails world, server rendered HTML partials; or maybe Blazor SSR in the .NET world). I use Tailwind and a Laravel backend, but have some experience with C#. If you think that’s interesting, send me your firm’s URL, I’ll consider applying. (Edit: or really anyone reading this who is interested - govern…

my firm is government, so do not expect too much... email to {trafalgar battle british general's last name]@rails.cl

Re: Plain Vanilla Web

#53

Post by reconnecting »

doc_manhat wrote: post #6

Question - why would you do this in current year ? Is it that much more performant? I might be ignorant but frameworks seem to be the lingua franca for a reason - they make your life much easier to manage once set up!

The use of a framework always involves a trade-off between independence, responsibility, and delegation of control.

Re: Plain Vanilla Web

#54

Post by panstromek »

gjsman-1000 wrote: post #29
pelagicAustral wrote: post #14

I work for about 2k users, they do not give a shit about reactivity... build a monolith, make it comfy, embrace page refresh (nobody gives a fuck about that in the real world), and get shit done.

I have seen more broken SPAs than MPAs, by far. Ironic, considering SPAs are supposed to improve conversion rates and user experience. Even from big companies with no excuse - Reddit is almost unusable on phones, X was straight up broken for a month straight with image loading on mobile. If you’re writing an SPA, and it isn’t Twitter or a content consumption platform, and it isn’t necessary to be API-driven, seriousl…

Might be a bit of a selection bias though. I certainly remember a lot of crappy MPAs before SPAs got big. The crappines just moved to SPAs as they became mainstream. Overall I agree that MPAs are better default, though, good SPAs are hard to build.

Re: Plain Vanilla Web

#55

Post by jakelazaroff »

90s_dev wrote: post #24
braden-lk wrote: post #4

Very cool overview and a great article—it’s fascinating to see how far web components have come. Data passing, interactivity, and state management still seem pretty tedious in vanilla, though!

Data passing seems inherently broken in web components, because all HTML attrs must have string keys and values. Such a model just can't be built on top of.

Imagine 50 years ago: “Data passing seems inherently broken in Unix, because all processes must use strings for input and output. Such a model just can't be built on top of.”

Re: Plain Vanilla Web

#58

Post by sn0n »

I missed the part where they show how to do something similar to ejs or PHP HTML includes for things like header.html and footer.html.

Re: Plain Vanilla Web

#60

Post by mbrumlow »

mmcnl wrote: post #44

This guide assumes web components is a viable alternative for frameworks like React or Vue. That's a very superficial assumption. React and Vue render the UI as declarative function of state, with the help of components. That's why we use those frameworks. Web components don't solve the state management problem.

State management, state manage management everybody yells when talking about web dev.

It’s not some sort of mystery, it’s just a global of your variables.

The example given clearly showed components backed by JavaScript. Which means you could implement a state management system in seconds.

But beyond that state management is overrated. I remember when react came out and somebody from face book was describing updating some pending message count number. And how they had trouble with it. The issue was they made shitty code, and the result of react was a solution that hid that shitty code. Because I bet to this day if you profile their example they still had the bug but the state management system silently hid it as a future performance problem.

Post reply on HN