67% is good enough for me. I am not using it as a medical device, and I am not an elite athlete. I just enjoy doing exercise, and every now and again I like to review the stats from my watch.
CRA has been a maintenance burden for my team for the last couple of years due to security vulnerabilities and incompatibilities in old packages.
We have several React apps (created with CRA) to support, embedded deep inside ASP.NET Web Forms apps (its legacy all the way down).
We decided to switch from CRA to Vite. It has worked great so far.
I am happy to see these docs recommend Vite as an option for adding React to existing apps, because at the time this decision was made on my team, it wasn’t very clear what the correct path was for replacing CRA. I don’t think we could have as easily switched to a framework like Nextjs.
If you are in a similar situation, I would recommend Vite.
Similar to wanting to start a blog, but instead of writing a post, spending significant effort building the platform. First post becomes ‘how I built my blog’.
Are these types of repos trust worthy, or is it best to download straight from Signal’s site?
Similarly, I noticed Signal is on Flathub [1] for installing via Flatpak, but the developer account is ‘unverified’. It’s always put me off installing via this method.
> Similarly, I noticed Signal is on Flathub for installing via Flatpak, but the developer account is ‘unverified’. It’s always put me off installing via this method.
I struggle with reading speed, and concentration in general when reading. No idea why. However, I love listening to podcasts, audiobooks, videos etc. at 3x speed.
Using text to speech has also helped. No longer do I delay reading long messages from coworkers, or dread reading boring documentation. I just use text to speech. It works really well on Windows (my current work laptop), but unfortunately not so much on Linux (personal laptop) or mobile (too fiddly).
It’s great that Google is extending the support, and that GrapheneOS can benefit from it.
I bought a Pixel 4a specifically for installing GrapheneOS. I used it happily for almost 3 years, until EOL firmware support. The phone worked fine, but I wanted the reassurance of firmware security updates.
I was going to get a Pixel 6/7 (I forget which was available at the time) to use GrapheneOS again, but I was so annoyed at Google for only supporting firmware for 3 years, that I decided to switch to an iPhone SE.
Shortly after this, I believe the next Pixel came out with 5+ years support. I had some regret, but the iPhone SE is OK, and I didn’t want to buy a new phone just for the sake of it.
I will probably switch back to GrapheneOS for my next phone, as it really is a great mobile OS. Hopefully the project is still going strong by then.
As a point of clarification: all Pixel phones starting with the 6 were guaranteed 5 years of firmware support. Some phones only had 3 years of OS upgrades (vs 5 years of security patches). Now everything is getting 5 years of OS upgrades.
Smaller companies have less traffic, need less expensive servers, and have no need to spend money optimising the language. They can focus on that when they make billions of dollars, like Shopify does.
This is how I've used DELETE. Something like DELETE /users/{uniqueUserId}. In ~10 years of building CRUD apps I don't think I've ever sent a body or query params with a request.
Some tools let you pass a parameter to indicate that you only want the request to take effect if the requested resource is in some specific state. For example, Google Cloud Storage uses headers to allow you to set preconditions that must be met before the action takes place. For DELETEs you can use this to say "delete this resource but only if its generation (sort of a timestamp) is exactly $foo", where $foo is the generation last known to the client.
What about where you're not just deleting a single entity by id? Like, for instance where a user can bulk select multiple items and then choose to delete them all (like email for instance), or maybe deleting by criteria, like "delete all Entities created before time X"
My gut says I would use query params though I typically stick with 1 action effects 1 record. I can't recall any specific times when I built bulk item management into an app but I'd say that's a personal preference on my end.
