That's only a hard requirement if you're creating a web component. Unknown elements are treated as inline elements by default, so if you're just using it for styling and using global attributes (even JS ones like onclick), you can use whatever tags you want. You only run into trouble when you start doing more advanced stuff with your non-standard elements.
Amusingly, I'm in the reverse situation: loving working in Haskell and reeally want to try Rust but I just don't have the time.
For what it's worth, Haskell can be compiled to code that's quite fast. Somewhat unfortunately, the difference between GHC's vanilla output and its speed-optimized output can be quite vast, which I think gives the impression that the language or a given program is necessarily slow.
Apple's T&Cs are so long because they usually show you like 6 different documents, most of which aren't even in regard to iTunes. (Google does this too.)
It depends on how you've packaged your application. Technically, yes, the user needs NW.js to run your application, but you can ship with NW.js if you like (it's just one fat executable). When NW.js is run, it looks for a NW.js app to run in the working directory, so all the user needs to do is run the NW.js binary you provided and it will launch your app.
> That's going to break so quickly here in Boston.
Depends on what you mean by "break". In Boston, you might just get, epic, hour-long pong battles. Seriously, the pedestrian signal situation in Boston is so haphazard you could hardly make it worse by introducing experiments like this.
I don't know, I always found the perl and zsh man pages to be rather pleasant. They were sprawling, sure, but having long ago given up on brevity, they have no fear of meticulously describing how a feature or flag works. And they're just man pages, so you don't need to read the manual-for-the-manual first like I always find myself doing when I'm forced to use info.
Between Bob's army and insipid comments rising to the top, the comments sections of a lot of interesting, community oriented channels became useless (more so, even, than before). If nobody is actually looking at the comments section, then it doesn't really make technical sense to keep it as it is - it's just busy work for their engineers.
So it makes sense then for them to either attempt further fixes, or, in true Google fashion, simply remove the feature altogether.
I don't know about the rest of G+, but since the integration, I've been unable to comment on YouTube videos with my G+ account, something that worked fine before. I'd certainly call that "not usable".
Google Translate actually doesn't do a terrible job on the article text (it's not perfect, but it's understandable). It does kind of mess-up the English in the email though.
> Also there are worse things in the world than having to have that discussion with your kid.
The rest of your post is totally valid, but I think the above is a big take-away for those of us who don't abuse our kids. Parenting is in large part discussion, and some of the more important discussions are about uncomfortable things.
I've wondered for a while if the price for television advertising was/is inflated due to the fact that there's no way to track its impact. Web advertisements usually pay per click these days, which at least measures some kind of engagement, and yet advertisers apparently pay significantly less for it in aggregate than they do television advertising, which seems backward to me.
Having gone to RIT in New York, which contains the National Technical Institute for the Deaf, that seems a dubious claim. I lived with and went to school with a lot of deaf people, many completely, utterly deaf (no hear aids of any kind), and even took classes taught by people who were completely deaf. While reading and writing English was difficult for some (due to learning it after American Sign Language and a frequent de-emphasis of English at many primary and secondary schools that admit deaf students), being unable to hear at all was not an insurmountable obstacle to reading and writing proficiency.
Without threading support though, you aren't really encouraging discussion; just a bunch of one-off comments on the original material. And even then, you end up with ad-hoc threading like you see on MetaFilter or 4Chan, where new comments address old ones by the user handle or comment id.
I'd agree with you on hidden but... the Vim defaults are (generally) the most vi-like settings, which makes some amount of sense. At the very least it keeps people from squabbling about what should be the default.
OTOH, the default vimrc has a bunch of stuff turned on and tweaked depending on your platform. So that could be a good venue for turning on some of these new, Vim-only features. That may sound like splitting hairs, but I think there's at least a bit of difference between "on by default" and "set to on in the config mkvimrc creates".
Historically, in the United States anyway, unions were less about making it harder to fire people (per se), and more about forcing employers to think about things like safety, reasonable work hours (supposedly, one of the first major labor wins was the bakers' 10 hour day), reasonable wagers, and harassment.
An employment market with too few workers (where it's easier to find a job) is good, but isn't enough if all the jobs require 14 hour days, working with deafening machinery with little to no safety equipment or training, for paltry wages.
Now, if we're honest, modern unions work for all of those things too, even if major unions are sometimes seen in less positive light sometimes.
My 5 year old had a much easier time understanding that Netflix needs to buffer or downgrade sometimes than why there are advertisements on television.
I think that's because Netflix buffering has an explanation that directly relates to the activity itself, whereas the explanation for advertisements is a lot more abstract.