What flavor of linux to replace windows?
-
@Donahue said in What flavor of linux to replace windows?:
For CAD, one thing that was mentioned and is very true, is that we constantly have to share CAD files with customers, and they are all using either Autocad or Solidworks. While those files dont have to be the native files, there are some more agnostic file types, it does make is simpler if we use the same applications as our customers. However, with that being said, I can easily see something like cloud versions being more common place in the next 5 years. We may not be able to replace the legacy way to do it now, but that will eventually change.
We use TransMagic and it is an absolute beast. Amazing software. We use SolidEdge and have to translate CATIA occasionally and a TON of STEP files. But, again, it's Windows only.
-
@scottalanmiller said in What flavor of linux to replace windows?:
@flaxking said in What flavor of linux to replace windows?:
What are the ERP application's dependencies?
.Net requires a Windows licence, but I believe Mono is supposed to be able to replace .Net 4.5 with feature parity
.NET not only doesn't require Windows, it's officially platform agnostic. Mono is basically dead because Microsoft moved .NET to being universally available. Not that Mono was bad, it was just never as good as "real" .NET. But now that both .NET and Visual Studio tools for it are available on Linux and MacOS too, there is no call for Mono really (and it will essentially vanish soon.)
https://www.microsoft.com/net/learn/dotnet/hello-world-tutorial
-
@JaredBusch said in What flavor of linux to replace windows?:
@scottalanmiller said in What flavor of linux to replace windows?:
@flaxking said in What flavor of linux to replace windows?:
What are the ERP application's dependencies?
.Net requires a Windows licence, but I believe Mono is supposed to be able to replace .Net 4.5 with feature parity
.NET not only doesn't require Windows, it's officially platform agnostic. Mono is basically dead because Microsoft moved .NET to being universally available. Not that Mono was bad, it was just never as good as "real" .NET. But now that both .NET and Visual Studio tools for it are available on Linux and MacOS too, there is no call for Mono really (and it will essentially vanish soon.)
https://www.microsoft.com/net/learn/dotnet/hello-world-tutorial
.Net Core and .Net Full are not the same. You can't try and run a compiled .Net Full app on .Net Core, but you can try to run it on Mono
-
@scottalanmiller said in What flavor of linux to replace windows?:
@Donahue said in What flavor of linux to replace windows?:
As far as the ERP, I don't know specifically what part of the application makes it dependent on windows, and honestly, I doubt the software company does either. But, I don't see this particular ERP as being a long term solution for us.
I would guess all of it. It's almost certainly written in 1990s era Windows desktop code.
If all of it is, then there is a good chance it can run using Wine. Not sure if it would be against the EULA of the runtimes though
-
@flaxking said in What flavor of linux to replace windows?:
@scottalanmiller said in What flavor of linux to replace windows?:
@Donahue said in What flavor of linux to replace windows?:
As far as the ERP, I don't know specifically what part of the application makes it dependent on windows, and honestly, I doubt the software company does either. But, I don't see this particular ERP as being a long term solution for us.
I would guess all of it. It's almost certainly written in 1990s era Windows desktop code.
If all of it is, then there is a good chance it can run using Wine. Not sure if it would be against the EULA of the runtimes though
Would be super unlikely for there to be a EULA requiring Microsoft branded OS libraries. Possible, but crazily unlikely.
-
Choosing .NET Core or .NET Framework depends on your need.
https://docs.microsoft.com/en-us/dotnet/standard/choosing-core-framework-server -
@black3dynamite said in What flavor of linux to replace windows?:
Choosing .NET Core or .NET Framework depends on your need.
https://docs.microsoft.com/en-us/dotnet/standard/choosing-core-framework-serverSummary.... .NET Core when you are a competent developer. .NET Framework when you are using legacy crap that you can't get away from.
They make it pretty clear which is first class and which is a crippled fallback.
