81–90 of 136 posts
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.
Earlier quoted context omitted.
I think about this a lot. About how ChatGPT is perhaps cementing a lot incumbent tech right now. I wonder if the existence of these tools might actually slow down advances in frameworks, packages, libraries, etc...
I don't think about it at all. ChatGPT isn't able to actually do anything I actually need to as a software developer. Code is the easy part, getting good requirements from stakeholders and implementing it as business logic that meets the goals of various other internal concerns is the hard part. ChatGPT doesn't know anything about that stuff. Sometimes I wonder if anyone clutching their pearls about LLM stuff being a…
It knows about that stuff just fine.
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.
useState and useEffect are quite simple small elegant API. It does not mean it's very easy to use for newbie. Maybe like Lisp?
Earlier quoted context omitted.
I think about this a lot. About how ChatGPT is perhaps cementing a lot incumbent tech right now. I wonder if the existence of these tools might actually slow down advances in frameworks, packages, libraries, etc...
I don't think about it at all. ChatGPT isn't able to actually do anything I actually need to as a software developer. Code is the easy part, getting good requirements from stakeholders and implementing it as business logic that meets the goals of various other internal concerns is the hard part. ChatGPT doesn't know anything about that stuff. Sometimes I wonder if anyone clutching their pearls about LLM stuff being a…
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.
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!)
> 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…