I once read a review of a sous vide machine that just would not work unless it was connected to a smartphone via an app. And then that app would not work properly without a connection to some backend. That backend died at some point, bricking the sous vide machine. What a wonderful world we live in.
That was said by one random, rather insignificant Microsoft employee who had no capacity to make such a claim. Not in a position to even have that kind of information on the company’s future plans.
And even if they did have the capacity, if you actually go look at what really was said, it’s reasonably clear that they wanted to say latest version but fucked up the sentence. I hate defending Microsoft but that thing has become a meme at this point.
Tailscale funnel is made for this.
Does this mess with DRM stuff? Or do they keep working because it’s the same hardware?
I once worked on a project where the main function would run the entire code in a try-catch block. The catch block did nothing. Just returned 200 OK. Didn’t even log the error anywhere. Never seen anything so incredibly frustrating to work on.
Mostly the latter. We don’t do any optimizations on our product whatsoever. Most important thing is to say yes to all the customers and add every single feature they want. Every sprint is spent adding and adding and adding to the code as much as we can and as quickly as we can. Not a single second is allotted to any discussion about performance or efficiency. Maybe when something breaks, but otherwise we keep piling on more crap at full speed non-stop. I have repeatedly been told “the fast way is the right way” followed by laughter. I was told to “merge this now” on multiple occasions even when I knew that the code was shit, and told the team as much. I am expected to write code now and think about it later.
As you can expect, the codebase is a bloated nightmare. Slow as shit, bugs galore, ugly inconsistent UI, ENORMOUS memory use, waaaaaay too frequent DB access with a shit ton of duplicate requests that are each rather inefficient themselves. It is a rather complex piece of lab management software, but not so complex that it should be struggling to run on dedicated servers with 8 gigs of RAM. Yet it does.
I have node named pve too. Small world.
Twice, because usually it’s two sticks.
In any case, RAM failure is rare enough that quadrupling its chances is not gonna make any meaningful difference. Even if it does, RAM is the easiest thing to replace in a PC. Don’t even need to go offline while waiting for a new stick. Someone who’s got the cash to build that thing in the first place won’t be too upset by the cost of another 32gb stick either, I don’t think.
Well you see one client demanded some absolutely stupid very obscure feature that was so absolutely stupid that it could only reasonably be achieved by hacking some bullshit together on their on-premise bare-metal installation that they insisted on not giving you proper access that you needed. Then something went wrong with that hacked-together one-off bullshit, and the digital equivalent of this was the only way to figure out what the hell was happening.
Podman has a built-in automatic update feature that monitors the source repo. Could be useful for you.
How is that? Does risc-v have magical properties that make its designers infallible, or somehow make it possible to fix flaws in the physical design after the CPU has already been fabbed and sold?
I agree, unfortunately. The only reason I stick with ddg over Google is because, unlike Google, they don’t smother me with captchas the moment I enter a VPN.
Have they given an explanation as to why that is? I mean why make it a fatal error that prevents compilation, when you could make it a warning and have the compiler simply skip it?
That’s… a rather huge drawback. Why even pay for a shield at that point?
In most actually companies you can try push to origin master, but it’ll likely get rejected by the repo’s security policies.
I also find ORMs and query builders much easier to debug than most mative SQL database queries. Mostly because native SQL error messages tend to be some of the most unhelpful, most undescriptive crap out there, and ORMs help a bit with that.
Seriously, fuck MySQL error messages. 9 times out of 10 shit boils down to “you got some sort of error somewhere roughly over there, go fix”.
I ran into that same DNS issue with pi-hole but in a docker container, and the (bandaid) solution was to put the container in host network mode too. But turns out it’s not an issue but a feature. By default pi-hole only responds to DNS queries from within its local network. The host machine’s LAN is an external network to the containers, unless you set the container’s network mode to host. Pi-hole does have a setting to make it respond to DNS queries from other networks as well, though. What I’m saying is, that might not have been a podman issue.
There’s nothing sane and readable about how Go insists you format dates and time. It is one of the dumbest language features I’ve ever seen.
And is hilariously overkill for what OP seems to want. It’s a pretty large and heavy package that comes with a whole lot of (for OP unnecessary) features.
So many of those are also fiction. There was a post somewhere, where the op had compiled a list of top relationshipadvice posts that were highly suspicious at the very least up if you went into their posters’ histories. People were eating them up.
That sub became mostly a creative writing gym a long time ago.