There's a lot more than indentation and newline policies. The default editorconfig is a few hundred lines. But there's also no reason not to standardize indentation and newline policies.
kogasa
joined 2 years ago
You say this, but C# does have official code style conventions. It's not about the compiler at all but about ensuring a relatively homogeneous coding style across the ecosystem, so a .NET dev can work on different projects without needing to refamiliarize.
For practical advice, I recommend starting a project with dotnet new editorconfig which covers many of the .NET coding conventions. If you want more strict standards you can use StyleCop, but you will need to configure it a bit to be consistent with the .NET conventions.
I can trust a user to install a part or an application, to maintain their car and update software. I don't trust them to make their own engine and drive it on public roads. Software that's responsible for the life and death of others on the road should be certified and you shouldn't touch it except in the ways that have been certified safe to do so.
"Regulation isn't working, so it's up to us to do something wildly irresponsible and dangerous instead of working towards better regulation"
Go away
No, the solution is not to deregulate automobiles.
I'm still a fan of Domino's pan pizza. A lot better than their regular pizzas IMO.
I agree totally. Ideally the car should be fully functional with barely any complex software like most cars before 2010. The only case where a failing software update should be able to brick your car is when it's fixing a low level OS bug that renders the car unsafe to drive without the update.
As distasteful as the overall story is, I'm glad the decision to have Geordi get eye surgery was walked back.
You shouldn't trust a customer to fuck with the OS of a vehicle. Vehicles aren't computers, breaking them can endanger yourself and others.
You think aircraft, space, and defence industries don't update their software...?
This is "unpopular opinion" not "wrong"