coyotebush

No, those two statistics alone don't say anything about the total number of CS majors. Per the article, CS represents ~20% (of students with declared majors).

This list appears to include only software packaged in Debian, but that fact does get a mention at https://www.debian.org/intro/about#history

Diceware is great, though the paper fairly points out that algorithms like that and https://xkcd.com/936/ necessarily often choose very uncommon words.

I suppose the Markov model could just as well use whole words (as done in all sorts of other scenarios), at the expense of substantially longer passwords.

Agreed that the expandable sections feel a little unusual for this type of documentation. They're great for drilling down to particular information, but not so much for skimming or reading straight through.

I might even suggest putting the sub-section navigation in the sidebar a la readthedocs.

By Kerckhoffs's principle, yes. https://en.wikipedia.org/wiki/Kerckhoffs%27s_principle

Cool to watch, though this is a fairly straightforward model of complex contagion on a finite grid. It's similar to Conway's Game of Life in that there's a grid and local rules, but beyond that, the nature of the rules results in a different kind of behavior.

https://en.wikipedia.org/wiki/Complex_contagion

http://www.ladamic.com/netlearn/NetLogo4/DiffusionCompetitio...

I believe using those together counts as two user-defined conversions and is rejected. But one or both of those might as well be declared explicit.

> I wonder if they weed out duplicate copies of, say, jQuery.

Linguist tries to filter out things like that:

https://github.com/github/linguist/blob/master/lib/linguist/...

> Migrate to a cmake-based build

> Legacy support and compile-time features

> Platform-specific code

Sounds like well-justified cleanup, although it's possible this project is underestimating the usefulness of feature selection.

> New plugin architecture

> New GUI architecture

Now that's cool and ambitious.

I wonder whether Bram has an opinion on this?

Twilight (color adjustment is in the free version) works nicely too.

So the jQuery regex, for comparison, is

  (^|/)jquery([^.]*)(\.min)?\.js$

while the Bootstrap regex in question is

  (^|/)bootstrap([^.]*)(\.min)\.(js|css)$

with the ".min" not optional. (Looks like this was the intent [1]).

The 68.9%/26.5% percentages match the 130k/50k ratio of bootstrap.css to bootstrap.js, so it looks like only bootstrap.min.js is being excluded?

[1] https://github.com/github/linguist/commit/d5002ef06a9f346391...

Firefox just shows broken images, because of

    <img src="data:image/png;base64data:image/png;base64...

Since multiprocess is in the regular Nightly, the code is in the main line of development (mozilla-central). Based on the preference, it decides at runtime how to handle the content/chrome interface.

But when Mozilla does branch off separate trees, VCS merges and lots of automated tests are largely sufficient.

Texas licenses software engineers, as do some Canadian provinces, and IIRC (from my SE ethics course) some other US states are implementing similar programs. https://en.wikipedia.org/wiki/Software_engineering_professio...

I only noticed one password hint that exactly matched the password -- I'd have thought that would be disallowed. Plenty of hints that were the password plus one character, reversed, etc.

Alternate degree structures and modes of instruction are definitely worth exploring.

Points #1 and #5, though, would likely not go over well with current university faculty. Reshuffling of faculty roles seems much better designed by those with classroom/advising experience. And who's to judge which are similar or niche fields of study, besides departments themselves?

The Mozilla community is very accepting of new volunteer contributors. Ask how you can help!

For Rust specifically, I found this: https://github.com/mozilla/rust/wiki/Note-guide-for-new-cont...

I guess the point that I was really trying to make was that reading the code and documentation can only get you so far, and doesn't help nearly as much with the bigger-picture "why" questions. (The code I worked on, in addition to being well documented, was also IMO pretty well organized and clear.)

Anyone else remember these from Amazon Trail (in the final scoring process)?

https://en.wikipedia.org/wiki/The_Amazon_Trail

Oops, that's right.

Beside the point, but

"a 40-year-old man" "He was a civil rights activist in the 1960s"

doesn't really add up.

My history file is de-duplicated (oh-my-zsh enables hist_ignore_dups), so this sort of approach is never accurate.

Git comes out on top, but presumably because most of my invocations are unique ("git commit -m ..."), while things like "ls" are farther down the list.

Relevant: https://github.com/paulmars/huffshell

Similar work:

http://www.cs.utexas.edu/~elie/networks.html (on HN: https://news.ycombinator.com/item?id=4914267)

http://ajverster.github.io/blog/2013/04/01/redditinteraction...

Heh, nearly 80GB... and that's with mostly testing out the queries on the smaller publicdata:samples.github_timeline dataset.

Yeah, per the footer, color is the primary programming language as identified by GitHub. A key felt like a bit too much clutter; you can always click on a repository to open its page and note the language listed.

Analyzing a larger dataset would be neat indeed, though somewhat more challenging. Especially for the layout algorithm to produce something nice in a reasonable amount of time.

There are ~11k repos with >= 100 stars, compared to the 825 I had here (fewer after filtering for the giant component).

Scroll to zoom. Sorry that's not noted anywhere.