> Am I wrong? Am I just creating an environment of anxiety?
No. Parenting and schools have gone completely to hell. You're not wrong, everyone else is. I still can't believe schools started letting kids carry their cell phones with them to class all day. As early as elementary school. WTF.
For my part, I figure my kids can have an unrestricted cell phone (and so, unrestricted Internet) as soon as they can pay for the device and plan on their own. If they can hold down a job to cover the bill, they can probably handle it. Fuck giving 8-year-olds personal smartphones. Or even 12-year-olds. That's insane.
Yeah, last I checked they paid under typical wages (already bad, by coastal standards) at local jobs in my area. Jobs that have much easier interviews. And many of them allow remote, too.
I didn't end up with a local employer (again—I have in the past), but I do have a remote job that pays more than local work. And it was easier to get than a GitLab job. So why even apply, unless they've significantly increased pay relative to other options?
This misses the part of the game where the doctor's office has you fill out forms giving them a bunch of the same info they already have. Twice. In the same visit. This may take 20 or more minutes. For no good reason whatsoever.
Then the ongoing ARG portion where you have to repeatedly sit on hold for hours with the provider's billing department, insurance, and the state insurance commission and/or your congressperson's office, to finally get all the billing sorted out without getting screwed, all while receiving all kinds of scary letters that the people on the phone will tell you to ignore.
[EDIT] Oh and I bet the Canadian version of the game doesn't even have some of the greatest antagonists of the American edition: the people whose entire job is to wander around emergency rooms bugging very sick people about payment and insurance.
>"Oh and I bet the Canadian version of the game doesn't even have some of the greatest antagonists of the American edition: the people whose entire job is to wander around emergency rooms bugging very sick people about payment and insurance."
Most, if not all the provinces do actually charge people in certain groups (tourists & recent immigrants) for medical care.
>the greatest antagonists of the American edition: the people whose entire job is to wander around emergency rooms bugging very sick people about payment and insurance.
Lol yes! One time I woke up with debilitating nerve pain shooting down my writing arm and went to the ER.[1] One of those people kept bugging me until I snapped and said, “I am totally happy to fill that out, just the moment my arm is functioning again.”
[1] Yes in retrospect should have gone to an urgent care, although I suspect they wouldn’t have been helpful either.
For what it's worth, we've changed Redux usage drastically in the last three years. "Modern Redux" with Redux Toolkit and React-Redux hooks is drastically simpler to learn and use than the older-style patterns, and we get feedback from users on a daily basis telling us how much they enjoy using RTK.
If you're curious to see what that looks like, I did a video discussing the changes and cooperatively live-coding an example app:
For what it's worth, I gave RTK a go after a rushed, failed attempt at using redux. Initially started as a POC for some internal tooling within the company. Due to its simplicity, it was a breeze to set up. Two years later, it's still great, and things like RTK Query[0] have made it even better, by removing the need to write custom data fetching logic, and adding other perks like caching.
Your second link briefly got my hopes up that I’d finally be able to learn a little about Redux today.
Nope, the tutorial tells me I better get good first in:
> React terminology: JSX, State, Function Components, Props, and Hooks
Does that imply you can’t use Redux without React at all?
Or does it just use part of React’s concepts?
I’d totally love to learn to manage my application state better. Do I really have to pull React in with that?
I use vanilla JS as much as I can because I want my apps to have a decent chance to still be working a decade from now.
Redux is 100% UI-agnostic. You can use it with any UI framework (React, Vue, Angular, Svelte, jQuery, web components, vanilla JS). This is also true with our official Redux Toolkit package, which is the standard way to write Redux logic today.
However, in practice, probably 90-95% of Redux users _do_ use it with React. So, yes, all of our tutorials are written under the assumption that you are using it with React.
Additionally, we see lots of people trying to learn Redux too early in their journey. It's bad enough that bootcamps throw people through "4 weeks of JS, 4 weeks of React, 4 weeks of Redux, GO!", and we can't do anything to stop that. We do want people to learn Redux, but we've found that it's best if most people are already comfortable with JS and a UI framework (which, again, is normally React), before they try to dive into Redux. That way there's fewer new terms and concepts to learn at once, and it's more clear what benefits Redux can add and how it fits into the UI layer.
If you'd like to focus on just the Redux core concepts, I'd recommend going through our "Redux Fundamentals" tutorial. It explains the underlying principles and techniques, and how Redux works:
There is content in the middle of that tutorial that explains how to use it with React, and if you want to use it with vanilla JS you'll have to recreate equivalents to some of those APIs yourself. But, the rest of the material should be directly relevant.
Also, please come by the Reactiflux Discord and ping us over in the #redux channel - we're happy to help answer questions!
> Does that imply you can’t use Redux without React at all?
Yikes, I hope not. One of my favorite things about Redux (last time I used it, maybe three years ago) was that it was easy, and even natural, to build an API client library around it that could be used almost anywhere that JS will run, because it wasn't tied to React.
No worries :) Non-React usage is still the minority use case, but it's one that we take seriously. Per my comment above, Redux and Redux Toolkit are still 100% UI-agnostic at their core. Even our new "RTK Query" data fetching API in RTK works with (or without!) any UI, which is why users have adapted it to run alongside NgRx, Vue, and Svelte.
Some graphQL clients can eliminate the need for these state management tools. Everything becomes just graphQL queries and mutations with very sophisticated caching. When you mutate some resource, other components that have queries that are affected by the mutation will re render with the new state.
I don't get why most projects need Redux when React has the context API already. Most people just need a place to store data shared across different components, and plain contexts do that easily.
Because Redux and Context are different tools that solve different problems, with some overlap.
Context is a Dependency Injection tool for a single value. Note that it doesn't "manage" or "store" anything - it's just a tube that you can pass something through. Any actual "storage" is normally done with React's own `useState/useReducer` hooks, which actually _do_ store and update values.
Redux, meanwhile, is a tool for predictable state management outside React. Very different kind of tool, for a different purpose.
They can, but for any reasonable sized application, you're basically recreating bare redux. If someone is good with both, it can architect and choses the correct one based on the needs of your software. But if you find that your global state needs are not small, you just chose redux - add a library like rematch on top to reduce boilerplate - so it's straightforward for your junior.
Redux historically had a pretty terrible API. Next stop: Boilerplate-ville.
But it's based on a sound model.
Go and check out elm, the project redux copied its structure from and you'll see what that model is capable of achieving in a decent language.
Today with hooks Redux is not too bad but still subpar. I used for years my own simplified store, these days I just use zustand.
AJAX was originally about speed, but as soon as it changed from fetching and injecting HTML fragments, to fetching data (usually JSON) and performing a bunch of transformations and interpretations of it before finally modifying the DOM, it's been in practice slow as hell compared with traditional server-side rendering.
Doing everything on the frontend is great for making the UI feel responsive, but once you start grabbing large amounts of data from an API, manipulating it on the frontend while keeping it in sync with the server, you run into some major headaches very fast.
Like with those "personality tests" where anyone with decent perception and reading comprehension can easily tell which outcomes each answer's going to push them toward, and so obtain any result they like.
Is the correct response to slip a Benjamin to another waiter to "accidentally" trip the one who screwed up, so you can judge from their response what your demeanor should be like when requesting a correction?
On that note, one that could open in one direction only would let the pet out, but not open inwards. To the extent that this helps though, I'd wonder more about other things that are risky, like flammable furniture foam/curtains. A room and contents fire gets out of hand faster now than they used to, because the old wood furniture and natural materials are much less immediately flammable. Either way, once the heat breaks a window, that room at least will suddenly have lots of air.
I did subscribe to a monitored alarm service specifically for the smoke detectors, on the theory that while I have little need for a burglar alarm here, I would really want the fire department sent if something started while I was out. I'm on my local department, and usually home, but the neighbours wouldn't know quickly if something happened while we're away.
What we bought has several flaps (to help with insulation) and a plastic cover we can put over it at night. The flaps would still be there; I just wanted a "cover" that would come off in an emergency.
I use weed for both these cases—shutting my mind up so I can sleep and/or dulling physical pain in case of illness so I can sleep, if it doesn't rise to the level of needing/being-able-to-get serious painkillers, plus (at lower doses, and far less often) for reducing anxiety during waking hours.
Works great, wish I'd started years ago. Leaves me much better-rested in the morning than other prescription sleep aids I've tried. On nights when I know I'll have a nice 9ish hours uninterrupted, I pair it with a little melatonin to keep me from waking up completely if I stir a little after the weed's worn off, and it's the best damn sleep of my life.
A+++++ would recommend. Screw you for lying to me, William S. Sessions.
When it became legal here several years ago, I tried it out a bunch. Turns out I'm the kind of person that cannabis generally makes anxious/paranoid. Probably for the best, but I'm kind of bummed it isn't as fun as people always made it out to be.
I got an ecc-ready used workstation on Ebay. After adding a smallish SSD for the system drive and upgrading the memory to 16GB I think my total cost was in the neighborhood of $200. Cost about as much as two top-end fully-equipped (case, heat sinks, disk) Pi4s, but is much more powerful, and, conveniently, includes space & ports for my SATA spinning-rust bulk storage disks.
It is a (fairly small) desktop tower, so it takes up quite a bit more space than a couple of Pis, though, again, it also encloses some internal hard drives, which is nice. I'm not sure about power use but I'd just gut-instinct guess it's equivalent to four or five Raspberries Pi, even if you take out the power to run the hard drives, so it is (probably) worse on that front.
No. Parenting and schools have gone completely to hell. You're not wrong, everyone else is. I still can't believe schools started letting kids carry their cell phones with them to class all day. As early as elementary school. WTF.
For my part, I figure my kids can have an unrestricted cell phone (and so, unrestricted Internet) as soon as they can pay for the device and plan on their own. If they can hold down a job to cover the bill, they can probably handle it. Fuck giving 8-year-olds personal smartphones. Or even 12-year-olds. That's insane.