4 ms·
What I personally do not enjoy as a developer about MS products is that eventually they hit end of life and you are left hanging. With open source stuff, if the
by partycoder 9y ago
What I personally do not enjoy as a developer about MS products is that eventually they hit end of life and you are left hanging. With open source stuff, if the project is used enough there will always be some maintainer.
- tluyben2 9y agoa) not true for reasons already given here b) they are(have) open sourcing a lot of developer stuff; I didn't check but would not surprise me if this ends up on github too if it didn't already with a good OSS license
- legulere 9y agoIt seems to me like it’s the other way around. Microsoft keeps comparability forever, which also has tons of negative consequences. With Linux it seems almost like you have to recompile everything anew for each system and each updates, where tiny differences in distributions can break things.
- partycoder 9y agoDepends on your choice of distribution. Some distribution will distribute compiled binaries for each architecture. And there are flatpaks that are distribution agnostic. For your own applications you will most likely use a container anyways and that gives you fairly reproducible builds.
- gcvbvghb 9y agoJust... go away. Thanks.
- partycoder 9y agoBackwards compatibility across releases of the same product, sure. But some products hit their end of life and that's it. If a product is deprecated, it may not receive security updates or fixes and such. As a user that puts you in a tough situation. Unfortunately as a user there's not a lot you can do to influence the governance of those products or try to do something to keep them around. If the vendor decides to sunset a product that's it. That's all I am trying to say.
- Dylan16807 9y agoA statically compiled application will run for just about forever on linux. glibc has extensive backwards compatibility too. If you pack your application with its libraries, there's very little to worry about. Kernel modules need constant recompilation but that's a very separate issue from programs.
- NicoJuicy 9y agoAre you a .net developer??? Everything of MS still works, nothing has been deprecated. The comment you gave is really plain wrong.
- seanmcdirmid 9y agoWPF has seemed to basically been WinFormed, it still works, they might fix the bugs, but it isn't going anywhere and will eventually feel outdated.
- ComputerGuru 9y agoBesides the fact that you're simply not right (COM, MFC, ATL, SWF, WPF, etc are all deprecated yet still supported and maintained), how is this on topic?
- dizzy3gg 9y agoShit WPF is deprecated, whats the Microsoft preferred way to writes GUI apps on the desktop?
- ComputerGuru 9y agoThe flavor-of-the-day is UAP/UWP, which actually has awesome APIs. The only problem is that it's Windows 10+ and can't make universal or standalone binaries.
- dingo_bat 9y ago> and can't make universal or standalone binaries Highly ironic for a framework that's called Universal Windows Platform :D
- ComputerGuru 9y agoTwo different meanings of the word. I meant a single binary that can run on multiple versions of Windows. They mean universal as in one codebase that will deploy to PC, phone, and Xbox.
- seanmcdirmid 9y agoUWP also is like Silverlight more so in that it is missing a lot of stuff from the original WPF, you have to basically relearn it. However, Win2D is pretty good, nice performance.
- corndoge 9y agoelectron
- j_s 9y agoThe main problem with Microsoft in the past is that they didn't make money except by selling more software licenses. Things have begun to change with the cloud stuff, but the mentality is still there in the dev tools and frameworks - instead of "if it ain't broke, don't fix it" it winds up being "every time we move the cheese we make more money". Microsoft's incentives still don't quite align with their developer/customers, but Microsoft does an amazing job pushing toward whatever is tossed out for sale as the new & shiny each year. The entire company is an amazing marketing machine. https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ Think of the history of data access strategies to come out of Microsoft. ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET – All New! Are these technological imperatives? [...] The competition has no choice but to spend all their time porting and keeping up, time that they can’t spend writing new features.
- deleted 9y ago[deleted]