That really smells of desperate developer that need to feel relevant just because they use the latest thing
Like, how the fuck it would be "simpler" if the deploy is literally just running a single script ?
1,252 karma · joined January 28, 2020
That really smells of desperate developer that need to feel relevant just because they use the latest thing
Like, how the fuck it would be "simpler" if the deploy is literally just running a single script ?
Then again jenkins job can be as simple as "download a repo and run some code in it" without anything fancy so even if SHTF you can migrate away relatively painlessly
I run something similar on personal site and it's literally just 2 identical configs but with different port/directory and some haproxy config.
It's what you have to do if you want less downtime. Normally it shouldn't span much more than 2-3 versions of application and it's rare that the annoying kind (say writing same data to "old" and "new" column) happens.
This also gives you a bit more resilience, if the app on node dies (out of memory/disk/bug/whatever), the proxy will just send the traffic to the other node without having to wait for DNS to switch
Container with it is just a few files in etc and binary blob itself. Same with container-less deployment.
Main difference would be storage speed and how it exactly is attached to a container.
users don't care, they aint taking the code for changing.
Arguably it also doesn't matter till you are corporation closing the code for profit. If all you do is OSS and are used by people that also release OSS, extra protection GPL gives are not useful. But of course real world is not that idealistic.
And for that of course BSD/MIT is better. No facility for anyone to get anything out of you so you can take and take without ever giving back aside from occasional bug report and outrage over someone having a bug they didn't fix in project they are not paid to develop in the first place
GPL gives one guarantee - that the code you give will not be closed down for money and used to save some corporation some dev-hours. Some devs don't like it because it is making their life difficult (and I'd also argue anything higher than LGPL for stuff like libraries is kinda pointless), but that's kinda the point.
> even though they were only distributing the viewer internally.
That is explicitly allowed. You just have to live with consequences of it being legal for any of the users to take and "bring back to the light".
It is either that this company didn't wanted their inside people to do that, or that Linden lied to them about what GPL implies
Like, how is even say a single developer of mildly popular lib doing one thing gonna setup financing ? Or get people to pay ? Anything from patreon to tips was tried to mild results at best
Big failures like OpenSSL fiasco happened - where sure, company was sustainable but due to skewed priorities coz of funding (companies that founded it founded features that from perspective of any other company were bloat, and not enough work went into modernizing the code) the code was shit and full of traps.
And it's still a fact that vast majority of developers of stuff used everywhere wouldn't be able to do it as full or even part time job for financial reasons.
All while the corporate is pushing same "BSD/MIT good, GPL bad" agenda, coz they don't need to contribute anything back to stuff they take
Would be simple to confirm with some scope probing CPU power.
I don't see why something similar couldn't be done, pay monthly and you can read whatever your want, and what you read depends on where the money from your subscription goes. And as distribution costs are lower, higher % of it should go to the writers. Hell, amazon could just do that, except of course they wouldn't give a fair cut...
At zero cost to try new authors it could possibly be a good way for more niche stuff, you can just page thru any book that you want with no cost but time
> What do you expect them to do? Force users to sign up for a weekly subscription and email out individually DRMed copies of the chapters each week?
There is actually one guy doing it on patreon but he already have YT audience for music gear reviews (book is about electronic music ideas and tips). So it is possible, just kinda hard as you already need to have publicity.
The cron way, where both 0 and 7 means sunday
It makes it easy for quick & powerful one-liners but sadly people then put the one-liners into actual programs instead of writing it in nicer way...
Coz they'd prefer to control the supply and get all the profits while giving actual writers a pittance and having in their contracts that anything they write belongs to corporation that paid them. Similar deal with code really...
It's not. They want you to pay them for the book instead of just getting it for free.
Similarly with patents stifling innovation, especially in industries moving way faster than patent protection and patenting trivial things just so they can "gotcha" the competition (or just patent troll).
And why it couldn't load that data for say month ahead ?
> What exactly would you expect in this case?
Not pretending it's the user's fault they built the phone wrong. That's just extreme arrogance on their side.