- mking1024 parentYou're being a bit disingenuous here. Other definitions of harm include: "have an adverse effect on" and "actual or potential ill effects".
- Anecdote: I have an Azure account with a monthly spend of around $100-200 (so, a very small customer). I ran into an issue with Active Directory B2C a couple of years back. I reached out - despite not having a support plan - and ended up with a Microsoft Engineer sharing my screen and helping me fix the issue.
- Being remote certainly helped Australia, but I think this "island" line is a massive cop-out.
Mainland USA only has land borders with Canada and Mexico, right? Do you believe that if those borders were impermeable that they'd have COVID beaten? And the only reason the outbreak there is so large is due to cases sneaking in from Mexico and Canada every day? In reality, the vast vast majority of USA's COVID cases came from the exact same place as the majority of Australia's COVID cases - people flying in, and community transmission.
Yes, Australia has had a few advantages when fighting COVID. But hand-waving Australia's success away as "it's an island!" just serves to ignore the lessons that could be learned from Australia's response.
- Of those 20 years you mentioned, the party we're discussing has been in power for around 14 of them - and the 6 years preceding that. I'd say the party that has been in power for over 75% of the last 25 years - and has actively campaigned against acting to reduce emissions - is somewhat responsible.
But what I don't understand is the relevance of climate change to the topic at hand: the assistance and access legislation harming Australian tech companies. And I'm still not sure what your original point was ("Australia's abysmal record on climate change affords it no sympathy"). Were you saying saying that Australia's tech industry deserves to be destroyed because a slim majority of the country keeps voting for a party that is, among other things, hesitant to act to reduce emissions?
- Really? We haven't had any problems with our .NET Core projects (a few web apps running on core and a bunch of libraries targeting core). In addition, ASP.NET Core (on .NET core) has been a great stack so far (using it since beta5); I feel very productive with it as well as enjoying the development experience. Why do people need to get fired for this? It doesn't seem like it will be hard to move from project.json back to (a new and improved) csproj.
- In the .NET world we have Dapper (https://github.com/StackExchange/dapper-dot-net), which lets us write queries in plain old SQL. It's a very useful little library. I believe StackOverflow use it for their data access.
Example:
var posts = connection.Query<Post>("select * from posts where user_id = @UserId", param: new { UserId = 1 });