Virtually all of Microsoft Gaming revenue growth over the last few years has come from the acquisition of Activision-Blizzard.

The opinion should merely read

> The Congress shall have Power To lay and collect Taxes, Duties, Imposts and Excises

(which it does, and expounds upon)

Yes but in practice they delegate this power to the executive. Congress doesn’t run the IRS themselves after all

> Yes but in practice they delegate this power to the executive.

No, they do not delegate the power to lay (set) taxes to the executive, they do assign the executive the function of collecting the taxes laid by Congress.

> Congress doesn’t run the IRS themselves after all

The IRS doesn't freely set taxes, it collects the taxes set by Congress.

> No, they do not delegate the power to lay (set) taxes to the executive, they do assign the executive the function of collecting the taxes laid by Congress.

The quote from the constitution is "The Congress shall have Power To lay and collect Taxes," not for the executive to collect taxes. If they can delegate collecting to IRS in the executive branch, why not can they not delegate the "Power To lay" taxes?

The moment Congress authorizes that the Executive may use discretion then the Executive can effectively levy taxes. They may be wielding a bat owned by someone else, but who swings it is ultimately what's important.

Now I'm generally of the opinion that Congress shouldn't be allowed to give the Executive discretion but seems no one agrees with that and Congress would rather let the Executive write "not quite laws" on their behalf.

They don't delegate the policymaking. Tax code is always congressionally approved, and I'm unaware of any even remote argument that changing tax policy is delegated to the executive.

OTOH enforcement of congressional policies is basically always the role of the executive, so the fact that the IRS exists and does things doesn't really impact delegation.

If dead code (1) is common in your codebase then your code base is missing heaps of refactors

(1) "dead" meaning unused types, unreachable branches

Not really, no. If you use a regex library it is very likely that 80% of that code is effectively dead code.

public interfaces are not dead code

The biggest change imo is that in the aughts, the idea that children should have unfettered access to personal computers, phones, and the internet was unthinkable. Now we have millennial parents seriously arguing their kids should have smartphones in class. But all this deanonymization garbage is downstream of that vibe shift.

I don't think it's responsible to blame any specific person or company, but I certainly can't excuse the Googles, Apples, Samsungs, Facebooks etc of the world. They manufactured a culture driven by putting as many devices in front of as many people as possible, using them as much as possible, while knowing as much about them as possible to monetize their attention. The careless disregard for how that affected the developing brains of two generations of people now is irresponsible and ugly.

It seems like no one is asking the real question here, which isn't why Roblox/Discord et al need to verify the age of their users. We should be asking how in the fuck there are so many children with unsupervised access to devices that this is a real problem.

>We should be asking how in the fuck there are so many children with unsupervised access to devices that this is a real problem.

Post of the day right here.

Reason is that parents, especially young millennial parents, are overworked, underpaid, and struggling, and they grew up in a world where technology wasn't as invasive, so they are willingly naive. They get home from work and their kid won't stop crying until they put a phone/tablet in front of him/her, and if it works, it works. short term wins for long term losses.

>> We should be asking how in the fuck there are so many children with unsupervised access to devices that this is a real problem.

I mean, I had unfettered access in the 90s. And look at how well I turned out?

Wait, don't answer that.

imo audio DSP experts are diametrically opposed to AI on moral grounds. Good luck hiring the good ones. It's like paying doctors to design guns.

Not sure your analogy works, Guantanamo had no trouble hiring medical personnel

> imo audio DSP experts are diametrically opposed to AI on moral grounds.

Can you elaborate on this point? I don't know the moral grounds of audio DSP experts, and thus I don't understand why in your opinion they wouldn't take an offer if you really pay them some serious amount of money.

Just to be clear: considering what a typical daily job in DSP programming is like, I can imagine that many audio DSP experts are not the best culture fit for AI companies, but this doesn't have anything to do with morality.

In my experience, most of the people in audio DSP are musicians or otherwise very well exposed to music and the arts, and many see using AI as fundamentally immoral or unethical. It's technology designed via theft with the intent to harm professionals in these spaces.

Like I said, it's like paying a doctor to design a better gun.

Yes, but, you see, guns are merely tools. If you give these guns to the right people, they will actually create more work for the doctors, and everybody wins.

Because it's fewer hoops and hurdles than using MinGW, in my experience.

We can't even make hand driers that don't discriminate on the basis of race. You think making complex law enforcement decisions based on data is going to be easier?

There's a generation of developers who seem to have forgotten an application can open multiple windows

GUI is much more than just cross platform windowing. Which fwiw, is a mostly solved problem in Rust - there's not a bunch of reimplementation or instability. The ecosystem is solidified behind winit (*).

Also, we don't have good cross platform desktop GUI libraries in C. That's why everyone started using Electron.

(*) with some small exceptions