That's not universally true, in fact, I'd say for large companies it makes less sense unless they negotiate insane off sheet pricing. The "We'll save all this money on data centers, headcount and hardware!" always becomes "Why have our monthly IT expenditures become astronomical?". Fixed and one time budgets have less political friction than variable monthly bills. When hard times come and the CIO is looking for savings, that multi-million $ AWS / Azure monthly cheque is going to be in their crosshairs, when the sunken no-check-to-write data center depreciation deduction never would. If you're a small company, then AWS is undoubtedly cheaper than your own DC or even most co-hosting.

Wait, they take CH4, and split it into H2 and a CO2 byproduct? Wasn't CO2 byproduct to whole impetus for electrification in the first place? So what is the killer benefit of fuel cells over batteries when the "what do we do with this CO2" problem still exists?

Was thinking the same thing. I'm fine with that, devs must be licensed and carry liability insurance, no problem. However, my rate is going to ratchet higher accordingly. Also that means that I'm ONLY responsible for errors and omissions in code that I green fielded. I can't be help responsible for other people's sloppy coding. So no fixing Dick's mess, I'll rewrite from scratch to cover my ass. You think eng hours are expensive now, just wait until this req comes into force.

Don't know about all states, but for 2 lane or more roads, absolutely:

Florida law also includes a bill that allows police to ticket those driving too slowly in the left lane when another car is trying to pass them. This offense puts points onto the driver’s license and carries a ticket fee of $143. What’s most striking with this bill is the fact that drivers could receive the ticket even when they are moving at the posted speed limit.

WRT to your "exchange between equals", I'm all for market wages, however, that also means employers can't go petition congress to increase immigration to generate additional labor supply. If labor has to abide by fixed supply and demand, business has to abide by fixed supply and demand. So if nobody wants a job at $16/hr, business can't claim labor shortage and ask to let Joe in on a visa to take that job, instead they need to offer $20, $50, $100, etc until someone agrees to take that job.

I think you missed the "regretted attrition" part of the article, these are people Amazon absolutely does not want to lose.

Go focuses on being readable, maintainable, portable, safe, and fast. It's really hard to deviate from the "expected" way to write Go, and that's the wole point. There are no affordances for clever abstractions and tricks in Go, and the payoff is the code is (usually) instantly familiar, has predictable overhead, and is relatively performant. I've done production work with just about every language that exists and I've seen some borderline unreadable C#, C++ and Java. That said, there 2 things I reproach Go, 1) that they elected to go with a GC instead of reference counting, and 2) the Java-like forced directory layout. Ignoring those "chpices" the compiler is top notch, the tooling arguably the best out there, the test env is a stroke of genius, and the language is dead simple. People who dislike Go tend to be the same whose code is unintelligible to to anyone but themselves since they have some "Einstein level" insight into how to meld inheritance and abstractions to completely obfuscate a code base. If it wasn't for the GC drawback, I'd be huge proponent of Go. I know you can disable the "auto" GC, but you still have to run it manually which is the definition of non-deterministic when dealing with multi-threaded apps.

You're right, (B) is the correct answer, this inflation event is primarily supply side driven. Since the primary issue we're dealing with is that supply remains constrained, the Fed has 1 of 2 options, increase supply or reduce demand. The Fed doesn't have effective tools to increase supply, though one could argue low rates could stimulate capital investment to eventually increase supply, so the Fed has chosen to pursue demand destruction via increased effective rates. Bezos may not be my idol, but he's right, inflation and wealth taxes are completely uncorrelated. The issue is the only tool available to fight inflation right now is to inflict intense financial pressure on lower / middle class consumers so they pull down the demand curve. Biden is dragging the wealthy into the discussion is a political move to make it appear they will "share the pain" which is complete nonsense. They will share the pain about as much as Putin is noticing how expensive groceries are in Russia. Confiscating the entire 4.5T in wealth from the 400 richest Americans would have virtually zero impact on this inflationary cycle.

I could argue that in tech, Asian candidates are favored over equally qualified alternatives, and that would be borne out by the fact that Asians are overrepresented in tech. My question to you, given that Asians, which includes dark-skin hued Indians, are statistically favored, is that racism or not? If not, then there's nothing to see here, but if it is, is the solution to discriminate against Asians?

You need to go visit again, it's much worse than even 10 years ago. I've not only seen poo, I've had the joy of witnessing someone dropping a deuce in broad daylight on a relatively busy sidewalk. It's not knee deep feces everywhere, but finding a pile would be one of the easier items on a scavenger hunt.

Quick somebody call Guido and tell him significant whitespace is dead and to rev Python ASAP!

AUM and DDR5 aren’t really comparable, AUM offers sustained 400GB/s throughput to DDR5’s peak 135GB/s. A better comparison would be if Intel included a massive addressable L3 cache.

C had loop unrolling long before Graydon even had the idea for Rust.

and to be fair, Python isn’t an OOP. Unbridled OO led to millions of years of technical debt, ironically we’ve reverted back to an abstraction of C static functions and structs with admittedly nicer semantics.

I hope they meant namespace collisions. If they’re trying to call instance methods directly via their mangled names, they’ve got bigger problems to worry about.