samcday
Joined 15 years ago
Joined 15 years ago
> How low of an IFR would it take before you accepted that exposure?
If we lived in a sane world that valued EVERY individual human life above the self-serving dreams of an egotistical, arrogant sociopath, the answer would be zero.
> Would incidentally exposing them to the common cold be ok?
Such a question screams for a sarcastic answer: in case you haven’t noticed, Covid-19 is not the common cold.
Now, I’m starting to think the US is already a failed state. I’m pretty frightened to be living in this timeline. It’s like the collapse of Rome, but with wifi, vape pens, memes and nuclear arsenals.
It’s one thing to spread propaganda in order to influence elections and get a crooked bureaucrat into power that can enrich some corporate buddies. But it’s another to deceive people about a global health crisis. If you’re successful, people go outside and trigger a second wave of infections - lots of people die and we’re back to square 1. Economy will still be fucked.
What am I missing here?
Weird angle. Unless the RPKI standard is somehow actively encouraging people to violate social distancing policies, I don't see any connection with Covid-19..
To me this whole article just reads like a network operator complaining that someone else is trying to hold them accountable.
I think the point is many suspect that is not the case.
https://thegrio.com/2020/04/01/amazon-worker-strike-covid-19...
Amazon share price and business activity is surging as a direct result of Covid-19. They need to hire 100,000+ workers to meet the demand. However, the same thing they are profiting from (Covid-19) should also increase many of their operating expenses. Things like healthcare, paid sick leave adequate for the situation (so at least 4 weeks for proper quarantine), good PPE, in-depth infection combat strategies, and so on.
The problem is those operating expenses are only obvious if you have ethics/morality/whatever that concludes individual human life is more valuable than money. So if you're a big corporation that has been designed to enrich shareholders and the space company fantasies of your ego-maniacal CEO, you fight as hard as possible against taking on those operating expenses.
At this rate maybe they'll have already produced something about the backstory of Adam Neumann + WeWork (who will at that point probably be in prison?) before I get around to watching the Theranos one.
In many peoples opinion (including mine), yes. This can all be considered wage slavery.
Of course the magnitude and severity varies. A worker in the Gigafactory (probably) has a higher standard of living than the one in the Foxconn factory, who in turn probably has a better standard of living than the worker in the Nike sweatshop. But it’s all the same thing.
But then you watch a video showing the charred carcasses of many beautiful Australian marsupial and bird species littered on the side of the road [1], and you realize jokes aren't really very useful here.
In fact, they've pointed out the 500 million figure is a conservative estimate, and is likely to be much higher: "... The true loss of animal life is likely to be much higher than 480 million. ..."
No idea about the law, but I would hope you value human life more than a stolen black suitcase.
PHP ....
... Doesn't ship with a production ready webserver. Yes, Python and Ruby also don't, but they have easy tools you can reach for (gunicorn, Puma) if you need to run them in a modern deployment stack where a whole nginx isn't really necessary.
... Doesn't have basic collection types in the core language. It's 2019 and PHP still thinks it's logical for the standard language to throw all Map, Set, List semantics into a single PHP array type. You can install the "phpds" native extension (and polyfill it from Composer) to get some passably usable implementations. But coming from Golang / Rust (or hell, even ES2015) I find them frustratingly limited.
... Doesn't have any sort of threading / async support. Even in a modest-scale webapp, this is going to hurt you when you want to do things like deploy PHP as a job queue handler. Or fan out even a trivial number of HTTP-client API calls from a PHP controller in a microservice-y world. The latter can be sort-of achieved with naive hacks like the cURL client concurrency support (Symfony HTTP-client supports it: https://symfony.com/doc/current/components/http_client.html#...) but that's a hack at best.
... Doesn't ship with a debugger out of the box. Even with great tooling like phpstorm IDE, you have to actually rub braincells together to be able to get xdebug installed / configured and ready to use.
... Has a somewhat decent package manager (Composer). But it doesn't ship with the language. Also, it's kinda crappy. It's painfully slow to do a composer install/update on anything larger than a toy project. It has all sorts of weird non-determinism issues (the composer.lock file flails around wildly between runs, changing case of metadata fields, etc).
... Has semi-decent static analysis tools (Psalm, phpstan), but they're pretty garbage compared to a proper compiler, or the quality of static analysis tools in other dynamic languages like Ruby / Javascript.
I could keep going. Profiling, code formatter, library ecosystem quality, and so on.
Where am I going with this? Honestly, I wish PHP would just die. It has some pros, but overall it's a terrible language that has no hope of modernizing enough to be relevant in 2019 and beyond. There's plenty of other excellent languages that do a better job in any category that PHP attempts to be good at. The effort being spent to maintain PHP as a language/runtime could be better spent on other languages that have made better choices in language design.
The developers who have become proficient in PHP, should continue to use their employable skills to maintain existing PHP codebases, but take a bit of time on the side to get proficient with another popular language if not already. And for the love of god, stop starting greenfields projects in PHP! Let it fade away peacefully.