Healthcare for the elderly will put huge strain on government budgets.
With the young struggling to afford housing with fulltime work, I find the authors disappointments about not getting those lavish vacations obnoxious.
Healthcare for the elderly will put huge strain on government budgets.
With the young struggling to afford housing with fulltime work, I find the authors disappointments about not getting those lavish vacations obnoxious.
Disclaimer: fmr Googler, used to work on YouTube
Likely, this isn't necessarily targeting Firefox/Safari/Etc, but rather is using the UserAgent as part of a tuple with other factors. It _is_ however an anti-adblock measure meant to determine if the video is automatically getting skipped forward.
The reason on why changing your useragent "fixes" the problem, is that you're changing the tuple and the anti-adblock system won't serve the code-at-issue until it determines whether you'd be a good candidate for the experiment.
Secondarily, YouTube has no financial incentive to actively punish non-chrome useragents. They make money in their division by serving ads, regardless of the useragent.
Nonsense. A Google controlled browser runs plugins Google allows with privacy settings Google creates. More data and no ad blockers is worth many billions of dollars to YouTube in the long run.
They directly benefit from people thinking Firefox is slow.
The importance of the distinction here is that Tesla can't argue the customer caused this...a cold shut can only happen at casting time.
Normally, failures come from some amount of non-repeatability or randomness that the systems weren't robust to.
The drive industry is special (in a bad way) in that they can exactly reproduce their flaws, and most people's intuition isn't prepared for that.
In traditional polygamy, the man with 10 wives would be the head of household for 10 wives with competing interests, so it does start to sound very managerial.
Also, "power user friendly" but hates CLI..... I see. You might have to hand in your power user card over that one
I am a diehard windows user but the OS's affinity for burying settings in nested, labyrinthine setting dialogs gets old super fast.
"You might have to hand in your power user card over that one"
And these attitudes are why most consumers almost exclusively use proprietary software. You have to let people be lazy to get mass adoption. Businesses know and exploit this, the foss world writes tools with steep learning curves and says "take it or leave it." And that's perfectly fine as long as we can be honest with ourselves: the vast majority of people will never invest the time to learn to use cmd line applications, or debug wifi drivers, or learn to use an environment that's more complicated than what they already have. Time is money so even a highly motivated person should question spending months to learn new tools.
I love Linux for being superior for servers and hackable and having so much powerful software available for free...but if I weren't a software developer and I didn't enjoy this stuff there'd be no justification for the time I spent learning it.
I think that Mr. Musk is an undiluted asshole and one of the worst douchebags to ever grace our planet, which he has proven again and again.
But analyzing his mental condition is sure as shit not up to me or to anybody else.
I don't like Musk, nor do I trust the things he says, but I usually err on the side of granting people some humanity.
Hackers like to obsess about Big-O, data structures, HoTT, and other high-theory stuff, yet the following skills, essential for software engineering, are almost never discussed and even more rarely practiced:
- Deciding what to write yourself and what to take from a library
- Identifying high-quality libraries and frameworks that meet your project needs
- Deciding where optimization is worth the effort and where it is not
- Writing code that will still be readable to you (and others) a few years from now
- Thinking about the project as a large-scale, complex system with software and non-software dependencies
In that spirit, I offer the following alternative challenge: Create a web search engine. Don't bother with string matching algorithms etc., others have already done that for you. "Just" make a search engine (and crawler) that can actually work, even if it only supports a subset of the web and a single concurrent user at the beginning.
It takes years for a single person to get a project to the point where it's a good learning ground for scaling and maintenance.
Gluing a few libraries together is real software engineering but unless you're really invested in the outcome it's not that engaging and it's not that educational.