It still feels very early stage to me, perhaps "polished" is the wrong term to use. It's also extremely difficult for a casual player like myself, focusing heavily on basic survival mechanics.
Vintage Story is quite polished in my experience. It's a bit disappointing content-wise though. The tech progression doesn't go very far, and what's there is nearly identical to the TerraFirmaCraft Minecraft mod.
Maybe be able to control the breathing speed (the circle animation speed) would be handy. Unless this is supposed to be scientifically the speed I should be breathing for optimal health or something. My body wanted to go a little slower than the circle moved and I found myself speeding up to keep time. Or is that the point?
I've been using Pocketbase for personal projects on the machine I use to self-host services. It's great. You get CRUD and real-time stuff for free and I didn't really have to spend much time learning to start working with it and having it running in an LXC.
It's one of the only games I play! I have it on Android and one thing I like is that it's fast to open up and play a bit, save, and then quit. No ads or a bunch of intros to try to skip, etc.
I normally agree with this sentiment but I have a story about this. I was in a situation where I was handed over old projects to expand on and the choice to rewrite or build on the same codebase was up to me and another dev (management didn't care or know what should be done in this regard). As "mature" devs we knew rewriting wasn't a great idea. So we code splunked for months, wrote tests, upgraded and cleaned out code bits at a time. Only after succeeding in this did we realize that 85% of the existing code was unused and most of the remaining 15% had pretty substantial bugs in it and naturally ended up mostly rewritten to fix. Turns out the previous dev worked alone for years, didn't use source control, didn't ever delete anything, and that the company has quite a history of pivots. After stepping back from this we realized we should have rewritten, that we basically did anyhow, except we took the longer road to get there but now still have to continue with some of the framework/lib choices the previous dev had made because we opted to stick with them in order to facilitate this piece by piece "rewrite". I don't think we did anything wrong here but it's funny how taking this mature approach, in retrospect, probably didn't help much and now we're beyond the opportunity for a rewrite. I know some folks will say that what we did was actually a first step towards a proper rewrite, and I'd agree, except the time to do that never came.
I'm so glad my demo today was specifically about local inference on... Windows. I guess working I finally found an upside to doing ML outside Linux ; we don't have Windows VMs on AWS!! :)
> Over the next few days, he cut up the plane into small pieces, and dumped the parts in trash bins in and around Lompoc City Airport.
I once helped a friend do something like this with a bunch of garbage from a house party he threw at his parents place and wanted to cover up. We drove around dropping bits of the 10+ bags of trash in bins here and there. I'm in awe imagining doing this with a plane.
Both my partner and I always have trouble with the McDonald's app (for ordering). I use Android, she uses iOS. As a developer, I've said to myself "This feels like a React Native app that's calling into a mess of microservices" (having worked on that type of project more than once myself).
Anyway, I only skimmed the article, but I had a chuckle seeing the title of this article pop up on HN at all.
I can't speak for other region's McDonald's apps, but the mymacca's app (Australia) is entirely native Java on Android, and still runs like absolute crap.
Completely unrelated probably but who knows but this reminded me of the time when my McDonald's receipt printout from that self-ordering terminal started with a bunch of XML, then the regular receipt part and then ended in a bunch of XML. That was fun.
Plexure are only used in select McDonald's markets. Almost all Hacker News readers are in markets where the McDonald's app is developed in-house by McDonald's.
I still consider this when hiring. I don't necessarily see a 10 year tenancy as major bonus points but do consider a flurry of short full time gigs to be a red flag. It's not about loyalty so much as that often it can take 6+ months to really get productive amongst an existing codebase and culture. That's also the point where the developer might really start to drive on more intense projects. If they're always leaving before this point that's great for them but not so much for us.
