No, you don’t need to do that.
No, you don’t need to do that.
It might be ‘state after G3’
pathological
I’m afraid this one is already taken, friend.
You can go fast again.
Motorcycle, actually.
It was no trouble.
Why did you write this here?
While I respect your choice to make things more ‘beautiful’ in your editor, I do not think we should ever do this by default.
It might seem nice visually, but suddenly we are not seeing things exactly as the compiler does. And as someone who has spent a lot of time helping folks debug their code, I feel quite strongly that this is just further obfuscating an already challenging field - for superficial gains.
No idea what held in is, but I live in vim, and … no ligatures, thanks. Same with italics. Ligatures with fixed-width fonts make no sense. I especially hate the combined arrow symbols: why draw attention to something so unimportant?
I appreciate them in print, but do not ever want to see them in my terminal.
deleted by creator
Definitely isn’t necessary, but if you search for ‘3.5" SAS lot’ on ebay you might find all the drives you’ll need to get to 50TB for the price of a couple new SATA drives.
Yeah, you don’t want a surveillance drive. They are optimized for continuous writes, not random IO.
It’s probably worth familiarizing yourself with the difference between CMR and SMR drives.
If you expect this to keep growing, it might make sense to switch to SAS now - then you can find some really cheap enterprise class drives on ebay that will perform a bit better in this type of configuration. You’d just need a cheap HBA (like a 9211-8i) and a couple breakout cables. You can use SATA drives with a SAS HBA, but not the other way around.
sometimes my brain’s just a can opener
wtf, one would be fine
ehh… I think you’re missing the part where Microsoft is actively exploiting its customer base throughout its entire product catalogue - the likelihood that this is an actual win is no.
They wouldn’t be, they would be sorted by signal strength. I think that’s around 40-50% of the joke, though.
You should probably attempt to understand the topic / post before diving in.
So will I.