I guess I overdramatized the situation a bit :) It's a passionate topic for me; as somebody who has been using C# at work for 10 years now, I'm just not happy with the direction the language has been taking.
You're right, it's not impossible and in general it's not among the hardest languages to teach. But I would argue, it is heading that way.
There are already so many ways to do things in C#. For example, try explaining the difference between fields and properties; sounds easy, but making it really stick is quite a challenge. And that's one of the simplest cases (and a feature I'm 100% in favor of).
And you will have to explain it at some point, because real codebases contain these features so at some point, it'll need to be taught. Learning a language doesn't stop when you can write a simple application, it continues up until at least you're comfortable with most of its features and their practical use. The quicker one can get people to that point, the easier the language is to teach, I'd argue.
One might also argue that learning never really stops, but that's beside the point :)
In general, my issue isn't any specific feature. C# has many features that are non-trivial to learn but still great: value types, generics, expression trees. Source generators are relatively new and I like them! I like most of the things they're doing in the standard library or the runtime. Spans everywhere is a nice improvement, most new APIs are sensible and nice to use and the runtime just keeps getting faster every release. Great. It's more the pure C# language side I have an issue with.
But every language has a budget of innovation and cognitive load that you can expect people to deal with, and C# is not using its budget very wisely in my opinion.
> I guess I overdramatized the situation a bit :) It's a passionate topic for me; as somebody who has been using C# at work for 10 years now, I'm just not happy with the direction the language has been taking.
You should come engage with us on this then :)
We do all our design in the open on github. And a lot of us are available to chat and discuss all this stuff in Discord and the like :)
> C# is not using its budget very wisely in my opinion.
I can promise you. Every feature you think are great had similar detractors over the years. EverySingleOne :)
> C# similarly has old warts that are discouraged now. .NET Framework is a great example (completely different from modern c#, which used to be called "dotnet core"). WPF and MAUI are also examples. Or when "dynamic" was used as a type escape hatch before the type system advanced to not need it. ASP being incompatible with ASP.NET, the list goes on.
Almost all of this is incorrect or comparing apples to oranges.
.net framework and .net core are runtime and standard library impl, not languages. C# is a language that can target either runtime or both. Framework is still supported today, and you can still use most modern C# language features in a project targeting it. WPF and Maui are both still supported and widely used. ASP predates .net - c# was never a supported language in it. ASP.net core has largely replaced ASP.net, but it's again a library and framework, not a language feature.
Dynamic in c# and the dlr are definitely not widely used because it's both difficult to use safely and doesn't fit well with the dominant paradigm of the language. If you're looking for STD lib warts binaryserializer would have been an excellent example.
> The order directs Attorney General Pam Bondi to create an “AI Litigation Task Force” within 30 days whose "sole responsibility shall be to challenge State AI laws" that clash with the Trump administration's vision for light-touch regulation.
The EO isn't about Federal Preemption. Trump's not creating a law to preempt states. So a question about how Federal Preemption is relevant is on point.
> My Administration must act with the Congress to ensure that there is a minimally burdensome national standard — not 50 discordant State ones. …
Sounds like leaving it up to Congress! But then the administration vows to thwart state laws despite the vacuum of no extant preemption, so effectively imposing a type of supposed Executive preemption:
> Until such a national standard exists, however, it is imperative that my Administration takes action to check the most onerous and excessive laws emerging from the States that threaten to stymie innovation.
So preemption link is relevant, I think; and at any rate, helpful to give background to those not familiar with the concept, which constitutes the field against which this is happening.
Also why are they small federal government states rights for things but big federal government centralized power for this? It doesn't make sense to me.
I think the message between the lines is what's important, and it goes like this:
"We in the executive branch have an agreement with the Supreme Court allowing us to bypass congress and enact edicts. We will do this by sending the Justice Department any state law that gets in the way of our donors, sending the layup to our Republican Supreme Court, who will dunk on the States for us and nullify their law."
We don't have to go through the motions of pretending we still live in a constitutional republic, it's okay to talk frankly about reality as it exists.
It goes deeper than that - the Supreme Council will issue non-binding "guidance" on the "shadow docket", so that when/if the fascists/destructionists [0] lose the Presidency, they can go back to being obstructionists weaponizing high-minded ideals in bad faith. As a libertarian, the way I see it is we can disagree politically on what constitutes constructive solutions, but it's time to unite, stop accepting any of the fascists' nonsense, and take back the fucking government - full support for the one remaining mainstream party that at least nominally represents the interests of the United States, while demanding they themselves stop preemptively appeasing the fascists. The Libertarian, Green, or even new parties can step up as the opposition. Pack the courts with judges that believe in America first and foremost, make DC and PR states to mitigate the fascists' abuse of the Senate, and so on. After we've stopped the hemorrhaging, work on fundamental things like adopting ranked pairs voting instead of this plurality trash.
[0] I'd be willing to call them something else if they picked an honest name for themselves - they are most certainly not "conservatives"
It's right in the text of the EO: they intend to argue that the state laws are preempted by existing federal regulations, and they also direct the creation of new regulations to create preemption if necessary, specifically calling on the FCC and FTC to make new federal rules to preempt disfavored state laws. Separately it talks about going to Congress for new laws but mostly this lays out an attempt to do it with executive action as much as possible, both through preemption and by using funding to try to coerce the states.
There's a reasonable argument that nationwide regulation is the more efficient and proper path here but I think it's pretty obvious that the intent is to make toothless "regulation" simply to trigger preemption. You don't have to do much wondering to figure out the level of regulation that David Sacks is looking for.
This is quite literally going to lead to a Supreme Court case about Federal Preemption. Bondi will challenge some CA law, they will lose and appeal until they get to the Supreme Court. I don't have any grace to give people at this point, you have to be willingly turning a blind eye if you do not see where this will end up.
Federal preemption requires federal law (aka laws written by congress). How else would it get to the supreme court?
The EO mentions congress passing new law a few times in addition to an executive task force to look into challenging state laws based on constitutional violations or federal statues. That's the only way they'd get in front of a judge.
If the plan is for the executive to invent new laws it's not mapped out in this EO
> Federal preemption requires federal law (aka laws written by congress). How else would it get to the supreme court?
1. No federal preemption currently. (No federal law, therefore no regulation on the matter that should preempt.)
2. State passes and enforces law regarding AI.
3. Trump directs Bondi to challenge the state law on nonsense grounds.
4. In the lawsuit, the state points out that there is no federal preemption; oh yeah, 10th Amendment; and that the administration's argument is nonsense.
5. The judge, say Eileen Cannon, invalidates the state law.
6. Circuit Court reverses.
7. Administration seeks and immediately gets a grant of certiorari — and the preemption matter is in the Supreme Court.
> passing new law … only way they'd get it in front of a judge.
The EO directs Bondi to investigate whether, and argue that, existing executive regulations (presumably on other topics) preempt state legislation.
Regardless, the EO makes it a priority to find and take advantage of some way to challenge and possibly invalidate state laws on the subject. This is a new take on preemption: creation of a state-law vacuum on the subject, through scorched-earth litigation (how Trumpian!), despite an utter absence of federal legislation on the matter.
the Task Force can try to challenge state AI laws. they can file whatever lawsuits they want. they will probably lose most of their suits, because there's very little ground for challenging state AI regulations.
> How is it possible that other users of Aurora aren't experiencing this issue basically all the time? How could AWS not know it exists?
If it's anything like how Azure handles this kind of issue, it's likely "lots of people have experienced it, a restart fixes it so no one cares that much, few have any idea how to figure out a root cause on their own, and the process to find a root cause with the vendor is so painful that no one ever sees it through"
An experience not exclusive to cloud vendors :) Even better when the vendor throws their hands up cause the issue is not reliably repro'able.
That was when I scripted away a test that ran hundreds of times a day on a lower environment, attempting repro. As they say, at scale, even insignificant issues become significant. I don't remember clearly, I think it was a 5-10% chance that the issue triggered.
At least confirming the fix, which we did eventually receive, was mostly a breeze. Had to provide an inordinate amount of captures, logs, and data to get there though. Was quite the grueling few weeks, especially all the office politics laden calls.
I've had customers with load related bugs for years simply because they'd reboot when the problem happened. When dealing with the F100 it seems there is a rather limited number of people in these organizations that can troubleshoot complex issues, that or they lock them away out of sight.
It is a tough bargain to be fair, and it is seen in other places too. From developers copying out their stuff from their local git repo, recloning from remote, then pasting their stuff back, all the way to phone repair just meaning "here's a new device, we synced all your data across for you", it's fairly hard to argue with the economic factors and the effectiveness of this approach at play.
With all the enterprise solutions being distributed, loosely coupled, self-healing, redundant, and fault-tolerant, issues like this essentially just slot in perfectly. Compound this with man-hours (especially expert ones) being a lot harder to justify for any one particular bump in tail latency, and the equation is just really not there for all this.
What gets us specifically to look into things is either the issue being operationally gnarly (e.g. frequent, impacting, or both), or management being swayed enough by principled thinking (or at least pretending to be). I'd imagine it's the same elsewhere. The latter would mostly happen if fixing a given thing becomes an office political concern, or a corporate reputation one. You might wonder if those individual issues ever snowballed into a big one, but turns out human nature takes care of that just "sufficiently enough" before it would manifest "too severely". [0]
Otherwise, you're looking at fixing / RCA'ing / working around someone else's product defect on their behalf, and giving your engineers a "fun challenge". Fun doesn't pay the bills, and we rarely saw much in return from the vendor in exchange for our research. I'd love to entertain the idea that maybe behind closed doors the negotiations went a little better because of these, but for various reasons, I really doubt so in hindsight.
[0] as delightfully subjective as those get of course
Theoretically you're supposed to assign lower prio to issues with known workarounds but then there should also be reporting for product management (which assigns weight by age of first occurrence and total count of similar issues).
Amazon is mature enough for processes to reflect this, so my guess for why something like this could slip through is either too many new feature requests or many more critical issues to resolve.
You're talking about the mostly peaceful protesters who tried to burn down the Federal building in Portland for over 200 nights, right? Sedition and insurrection.
> tried to burn down the Federal building in Portland for over 200 nights
If you're pissing your pants in fear of people who fail to do something 200 nights in a row, I'd argue that says a lot more about you than it does them.
Can I say Singletons are not recommended but also agree that there are contexts where it's an "okay enough" option? Singetons are never the "best option" in modern software, but it's not the "worst" in every case either.
Now, filling your code base with incorrect calculations: pretty much always a bad idea.
Did Dominion have a party affiliation? I would assume we just went from neutral party affiliation to strong party affiliation, not from one party to another.
That’s two reductive and poor arguments. Both sides fallacy doesn’t fly in 2025.
Voting machine anxiety for lack of a better term has been a presence for some time and isn’t a partisan issue. What is a partisan issue is President Trump’s baseless allegations re the election he hasn’t acknowledged losing in 2020.
Party affiliation is absolutely an issue with respect to Marvel villain parody that the modern Republican Party has become. I can’t read the article because Substack, but if the new owner is in fact a MAGA guy, (and this isn’t just drama) that’s a big problem.
reply