Ah ok. I saw there was issues with federation and communities getting blocked, didn't think either of those would be it. Thanks for letting me know!
8
A Brief Introduction to the .NET Muxer (aka dotnet.exe) - Steve Gordon - Code with Steve
(www.stevejgordon.co.uk)
When I click on it, all is I see is this 3 dots going 1, 2, 3, 1, 2, 3, 1, 2, 3,... I can get into other Communities fine.
Yes, provided you meet the criteria, so I'm guessing maybe he doesn't... or maybe he just wants to make the point that MS are earning income from this and yet not providing any more support than a free product is providing.
He's referring to Visual Studio.
Yes, that's his point. That if you've released your app close to the end of the period, then you're forced to upgrade your app right away, even just to keep getting security patches, on top of any bugs you might already be trying to get on top of with your newly released app. Other systems have a longer support period and you wouldn't be faced with that.
Sorry. Hadn't occurred to me you may not be able to see it (usually it's me who can't see things others post! 😂 ).
In a nutshell it boils down to the release schedule for .NET/C# - which people are paying to use - is too quick with too short support periods. He compares to another language, which is free (from memory I think it was Rust? I'd have to watch it again to see) which has the same short support periods, but is FREE. i.e. what are we paying for if we're not getting support for any longer than something which has the same support period for free? He's saying since MS is charging people for this, the support periods need to be longer, specifically security patches. e.g. if someone releases an app near the end of a period, then has only say 6 months before they have to upgrade it already, just to keep getting security patches. People don't have the option to stay on their stable release for a decent amount of time, even though they're paying for it. He just wants them to slow down the speed and increase the periods (we all know MS is all about pushing out new features over fixing bugs).
the .NET environment is vast and can be confusing, especially when new to it.
Yeah it was prompted by someone on Mastodon asking about it, and Rocky saw it. I saw the reply too, and thought it was still a little vague, then a few days later this blog post turns up :-)
BTW if anyone wants to follow him he's Rocky Lhotka. He's on Pixelfed too (and Bluesky), but not as much work stuff on his Pixelfed account.
I think omitting .net core is not the best decision.
Yeah that confused me a bit too, then I found he talked about it underneath the table
My high school taught Java, but I didn’t get OOP
Yes, the correct sequence of events - one thing at a time, basic programming, then OOP. :-)
Python is not that.
It's not a lot of things, which makes it poor for a teaching language.
P.S.
not just to the point of ignoring, but actively down-voting
I've been downvoted when I've made actual factual statements (which should be upvoted!) - people do like to express their displeasure 😂
I guess this community doesn’t want this kind of content, even if it’s the official dev blog
No problem. Feel free to ask me questions.
view more: next ›
Just to be clear, it's not MY book, but the book of whoever's blog that is (Michael someone) - that's the title of the blog post "My book...".