This is simply false. The link in the opening gives the actual text of the proposed law:

" Article 19. Speed Limiter Technology

28170. As used in this article, “intelligent speed limiter system” means an integrated vehicle system that uses, at minimum, the GPS location of the vehicle compared with a database of posted speed limits, to determine the speed limit, and electronically limits the speed of the vehicle to prevent the driver from exceeding the speed limit by more than 10 miles per hour."

Hmm. Is this something you type in manually? I was operating under the assumption it was a hard-coded URL.

626 IP addresses is a minuscule % of all computers running Windows (what do you think, 10s of billions?), yet the fact that these computers consistently use the wrong domain suggests there's something different about those computers: likely they had bad RAM (or bad cache). If that's the case then the severity of such an attack must be compared to the severity of having bad RAM to begin with, e.g. writing bad data to random places on your hard drive. ECC RAM should fix this problem, though that's rare on desktops; a simpler solution would be to simply use SSL for everything and solve the entire problem completely. But either way it's a rare problem. It's an interesting study, but limited practical application. It'd be a lot more interesting if they got a radiation source and cranked it up to simulate long periods of time/many systems running in parallel. Then they could measure what the probability of this occurring is and determine if it's worth trying to solve or just ignore.

As I said, America (I speak of America because that's where the 77% and 93% figures come from) has an employment gap between the genders. Part of it is division based on traditional gender roles in employment, and certainly that should be addressed. Though certainly there's a mixture of self-inflicted and other-inflicted harm there.

But regardless, the ideal is still equal pay for equal work. This is an ideal that cannot be met if you get equal pay for different work. And if the world of corporate finance has taught us anything, it's that attempting to make special cases for things just creates loopholes that invariably get abused.

The real story here is that some people hold so much hatred for a specific group of people (bros) that the mere mention of that group of people is offensive for them, and they prefer to remove a common, innocuous word from the English language than to ever have to hear it in any context. I had to think a bit to come up with another case of this type of thing occurring: Nazis (oh yes, shit just got real!). Albeit it's not a perfect match. Nazi is a proper name that does not have any other function in the English language, while bro is a commonly used abbreviation of a common English word. So clearly people hate bros significantly more than they hate Nazis, which in itself speaks volumes about modern culture. But it's the best analogue I can come up with.

Ah yes. First came the sexualization, now you've injected race into the mix (and in a particularly derogatory manner, to boot). Do you ever think of anything other than race and sexuality? The topic of discussion is the Brotli file format, which is neither sexual nor racial. Can you please stop thinking about sex and race long enough for us to discuss technology? This is a news for nerds site, afterall.

I would too. And I'd laugh at the mental image before going about my business. If .bro is anything, it's funny.

You... you are being satirical, are you not? Your post sounds like you're bashing SJWs by pretending to be a particularly stupid one.

But assuming you're not, I'll address the topic of salary. The concept of the "wage gap" is widely misunderstood. The study most commonly cited as evidence (the 77% number) explicitely cautions not to misinterpret the number. The number is the ratio of all women in all jobs vs. all men in all jobs. More detailed studies that actually compare pay in the same job put the number at 93% at a minimum (there are additional variables that cannot be reliably controlled for, and may reduce the gap even further). In general there is not a wage gap but rather an employment gap. Women work fewer hours than men, are less senior because they've been with the company for less time, are more likely to be part time, are more likely to sacrifice salary to get better working conditions, and simply avoid some of the high-paying jobs like software engineering. Most but not all of these are probably related to motherhood, but the facts are quite clear: women make less than men on average because they do less work than men on average (or other things that if men did them they'd make less too). To expect equal pay for different work is a tautology of the definition of discrimination.

That said, what on earth does any of that have to do with the topic at hand? "Bro" is at worst misandric (and even that is questionable). You might have never heard of that word, but it means derogatory (possibly offensive) to males. And I think I speak for just about everyone when I say: we males do not need you to get offended on our behalf. We can take care of ourselves.

And it seriously didn't occur to them that "br" is ALSO an abbreviation of "brother"?

You know how a lot of people think "politically correct" or "social justice warrior" mean a person devoid of intelligence who goes out of their way to racially or sexually charge things that have nothing to do with race or sex to give them something to be offended about? Yeah, this is why.

Really I think the reason people are putting him down is because a lot of the maker community immediately jumped to his defense, then felt deceived when they learned he hadn't even made the thing himself. Of course this response is directed at the wrong party - the ones who were deceptive was not Ahmed but the media that blew the whole story enormously out of proportion and made him look like a boy genius. Nevertheless, feelz.

The article makes some good points and some not so good points. Here's the TL;DR version of this whole affair as best anyone can tell from the evidence so far:
- Ahmed brought disassembled clock to school for show and tell
- Ahmed never claimed it was a bomb
- Neither the school nor police actually thought it was a bomb (if they had, the entire event would have gone down much more dramatically)
- Given that, it's entirely possible the whole affair was racially motivated (or some idiotic zero-tolerance thing where they thought scaring him would teach him a lesson)
- Ahmed did not build the clock in question, he merely disassembled a store bought clock
- Ahmed is a fledgling tinkerer and may have a productive career in engineering when he grows up...if he doesn't crack from the pressure of being a world-renowned boy genius and shining jewel of Muslim-Americans
- Disassembling a clock at 13 does not a boy genius make. Even building a clock from a microcontroller at 13, while nothing to sneeze at, would fall short of the title of "genius".
- Obama's presidency will be ending soon, but the memories (and pictures/videos) of him inviting a kid that disassembled a clock to the White House are forever

Sorry, but at least two of your points are factually incorrect.

* ReFS is lacking a few notable features, including file compression / encryption, sparse files, hard links, extended attributes, disk quotas, and others[1]. You could say that the only notable improvements over NTFS that it has would be much improved resiliency and higher capacity limits. You can't compare this to BrtFS. At all. The two aren't even in the same ballpark. ReFS is there to store millions of large files and managed bad blocks in a smart way without taking the volume offline. It supports little else.
* Dynamic access control can't even be compared to SELinux. SELinux can restrict a program to running from a certain location, it can restrict which ports in the TCP/IP stack it can/can't open, it can restrict which hosts a specific process can talk to, and yes, it can alter the fundamental view of the file system hierarchy based upon access levels granted. Dynamic access control is really just more complexity in the form of an ACL on top of the already present windows file system ACLs, and it impacts nothing outside of files[2]. Now, you can use claims (which dynamic access control is built upon, at least partially) to control other aspects of your environment, but that isn't "dynamic access control" as far as MS is concerned. Further, it really is another layer of complexity -- if your claims server (which is a web server(!)) goes down, you're losing access to stuff (but if you're a decent sized MS shop, this will likely not be an issue, as you're already maintaining decent uptime on your DCs). Then the file system level ACL comes into play again. It's going to be crazy stupid hard to diagnose a claims access issue in a large production environment, no matter what MS has done towards fixing these issues. Somewhat amusingly, dynamic access control isn't supported on ReFS at all [2].

Now normally I'd just trust you that you googled around to find this stuff, but you've got some powershell in your signature, which leads me to believe that you've done a bit more checking than the "stereotypical slashdot linux sysadmin" and this only goes towards scaring me a bit.

[1] http://blogs.msdn.com/b/b8/archive/2012/01/16/building-the-next-generation-file-system-for-windows-refs.aspx
[2] http://technet.microsoft.com/en-us/library/hh831717.aspx

Aw crap, you're one of *those* engineers who manage to break their machine every 30 days like clockwork, and who makes the life of everyone involved with fixing PCs in a big corporation miserable.

Two sides to the coin... I'm not saying that any one side is more right than the other, but seriously, two sides to the coin.

I'd also like to see large bodies of water. Right next to Salt Lake City is... the Great Salt Lake, and right there is a massive area where the wind just dies. It makes sense (moisture rising, disrupting the existing airflow), but seeing that defined would be awesome.

It's almost entirely unrelated to virtualization. This is more like highlighting the fact that you can switch browsers by hitting alt+tab, only they built the alt+tab button into the hardware.

It's more complex than that (because every one of those will have a different libc, and android doesn't use the same libc, never mind the rest of the libraries), but functionally that's what userspace switching is. The same kernel (OS) keeps running...