We run their on-prem in our colo, and it works great for us.
683 karma · joined October 31, 2013
We run their on-prem in our colo, and it works great for us.
I think it is a given that Amazon will open up to other companies to use their delivery service. Opening up their distribution, IT, and supply chains is part of their general business plan. Eg AWS; Amazon Warehouse fulfillment; Listing your products on Amazon's site, but doing fulfillment yourself, Amazon Connect.
https://techcrunch.com/2017/05/14/why-amazon-is-eating-the-w...
Just because someone took a formal course in something does not give them the right to say that I have nothing further to learn in a subject.
>> I won't pay for redhat style software at all.
Will you pay for software? Or do you write and build all of your software yourself? If I ran my business on Centos, I would consider buying Redhat subscriptions once I got to a certain scale. Depending on your business, you might need to have vendor warrantied and supported software for compliance with your insurance and industry regulations, for example.
Open source and free software is all fine and well when you are tinkering with in your bedroom, or at a small startup, or indeed when doing proof of concept or small projects, but when your operations start to scale up and you are looking at resource allocation and want to make the best use of your own resources, having support contracts often makes loads of sense.
A friend of mine work in the Aerospace industry and they where running to some weird bugs with their Java application when they upgraded their Redhat servers. It ended up being some weird kernel thing and Redhat sorted it within a few days. It sure beat them hiring their own kernel dev.
This reminds me of the adage: "When the product is free, you are the product".
https://www.kickstarter.com/projects/andrewgodwin/schema-mig...
I don't have a problem with the author wanting to charge for it as it is his software afterall, but I really wish more software vendors would follow Redhat's model of charging for the stable and supported version of their software, and giving away the bleeding edge 'Fedora' version for free.
As a techie, I love getting my hands on the new and most innovative stuff; I'm okay with breakage.
As an IT manager, I just want the stuff to work and be stable, with well planned upgrades.
I'm not sure where software authors got the idea that charging for their newest and buggiest features was a good idea. When I'm buying software, I am buying robustness and stability. I just want it work.
We love Ruby too, but being on one platform has been hugely helpful for us.
Ethereal was released in 1998, and changed the name to wireshark in 2006 or 2007. Doesn't feel like last week to me, but then again different people, so different perceptions.
So for us, that is now 6 Devs on Python/Django plus some consultancy support. So we've move from 2 python Devs to 6 Python devs within the last year.
It is now safe to burn.
There is always compromise. We can ask Linus to compromise, or we can. Are his inputs better put in at a technical level or at a human touchy-feelie level? What do you think is the best use of Linus' time?
It is incredibly easy to offer criticism, but very much more difficult to offer real and implementable solutions.
Leasehold is something that has been in the news lately. Leasehold is a legal apparatus that makes some types of property management work, somewhat akin to stratifying a property in American and Canadian terms.
Freeholders owns the underlying land, with the leaseholder owning a right of access of sorts. Freeholders generally charge the leaseholders service charges, but like anything, this can and has been abused. Like the current controversy with Leaseholds being sold to unsuspecting home buyers.
There is chrome plugin that blocks autoplay for video and audio, but you then have to give it rights to access all data on webpages. How does this square with with online purchases where you put your credit card in?
Your interface with the machine is only a part of the equation, and your interface with the team is so important.