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

Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

news.ycombinator.com

Post reply on HN
Print view View original

71–80 of 136 posts

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#71

Post by steve_adams_86 »

ramesh31 wrote: post #63
hactually wrote: post #57

Earlier quoted context omitted.

Did react win? Or did it become the foundation for Next.js? We're using Vue here and missed the memo about it being an also run :)

>We're using Vue here and missed the memo about it being an also run :) I don't hate Vue and I wouldn't judge anyone for choosing it, but my question is... why? It just seems like that entire community is set on reinventing every React feature with a two year delay.

Isn't Vue quite a bit different? It's more of a framework than React is, with official packages for routing, state management, testing, SSR, SSG, building... It also uses a reactive data model, whereas React doesn't (though in practice it appears to).

Vue was also ahead of React on some of the features they share if I'm not mistaken.

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#72

Post by dylan604 »

steve_adams_86 wrote: post #70
dylan604 wrote: post #41

Earlier quoted context omitted.

AI generated crypto funded JS framework written in Rust

> JS framework written in Rust This isn't far from reality these days

That's what makes jokes/conspiracies/lies/memes so compelling. Not that my comment was any of the above including compelling

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#73

Post by fomine3 »

v3ss0n wrote: post #53
steve_taylor wrote: post #36

Earlier quoted context omitted.

> not mature Svelte was first released in 2016 and has become bigger than its original creator, Rich Harris. It has quite a thriving ecosystem and a big community. The tooling around it is more mature than React's has ever been. > surface is so small I actually find the opposite to be true. React still has a relatively small API surface area. One-way data flow makes it easier to understand. However, a smaller surface…

This is wrong in so many levels. You need to learn useState,useEffects in react. You only need to learn how to put {varName} in svelte.

useState and useEffect are quite simple small elegant API. It does not mean it's very easy to use for newbie. Maybe like Lisp?

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#74

Post by darepublic »

square_usual wrote: post #24
gejose wrote: post #18

Earlier quoted context omitted.

> I have seen many, many sites switch to Next and completely bungle it, making the user experience worse than it was before the change. What are some specific sites you've seen that adopted react and ended up worse as a result of it? > doesn't have a "relatively small surface" any more, because even the React team doesn't recommend that you use "just" React Isn't this evidence of it having a relatively small surface…

> Isn't this evidence of it having a relatively small surface area that frameworks and other tools can build on top of, much like html, css etc? No? You can build on top of a large surface area, too? Of course, the funny thing is, even if you are right and React has a "relatively small surface area" (relative being the operative word,) what good is it when the creators of the framework say that you shouldn't use that…

Another example is new reddit

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#75

Post by scotty79 »

v3ss0n wrote: post #53
steve_taylor wrote: post #36

Earlier quoted context omitted.

> not mature Svelte was first released in 2016 and has become bigger than its original creator, Rich Harris. It has quite a thriving ecosystem and a big community. The tooling around it is more mature than React's has ever been. > surface is so small I actually find the opposite to be true. React still has a relatively small API surface area. One-way data flow makes it easier to understand. However, a smaller surface…

This is wrong in so many levels. You need to learn useState,useEffects in react. You only need to learn how to put {varName} in svelte.

You don't need to learn useEffect until you need to plug arbitrary js libs and components into react. That's the intended use of useEffect. Using it for anything else is usually a bad idea.

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#76

Post by scotty79 »

karaterobot wrote: post #50
simonsarris wrote: post #13

Earlier quoted context omitted.

haha, I basically feel this way about Svelte/Kit. It's not mature, but the surface is so small and learning curve so pleasant that it's our go to choice now for internal webapps. (We have no external webapps because my company, funny enough, builds a JavaScript framework!)

I'm not a web dev anymore, I stopped right around the time hooks became a thing in React, and while Svelte was an exciting technology no big players had adopted yet. In fact the last thing I did for my old job was a little make-work exploration to test whether Svelte was was ready for them to use in prime time. My conclusion was that it was remarkably slick and empowering, but was not ready yet due to the lack of eco…

How's Svelte different from AngularJS 1? I have such bad memories that I refuse to touch any code-in-html framework with a 10 foot pole.

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#77

Post by mmusc »

ramesh31 wrote: post #63
hactually wrote: post #57

Earlier quoted context omitted.

Did react win? Or did it become the foundation for Next.js? We're using Vue here and missed the memo about it being an also run :)

>We're using Vue here and missed the memo about it being an also run :) I don't hate Vue and I wouldn't judge anyone for choosing it, but my question is... why? It just seems like that entire community is set on reinventing every React feature with a two year delay.

The Dev experience and documentation is way better

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#78

Post by revskill »

scotty79 wrote: post #75
v3ss0n wrote: post #53

Earlier quoted context omitted.

This is wrong in so many levels. You need to learn useState,useEffects in react. You only need to learn how to put {varName} in svelte.

You don't need to learn useEffect until you need to plug arbitrary js libs and components into react. That's the intended use of useEffect. Using it for anything else is usually a bad idea.

How can you "fetch something when your state change ?". It's the main use case for useEffect.

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#79

Post by EspressoGPT »

dimal wrote: post #46
duluca wrote: post #38

IMO a JavaScript revolution is quietly brewing. Today’s frameworks have gotten amazingly complicated and EcmaScript spec is gaining new capabilities at a rapid clip, so some of critical features for modern web dev is built in. This project is a great example of what’s coming https://www.arrow-js.com . I think the right move will become avoiding these large and complicated frameworks unless they’re truly called for.

I’m starting to feel the same way. React’s big selling point when it came out was that it was “easy to reason about”, and that was true at the time. With hooks, server components, and 10,000 different strategies for managing state and side effects, I can’t say React is easy to reason about anymore. We can do things now that were impossible back then, but now we need to do even more than that, and it feels like it’s t…

Yes. Frontend development has always has been a pendulum swinging between "heavy server, lightweight client" and "lightweight server, heavy client". React brought us to the heavy-client side of things and I think the pendulum is about to swing back.

Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?

#80

Post by [deleted] »

revskill wrote: post #78
scotty79 wrote: post #75

Earlier quoted context omitted.

You don't need to learn useEffect until you need to plug arbitrary js libs and components into react. That's the intended use of useEffect. Using it for anything else is usually a bad idea.

How can you "fetch something when your state change ?". It's the main use case for useEffect.

[deleted]
Post reply on HN