I think it's just such a clear business-razor because of the cloud: can I take my app and spin up a bajillion cheapo servers with no licensing costs using that stack?
If the answer for .Net was 'no' then there are meaningful domains where people would just jump ship in a second. Research, academia, teaching, and certain government areas pop to mind. Keeping Linux support, because of that server dominance, is a core concern for them.
There's also the context to consider: if I'm scanning someone elses' code in an unfamiliar subsystem, there's a high chance there is a bug or something time critical. Not the time for extra annoyance and work.
Finding code that suddenly zigs where all the rest of the systems code zags takes extra mental overhead. It's annoying, and misleading. All too frequently bugs are coupled to such style violations, adding extra frustration around such misleading code.
> All too frequently bugs are coupled to such style violations
That's a really good point actually. Style violations can make the code look like it does something that it doesn't, `if (a=b)`, missing curly brackets in C/C++, missing semicolons in Javascript, mismatched brackets, etc. An autoformatter can make it more obvious when you've done something wrong.
Parler ignored repeated notices of TOS violations from Amazon, were given a chance to address their frequent TOS violations and incomplete enforcement of TOS violation notices, and came back with a very weak plan while still ignoring specific TOS violations AWS had notified them of.
Parler had ample time. They ignored warnings, they did not address their TOS violations. Then their contract was terminated, and AWS is helping them migrate after the fact. Parler displayed an ignorance of the law and how web hosting works.
Web companies that repeatedly violate the TOS of their hosts deserve to be at the mercy of their failover plans. That responsibility is borne by the web company, not the host.
That you brought that interview up at all guarantees you didn't listen to it.
Abigail Shrier is very supportive of transgendered people, and conveyed in some depth her numerous interviews with medical health professionals who provide aspects of gender reassignment and agreed with their unequivocal experience that it's helping people.
Her book is specifically about statistically aberrant behaviour in small groups of female teens that show atypical behaviour compared to normal transgendered people that are being given hormones and life altering treatments with minimal oversight, often to their lasting detriment.
> Spotify employees have the right to voice their concerns if the company they work for is alienating them.
For sure... So why is Bill Cosby still on Spotify?
And if transgender rights are our priority, why are endless numbers of outspoken anti-trans a-holes like Ted Nugent still on there?
Or, hey, what about the incredible number of songs stuffed with the n-word, the b-word, the f-word, the r-word, the c-word, anti-trans sentiment, and detailed descriptions of lawbreaking and violence?
I'm unsympathetic to shallow, hypocritical, and inconsistent morality plays.
There are also some critical tooling gaps that mean .Net Core is still broken for scenarios that worked a decade ago (FSI package management with F#, specifically).
Sorry for the loose term. Not package management a la NuGet, but how packages and their references are handled (ie managed), so that they're not available and operative in FSI on .Net Core in VS.
The API is made to make automation around calendaring tasks easy. You can pull up appointments, see who booked them, and manage their state. (https://developers.google.com/calendar/overview)
Tracking activity in activity planning software isn't quite as nefarious as looking at peoples emails. Pulling up the meeting bookers boss and sending an email to them & legal is pretty bog standard integration work.
As stated, I can't see any requirement for a client-side footprint...
> but does that cost you the opportunity to make even more than that, given you're probably moving slower or at least less efficiently than you otherwise could?
The potential opportunity of fast-moving cloud features needs to be weighed against the opportunity costs of slow-moving cloud features. Where bespoke solutions can immediately provide tailored performance and maximize technical capabilities, a missing feature in any of your cloud providers services can be a showstopper or unmitigatable roadblock. And while lots of the technology is past the bounds of reasonable economical replacement, some of the technologies being shared through the cloud are nigh unfathomable to recreate.
Which is to say that the black ju-ju behind Windows update probably takes making a new MS to build up to present maturity, and unless you're a certified "big boy" letting small teams somewhere else fully dictate what you can and can't do at service boundaries probably impacts you in the long run.
Based on that, and IMO/IME: the answer isn't a binary choice but a constantly shifting point on a spectrum between the two, where on-premise/local-cloud and remote-cloud services are aware of one another and maximize capabilities while minimizing costs. Hybrid installations are just stronger, and are easier to reshape according to costs.
Another way of framing that: BOFHs went from being necessary to the business to preventing the business from acheiving its goals, and got replaced by competition that was more amenable at a higher price.
They weren't seen as so unprofitable they had to be eliminated, but unprofitable enough that competition could triangulate their price vs pain.
If the answer for .Net was 'no' then there are meaningful domains where people would just jump ship in a second. Research, academia, teaching, and certain government areas pop to mind. Keeping Linux support, because of that server dominance, is a core concern for them.