JOnAgain
So, whenever you think about purely capitalistic policies with no social policies, we just have to be okay with having a large number of babies and toddlers starving on the streets in front of us.
When you hear about republicans cutting $900 billion from Medicaid, and millions of families losing coverage, that means children. Almost 50% of Medicaid recipients are children. Most of the other 50% are their parents. So millions of children now do not have healthcare. Your post advocates for millions more to lose coverage. That translates to children dying and having lifelong disabilities from otherwise preventable illnesses.
The other inevitable outcome of policies like this is exploitation of women. It might start with “voluntary” sex work, but it becomes a bigger business that invites true exploitation and rapidly leads to human trafficking. Btw, that “voluntary” is there because it’s usually a choice between sex work and spiraling into homelessness and poverty - so not super voluntary to begin with. And we’re not even counting women more women who stay in abusive relationships because they are fully dependent on their partner for sustenance and shelter.
All that is to say that anytime advocate for a certain set of social policies over another, it’s usually informative to look at how they impact the most vulnerable in our society. Start with kids, then consider disabled and women. And finally ask why we’re generally okay with men starving on the street but not toddlers.
Is this just curl with a simpler syntax? This is advertising CLI integration, so what's the VSCode feature people seem excited about?
Please update in 1 year
Except you’re at a company where everyone has figured this out so now you have 4 competing libraries with their own teams which are all 1/2 done making every engineer less productive cause they all have bugs and slightly different priorities.
Add in compliance, auditing, etc. all things that you can set up out of the box (PCI, HIPPA, lawsuit retention). Gets even cheaper.
Thank you.
Yes they do. This is exactly the problem. Specifically in big cities. Zoning and nimby-ism holds back building. Even Toronto which builds a lot doesn’t build enough housing units to keep up with growth. And they only build as much as they do because the province is constantly overruling the city.
Every western major city is blocking building on any meaningful scale. This leaves cities at effectively net 0 increase in supply. In major US cities, new builds are more expensive to own due to changing property taxes. And California is just a huge F U to young people by making new owners have to pay higher taxes than the old ones.
I remember when S3 and EC2 were coming out. They tried to make us working on the retail website move year after year. Our excuses became their roadmap. We (developers working on not AWS) really didn’t want to move to AWS. It was 100% worse than what we had before.
“Network is slow”, “it’s not PCI compliant”, “the drive is unreliable”, “the load balancer is missing a feature”.
It took years and years. But they did it. Google and Microsoft don’t have the willpower to force this, and its why they will always be behind AWS.
When Google tries to sell you Google Cloud, remember they don’t use it for anything internally. They don’t think it’s good enough. So why should I?
It wasn’t good enough. It purported to be great, but it had random connection issues. Given that destiny, a 1st person shooter, was their flagship game these flaws really jumped out.
You also really needed good internet. Like really good. Mine performed well sometimes when it was hardwired, but lagged regularly over WiFi.
I think these things were fixable, but that thing was dead within a month of launch. Google didn’t get fully behind it, so all the people that launched it got their promos, saw the writing on the wall, and transferred out.
What kills me is trying to search in an area and having it pan out or pan over to show me an ad. I think it’s their monetization that is killing UX.
Another one bites the dust
And another one gone, and another one gone
Another one bites the dust (yeah)
Hey, I'm gonna get you too
Another one bites the dust
Before we get to the 7 reasons, let’s describe what Google is …
Not a good look.
I loved this.
In this case, I would prefer to manage 1 set/type of hardware for all my uses unless I really needed to deviate. If the difference is $100 in overkill for a Pi-hole, but right-sized for other use cases, I find value in the consistency.
1 form factor, 1 OS, 1 set of hardware compatibility, if a script works 1 place, it works everywhere, etc.