r/programming • • May 18 '20

Microsoft: we were wrong about open source

https://www.theverge.com/2020/5/18/21262103/microsoft-open-source-linux-history-wrong-statement
642 Upvotes

284 comments sorted by

View all comments

Show parent comments

136

u/jl2352 May 18 '20

There has also been a cultural change in how businesses see software.

I remember during my internship the team I was in bought about 100 licenses for WinRaR. At the time I said they could just use 7-Zip. It was blackballed because ... it was free. Literally the fact it was free meant it would never be considered. Paid software was just seen as superior and more reputable due to a tonne of presumptions.

That still exists today. Not to the same prelevance. Today using free is considered.

77

u/master5o1 May 18 '20

With a lot of things, when you pay for something it gives you someone to blame if that thing goes wrong.

0

u/[deleted] May 19 '20

[deleted]

2

u/monsto May 19 '20

You can't be serious. /s

→ More replies (1)

16

u/doctorcrimson May 19 '20 edited May 19 '20

To be fair the early versions of 7zip sucked and a lot of open source software has support or updates cut off at random.

Even worse is when modernization of open source starts and the company working on it suddenly runs out of money so you get a less stable release than before with the new features you require and no option to use an updated version of the old suite/client/UI.

If somebody made that WinRar decision today I would call them stupid, though.

4

u/Angeldust01 May 19 '20

bought about 100 licenses for WinRaR

Greatest business day for Winrar, ever.

9

u/ptoki May 19 '20

Actually the explanation is even simpler.

Ignorance. When given WinRaR and 7Zip it takes literally 2-3 months of setting it for a limited number of people/users and checking if there are any hard problems with it.

If back in time someone decided that they cant use 7zip "because" then that was just ignorance. No need to call it any different.

There is also other side of this story. Cost of WinRar per user is small. If the user wastes more than hour of learning 7zip then almost all of the profit is lost. At least for about a year or two (when you might need to renew support to get more updates - if needed).

Today the challenge is different. Lots of stuff is free now. But the commercial free comes with vendor lock-in.

If you are not ignorant you can avoid the big problem which this makes. Yet a ton of PMs dont see a reason to go with terraform instead of straight aws, azure, google cloud solutions.

Ignorance, ignorance everywhere.

2

u/pdp10 May 19 '20

Install them side-by-side. Instrument systems to see how often each is used.

Debian Linux has a "popularity contest" that does something like that. You can use that as a model, or you can do something like write a wrapper script that adds some explicit logging.

1

u/MrEllis May 19 '20

I've never heard of that service. What is the advantage of Terraform over strait aws/gcs/azure?

4

u/ptoki May 19 '20

Its kind of abstraction layer.

Instead of coding AWS api or google api you code in terraform api and it will translate the calls and will manage all the underlying vendor services.

Its still possible that it will flop but there is a chance that you will be able to leverage all the profits of multiple cloud providers.

Im not an expert on this but thats the way people can make their infrastructure more bulletproof.

3

u/[deleted] May 19 '20

Terraform allows you to create stuff regardless of the cloud backend, so you can deploy to azure, AWS, gcp, all from Terraform

12

u/badtux99 May 19 '20

Theoretically.

Reality is that you're going to have to do a lot of modification of your Terraform recipes to move anything between clouds.

Still better than a complete rewrite to something entirely new.

5

u/[deleted] May 19 '20

Exactly. Terraform still tightly couples a module's implementation to the cloud vendor it was implemented for. Your Terraform for defining IAM roles WILL NOT WORK IN AZURE. FULL STOP.

That being said, the advantages around using Terraform are countless. Let's compare it to AWS's equivalent: cloudformation. With cloudformation, you have to define everything for your infrastructure in a single file which relates to a single stack. If you want to logically organize your infrastructure, you gotta make separate cloudformation stacks with separate definitions. Need to reference a resource from your IAM stack in your Lambda stack. Global variables. AWS Account wide string based global variables. Good luck refactoring that.

Let's say I want to define some infrastructure which directly competes with AWS. Say I want to setup some monitors in DataDog becuause my enterprise cut a sweet deal with their data aggregation services. Terraform: no problem, there is a module for that; you can define you app's infrastructure in the same language as your app's monitoring. AWS: yeeeeaaaaa you know what, I'm gonna need you to define those resources in a way which enriches AWS' bottom dollar; no outsiders allowed!

Hey I want to use this infrastructure as code tool to see what the heck will be changed in the infrastructure when I change this variable name. Cloudformation: OK I will tell you what resources will change, but I will barely tell you anything about what actually will change in that resource Terraform: I will change this variable from state X to Y. Additionally this is a update-in-place change which means I will not destroy this resource to perform that change.

Let's say I want to setup a database with a configuration where there is a single master instance and several read-slaves. AWS: yea you know what go ahead and duplicate all of your database definitions; make as much code to define the read slaves as it takes to define the single master instance. Terraform: there are tools which exist to reduce code duplication. You can make 1 piece of code define all of your read slaves.

Terraform is vastly superior tool when compared to equivalent solutions like cloudformation. But let's please stick to the facts when discussing this engineering tool, and not let ourselves buy into the whole: write once run everyone BS that everyone is selling. That just is not representative of the reality of the tool, but should not discourage the discussion about the relative pros and cons of each tool.

Please if I have misconstrued any facts I would like to see some evidence about this so I can intelligently engineer solutions in the future.

Source: in the software engineering trenches 9-5 for a decade or so

→ More replies (5)
→ More replies (1)

0

u/meneldal2 May 19 '20

Over time you'd lose more time with WinRAR because it's less efficient.

0

u/[deleted] May 19 '20

[deleted]

1

u/meneldal2 May 19 '20

I'm more thinking about when you need to compress stuff, smaller files are also faster to send. Decompression is about the same obviously unless it's a huge file.

0

u/[deleted] May 19 '20

[deleted]

→ More replies (3)

1

u/double-you May 19 '20

You'd only lose time if you do nothing when the files are being sent. The overhead and variance of people warbling around is much more than what the file size might ever give you.

→ More replies (3)

1

u/ptoki May 19 '20

Maybe. But first you need to make at least simple POC and measure this or that.

Stating that A is better than B with no proof is silly. There is a multitude of cases and one organization needs speed, other needs reliability of handling large files, other will be more focused on archive size. 7zip may not be most efficient in all cases.

1

u/meneldal2 May 19 '20

There are plenty of benchmarks and 7-zip wins for both speed and efficiency against WinRAR. For reliability I'm pretty sure either is very stable now, you're not taking any risks.

2

u/pdp10 May 19 '20

At the time I said they could just use 7-Zip.

Earlier than your case, we once had a small panic about the licensing of WinZip. It must have been raised by one of our VARs or something, because by a week later when another team had tracked down an open-source replacement, the concern was already over.

Paid software was just seen as superior and more reputable due to a tonne of presumptions.

In the early days, the "open source movement" spent a considerable time distinguishing itself from shareware and freeware.

Then there's also the old descriptive: "reassuringly expensive".

1

u/audion00ba May 19 '20

Paying is arguably better business, assuming support is included where support means SLA with hard deadlines (which I have not seen any vendor do, other than "engineer on site within X hours/days").

→ More replies (2)