Plain Vanilla Web • Hacker News Board

Re: Plain Vanilla Web

#711

Post by 6P58r3MXJSLi » Mon, May 19, 2025, 8:37 AM UTC

cheikhcheikh wrote: post #703

6P58r3MXJSLi wrote: post #693

Earlier quoted context omitted.

> unhinged while wanting to monitor what the delivery guy does while doing his job and pretending to "help" him because you truly believe that having tipped a couple dollars makes him your butler, that's completely normal... alright... There’s a reason why everyone hates the USA right now — one major reason is that, unlike in much of the world, you truly believe that workers don’t have rights.

honestly wtf are you talking about. What is these insane leaps and projections you're making?? how did you go from having a map that shows you where the driver is to "makes him your butler" and "micromanaging" and "workers don't have rights".

> how did you go from having a map that shows you where the driver is to "makes him your butler" and "micromanaging" and "workers don't have rights".

I sometimes forget that HN is mostly US people, unaware that there is a World out there.

It's illegal or challenged in courts in many developed countries, that are actually developed.

> showing a driver's location on maps in apps like Glovo or Uber can potentially infringe on workers' rights in Europe, particularly under EU labor and data protection regulations. In Europe, the legal status of gig economy workers on these platforms has been a contentious issue. Several European courts and regulatory bodies have made rulings that impact how these companies can monitor and track their drivers.

> the practice of constant monitoring of delivery drivers by app users (where customers can track drivers' real-time location) has been challenged in several European contexts

ELI5 for you: would you accept a webcam pointed at you that your client (or your employer's clients) can constantly watch, to see if your doing you job the way they want you to do it?

For example, would you accept that a McDonald's customer could monitor how their burger is being made and could give instructions to the people working there, by the sheer overwhelming power of having bought a burger?

And why not?

Re: Plain Vanilla Web

#712

Post by tomhow » Mon, May 19, 2025, 1:20 PM UTC

mikebelanger wrote: post #80

90s_dev wrote: post #24

Earlier quoted context omitted.

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.

You can invoke custom methods and pass in any kind of data into them. As in class SomeElement extends HTMLElement { constructor() { super(); } someMethod(x) { this.innerHTML = ` ${x} `; } } // ignore registry stuff const customElement = document.getElementById('custom-element-id'); customElement.someMethod(42); But you won't learn that from most mainstream custom element tutorials though, for whatever reason.

I'm late getting to this but someone emailed us to point out that your attempt at code formatting didn't quite work, so I fixed it, using the formatting markup documented here: https://news.ycombinator.com/formatdoc. Hope that's OK!

Re: Plain Vanilla Web

#713

Post by mmcnl » Wed, May 21, 2025, 8:55 PM UTC

evantbyrne wrote: post #72

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 should really only be kept at rest in the backend, form elements, and the occasional variable. SPA state management is fun to puzzle around with, but gives developers the false impression of productivity and is totally redundant to the browser's built-in capabilities for shuttling data back and forth to a server.

Is UI state really a backend concern? I think this is a nice theory but anyone who has built a sizeable SPA (web application, not website), knows you'll be dealing with UI state complexity very soon.

Re: Plain Vanilla Web

#714

Post by mmcnl » Wed, May 21, 2025, 8:58 PM UTC

mbrumlow wrote: post #60

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…

The solution to not using a framework is... building your own framework? What problem does that solve?

Re: Plain Vanilla Web

#715

Post by sswatson » Fri, May 23, 2025, 1:56 PM UTC

6P58r3MXJSLi wrote: post #619

bondarchuk wrote: post #551

Earlier quoted context omitted.

You want pizza or not?

I also want to be paid when I work.

The idea is thoroughly absurd. Our days are filled with unpaid labor. Getting dressed in the morning, collecting the items you want to buy in a grocery store, making your bookings for a vacation, giving your spouse feedback on their wardrobe selection, etc. — all of these things are work.

If you want to argue that they are not work, then surely helping a delivery person who's lost in your neighborhood also counts as non-work for the same reason.