Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
b_e_n_t_o_n
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
61.
▲
by
b_e_n_t_o_n
1y ago
Yeah, but when it's used in conjunction with js frameworks it ends up being more complicated than pure SPA or SSR.
62.
▲
by
b_e_n_t_o_n
1y ago
Especially since they put effort into making it backward compatible. You can mix Svelte 4 components with Svelte 5 components. Which is pretty reasonable.
63.
▲
by
b_e_n_t_o_n
1y ago
It does everything at runtime, Svelte compiles declarative code into imperative code via static analysis.
64.
▲
by
b_e_n_t_o_n
1y ago
React also uses a declarative model, in fact React might be more declarative because it's still declarative at runtime, whereas Svelte et al. do a lot of static analysis to turn declarative UI into imperative targeted dom updates.
65.
▲
by
b_e_n_t_o_n
1y ago
Hmmm, it's kind of complicated. A lot of the innovation in JS frameworks has been at the meta framework level, because the client-side framework itself can't really control how data is loaded or how the app is bundled. A lot of wo
66.
▲
by
b_e_n_t_o_n
1y ago
I was being a bit tongue in cheek, I doubt an AI wrote the whole article but it feels a bit off in a way that AI can do.
67.
▲
by
b_e_n_t_o_n
1y ago
It automemoizes objects that would otherwise be recreated on each render, which would then cause rerenders down the tree. By memoizing these objects, they reduce the amount of rerendering done without actually changing the semantics of the
68.
▲
by
b_e_n_t_o_n
1y ago
I think most are still using React with maybe React Router. Node and Pnpm aren't really complicated or difficult to use, neither is Vite.
69.
▲
by
b_e_n_t_o_n
1y ago
Is this AI? How is Blazor a JS framework, let alone a popular one? Also no Solid.js?
70.
▲
by
b_e_n_t_o_n
1y ago
Both jquery and htmx style approaches lack the concept of components, data flow, template binding etc. At most you get string templates. You end up manually wiring up dom updates when state changes, and that kind of thing is brittle and is
71.
▲
by
b_e_n_t_o_n
1y ago
Bundlers will convert let/const to var, assign classes and functions to var etc but generally people don't write it themselves unless they want to (ab)use its semantics for performance reasons.
72.
▲
by
b_e_n_t_o_n
1y ago
It sounds nice in theory but then eventually you wind up needing to implement a feature where you wish you had React et al to implement it. Easier just to start with it from the beginning. Assuming you're a full stack / front end
73.
▲
by
b_e_n_t_o_n
1y ago
Those are part of what I'm talking about re. brittle and hard to maintain. Similar to jquery, just server sideZ
74.
▲
by
b_e_n_t_o_n
1y ago
It's a reference to this: https://news.ycombinator.com/item?id=8863
75.
▲
by
b_e_n_t_o_n
1y ago
This is super nice!
76.
▲
by
b_e_n_t_o_n
1y ago
and rsync works fine for people too, I guess that's why nobody uses Dropbox
77.
▲
by
b_e_n_t_o_n
1y ago
I don't know to what extent that's true compared to the npm ecosystem, but the js ecosystem largely rejects the monolith framework approach. It's focused heavily on frontend / browser, and the most popular JS frameworks
78.
▲
by
b_e_n_t_o_n
1y ago
Ime progressive enhancements are brittle and hard to maintain. If your site doesn't need any JS it's fine, but as soon as it needs some interactivity beyond the absolute basics you benefit from having reusable components and autom
79.
▲
by
b_e_n_t_o_n
1y ago
What if you're building a highly interactive front end?
80.
▲
by
b_e_n_t_o_n
1y ago
JS has multiple full stack frameworks similar to Rails. There is even a framework called Sails... The problems people solve with JS are different from the ones solved with Rails. Which is why the frameworks look different.
81.
▲
by
b_e_n_t_o_n
1y ago
In practice you don't run into these issues often. I'm annoyed when you see different function declaration conventions in the same codebase, but generally () => is used for either one line functions or inline lambdas, and funct
82.
▲
by
b_e_n_t_o_n
1y ago
We tried that last century.
83.
▲
by
b_e_n_t_o_n
1y ago
Oh true.
84.
▲
by
b_e_n_t_o_n
1y ago
No but a monopoly also doesn't mean a majority market share, or being so much better than the competition that everyone chooses you.
85.
▲
by
b_e_n_t_o_n
1y ago
My point is that you don't need half of the things the author thinks you need for a JS frontend with Vite, TS, React, and Tailwind....
86.
▲
by
b_e_n_t_o_n
1y ago
NPM comes with Node. And obviously you need to install node, just like you need to install Ruby....
87.
▲
by
b_e_n_t_o_n
1y ago
If you're gonna rant about the JS ecosystem at least get it right. You can set up a Vite + React + Tailwind setup with two commands npm create vite npm i @tailwindcss/vite tailwindcss If you want automatic code formatt
88.
▲
by
b_e_n_t_o_n
1y ago
Does Microsoft actually have a monopoly on anything these days? Maybe gaming? I saw its like 95% windows on Steam.
89.
▲
by
b_e_n_t_o_n
1y ago
How can the government regulate companies into providing good customer service when they can't even provide good customer service to their citizens?
90.
▲
by
b_e_n_t_o_n
1y ago
You'd be surprised how far white sneakers and some $5 flip flops can take you. Unless you're in a situation where you need a suit, but then you aren't one bagging it anyways...
More ›