Having used a bit of Svelte 3, the label is quite easy to understand. On top of that, it's valid JS.
> Redux is good as long as you understand what it's good for and only use it when it buys you something. My default recommendation is to not use a state library until you find you need one.
- People thinking Redux is brilliant. It's good, but it's a far too complex system to simply manage state. I'm aware this isn't React, but I have worked on very few React projects that don't have Redux
- Run-time load. Back to Svelte. It's inspired me to remove as much run-time work as possible.
- API complexity. The React API has exploded over the last year or two. Hooks, memo, portals, error boundaries. Most of them are clever solutions, but are only required due to the limitations of React.
The article is titled "I Don't Believe in Full-Stack Engineering", yet states "If you’re only hiring full-stack engineers" as though they are something the author believes exist.
It seems that the real approach of this article should have been to outline why hiring ONLY full-stack engineers may not be a good idea.
When I implemented GRPC on ELB, we used a multiplexer to re-route the GRPC requests. See: https://github.com/soheilhy/cmux/. The only other issue we had was that ELB's would not let connections live longer than 30 seconds.
Hi there, I'm the creator of rise. I've been using a number of tools to help perform text substitution and interpolation (eg: envsubst, m4), but I wanted something that provided me with a lot more power and was easier to get going with. After using terraform and reading through their hil and hcl libraries, I decided to create rise.
It's early stages in the projects development, but I am rapidly adding interpolation methods. Thanks!
> Redux is good as long as you understand what it's good for and only use it when it buys you something. My default recommendation is to not use a state library until you find you need one.
Agree 100%