This .NET core is heading for a disaster. It wants to go the Linux way with nuget packages, but my experience with all of this is that packages can break things. When I develop for .CORE I have lost control over my code and am at the mercy of others creating packages.
I never have a code version that can be predictable stable.
Gotta learn how to stay on top of your csproject file and learn how to use build targets. .nets package management is excellent was one of the first modern languages with an actual one built into the language itself. Every other one (JS)npm,(Python)pip,(Ruby)ruby gems neglect framework targets and you have to use some other tool on top of the rudimentary package manager usually developed by a third party (nvm,anaconda,rvm, etc...) package management is an afterthought and still suffer all of the problems you talk about.
Where Microsoft is behind right now is that they haven't migrated to a linux kernel and re-implemented the windows apis on top of a core that supports lxc. The container solution on windows is the most bastardized thing i've ever seen.
I keep on inheriting these projects that tried all these packages and failed miserably over time when these packages grows out of tune.
Projects that can be perfectly done by one single person, now requires a complete SCRUM team, a PO and SCRUM master plus many dependencies of code by other SCRUM teams, specialized deployment tools, specialized unit tests and worst of all these projects SUCK in performance and the ability to easily adapt them!
The other issue is they keep on changing these packages every single day. You blink and they just released yet another new version that breaks older code. 90% of out time is wasted on keeping up with the rat race while we could have used this in productivity.
There is one good thing in all of this, it forces my mind to keep on evolving and find solutions where others fail. All these new technologies are destined to make projects fail, and then there is where I get hired, to save these projects.
Yep dependency hell I've seen it in python and ruby too. I think the key to mitigating that is microservices that are only doing a very niche thing with maybe 1000 lines of code. When its hard to upgrade you throw it in the trash and rewrite it with something new that's easier to deal with and up to date and only maintain the api signature. Then you split up all the monoliths into a maybe a few hundred of those. The key to making it viable is you need containers and an orchestration system to manage deploying, monitoring, recovering from faults.
Microsoft programming chief to devs: Tell us where Windows hurt you • The Register
'Will Microsoft continue to have three separate products – Visual Studio, Visual Studio for Mac, and Visual Studio Code?'
'Actually Visual Studio for Mac and Visual Studio on Windows already share a lot of components. '
'Going back to Windows desktop development, there are a confusing number of frameworks available, with Windows Forms, Windows Presentation Foundation (WPF) and Universal Windows Platform (UWP). '
'So Windows developers will get all the advancement we have made in our .NET Core framework and runtime."'
'Build "We're going to reinvigorate Windows desktop development," claimed Julia Liuson, Microsoft's corporate VP responsible for developer tools and programming languages. '
5 comments
0 u/roznak [OP] 10 May 2018 23:22
This .NET core is heading for a disaster. It wants to go the Linux way with nuget packages, but my experience with all of this is that packages can break things. When I develop for .CORE I have lost control over my code and am at the mercy of others creating packages.
I never have a code version that can be predictable stable.
0 u/AnthraxAlex 11 May 2018 00:48
Gotta learn how to stay on top of your csproject file and learn how to use build targets. .nets package management is excellent was one of the first modern languages with an actual one built into the language itself. Every other one (JS)npm,(Python)pip,(Ruby)ruby gems neglect framework targets and you have to use some other tool on top of the rudimentary package manager usually developed by a third party (nvm,anaconda,rvm, etc...) package management is an afterthought and still suffer all of the problems you talk about.
Where Microsoft is behind right now is that they haven't migrated to a linux kernel and re-implemented the windows apis on top of a core that supports lxc. The container solution on windows is the most bastardized thing i've ever seen.
0 u/roznak [OP] 11 May 2018 01:16
I keep on inheriting these projects that tried all these packages and failed miserably over time when these packages grows out of tune.
Projects that can be perfectly done by one single person, now requires a complete SCRUM team, a PO and SCRUM master plus many dependencies of code by other SCRUM teams, specialized deployment tools, specialized unit tests and worst of all these projects SUCK in performance and the ability to easily adapt them!
The other issue is they keep on changing these packages every single day. You blink and they just released yet another new version that breaks older code. 90% of out time is wasted on keeping up with the rat race while we could have used this in productivity.
There is one good thing in all of this, it forces my mind to keep on evolving and find solutions where others fail. All these new technologies are destined to make projects fail, and then there is where I get hired, to save these projects.
0 u/AnthraxAlex 11 May 2018 01:36
Yep dependency hell I've seen it in python and ruby too. I think the key to mitigating that is microservices that are only doing a very niche thing with maybe 1000 lines of code. When its hard to upgrade you throw it in the trash and rewrite it with something new that's easier to deal with and up to date and only maintain the api signature. Then you split up all the monoliths into a maybe a few hundred of those. The key to making it viable is you need containers and an orchestration system to manage deploying, monitoring, recovering from faults.
0 u/derram 10 May 2018 23:40
https://archive.fo/0eJYU :
'Will Microsoft continue to have three separate products – Visual Studio, Visual Studio for Mac, and Visual Studio Code?'
'Actually Visual Studio for Mac and Visual Studio on Windows already share a lot of components. '
'Going back to Windows desktop development, there are a confusing number of frameworks available, with Windows Forms, Windows Presentation Foundation (WPF) and Universal Windows Platform (UWP). '
'So Windows developers will get all the advancement we have made in our .NET Core framework and runtime."'
'Build "We're going to reinvigorate Windows desktop development," claimed Julia Liuson, Microsoft's corporate VP responsible for developer tools and programming languages. '
This has been an automated message.