They barely have any revenue and they're struggling. It's probably one of the next companies to be acquired in the coming years.
I have always wondered what this enterprise support means? So if a big company starts using vagrant, they would dole out 100k for a support contract? I find this hard to believe but what do I know.
My enterprise company wont even get us Postman Premium to the tune of ~$150 per seat per year...
So here we are slacking postman collections back and forth on our current year mac books.
So...what is the future of enterprise open source? Is there a future for enterprise open source? If you start a company and open source your core/clients, your product becomes part of AWS, and AWS runs you into the ground. If you mix in proprietary licenses to protect yourself, AWS forks your core, adds in open-source licensed clients, then runs you into the ground (and you lose open-source contributors/supporters as…
I think Hashicorp[0] has nailed down the open source enterprise model perfectly. Where they make open source software for enterprise and provide services to support. [0]: https://www.hashicorp.com
Hashicorp is one of those companies I want to support, but all of their pricing and enterprise details are behind a "Contact sales" button, so it is really hard to get to know their offerings and their pricing.
I understand we might be too small to matter for them if we aren't ready to dump thousands of dollars per month into their bankaccount, but it does makes me cautious about what is going to happen with them when their investment money runs out.
They barely have any revenue and they're struggling. It's probably one of the next companies to be acquired in the coming years.
I have always wondered what this enterprise support means? So if a big company starts using vagrant, they would dole out 100k for a support contract? I find this hard to believe but what do I know.
You would be amazed at the spread between big companies who decide "we won't pay $20 for support for something critical!" and other companies who decide "OMG, we can't run /bin/bash without a support contract and someone to yell at if it goes wrong!"
Maybe. At least our company won't touch GPL code; as one colleague described to me, if you violate a proprietary license, a company will come after you for money, while violating a GPL license gets the EFF involved who will come after you for your source code. I'm still wary, though. I could imagine if the resultant fines or source code releases from violating a GPL license weren't a strong enough deterrent, you coul…
The only claimants to your source code are those to whom you've distributed binaries built from GPL sources. Anyone else can pound sand.
not the case for AGPL: then it's everyone who has access to your online service built with the code.
So...what is the future of enterprise open source? Is there a future for enterprise open source? If you start a company and open source your core/clients, your product becomes part of AWS, and AWS runs you into the ground. If you mix in proprietary licenses to protect yourself, AWS forks your core, adds in open-source licensed clients, then runs you into the ground (and you lose open-source contributors/supporters as…
This is incredibly deft on F5's part. What are the alternatives to F5's products? Cloud products, and home rolled Nginx configs.
So...what is the future of enterprise open source? Is there a future for enterprise open source? If you start a company and open source your core/clients, your product becomes part of AWS, and AWS runs you into the ground. If you mix in proprietary licenses to protect yourself, AWS forks your core, adds in open-source licensed clients, then runs you into the ground (and you lose open-source contributors/supporters as…
The main reason I switched to nginx from apache years ago was due to configuration, which was much nicer from my side. If I was to switch away from nginx because something happened, I'd probably find something similar configuration and speed wise. Caddy looks nice.
https://caddyserver.com/products/licenses i would end up paying twice as much for caddy as i do for server
So...what is the future of enterprise open source? Is there a future for enterprise open source? If you start a company and open source your core/clients, your product becomes part of AWS, and AWS runs you into the ground. If you mix in proprietary licenses to protect yourself, AWS forks your core, adds in open-source licensed clients, then runs you into the ground (and you lose open-source contributors/supporters as…
My understanding is that Google has recently deviated from this strategy. The result of the strategy you mention is that the industry standardized on other companies' implementation of ideas that came from Google: Hadoop (MapReduce), HDFS (GFS), ZooKeeper (Chubby, and more. For examples of newer open source projects that see more active maintenance from Google, see Kubernetes and TensorFlow.
I know some people who develop on top of Tensorflow; from my conversations with them, Tensorflow's moat is Google making a lot of breaking changes by incorporating a lot of new functionality. I've also heard complaints that the online documentation isn't terribly great for triaging not-happy paths, to the point where you kind of have to just dig through the source code to figure out what's going on. Also, if you want to poach the maintainers, you would somehow have to poach them away from Google (which isn't happening, since ML at scale is something Google does best, and is an ongoing field of research). You can't become as good at using Tensorflow as Google is by simply forking the project.
What are some of these "many ways"? because I strongly favor the quality of life under nginx over that of apache. For smaller projects, these days I reach for Caddy which is even more pleasant to use than nginx.
My personal reasons:
- PHP under apache is faster
- Small config files per site
- .htaccess at the folder level when required
I usually use both and serve php from apache and serve static content over nginx. Best of both worlds.