Shutdowns also give the virus more time and incentive to evolve into more contagious variants with much milder symptoms. If we delay it long enough it can actually end up just being like the seasonal flu.
I know nothing about this, but from what you're saying it sounds like the more contagious a virus is, the milder it's symptoms are? Is this usually true for all viruses or did I just misread your comment
Indeed, Perl does have named function parameters, the same as almost all modern languages - and I highly recommend using them.
(I use them throughout my code, except for modules that should stay compatible with very old versions of Perl.)
But folklore is a thing. Many people learned Perl before named parameters, and to be fair they took about 20 years to arrive (and are still called "experimental"!). People don't like to change now.
I think most people writing new Perl code still use the no-named-arguments idiom, just because it's old and familiar. Which makes code look more arcane than it needs to, to outsiders, unfortunately.
> "I hope there are discussions at REDACTED today about whether featuring SQLite on their front page is consistent with their values."
> "The message is clear: if you're concerned about diversity, decency, and inclusiveness, stay well away from the SQLite project."
> "I wonder if SQLite Consortium member organizations @mozilla, NDS association, @BentleySystems, @expensify, @business were consulted on this move."
> "This is the as*le: https://en.wikipedia.org/wiki/D._Richard_Hipp … (thanks @weigandtLabs for finding that out). He _is_ the main SQLite dev. And that's the community he's building. So SQLite is now dead -- or, at least, it should be."
Pathetic. I am not a user of twitter precisely because I have no interest in reading those sort of reactions. But I am strangely fascinated by this continuous stream of 1st degree, knee jerk reactions, it's kind of like watching shit flowing out of a bull's ass...
My company uses Mojolicious for all our webdev and Perl for all our in-house stack. Full disclosure, it was my decision ;) but the work is so fast and smooth, I can't imagine switching to anything else.
Since it is built from the ground up around an event loop, asynchronous requests and responses as well as websockets work much more naturally. With Plack-based frameworks the PSGI spec is not built for asynchronous behavior, so you have to rely on hacks and use specific PSGI servers like Twiggy.
Here is the Free Redistribution section: "The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources."
Yiftech commented that the reason for making the switch was that "AGPL does not prevent cloud providers (such as AWS) from building managed services from these modules". The entire reason for making the switch to licensing the modules under the new license is that the Free Redistribution aspect of AGPL and other open source licenses allows cloud providers to use the software in a way that Redis labs doesn't like.
Cloud providers are not "giving away or selling" the software, they are running it, which isn't covered under that section.
You're probably looking for #6:
> 6. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research. ... or in this case, "offering Redis with extension X as a Service"
> You're mixing up Open Source and Free Software, those two are not the same.
There is an ideological difference between the movements, but very little practical definitions between the OSI Open Source definition and the FSF Free Software definition. Yes, they are worded differently, but in practice they are virtually identical (I don't think a single license has been reviewed by both entities with a different conclusion.)
They have different ideologies behind them, but they refer to almost exactly the same class of software. A license that doesn't allow commercial use is proprietary and closed source.
Not closed source since the source is public and freely given [1].
Not open source because the license [2] forbids use based on field of endeavor which is required in the OSD [3].
As for the other direction, you can't have software be Open Source and closed source simultaneously since being Open Source requires the source to be available. Or in symbols.
According to most of people who invented the term "open source", the OSI and their open source definition, propritary software, even if you can see the source, is not "open source".
Nearly everyone uses the term "open source" this way, and to use it otherwise is grossly misleading.
Of course, if you follow the osi definition you are absolutely correct. [1]
"the obvious meaning for the expression “open source software”—and the one most people seem to think it means—is “You can look at the source code.”" [2]
The main problem imho lies in the fact that afaik we still don't know how to call proprietary software with released source code, although this is mighty common (again, see github). If that problem is solved, the osi definition is much better applicable.
(On a side note: A word that might describe such software is public. Public Software vs. Open Software Software. This however is again problematic because of "public-domain" software.)
> the obvious meaning for the expression “open source software”—and the one most people seem to think it means
I disagree. I think if you ask nearly people who know what the term "source code" means, if you ask them what "open source" means, they'll give the OSI definition (which is in practice the same as the FSF's 'free software' definition). They'll say it's more than "I can look at the source", but includes the rights to share and build on it.
Microsoft tried the term "Shared Source", which might be what you mean.
One of the reasons i really like Perl is Mojolicious. Thanks to it we don't need separate servers for websockets and HTTP anymore. https://mojolicious.org
