61–70 of 348 posts
Earlier quoted context omitted.
It just makes sense to run a server OS that works well and is full-featured when there is no GUI.
You know, I was thinking this, but honestly how much overhead is the Windows GUI when no one is logged into it? I know it's not nothing, but I suspect it's not that much, is it?
I bought books such as Linux Programming Interface to learn linux so that I can apply for jobs. Later I discovered that when the companies say Linux, they don't mean writing native applications on Linux, but that they are actually talking about java applications on app servers such as JBoss. Does anyone write native applications like thick client native applications on Windows which is also rare these days.
You'd think that C++ would be relatively portable (though not as portable as Java), but you'd be mistaken. So many things are not portable.
This is hardly surprising. Not to crap on MS, but I do think Linux has traditionally just been a better operating system for servers, probably due to the fact that that's where most of the funding for Linux ends up going, with the desktop versions of Linux being sort of secondary. It doesn't help that a lot of serverey software is kind of designed with POSIX-ey stuff in mind. Node.js took awhile to get Windows suppor…
Windows came from the single-user domain. Unix came from server space. It is literally two different evolutionary paths. From day-1, Unix was built for shared file systems, multi-user accounts, and distributed computing. Networking on Microsoft was an afterthought until the mid-90's. Sure there were token ring and banyan vines drivers in the late 80's early 90's, but that was to share a drive letter. The entire idea…
Even a simpler example though; the fact that there wasn't really a built-in analog for the "pipe" until PowerShell sort of boggles the mind. Yes, I'm aware that Windows isn't command-line focused, but it baffles me that software engineers didn't really see a need in Windows to compose programs together. (Someone, please correct me if I'm wrong on this point, I haven't touched Windows in any serious capacity in almost a decade).
Earlier quoted context omitted.
Windows came from the single-user domain. Unix came from server space. It is literally two different evolutionary paths. From day-1, Unix was built for shared file systems, multi-user accounts, and distributed computing. Networking on Microsoft was an afterthought until the mid-90's. Sure there were token ring and banyan vines drivers in the late 80's early 90's, but that was to share a drive letter. The entire idea…
I think both are a mess under the hood. I cannot make sense of where things will be configured in Linux. maybe /etc/, maybe somewhere else, with loads of setting file configurations. There's not a huge amount of consistency. What would be interesting is a complete re-imagining of a server OS. Consistent file locations for everything, which are automatically versioned a la git allowing you to roll back any specific ch…
There's a good reason why Linux absolutely dominates the server space.
Earlier quoted context omitted.
Windows came from the single-user domain. Unix came from server space. It is literally two different evolutionary paths. From day-1, Unix was built for shared file systems, multi-user accounts, and distributed computing. Networking on Microsoft was an afterthought until the mid-90's. Sure there were token ring and banyan vines drivers in the late 80's early 90's, but that was to share a drive letter. The entire idea…
I think both are a mess under the hood. I cannot make sense of where things will be configured in Linux. maybe /etc/, maybe somewhere else, with loads of setting file configurations. There's not a huge amount of consistency. What would be interesting is a complete re-imagining of a server OS. Consistent file locations for everything, which are automatically versioned a la git allowing you to roll back any specific ch…
It's as opinionated as you are.
(FWIW there has always been a level of consistency in Linux w.r.t. file paths, if you stick to your distribution maintainers packages)
I'm interested to know what the majority of the Windows machines are used for. I can't think it'd be anything other than 'big enterprise' applications, where there seems to be a lot of bespoke stuff built specifically for Windows Server (e.g. finance software, healthcare systems, marriage registration, taxi licensing, nursing home management, etc). Unfortunately this sort of stuff is fairly rare to be available in th…
Earlier quoted context omitted.
Windows came from the single-user domain. Unix came from server space. It is literally two different evolutionary paths. From day-1, Unix was built for shared file systems, multi-user accounts, and distributed computing. Networking on Microsoft was an afterthought until the mid-90's. Sure there were token ring and banyan vines drivers in the late 80's early 90's, but that was to share a drive letter. The entire idea…
I think both are a mess under the hood. I cannot make sense of where things will be configured in Linux. maybe /etc/, maybe somewhere else, with loads of setting file configurations. There's not a huge amount of consistency. What would be interesting is a complete re-imagining of a server OS. Consistent file locations for everything, which are automatically versioned a la git allowing you to roll back any specific ch…
> What would be interesting is a complete re-imagining of a server OS
Not sure how 'complete', but aren't you after something like NixOS?
Earlier quoted context omitted.
Other than bespoke enterprise apps, my guess would be the majority of the remaining Windows machines run SQL server.
Doesn't SQL server run under Wine or https://reactos.org/wiki/ReactOS ?
https://www.microsoft.com/en-us/sql-server/sql-server-downlo...
No need for emulation.
I bought books such as Linux Programming Interface to learn linux so that I can apply for jobs. Later I discovered that when the companies say Linux, they don't mean writing native applications on Linux, but that they are actually talking about java applications on app servers such as JBoss. Does anyone write native applications like thick client native applications on Windows which is also rare these days.
I'm in a bit of an odd place here, but we develop C++ on Windows (both client and server software). You'd think that C++ would be relatively portable (though not as portable as Java), but you'd be mistaken. So many things are not portable.