"it is .NET Core 3.0 which will get devs excited." really?
you sure about that?
I strongly suspect it is all more lipstick on the boar, and on the non-oinky end. again. wheeeeee.
when ".Net" was first conceived, back in the early noughties, it was for an IIS web back end. Its overall design looks more like what "they" (the object-oriented evangelists) want EVERYTHING to look like. At least, that's my perception of it.
Then MS tried to shove this down the throat of EVERY developer, in EVERY version of DevStudio, by requiring you to JUMP THROUGH HOOPS to EXCLUDE it from your C/C++ build. I mean, WHO wants that monolithic do-nothing "you must have the latest" '.Net runtime' thing installed along with your application?
Granted, the DevStudio hoops aren't THAT difficult, but it requires some specific targeted "un-tick the box" settings changes in the project, and a careful test at the end to see if it's STILL hauling in ".Not" as a dependency. It's the fact that you HAVE to do them in the FIRST place that bugs me.
To think that non-windows developers might actually USE this is laughable. Ok maybe one or two. But still...
Remember how much *hate* there was when Gnome added 'tomboy' as a dependency, which THEN caused all of the mono stuff to install along with Gnome? I do. In particular, one of the Debian packages did this. I'm not 100% sure it was all gnome desktops, in case it wasn't. But that was enough for me. I went out of my way to make sure tomboy and all of that ".Not"/mono garbage was OFF of the system!
Well maybe devs WILL get 'excited'. But perhaps that word does not mean what you THINK it means...
icon because 'facepalm'
The news I'd lke to see: a C language toolkit that wraps Win32 API calls and runs on X11-based systems with unmodified Win32 API code. You know, like 'Wine' except sanctioned by MS.