the macos file browser, Finder, lets you set a background for a folder, move file icons around to arbitrary positions, other shenanigans. in order for this to work across systems on removable storage media and network mounts, they have this.
the macos file browser, Finder, lets you set a background for a folder, move file icons around to arbitrary positions, other shenanigans. in order for this to work across systems on removable storage media and network mounts, they have this.
check out https://sandstorm.org/ , the project is pretty dead but they had the right idea
I’d like to see this fix the most annoying part about subtitles, timing. find transcript/any subs on the Internet and have the AI align it with the audio properly.
I think we’re closer with hardware than software. the xreal/rokid category of hmds are comfortable enough to wear all day, and I don’t mind a cable running from behind my ear under a clothes layer to a phone or mini PC in my pocket. Unfortunately you still need to byo cameras to get the overlays appearing in the correct points in space, but cameras are cheap, I suspect these glasses will grow some cameras in the next couple of iterations.
check out Supreme Commander, it’s a game from the erra of good RTSes, and I think has some of the features you’re taking about, e.g. beforehand of multiple bases, automation… you can do things like produce x units, send them to this area, have them start doing this patrol, etc. You can pause the game, to make these orders too. My favorite gimmick though, is that the map is zoomable, from a classic here’s your dudes and tanks view, up into a strategic view with icons representing everything. This also opens up the ability to have units be different sizes. vehicles are appropriately larger than infantry, and you can have giant mechs to which other units are literally ants.
I think you can link a second Whatsapp app, similar to the web client. your primary one needs a webcam to read the QR code though
… but cd
is a built-in
A JavaScript VM in the kernel is inevitable.
not by any means modern, but I used to really like pal
I highly recommend installing fzf, and its shell integration. Makes your Ctrl + r magnitudes more pleasant to use!
More than that, your editor doesn’t run with root permissions, which reduces the risk of accidentally overwriting something you didn’t mean to.
it feels to me, like they’re less looking for new people to start doing this “work”, but more to connect with people who already happen to be enthusiastically going to events and showing off their laptops.
This is up there with left-pad now!
I really think that’s the secret end game behind all the AI stuff in both Windows and MacOS. MS account required to use it. (anyone know if you need to be signed in to apple ID for apple ai?) “on device” inference that sometimes will reach out to the cloud. when it feels like it. maybe sometimes the cloud will reach out to you and ask your cpu to help out with training.
that, and better local content analysis. “no we aren’t sending everything the microphone picks up to our servers, of course not. just the transcript that your local stt model made of it, you won’t even notice the bandwidth!)”
Are you using PersistentVolumes? If your storage class supports it, looks like there’s a volume snapshot concept you can use, have you looked into that?
Not sure what you’re doing, but if we’re talking about a bog standard service backed by a db, I don’t think having automated reverts of that data is the best idea. you might lose something! That said, triggering a snapshot of your db as a step before deployment is a pretty reasonable idea.
Reverting a service back to a previous version should be straightforward enough, and any dedicated ci/cd tool should have an API to get you information from the last successful deploy, whether that is the actual artifact you’re deploying, or a reference to a registry.
As you’re probably entirely unsurprised by, there are a ton of ways to skin this cat. you might consider investing in preventative measures, testing your data migration in a lower environment, splitting out db change commits from service logic commits, doing some sort of blue/green or canary deployment.
I get fairly nerd-sniped when it comes to build pipelines so happy to talk more concretely if you’d like to provide some more details!
I use these two vim plugins for the same functionality without leaving $EDITOR:
I’ve also started dabbling with using fzf in scripts for the team to use. Don’t sleep on the --query
and --select-1
flags!
don’t forget to install gti