1,134 karma · joined August 22, 2011
Beyond that the kernel developers value both correctness and performance. Most of these bugs involve multiprocessing and a huge amount of effort has gone into getting rid of them global locks, but even they aren't easy to reason about at that scale - I think you're missing the common thread in "deadlock" and "Global Interpreter Lock". Pretending that a world could exist where we can simply reason about something like the Linux kernel and then using it to state that devs can simplify or improve the logic is taking a completely unsupported cheap shot and the disclaimer about the real world doesn't change that. I'm not even sure what your motivation for the equivalent of "if you pretend that friction & drag don't exist it's really easy to figure out aerodynamics, so plane designers need to do better" (hint, it's not) is, but it certainly isn't to inform, contribute, or facilitate the debate.
He still trots that disaster out as proof of his fitness to lead, so it's hard for me to trust that systemd is both well-designed and likely to not be abandoned by him for his next shiny pursuit of Windows. The involvement of other devs helps, but not enough to convince me systemd is worth getting near. Two years of audio fail made a good object lesson for me about Lenart's professionalism and dedication.
As a side note, I'd love to have something like "freebsd-update rollback" for most Linux distros. I've seen attempts at it, but the only one that worked well for me was openSUSE integration of btrfs snapshots and the package manager. That's kind of swatting a fly with the complete works of Knuth, but it did the job.
http://www.freebsd.org/doc/handbook/updating-upgrading-freeb...
McKusick and his partner Eric Allman (sendmail & syslog) are the kind of older open source developers who're famous to Unix people and more Unix-inclined Linux people, but aren't as well known now as Stallman or de Raadt, say. Even now there's a high chance than any human being using the net has had their email, IM, or web traffic pass through software written by either of them.
With a bluetooth keyboard and mouse I could work much more comfortably than with the exact same hardware running Cyanogenmod. Being able to do Perl/Ruby development and run a real RDBMS is possible on Android, but it's not natural. When webOS came out GUI was also more pleasant than Android or iOS for a lot of things and definitely better at multitasking, but they couldn't compete in the market. Luckily some of the webOS UI folks ended up at Google and Apple (and some had come from there), so things like the Android notification system benefited.
I'm digging up some references now.
The model here relies on teaching officers to select people based on whether they think they're lying, it's a perfect situation for prejudice to distract from actual threats. Bruce Schneier and others have pointed how this wastes resources and increases the attack surface for terrorists, but the TSA has been highly resistant to feedback & criticism. It's the equivalent of having the physical security guys for a building do sweeps at night to look for post-its with passwords. That's not the computer security threat and it's not the breaking & entering one, so why do you have them wandering around in the dark?
Perhaps GIFV or equivalent should be defined as either requiring the browser not to play audio or as making audio optional, but required to default to off at start of play. The latter would require a minimal transport control, but I could live with a transparent mouseover-only volume button. There's no technical reason that a GIF successor must include or play audio. For that matter it would make a greasemonkey script or perhaps extension that forced sound off for regular mp4 much easier to write in this case.
In one case where I and others were laid off we were told it was a layoff, our severance paperwork said it was a layoff, and the government was informed (for each of us individually) that it was for cause. The motivation was to get around the legal restrictions for layoffs and avoid an increase in their unemployment insurance contribution. In another case I was the only person laid off (from a small team), it was explicitly a layoff & my severance was paid out, and I later found out that it was part of a deliberate attempt to spread fear, uncertainty, and doubt in the dev team. The company officer in question was later abruptly terminated and may have faced criminal charges.
In both of those cases you could argue by the standard you're using that I was fired instead, but I've got the legal documentation and if needed the witnesses to prove otherwise.
The CPU & graphics are almost more of a programmer convenience than a fundamental selling point. You've got to have them, but they're there to control other things and do some basic number crunching.
OTOH complete loss of storage resulted in sub-second data loss with autorecovery the first two times using a five year old Pg installation and minimal issues the third time. The master server had a three year uptime on the main server process when it went down. Overall I'm pretty comfortable with that track record.
• Guys I'd taught to use network tools months earlier (ngrep, paratrace, etc.) were eager to teach me to use the same tools and suddenly started giving me less credence.
• People in meetings (especially men) presumed I was from marketing or sales even when I was introduced as tech lead.
• When members of another group needed access to code I'd written my boss pointed them at me and told them I'd written it - so they came to ask me who knew the code and could explain it. I spent north of 10 min trying to get through to some very sincere, confused devs that no, there wasn't a "guy who wrote the code" that I was hiding from them and I was the only person who could help them.
• In meetings a male dev who reported to me started getting all the questions and was expected to sign off on things. When I made the final call on something people would ask him his decision.
• I lost two to three feet of personal space in elevators, break room conversations, and hallway discussions with management types and got talked over much more.
• I was happy that the invitations (I refused once I knew what I was in for) to beer runs/golf/bars with scantily clad servers stopped, but so did the "male execs go out in cliques" lunches. There's a lot of social currency, inside information, politics and gossip when guys go out like that and poof, your access is gone (or you never had it if you're a cis woman).
• Upper management stopped defaulting to believing me about deadlines, security issues, redundancy, etc. My concerns were far more likely to be considered overrated.
Every single one of these things I noticed _and_ had others mention to me. Imagine the combined effect of 10 years of that on someone's career and you'll understand why so few women have made it up the ranks in tech companies..
test -z "$BASHPROFILEREAD" || return
(to avoid double-sourcing) and there's no good way to fix them. I haven't tested ksh93/zsh yet, but I suspect similar issues. I suspect the developers do little more with their shell initialization than set a few aliases and variables so it's not an issue for them, but fixing it for myself is far more work than worth it. It's too bad, everything else works well for me with mosh.
Even presuming that counter to actual experience the generic trolls are deterred by a real names policy, there are others who become a much bigger problem when they've got access to real identities. Why do you think doxing is considered such a big thing? SWATing, offline stalking, physical assault, etc. are all risks as soon as a harasser has your info. Even worse when you're talking about something like domestic violence support groups there's a very real danger of the abuser escalating if they discover the victim has been talking to other people. That's 2.1 million people in the US alone who report physical assault by a partner in a single year who could really use access to resources without revealing themselves.