Language Selection

English French German Italian Portuguese Spanish

Microsoft and Linux must co-exist

Filed under

The fact that such a Linux pioneer as Central Scotland Police should rethink its strategy may lead some open source fans to reconsider their opinions.

The Scottish force reviewed its technology strategy and realised a standardised infrastructure was the key to increased integration with other criminal justice agencies. And, as a result, it's replacing much - though not all - of its open source infrastructure with Microsoft technologies.

Of course there is a whiff of 'man bites dog' about any story that involves companies replacing Linux with Microsoft, simply because there seems to be such a general shift towards open source, especially in the public sector.

But at the same time this case illustrates an important point.

Technology decisions are not made in isolation.
Few IT organisations have the luxury of being able to choose an all-Microsoft or an all-open source infrastructure. And even if they could, it's unlikely they would survive by doing business only with suppliers or customers that had the same simple set-up.

Co-existence and integration has to be the name of the game in IT. If you've installed a great technology that won't integrate with the rest of your - or your partner's - systems then you've wasted your money.

The history of tech is littered with the rusting hulks of companies that built great technology that just didn't fit in. Developers have to think broadly about not just what their applications or systems will do but how they will relate to the others around them.

This is likely to be one of the big challenges for open source, as at the moment Microsoft is the de facto standard for many corporate applications - especially when it comes to the desktop.

Open source can bring many benefits for its users. But if businesses that start using open source find it hard to do business as a result they will head back into the Microsoft fold.

More in Tux Machines

KNOPPIX 7.7.1 Distro Officially Released with Debian Goodies, Linux Kernel 4.7.9

Believe it or not, Klaus Knopper is still doing his thing with the KNOPPIX GNU/Linux distribution, which was just updated to version 7.7.1 to offer users the latest open source software and technologies. Read more

CentOS 6 Linux Servers Receive Important Kernel Security Patch, Update Now

We reported a couple of days ago that Johnny Hughes from the CentOS Linux team published an important kernel security advisory for users of the CentOS 7 operating system. Read more

Games for GNU/Linux

  • Why GNU/Linux ports can be less performant, a more in-depth answer
    When it comes to data handling, or rather data manipulation, different APIs can perform it in different ways. In one, you might simply be able to modify some memory and all is ok. In another, you might have to point to a copy and say "use that when you can instead and free the original then". This is not a one way is better than the other discussion - it's important only that they require different methods of handling it. Actually, OpenGL can have a lot of different methods, and knowing the "best" way for a particular scenario takes some experience to get right. When dealing with porting a game across though, there may not be a lot of options: the engine does things a certain way, so that way has to be faked if there's no exact translation. Guess what? That can affect OpenGL state, and require re-validation of an entire rendering pipeline, stalling command submission to the GPU, a.k.a less performance than the original game. It's again not really feasible to rip apart an entire game engine and redesign it just for that: take the performance hit and carry on. Note that some decisions are based around _porting_ a game. If one could design from the ground up with OpenGL, then OpenGL would likely give better performance...but it might also be more difficult to develop and test for. So there's a bit of a trade-off there, and most developers are probably going to be concerned with getting it running on Windows first, GNU/Linux second. This includes engine developers.
  • Why Linux games often perform worse than on Windows
    Drivers on Windows are tweaked rather often for specific games. You often see a "Game Ready" (or whatever term they use now) driver from Nvidia and AMD where they often state "increased performance in x game by x%". This happens for most major game releases on Windows. Nvidia and AMD have teams of people to specifically tweak the drivers for games on Windows. Looking at Nvidia specifically, in the last three months they have released six new drivers to improve performance in specific games.
  • Thoughts on 'Stellaris' with the 'Leviathans Story Pack' and latest patch, a better game that still needs work
  • Linux community has been sending their love to Feral Interactive & Aspyr Media
    This is awesome to see, people in the community have sent both Feral Interactive & Aspyr Media some little care packages full of treats. Since Aspyr Media have yet to bring us the new Civilization game, it looks like Linux users have been guilt-tripping the porters into speeding up, or just sending them into a sugar coma.
  • Feral Interactive's Linux ports may come with Vulkan sooner than we thought
  • Using Nvidia's NVENC with OBS Studio makes Linux game recording really great
    I had been meaning to try out Nvidia's NVENC for a while, but I never really bothered as I didn't think it would make such a drastic difference in recording gaming videos, but wow does it ever! I was trying to record a game recently and all other methods I tried made the game performance utterly dive, making it impossible to record it. So I asked for advice and eventually came to this way.

Leftovers: Software

  • DocKnot 1.00
    I'm a bit of a perfectionist about package documentation, and I'm also a huge fan of consistency. As I've slowly accumulated more open source software packages (alas, fewer new ones these days since I have less day-job time to work on them), I've developed a standard format for package documentation files, particularly the README in the package and the web pages I publish. I've iterated on these, tweaking them and messing with them, trying to incorporate all my accumulated wisdom about what information people need.
  • Shotwell moving along
    A new feature that was included is a contrast slider in the enhancement tool, moving on with integrating patches hanging around on Bugzilla for quite some time.
  • GObject and SVG
    GSVG is a project to provide a GObject API, using Vala. It has almost all, with some complementary, interfaces from W3C SVG 1.1 specification. GSVG is LGPL library. It will use GXml as XML engine. SVG 1.1 DOM interfaces relays on W3C DOM, then using GXml is a natural choice. SVG is XML and its DOM interfaces, requires to use Object’s properties and be able to add child DOM Elements; then, we need a new set of classes.
  • LibreOffice 5.1.6 Office Suite Released for Enterprise Deployments with 68 Fixes
    Today, October 27, 2016, we've been informed by The Document Foundation about the general availability of the sixth maintenance update to the LibreOffice 5.1 open-source and cross-platform office suite. You're reading that right, LibreOffice 5.1 got a new update not the current stable LibreOffice 5.2 branch, as The Document Foundation is known to maintain at least to versions of its popular office suite, one that is very well tested and can be used for enterprise deployments and another one that offers the latest technologies.