Base price went up, as did storage and the new price is cheaper than the previous price + equivalent storage I think

Today? It's been criticized for almost a decade

https://steamcommunity.com/app/612880/discussions/0/14708409...

https://www.newstatesman.com/science-tech/2017/06/alt-right-...

I don't really agree that "best practices around useEffect have changed a lot". It's more that that particular hook was used a lot when it didn't need to be so the team finally wrote some guidelines.

yeah same... i have always tried to useState and minimal effects, those have not really changed in 7 years

Probably due to the longstanding bugs with it. I still use it on all my laptops, but Finder in particular gets tripped up with what the drag state is when using it.

This is amazing. Assuming yes, but is there any way to get a camera feed to automatically pop up if motion is detected?

Thanks – well, in theory yes. I will add this as a feature request to Git and consider how to implement it.

There is update 1.3.1 pending review at Apple which introduces doorbell support – it opens camera feed when someone rings.

What shell scripts would help here? I love me some shell scripting but always reached for debfoster before falling in love with Pac-Man's `-Qe` and `-Qt`

Edit: oh this aptfile doesn't do the one thing I actually use brew bundle for: cleaning up the mess of leftover packages

I've been loving the Alpine Package Keeper, especially easily maintaining desired packaging state in /etc/apk/world

https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#Worl...

What is this tool solving that I can't do with apt+bash already?

Probably nothing other than the fact that you don't have to maintain it and have less worries about portability, like most command line utilities.

Still, can you share your script?

A pet peeve of mine is JS monorepo tools that only run package.json scripts.

Like yeah it's totally reasonable that they go that route, but please just let me pass a command that can be executed without having to wrap it in a package.json script

I don't know for others but pnpm has `pnpm exec` which allows running arbitrary commands on some or all of your packages

Picture the traumatized Mr. Incredible meme with the text "lowering the barrier means more exploits are found"

I bought one for my cat, never did help with finding him, just the general area.

They're not great for tracking things that move on their own, or things that avoid people.

We use them on our cats and have found the trouble-maker cat 3 times out of 3 when needed (in an urban apartment area; most recently the cat was scared by a noise which may have kept her hidden out all night in the cold, unless we had found her/shooed her back to the house)

we have them for our cats, they're great. Sometimes they're hiding in bushes and we don't realize they're 10 ft away. Other times they're down by the neighbor's house. It's not perfect but it tells us which direction more or less. And definitely more peace of mind if they ever got lost. They

They make breakaway collars so if they get caught on something it won't trap them.

Can't compete with a Tractive, though.

I found gitlab ci's yaml the smallest of the 3 I've used (gitlab, GitHub actions, CircleCI).

But does gitlab ci have anything for sharing? GitHub actions are built around it, and CircleCI has orbs and contexts.

For example, muse's guide for gitlab involves making your own container and managing the cache yourself (ref: https://mise.jdx.dev/continuous-integration.html#gitlab-ci)

GitHub actions is a couple of lines (ref: https://mise.jdx.dev/continuous-integration.html#github-acti...)

Not sure what you mean by "smallest". With GitLab you create docker images. That means you can easily run them locally and share them. In the example you gave the GitHub actions one looks like more lines of YAML but only works because they made an "action". If they had provided a Docker image then GitLab would be just as easy (and trivial to test locally).

mise already is trivial to test locally though, and I'm not sure I agree that maintaining a CI config + Docker image is just as easy as maintaining a CI config.

Missed my edit window, but the just-docker solution also doesn't do anything for caching, that's still left up to every job, and the `mise install`.

Again, I don't mine gitlab ci, but they have no solution for sharing repeated tasks.