3 ms·
Man.. All of these words did proof you were wrong. > The difference with cargo or go or pip is that all of these are found in every linux distribution, while .
by exceptione 2y ago
Man.. All of these words did proof you were wrong.
> The difference with cargo or go or pip is that all of these are found in every linux distribution, while .net is in none.
This statement is false. It is also in arch. If it is not in debian and ubuntu, that is their fault. (But it would not surprise me, any user will soon run into the fact that even for non-obscure software there are no up-to-date packages in the main repo. The default escape hatch is to add extra repo sources, but my advice is to skip those distro's altogether anyways, unless you have very specific needs.)
But then again, if you think package management is a serious topic and then dismiss .net for the python mess, come on.
> the APIs are windows oriented?
The design of this particular API might be off. I guess this dates from the pivot to cross-platform. Usually, tuning for .net performance is better on Linux. I think nobody in MS believes in Windows as a platform really, it is a sinking ship.
- LtWorf 2y ago> It is also in arch. If it is not in debian and ubuntu, that is their fault. Of course. Microsoft is a tiny poor company. It couldn't possibly afford to hire a consultant to do this kind of job. > But then again, if you think package management is a serious topic and then dismiss .net for the python mess, come on. What mess? apt solves the mess, there's no mess if you stay away from pypi (which I advice you do). > I think nobody in MS believes in Windows as a platform really, it is a sinking ship. I'm rather sure governments will still use it in 20 or 30 years.