andrewstuart2

I added it pretty shortly after I commented via edit but I think they'd probably already started their response and didn't see the edit first.

Yeah this is one of my biggest questions from a lot of the high profile departures during the Trump admin early days (both times probably). Sure, you save face a little maybe, and you register your protest, but then you are replaced with a yes man almost certainly, which is significantly worse.

But also, then, I know exactly how I would feel about continuing to work if my purpose is now to just be a roadblock. It must be pretty demoralizing and can you really ask that of someone else or be upset if they aren't up for that? I would certainly be tempted to jump ship for a chance to get paid better doing something I enjoy.

I mean that could still be encrypted. But passwords should never be reversible. It should be hashed with scrypt or apparently now Argon2id.

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.

My favorite was right before that.

Text: You have rights to what you make.

Music: You own what you make.

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.

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.

Congrats. Happy for you. Nice.

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 thought for sure this would be for f1tv.formula1.com but apparently that's only 134 and I thought that was ridiculous.

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.

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.

Off topic, but I love your username.

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.

I would call it clever. I'm not sure I'd call it genius.

When I'm working with data I'm working in a specific set of languages. Usually one. Yeah, other people might be working in other languages, but no individual author really needs a language-agnostic way of accessing data beyond compile time. Add to that the likely runtime boundaries that may need to be crossed instead of e.g. inlined by the compiler because it's in-language and dealing with known offsets or tags (depends on the data format of course). To the other commenter's point, am I going to have to sandbox all data access code just to be sure it's not able to do something unexpected? There's a lot of complexity here. And the inherent risk is going to slow down the operation that should be the simplest and fastest: interpreting bytes.