Actual link is https://github.com/openzfs/zfs/pull/15022#issuecomment-18024... but HN's dup detection links to a story from 83 days ago. @dang et al, would be nice to consider anchor text in the duplication feature for such occasions.
15,526 karma · joined July 20, 2008
Another good reason to defork is that, as we saw with the youtube-dl fiasco, there are some non-software-related reasons that MS may feel inclined to offline the entire fork tree. That'd be the bigger concern for me.
OpenBrush was imo one of the best apps for it and I wanted to start playing around with the code, but had some friction even getting a build started and eventually lost interest. Installed several SideQuest builds, of course, but after I couldn't get a working distributable with built-in Icosa even all the way into September, I got annoyed and I haven't started the app or looked at the project since.
Just getting the Oculus dev env set up to the half-assed extent I did, it's risky, dubious, and feels bad. I never know which agreement I might accidentally click that'll allow Zuckerberg to Quest2 into my house backwards, or whatever.
I guess this is probably a lot less helpful than I thought it would be when I started typing. Sorry!
Agree, and this is often overlooked. There's a handful of people I used to admire whose tendency to readily believe whatever's being sold by their middling middle management chain has left me deeply disappointed.
Middle management is a necessary evil, but there's little hope if upper management fails to recognize and subvert its inherent incentive structure.
If you're at the PIP stage, it generally means your boss and your superboss have decided that it's time for you to go, but for legal purposes, they need to look like they tried to give you a chance, so they work with HR to craft specific-but-typically-unattainable goals which would theoretically allow you to save your job if you hit them all. But with boss+superboss already wanting you gone, the likelihood that they'll agree you've hit an improvement goal that's usually a thinly-veiled form of "stop me from hating you anymore, lol" is pretty low.
If you get a PIP, in nearly 100% of cases, you should just take it as notice that your employment is going to end at the specified review date in the PIP. It's not usually worth trying to hit the goals. Focus on interviewing.
That said, I once managed an individual who had survived 4 PIPs by the time he reported to me. I heard that he was eventually fired about 2 years after I left, but not sure if it was his 6th or 7th PIP. He was a particular discrimination liability at a company that was very sensitive to that type of thing.
Help your people and don't be a dick and you'll be amazed at the bounty of unearned gratitude that comes back around -- and often not just once, but continuing for years. Being a good boss is "the gift that keeps giving" to good bosses everywhere.
Seems to work in bash too, fwiw.
[0] https://fishshell.com/docs/current/interactive.html#copy-and...
I'm not a biologist so I don't really know what any of this means, but there seems to be debate around the presence of a "furin site" [0], which apparently could have emerged naturally, but also could have been artificially spliced in the course of gain-of-function research. Is that how GOF research is normally conducted? I don't really know anything here, but at least some people believe there are genetic markers indicating potential lab manipulation, thus adding another datum in the long list of circumstantial evidence.
[0] https://threadreaderapp.com/thread/1266805310313967617.html
These guys might have a hard time fitting a recruiter's definition for a "rock star" but they're the best set of colleagues I've had in a very long time, and that's after working at multiple flashy tech companies.
Long live Perl. We can only hope to get another generation of programmers as committed and useful as the people who still write Perl every day.
I switched from Firefox to Brave in October and suggest others do the same. Personally, I believe Brave would indeed "deep-fork" the Chromium codebase if necessary, and I'd guess there's a significant chance that other Chromium-based browsers would use it in preference to a submarined upstream.
It might cost more in shipping and delivery time, but it's strongly preferable to having my desk catch fire due to missing or defective safety components, which are very common among knockoffs. At least there's someone to sue if that happens with an authentic battery.
There's a world of difference between the amalgamation of hacks that comprise cgroups and something like BSD jails, which are and afaik always have been intended to be a security boundary, which implements real first-class kernel isolation for jailed processes, not just another subtree under proc that provides some direction to the kernel around resource consumption/priority and relies on UID/GID hacks to control access.
Friedman would certainly be removed by Microsoft if he jeopardized GitHub's legal protections by defying the mandated process, to say nothing of the potential of creating personal legal liability, both criminal and civil.
youtube-dl remains freely available off-GitHub (not to mention on the local disk of anyone who ran `git clone`). I just used it 10 minutes ago. There is no public good served by defying the law here, and there is no reason to put the whole kit and kaboodle on the line over it.
tl;dr, ignoring the DMCA process isn't just a "somewhat risky move". If we're going to break out the pitchforks, let's at least point them in the right direction: write your Congresscritters and tell them you want to see copyright law reform.