So expensive.. or so profitable that the payments need to be lowered to look palatable over 7+ years.
Readit Newsj45 commented on Cars are so expensive that buyers need seven-year loans bloomberg.com/news/articl... · Posted by u/MrResearcher
j45 commented on Reading for pleasure plummets by 40% in the US medicalxpress.com/news/20... · Posted by u/geox
While mindless scrolling may have replaced some of that, intentional reading is way more rewarding.
It's pretty astounding what reading to kids every day can do for them regardless of the environment they grow up in.
I'm thinking of a beefy mini-PC + USB-C 8+ hard drive enclosure.
I feel like I rarely upgraded anything except GPU and storage. And GPU's are not needed for a server.
Enclosure means easy storage upgrade and I can always reattach the enclosure to another machine quickly. Might even install OS on the enclosure, then the whole setup will survive compute upgrades until the predominant architecture changes.
I tend to want to keep storage (NAS) separate from compute and databases, in the form of I never want to touch or think about this so I can spend my time on other things.
Having a couple of pre-built nas' from QNAP or Synology can go a long way to getting one's feet wet to learn what they offer that we sometimes learn the hard way about.
I have repurposed retired laptops for my tech lab at home. They no longer keep up with the current software bloat for wife and kids usage, but make reasonable linux servers. Currently serving up 3 databases on one, kafka and networking on another and services/applications on a third. They take up very little space under my desk.
A good way to keep the laptops operating as well. It reminds me I have a few old macbooks with decent specs that should be at least running.
I agree and already got two minipcs I selfhost a lot of stuff now. I just now realized it is basically the future Gabe Newell predicted and wanted to make with Steam Machines [1], but he was wrong by targeting gamers and a little too early (perhaps?). Maybe they will succeed precisely because of this revolution.
I got soooo tired setting up a gaming system for parties on my projector. There are so many various problems and tweaks, gamepads disconnecting if you put a hand between the gamepad and the pc/playstation etc. BSODs on windows, driver problems and stupid obscure things varying from pc to pc. I want plug and play, but consoles have their own problems and limitations. I am too old to debug this stuff to play a game for so little time, I would rather not. I didn't really believe in steam machines at the time, but now I sort of do, especially with game streaming and local LLMs that might be hosted there now.
Self-hosting has become orders of magnitude easier and simpler over the past 5-10 years.
I've been using Go more or less in every full-time job I've had since pre-1.0. It's simple for people on the team to pick up the basics, it generally chugs along (I'm rarely worried about updating to latest version of Go), it has most useful things built in, it compiles fast. Concurrency is tricky but if you spend some time with it, it's nice to express data flow in Go. The type system is most of the time very convenient, if sometimes a bit verbose. Just all-around a trusty tool in the belt.
But I can't help but agree with a lot of points in this article. Go was designed by some old-school folks that maybe stuck a bit too hard to their principles, losing sight of the practical conveniences. That said, it's a _feeling_ I have, and maybe Go would be much worse if it had solved all these quirks. To be fair, I see more leniency in fixing quirks in the last few years, like at some point I didn't think we'd ever see generics, or custom iterators, etc.
The points about RAM and portability seem mostly like personal grievances though. If it was better, that would be nice, of course. But the GC in Go is very unlikely to cause issues in most programs even at very large scale, and it's not that hard to debug. And Go runs on most platforms anyone could ever wish to ship their software on.
But yeah the whole error / nil situation still bothers me. I find myself wishing for Result[Ok, Err] and Optional[T] quite often.
I wonder if Go was setup in part to help large, complex or critical codebases on even older old school syntaxes progress relative to where they are.
j45 commented on Everything I know about good API design seangoedecke.com/good-api... · Posted by u/ahamez
j45 commented on Everything I know about good API design seangoedecke.com/good-api... · Posted by u/ahamez
Anyone else old enough to remember when "API" also meant something that had nothing to do with sending and receiving JSON over HTTP? In some cases, you could even make something that your users would install locally, and use without needing an Internet connection.
APIs are for providing accessibility - to provide access to interactions and data inside an application from the outside.
The format and protocol of communication was never fixed.
In addition to the rest api’s of today, soap, wsdl, web sockets could all can deliver some form of API.
Looking beyond Apple/Intel, AMD recently came out with a cpu that shares memory between the GPU and CPU like the M processors.
The Framework is a great laptop - I'd love to drop a mac motherboard into something like that.