Unrelated to the topic at hand but related to the technologies mentioned. I weep for Redux. It's an excellent tool, powerful, configurable, battle tested with excellent documentation and maintainer team. But the community never forgave it for its initial "boilerplate-y" iterations. Years passed, the library evolved and got more streamlined and people would still ask "redux or react context?" Now it seems this has carried over to Claude as well. A sad turn of events.
Redux is boring tech and there is a time and place for it. We should not treat it as a relic of the past. Not every problem needs a bazooka, but some problems do so we should have one handy.
Yup. I'm the primary Redux maintainer and creator of Redux Toolkit.
If you look at a typical Zustand store vs an RTK slice, the lines of code _ought_ to be pretty similar. And I've talked to plenty of folks who said "we essentially rebuilt RTK because Zustand didn't have enough built in, we probably should have just chosen RTK in the first place".
But yeah, the very justified reputation for "boilerplate" early on stuck around. And even though RTK has been the default approach we teach for more than half of Redux's life (Redux released 2015, RTK fall 2019, taught as default since early 2020), that's the way a lot of people still assume it is.
It's definitely kinda frustrating, but at the same time: we were never in this for "market share", and there's _many_ other excellent tools out there that overlap in use cases. Our goal is just to make a solid and polished toolset for building apps and document it thoroughly, so that if people _do_ choose to use Redux it works well for them.
Redux should not be used for 1 person projects. If you need redux you'll know it because there will be complexity that is hard to handle. Personally I use a custom state management system that loosely resembles RecoilJS.
Well, the tech du jour now is whatever's easier for the AI to model. Of course it's a chicken and egg problem, the less popular a tech is the harder it is to make it into the training data set. On the other hand, from an information theoretic point of view, tools that are explicit and provides better error messages and require less assumptions about hidden state is definitely easier for the AI when it tries to generalize to unknowns that doesn't exist in its training data.
The previous company I was working at had quite a lot of TCL code for their back end logic. Betting sector, well known in US and Europe. They still actively hire people to maintain the codebase. Rock solid code, no surprises, was able to handle tens of thousands of concurrent bets.
People in this thread hating on React seem to miss the crucial point that 2016 React was a godsend compared to just about every other option available. Vue only picked up steam quite later as React became more and more bloated or had its development forced by Vercel down a certain road. Angular was THE framework to avoid working on and people hated having to define multiple files for a simple component. The timing for React was just right back in the day.
Given how FEs are re-written every 7-10 years there is ample room for other frameworks to knock React off its throne, but before asking "but why not X" you also have to consider that organizations by now have almost a decade of experience building React apps and this plays a major role when deciding on which UI framework to rely on.
I believe we are having this discussion from a purely technical perspective and not from a business one. Let's take slack for example. Assuming a company can perfectly clone it, why would they? Yes they would skip paying for it, but they would have to maintain it, starting from its infrastructure all they way up to its UI. Will they think of new features? Will they follow industry developments in sound / streaming technology? Will they keep integrating other tools into it? I am sure they would rather pay to have somebody else do it for them, someone like slack itself.
Also, assuming a company has the capital to burn through enough tokens to create something so big and complex, why spend it on an internal tool? Shouldn't they be spinning slack-sized apps to expand their existing market share or try to disrupt new markets?
The way I see it using tmux to orchestrate multiple agents is an intermediate step until we get a UI that can be a product offering. Assuming we get orchestration to the level it has been touted, there is a world where tmux is unnecessary for the user. You would just type something to one panel in which the "overlord" agent is running (the "mayor" if we talking gas town lingo) and that agent will handle all the rest. I doubt jumping between panes is going to stick around as the product offering evolves.
Does it count if I share my experience with AI and nvim? I use it to update my configuration, discover new plugins, write custom lua code (I don't know lua) and inquire about motions that would help me in specific workflows. I started learning vim motions last summer and AI really lowered the entry barrier and allowed me to focus on the motions rather than the setup.
Also related to my nvim workflow but not strictly vim related: I use AI to write and update a bash script that handles tmux windows. Again, it lowered the barrier to entry and it made switching to nvim as my primary editor easier.
This is an incredibly cringe article. From using “wolf” in a completely forced way, to full quoting a conversation that seemingly only misses “and that testing framework’s name? Albert Einstein”.
Man I'm glad someone said this. Incredibly cringe and unnecessary using the whole wolf analogy for, essentially, "someone who's good at their job". Gives off vibes of the whole "alpha/high value male" thing going on in social media.
I have to admit reading heroic stories like these is a guilty pleasure of mine. It's ridiculous, but strangely inspiring in a completely unrealistic way.
I built a new pc for gaming 2 years ago with windows 11 and I can’t see myself using this OS again when I retire it. From randomly losing Bluetooth, to keyboard resets, to the hilarious failure that is the new right click menu (which lags a bit before appearing, something that I find hilarious) it’s just a bad user experience through and through. My new pc will either run Linux or be a Mac mini. Hopefully Linux gaming will continue to improve and I will be able to completely ditch windows once and for all.
Redux is boring tech and there is a time and place for it. We should not treat it as a relic of the past. Not every problem needs a bazooka, but some problems do so we should have one handy.
reply