this post was submitted on 08 Sep 2023
57 points (70.2% liked)
Programming
17502 readers
17 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The title makes it seem like it's a wide spread thing in the industry but according to the video it's 3 frameworks.
Yeah, it's additional work but I've found that really convoluted or complex type definitions usually mean you should consider refactoring. Of course this is a bit different when it comes to developing frameworks where you might want to support a bunch of different use cases.
Maybe I'm biased because I've been using TS ever since it first came out.
And Rich Harris (Svelte) said, it's an issue for people in his position, aka, people making tools for developers - he fully expects and respects that the end users (developers using those tools) don't really experience the downsides.
That said, I feel like we're seeing a lot of versions of complaints about how big the stacks are getting, how big the foundation is that we "need" just to get started. That desire for minimalism is core to the developer mentality imo, it makes us good at our jobs. I think we're going to see more paring down and culling in the coming months/years.