The fact that most universities will graduate CS majors without ever teaching them how to use a debugger, build system, or version control system shows how useful they are to actual engineering work.
The fact that most universities will graduate CS majors without ever teaching them how to use a debugger, build system, or version control system shows how useful they are to actual engineering work.
“Right to work” refers to the fact that in those states, unions cannot force membership or payment, or force you to participate in labor strikes. You can still have a union in those states, but it’s very difficult for them to be effective because most people will choose not to pay into it, and strikes have significantly less bargaining power if there’s no legal obligation for union members to follow through with a strike.
The result is that in such states, there are very few unions, and so very few protections against firing workers for arbitrary reasons.
It seems silly to be distrustful of proprietary BIOS firmware without having the same skepticism of the actual hardware.
Wow, I had no clue. TIL
3 nanometer
That’s a silicon lattice just six atoms thick. What a time to be alive!
TIL a single T-72B3 costs less than $2M.
Inference, yes. Training, no. Derived models don’t count.
I had a linux 5520 and it was terrible. Standby and bluetooth never worked properly. Are the new models any better?
I think it’s more like “snuck up on us” than any kind of nefarious connotation. Kind of like “how did a niche game like BG3 sneak into the top ten games list”?
I have 7 trees on my property. If you pay me $700 I’ll promise not to cut them down for five years, and you can subtract 35 tons of CO2 from your environmental balance sheet.
That’s how carbon offsets work. They’re bullshit.
Deliberately using software encryption mode is slow; no shocker there. Their same testing showed no significant difference when hardware encryption mode was used.
Say it with me everyone - CORPORATIONS ARE NOT PEOPLE
It’s not even clear to me that the mechanism they’re using today is problematic. I don’t know what it is, but the author seems to think they do but aren’t sharing details beyond “trust me bro”. I agree that some kind of inspection-based detection might run afoul of the law, but I don’t see why that’s necessary. All you need to know is that the client is requesting videos without any of the ad requests making it through, which is entirely server-side.
I don’t even know why they’re trying; the only people I know who have comcast have literally no other choice. Their marketing could be “get fukd what you gonna do get satellite internet?” and their subscriber base would drop less than 5%.
It doesn’t really matter what you personally use if you’re going to make sweeping generalizations about the quality of streaming music. It’s like saying stainless steel knives are trash just because there exist knives made of tungsten carbide.
When you’re listening on a shitty bluetooth speaker or earbuds it really doesn’t matter.
Only if they are well-known in the language you’re using or domain you’re writing for. x
and y
are fine for coordinates. i
and j
are fine for loop indices. But abbreviating things unnecessarily is bad IMO. s = GetSession()
is too terse, for example.
That’s by draining the battery, not by sustaining a charge. If it gets 710km in the sun and 660km in cloudy weather, it probably gets 610 without any solar panels at all.
So the solar panels contributed an effective 1.2 MPH to the trip.
Not really a problem with UDP itself, but with some very old protocols like DNS that rely on UDP but can’t be changed because of compatibility. If you’re writing a new service that uses UDP, there’s nothing stopping you from designing it so that it doesn’t provide an opportunity for bandwidth amplification.