This falls in the category of “looks shitty, but could be pretty good”.
I once had a variation of this with devilled eggs with minced chicken cooked in a broth mixed in. It was fantastic, so meat in devilled eggs could probably work?
This falls in the category of “looks shitty, but could be pretty good”.
I once had a variation of this with devilled eggs with minced chicken cooked in a broth mixed in. It was fantastic, so meat in devilled eggs could probably work?
I mean, for 10 bucks anything is a decent deal. Those specs are pretty decent for a simple home server. I’m not familiar with HP thin clients, but I assume you can install a Disdro of your choice on it? My big reason to avoid HP is their crap software and warranties, both of which are moot here.
I would say relatively light software like tailscale, pihole and such would be fine. Docker containers might be pushing it, but that depends largely on what containers you want to run, same goes for nginx; by itself the requirements are fairly low, it depends on what you want to run on it.
Jellyfin might be a stretch, and as you alluded to, real-time transcoding is probably out. It strongly depends on the decoding capabilities of that chip and wether it does hardware decoding or if it all happens in software. The latter might be too much for it. If it can handle it though, it might be interesting as a media player hooked up to a TV, rather than acting as a transcoding or DLNA-esque server.
The original Test Drive Unlimited was great, but it rightfully bombed in reviews due to some really bad technical issues. Some of the car characteristics were really bad and off the mark, and the game suffered from an engine issue that was a problem other racing games had solved long ago;
On long slopes, the geometry of the road didn’t curve properly; the angle would have a polygonal jagging issue. This was most likely to shave off performance cost on the 360. Other games had already solved this issue by effectively smoothing angle changes, but TDU did not do anything of the sort. The result was that on hilly terrain cars would constantly bump around and lose traction due to weird unexpected air-time. Some cars were affected far worse than others, particularly super cars had a bad time.
I loved TDU, I loved cruising around in my Shelby Cobra and doing the one-hour tour around the island for decent money.
But the list of flaws is pretty long, and the technical issues made it a nonstarter for anything competitive.
It honestly wasn’t so bad. I played about 80 hours of it, right after launch. In typical Bethesda fashion, I used a few ini tweaks and such to tailor it to my tastes. Mostly fixing the Stealth (which was horribly broken at launch) and balance changes like reducing the bullet spongyness of enemies.
Both are now patched and configurable through the built-in difficulty settings.
I enjoyed my time with it. I went in expecting a space-skyrim with typical Bethesda jank, and that’s exactly what we got.
Yup, I don’t even dislike Dead Space 3, but I would rank Callisto Protocol far, far, below that game. I finished the entire game and felt like I had simply wasted a colossal amount of time. The story was abysmal, the world building was weak, the gameplay was repetitive sidestep nonsense. I literally see no reason to ever recommend that game to anyone.
What’s wrong Glen? I thought you said this game was your baby, exactly how you envisioned Dead Space was supposed to be, if you had completely creative control?
Turns out maybe the problem was you, Glen. Because that DDR-inspired wet napkin of a game that was Callisto Protocol, had zero of the appeal that draws people to Dead Space. The DLC was something you should creatively be absolutely ashamed of and made it pretty much impossible to actually continue the story.
Hey Op, since you appear to be somewhere in the EU based on your mention of Euro pricing, would you be willing to name and shame the wheelchair manufacturer and/or model?
Without giving too much of my own personal information away, I might be in a position to cause a bit of ruckus for this particular company in terms of bad PR, possibly legislatively. I work for a company that profiles itself on doing this stuff “the right way” (secure practises, not screwing users this way, etc) and we are working on building a list of practises we are hoping to root out EU-Wide with some examples that are clearly exploitative.
I need nothing personally identifiable, just the brand and model, and I can pass it along to the team that can investigate further.
I frequently amaze new colleagues when I show them that deploying an update for our backend application is a sub-second affair. Our pipeline keeps track of what git tag was deployed last, diffs between that tag and the new release, and uploads the files to each of the deployment targets. It takes longer for the pipeline agent to spin up from Cold on a Monday morning, than it does to actually deploy.
The core of the application is just php scripts, and those are either immediately up to date whenever the next call is, or swapped out the next time that component finishes a processing cycle.
Docker containers are nice, but nothing beats the cause of a stack trace being fixed, tested and deployed to the acceptance environment within minutes of it arriving.