My problem with that, and this article, is that it doesn't say what dosage does that?
It just skips right on to meth, and dosages, and never mentions Ketamine again.
We get that 280mg a month mostly doesn't, and 90,000mg a month can.
But are these "party people" the same as the people doing that higher amount prorated to daily? More specifically, are the "party people" I've been around secretly having bladder problems and getting a hole in their belly and not really ubering home but ubering to the hospital?
Let me know when you, or anyone passing by, find that article
I've known many users over the years, many OD while others decay over a few years.
One customer in particular used ketamine heavily. Due to a string of poor decisions, he was on federal probation and subjected to random drug tests.
He determined two drugs were not detectible by the tests at that time: ketamine and GHB. And he frequently consumed them. I remember him stumbling around my store, sipping caps of G every so often... sniffling behind tall pallets to suck up another key bump.
Over a year or so, he developed severe problems with his bladder, but wouldn't / couldn't stop his drug use, even after I broke it down to him plainly; "Bro, you are killing yourself."
From what I can tell, users don't keep track of doses, or much of anything. Their objectives are short term in nature: get high asap.
I suspect any such article that provides hard numbers like what you want will provide guestimates at best.
Oh, that is just peritoneal-dialysis. Lots of people do that when there kidneys are shut and they want to continue a "normal" life without constant blood dialysis via machine.
The real con here is that you must limit your intake of fluids drastically
No argument there, but I think it's funny that just about all of the Venezuelans and Iranians that I know (fairly large sample in my case) would see "the bad guys" as the Venezuelan and Iranian governments.
Me personally, I see "the bad guys" as RT. Not a big fan of their work.
I’ve met many Iranians and I have to say they were without exception exceedingly polite, friendly and welcoming and immaculately mannered and hospitable.
The need for shorts largely goes away if you make stock buyers hold for at least a year before selling.
Remember, the purpose of the market is as a funding mechanism for companies to pursue growth and innovation, not to allow a bunch of "banksters" to game the system. That means that investment should always be longish-term. So let's make their stupid games not worth playing.
FWIW, If you do allow intra-day trading, applying a random delay of up to, say, four hours would eliminate most of the problems...
Containers don’t have to be complex. Docker and docker-compose are very simple to use. Docker swarm (rip) and Nomad are similar to kubernetes but orders or magnitude simpler.
I used to be a Docker fanboy. But after writing a few semi-complex Dockerfiles, and seeing more of how complex and FUBAR things like networking is [1], I changed my tune.
This was years ago, so maybe they greatly simplified things. But somehow I doubt it =/
[1] " Docker, by default, punches massive holes through your firewall in non-obvious ways. People don't realize that with a default Docker configuration, containers are ignoring any normal firewall rules you may have setup with iptables or ufw." - https://news.ycombinator.com/item?id=25834444
Can you explain the whole concept of Kubernetes to someone whose knowledge of computers is limited to making simple webpages with HTML and using Excel/VBA?
In a 'normal' scenario, you might host your web page on an Nginx web server, on a Linux server somewhere. A container lets you do the same thing, but in an isolated area of the operating system. That means you can have an isolated area which has your web pages, the Nginx web server, and some other dependencies, all grouped up together into a distributable package called an image. And then you can pull that image on other servers and just start running it and it'll have your web pages and your Nginx running nicely.
So far that's Docker, or containers to put it more generally.
Now if your web page is so amazing that it receives a lot of traffic, your little container is going to get overwhelmed. And if it falls over, then it's dead and nobody can see your web page until you bring the container back up. Fortunately there are tools that let you manage this aspect of the image, called orchestration. You can tell orchestration tools how to figure out if an image is unhealthy and needs replacement, and if it falls over whether to bring it back, and importantly, how many copies of the image to run to handle the traffic. And if you need to push an updated image with an updated web page in it, how to gently make that new container available to the world without interrupting the traffic.
There's more to orchestration, you also tell containers how to talk to each other if needed, how to manage secrets, encryption, load balancing. There are lots of aspects of hosting that fall into this.
The two main orchestration tools I know of are Docker Swarm and Kubernetes. Docker Swarm is bundled with Docker already. It's pretty easy to shift from normal Docker use to Docker Swarm use, it works well enough for small-medium deployments. Kubernetes is a tool for much larger and highly flexible use cases, and it has a lot of levers and buttons and swiss army knives with its own swiss army knives. Many aspects of Kubernetes like the load balancing and secrets are all pluggable and you can use different tools in there.
Now you're at this article's topic, which is Kubernetes. K8s as it's called has a larger mindshare of the ops world, therefore everyone wants to use it, but it's very complicated, so a tool has been introduced to try to simplify it.
You know how there are linked references in Excel files that refer to other Excel files? What if you want to keep multiple copies of your Excel file with macros that refer to different files with data? And so you can run them on Windows, Mac or in your browser?
Kubernetes basically lets you define your references not as "c:\jon\reports\fy2020_final_final_2_comments_review_Bob_final.xlsx", but as "fy-report", with "fy-report" being defined elsewhere.
This is required to help you run the same program in different circumstances without breaking everything. You can say "run it on this slow computer with this test data", or you can "run it on many big computers with real data", but the program is exactly the same.
What makes it so complicated is that Kubernetes tries to abstract everything a given program would need, so it's not just references to external files, but practically the whole computer with all its network connections that must be defined elsewhere using Kubernetes' special language.
A lot of this special language is the same for 99% of programs, like in Excel you want your VLOOKUP to work on a $-pinned range with the last parameter set to FALSE 99% of the time. This makes people make the same stupid mistakes and finding them is hard.
And of course, this special language means you have to relearn a lot you know about running programs on computers, like when you move from Excel formulas to VBA.
I think this is one of the bigger factors when people choose to quit social networks, even if they don't realize it explicitly. There's such a "hustle culture" to get likes and favorites that it really warps what you can post. You can't really be vulnerable on a social network because it either gets ignored or interpreted as another hustle ("You got this!!!") because the surrounding content from everyone else is "Look at how great I am!". YouTube creators have to explicitly say "Please like and subscribe!" but that's implicit and pervasive on Twitter and Facebook by their very nature.
I used facebook for promoting local events but in the last ~5 years it was less and less effective for that.
Then I used it only for meme groups and getting angry at strangers.
Hard quit last summer and never looked back.
Developers already have an incredible amount to learn without making them devops too.
This is the sort of thing than non tech management would love though.
It’s a great slogan.
Essentially the sign of mismanagement dressed up as innovation.