Some of the concerns around generics and why it took so long were for the users as well. One of the biggest draws to Go has always been that you get the performance of a compiled language and yet compile times are so low that it can feel like you're developing with an interpreted language. The design of generics needed to maintain the compile time advantage or else it wouldn't feel like Go any more.
Languages like CLU, Ada, Delphi, Standard ML, OCaml, D, were having Go like fast compilation times, with generics, some of them decades before Go was created on much weaker hardware.
Command and Conquer was almost certainly my first exposure to him. I guess it's time to go replay Red Alert 3 and enjoy those cutscenes all over again.
A regular yearly replay is in order for me, too. Already done with SC2... just SC1/WC3/DoW(2)/RA2(mental/flippedmissions/etc)/RA3(uprising)/HOMM3/etc/etc/etc. Ah well.
An underrated fallacy in general. (Of course I'm just giving a common name to something that was identified, not accusing anyone of having the etymological fallacy in this conversation.)
Yeah, I built mine in 3090 times and told myself I'd upgrade every 2-3 GPU generations. I do have 128G ram and I'm thankful for that but I'm definitely not on the same upgrade schedule any more.
I have 32GB and an aging 5800X3D and I have not had any issues running games yet. Honestly would love to know what games need more powerful RAM/CPU outside of stuff like Flight Simulator, or running at 160fps without framegen.
Honestly I have a steam deck and that has gotten me accustomed to not sweating the lower frame rates. That and the ridiculous number of great indie games that aren't heavy on the graphics, and I'm not too worried about upgrades as much as I am worried about replacements if/when the time comes.
I like to think of myself as pretty well-versed when it comes to hardware and software and even some RF. But this conversation has me hitting search a lot, lol. It's fascinating reading experts talk about a domain I have less experience in.
Heh, welcome to RF; there are more rabbit holes to go down in domain specialty than I think there are grains of sand on a beach. I've gone down like... two. And I'm pretty overwhelmed.
I think that's why a lot of EEs and developers wind up getting an amateur radio license, or at least running a few fun RF projects.
Glad I’m not the only one. I’ve been tinkering with sensors, robotics, sdr and similar stuff for 20 years now, but this conversation was way over my head.
Showing its age is also a pretty significant plus, for such a critical part of one's infrastructure. That means it's been beat up on and run through the ringer for a decade plus at this point and had lots of chances to fix CVEs and other bugs. Not to say there won't be more, but being older and time-proven for an IdP is a major positive.
I hope/wonder if it will go the way computers did. We may learn to more effectively build RAM or parallel compute, and use it more effectively, in the coming decade in such a way that we can democratize more and more like we did with processors to the point that they're ubiquitous.
reply