4 ms·
If you take this attitude you should write all of your own tools, make your own hardware, not use any libraries (I might actually be able to make a case for thi
by BatFastard 5y ago
If you take this attitude you should write all of your own tools, make your own hardware, not use any libraries (I might actually be able to make a case for this one).
I am most familiar with AWS, so all I can say is their prices have gone down over times, the availability has gone up, and the total number of services is amazing.
With other cloud vendors I think you might be at more risk of them shutting down services, but if they start doing that with out giving you multi-year notice it means they are going out of business.
- rmbyrro 5y agoExactly. If your $open_source is abandoned tomorrow, what are you going to do?...
- sojournerc 5y agoFork it, and continue on...
- sokoloff 5y agoGenuinely can't tell if this is sublime sarcasm or a straightforward argument.
- JasonCannon 5y agoStay on the version that already works and provides the features you need? Fork it to add new features if needed? You don't need to constantly update software dependencies.
- Epa095 5y ago> If you take this attitude you should write all of your own tools, make your own hardware, not use any libraries (I might actually be able to make a case for this one). No. Just...no. There are more than the two possible positions, its not either "ignore technological dependencies completely and blindly give your balls to a single vendor" or "create everything yourself from the ground up". You can look at your stack and consider how vulnerable you are compared to how much you gain. Sometimes you will find that it's worth it going all in with one vendor, but it should be a conscious decision. Business have to consider their vulnerabilities all the time and it boils down to compromises and tradeoffs.