forgottenpass

>To be clear, if you dispute and counternotice everything

This isn't happening under the DMCA, it's Google's own brand of copyright process more tailored to appeasing the giant media companies.

I vehemently implore you to spend some time outside the Valley bubble.

But how'd they get there in the first place? Contact with a D12 is terminal? What set our hypothetical failure apart from a 20-something guy that drinks, does drugs, plays games, is in a relationship and leads a rewarding life? Allow me to blast some copypasta about for an idea I can't quite articulate myself:

>Everything is systemic until it's people you don't like, and then suddenly they're personally morally culpable for their shit ass attitude. A whole generation of men simultaneously said "nah fuck it having a life is for fags"? When you see this many people with the same problem, the word "systemic" should come to mind immediately. They need to wipe their own ass obviously but I'm in no rush to blame a whole generation of teenagers for burning out the exact same way; I wanna know who sold them the video games, weed and tendies.

>the amount of men don't cry, men don't show emotion

>I'm actually sad that most men don't feel like they can talk about their vulnerabilities and emotions.

Do they not talk about it, or have they not talked about it _to you_?

I used to believe the narrative that men don't talk about emotional issues, assuming my lifetime of experiences talking to other men about our perspectives, fears, limitations and feelings was some sort of aberration. It finally fell apart when I made some friends in the trades. If _they_ didn't even follow the mold, and were willing to confide in me whenever something was on their mind, then why is this assumed to be a widely-pervasive male trait?

As far as I can tell, men are more than willing to talk about personal topics they keep guarded. It just has to be with someone that they care to have a real conversation with.

>After living on the google tech island for a while, it's surprising how much of this people have tried to "solve"

You're missing the point of the article. Most people and organizations have written libraries and services that make common development tasks much easier when developing within their own software ecosystems. Google is just one of many.

The question this article is getting towards is solving those problems in a pattern that transcends individual implementations and the conceptual model becomes as ubiquitous as the filesystem hierarchy.

Dumping a "this works for $DAYJOB" solution onto the public by publishing a standard isn't the answer. If that worked, those problems would be solved and this article wouldn't exist.

You're assuming this was a "didn't know" failure mode, not a "didn't care" failure mode.

I'd wager it was a "didn't care". They knew about the limitations, figured the product would work often enough to make some money and labeled everyone pointing out the problem as haters or technophobes.

Someone probably even pitched a keypad password based redundancy and got drown out in valley buzzwords about MVPs and shipping fast until they gave up.

>If you feel attacks on toxic masculinity are attacks on you fathers/husbands/sons maybe there should be some thought about what about their behavior overlaps the above, and whether you think that's ok?

My favorite part of social commentary these days is how it's layered in "I'm not poorly conveying a point, you're hearing me wrong and/or you're the problem."

How is point "C" anything more than "People on that side of the fence are not thoughtful, unlike people on this side of the fence"?

>This seems like a pandora's box.

Of what? Damages can rarely be calculated perfectly.

It's not the court's fault Apple falsified timecard data.

So my personal email account just got $490/year more expensive? Or $24990/year if we count non-english dictionaries?

And I ought not to have it because I'm not hosting an online store or marketing materials for a megacorp? Fuck me for trying to have something nice without commercializing it, right?

>They help teams manage complex interdependencies by creating strong ownership boundaries, strong product definition, loose coupling, and allow teams to work at their own velocities and deployment cadences.

You just described library boundaries. You did not describe why the interface has to be a socket.

>the average engineer doesn't need to know about the eventually consistent data model of your active-active session system

People can create unnecessarily connections between microservices too. It's only slightly harder than punching an extra hole through the public interface of an in-process API. Is that what we're spending so much time and money on.

>Mostly what we have are jigs. [...] Of course, it's not a shitty jig like in the bad old days of shell scripts[.] Instead of making it out of scrap wood, we now make it out of scrap steel with a MIG welder. We're advanced now.

Early contender for Best Analogy 2020.

underrated comment