5 ms·
Just check kernel32.dll, it was CLEAN for years, now there are references to .net framework and it is becoming a mess. Believe me, Windows are becoming a mess,
by _o_ 8y ago
Just check kernel32.dll, it was CLEAN for years, now there are references to .net framework and it is becoming a mess. Believe me, Windows are becoming a mess, I never liked linux (actually I hated it) but the directions that Windows are taking are worrying (it is the same perspective when I say linux is becoming a bloated piece of , with each release it is becoming worse but at least it is open source. But dont get me wrong, I am writting this from purely technical perspective, for a typical user, everything is just fine. No need to worry, except maybe Windows 365 in 2020.
(I will refrain from further commenting as my technical perspective is hitting into large fanbase of both systems and karma here is really not beeing able to handle it. At the end it is the terror of the less technical average.)
- Const-me 8y agoThe dependencies with long DLL names beginning with api-ms-win- are unrelated to .NET framework. Here’s more info: https://scissortools.wordpress.com/2011/11/23/more-on-windows-7s-undisclosed-api-layering/ https://scissortools.wordpress.com/2011/11/23/more-on-window...
- _o_ 8y agoI am not talking about dependencies, I am talking about COM exports from kernel32, than manifests, multiple versions of same library on the system which now matches linux xzy.so,xzy.so.1,... they had a clean userspace with backward compatibility, now they are having a mess.