I just got a new job, hired as level 5 with official title Software Engineer (Mid-career) although my boss tells me I'm Chief Engineer. All the level 2 people on my team seem to be Senior Engineer or Lead Engineer.
> If you really think "the whole moon thing is pointless" NASA is pointless.
There's more to NASA than Artemis! NASA's robotic spaceflight programs generate extremely high science return at relatively low cost. Missions like Psyche, Europa Clipper, and Dragonfly are humanity's real explorers.
And their aeronautics work is valuable as well. Low-boom, etc.
I skimmed this. I use web components a lot. Unless I'm mistaken, they don't provide reactivity; you have to write that yourself. Reactivity was the feature that launched modern js frameworks so I think the article really overstates the case.
The article also misses something more important: broad native ES module support in browsers means you don't need a build step (webpack).
The "AI makes it easy!" part of the article makes me want to hurl as usual. And I'll stop short of an accusation but I will say there were some suspicious em dash comparison clauses in there.
Yes. You can tell the author either doesn't have experience using web components in a non trivial page, or they are intentionally hiding the complexity. Realistically, you don't want to make pure web components. You want to use a framework to build it for you.
Put it another way, you can make a page out of web components without using a framework, but you are not going to convert a React page with that approach.
> they don't provide reactivity; you have to write that yourself. Reactivity was the feature that launched modern js frameworks so I think the article really overstates the case.
This is the truth that a lot of web component advocates gloss over on purpose. They know this, just like they know that there's no decent templating solution either as tagged template literals still need escaping. Then there is efficient DOM updates, etc. (aside, I got Claude to write a web component recently, and it's code had every single keystroke assigning the same class to the element)
There are many features like this, and when you finally get them to admit it, they just say "write your own"!. Well guess what, frameworks already provide all of this.
The really funny part is that Stencil, one of the popular tools for writing web components actually does provide all of the above! Their web components have exactly the same type of features you'd expect in any other framework *because it IS a framework*.
Which again highlights how stupid the discourse is here. It's not "independence" of frameworks, your components will still depend on a framework of some kind, be that Stencil or Lit or whichever thing YouTube uses now or your own supporting code to get back even half the features you get elsewhere.
It all starts to make sense when you realise that the Chrome developers hated frameworks because they didn't understand them, pushed for web components, not realising frameworks dealt with all of the above.
https://youtu.be/UrS61kn4gKI?t=1921 32:00 (but the whole video is valuable and I wish everyone on both sides of this debate would watch the whole thing).
I think the only thing I like about web components is they scope "this" to the element it owns.
Not that votes matter on HN, but I do find it typical of the type of discourse around Web Components I dislike. My comment had +3, now it has 0. It seems no one is able to admit WC's have big problems.
On the inside, but not on the outside. Web Components standardize the interface for components to interact like MCP standardized the protocol but the server itself can be in and language. You can't just mix Solid, React and Vue components together but you can use any web component in a Lit app.
This has never been the case. Custom elements are DOM Elements and so are just JavaScript objects. Just like you can do aEl.disabled = true, you can set any prop to any type of value.
For the millionth time, would it kill ya to spell out the abbreviation the first time you use it? My googling suggests we're talking about https://en.wikipedia.org/wiki/Objectives_and_key_results , but my googling isn't always right.
I think fantastical isn’t totally inaccurate, and I’m not being snarky (for once). The personal observations and sometimes colorful language has been something I like about Ars. Benj in particular, with his warm tributes to BBSes. Or Jim Salter’s very human networking articles. The best stuff on Ars is both technically sound and rich with human experience. “Fantastical” taken to mean something like, capturing the thrills and aspirations that emerge from our contact with technology, seems fair I think.
I’ll be interested in finding out more about just what the hell happened here. I hardly think of Benj or Kyle as AI cowboy hacks, something doesn’t add up
It has a second definition which means something like "unbelievable in its strangeness/perfection", which can be used to imply that a real thing feels made up.
I agree that it's not a good word choice when describing a thing that could actually be fake, but you could describe a view from a mountain as fantastical even though it was 100% real.
I confess I find the growing prevalence of these sorts of errors on HN dispiriting. Programming requires precision in code; I’d argue software engineering requires precision in language, because it involves communicating effectively with people.
In any single instance I don’t get very exercised - we tend to be able to infer what someone means. But the sheer volume of these malapropisms tells me people are losing their grip on our primary form of communication.
Proper dictionaries should be bundled free with smartphones. Apple even has some sort of license as you can pull up definitions via context menus. But a standalone dictionary app you must obtain on your own. (I have but most people will not.)
Jesus christ man, you are pulling out a lot from a single typo, eh?
English is just not my first language (and not the last either). Having an accent or the occasional misspelling on some forum has never impacted me professionally.
Slow down. If you read my comment it’s about an aggregate trend, not you or even your comment, which I don’t mention. Plenty of native speakers are slipping. (Fwiw the quality of your writing is pretty native feeling, so good work)
Oh, it's a mostly nonsense (IMO) document that a design contractor did for a new Pepsi logo. I don't really know much about it but it gets posted on HN frequently when someone makes fun of designers. I dunno if it leaked or what, but here's a reddit thread about it: https://www.reddit.com/r/Design/comments/hspqgd/pepsi_logo_r... . I'd bet the GP post of this had their opinion formed at least in part by this document.
reply