skysight-inc/HackerNews huggingface dataset:
I have found the tutorials and references on git-scm.com to be effective. http://git-scm.com/doc

Learning and adopting Git was definitely worth it for me and organizations I've worked with. It provides advantages that are difficult to describe in words and best experienced first hand [1]. Once you understand it, it's like a swiss army knife, or a power tool capable of manipulating source code commits any way one desires. The user experience might not be simple, but the semantics are simple in a way that makes operations easy to perform in Git that are challenging in other source control systems.

You can probably take better advantage of source control than checking in on a monthly basis. Personally, I recommend checking in about every 30 minutes to folks I work with. However, we're used to quick release cycles where code might reach production hours after we submit it, not years. I personally favor frequent commits also because it acts as an additional layer of protection against data loss, as well as facilitating frequent code reviews and visibility by coworkers, frequent integration testing, etc. These benefits support developing code as a team, and support a quick release process.

If you'd like to learn Git, then I'd recommend integrating it into your daily habits such that you're committing regularly, perhaps every 30 minutes to an hour. It will be difficult to learn the tool effectively if you use it only once per month.

[1] I'm happy to try if anyone wishes, but there are plenty of arguments out there. I would summarize by saying that Git simply works better than anything else I've used, including CVS, Subversion, Perforce, etc. Upon familiarizing myself with Git, it feels like those tools, through lack of capability, create a lot of problems and friction that Git avoids.
You can start with https://github.com/DigitalMars/DMDScript which is an open source (Boost licensed) JavaScript engine written in D.
It's a really good way of targeting mid-20s college-educated white men who smoke too much weed.
Mozilla Is Flailing When the Internet Needs It the Most
Linux Kernel Development, 1991-2015
Monopoly the name and logo would be trademarked.
Monopoly's board design and text would be copyrighted.
Monopoly's mechanism of action (how you play the game) would be patented.

More or less, IANAL, etc.
> The only serious advantage the car would have over the Tesla would be the 15 minute charger, which apparently isn't finished yet.

The Mission E looks much, much better than any Tesla model.
as some one who speaks two languages and is commonly labelled a genius (against my wishes) i feel i have some valid input here...

i do not have particularly great self-control and discipline.

one data point, but still, since its myself i do feel quite strongly that the idea that bilingual people have better discipline is an over generalisation.

in particular, living in the uk, where most people speak english as their only language, most of the people i consider to be substantially smarter and more eloquent than myself are not bilingual.

so the idea that bilingual people have a cognitive advantage is completely at odds with my personal experiences.
Your spelling is fine Kivutar, just one mistake left... 'sentances' should be 'sentences'.
An Inside Look at a Facebook Data Center
On a related note, Derek also covered dimethyl cadmium, which was new to me at the time: http://blogs.sciencemag.org/pipeline/archives/2013/05/08/thi...
What does the panopticon mean in the age of digital surveillance?
>Cliché is a noun and is not an adjective.

I wouldn't call this 'misuse', but evolution.
Hoare's CSP is exactly this. It's not a programming language per se, but I know of several DSL's that were built using CSP syntax.
https://en.wikipedia.org/wiki/Communicating_sequential_proce...
"Gun epidemic" is a nonsense phrase. This is all complete tripe. If people want to talk about reducing violence then great, let's talk about that. Political game playing like this isn't helping anybody.
Prescient New York Times article about Japan and oil, 1935: http://query.nytimes.com/mem/archive/pdf?res=9F02E1D6123DE53...

And the US military was busier in China that you might think:
http://query.nytimes.com/mem/archive/pdf?res=9803E1D6163BE43...

http://query.nytimes.com/mem/archive/pdf?res=9D0DE2DF1E38E43...
I've had this same problem for a time, but then I realized that forcing myself to commit a lot of times and keep commits meaningful (commits must have a message, and so the committed changes must all be related to that message) also forced me to work in a more focused way: one feature/fix at a time. That is very very good.
Prominent Docker, Inc., employees have spent years arguing against it, and they don't prioritize bugs around that use case. Which matters.
> Seems like a whole lot of wealthy tech writers/bloggers want to sell themselves on getting a Tesla because somehow its similar to buying an early mac.

Surely if you think Apple/Tesla is going to be great, the smart move is to buy early shares, not early products? The products will still be good/relatively cheap in future - the shares won't.
100% scroll hijacking by this website (and its badly done too) -- I had to scroll my mouse-wheel dozens of times before I even saw any content and navigation.

If you want to make a website that tries to illustrate Flash vs HTML, make the HTML part half decent and don't make it a horrible full screen canvas element that breaks scrolling and completely ignores any accessibility issues (much like Flash does).
Base65536 – Unicode's answer to Base64
Show HN: CrimeStream – Tulsa's police dispatch calls mapped out in realtime
Much better.

However, I suspect they will change the front bonnet design significantly in order to comply with pedestrian safety standards. Which would be very unfortunate for the aesthetics of the vehicle.
> No it isn't.

Hence the word "poised" as in it will at some point compete with Tesla.

Given that (a) the Tesla S has a pretty cheap looking interior, (b) Porsche is a premium brand with exceptional design sensibilities and (c) Tesla has limited distribution channels I suspect Porsche will easily be a match for Tesla.

When Porsche enters new markets they usually do so with very solid products e.g. Cayenne, Macan.
Actually, thinking about it, they are doing something akin to the iPhone model -- initially iPhone development was supposed to be done as html+js web apps, and devs revolted, and then we got a real SDK.

WatchKit is the html+js of WatchOS development. OK, not that bad, but the situation is analogous.
I think it's more of people treating their containers like VMs and stuffing it with things like sshd, syslog, a webserver, etc.
dupe.
https://news.ycombinator.com/item?id=10677686
The issue isn't your computer, it's the coding on their website -- it's creating a full screen canvas element to draw everything instead of using HTML markup with progressive enhancements.
It's a very interesting project and quite attractive.

However as others mentioned it would be useful to see some sort of scale for the dots, scale for the colors, and specifics on those numbers. For example, I have no idea what "Blue corresponds to levels below the W.H.O. yearly recommendations, light blue is below the W.H.O. daily recommendations etc." means... Does that mean "In one day at a Blue dot you will breathe in a whole year's worth of particulates, while at a light blue dot for one day you will breathe in one day's worth of particulates?"

As it stands, I will stick with aqicn.org for my Chinese pollution forecast simply because it has much more, more specific, information for me -- including intra-city maps. It would be more useful to me if there was perhaps a radio button where I could change between PM2.5 and NO2 for example.

It is very cool to see this on a worldwide scale though. And don't US embassies have public air quality data that you can scrape to fill out things like Africa? Or is that just US embassies in China...?

Anyways, thanks for your efforts.
How would that put more vehicles on the road?

Don't forget carpooling. What if one car could take everyone home then return to it's owner?

Also how would public transportation lose its advantage? It could be cheap, more direct, and more granular.
Indeed - anyone who bought a Model S in late 2012-early 2013 would have made $500k+ had they bought stock instead.
True. Yet a standard async DP API + wrapper around a process pool to integrate with it would be nice so ORMs move on. Righ now we are stuck with the status quo and all asyncio adapters for peewee / SQLAlchemy reinvent the will by creating some kind of pool and an ugly syntax to write each call.
Hopefully autonomous safety features will allow the relaxation of the aesthetic robbing requirements.
Tobacco smoke has finer particles than standard glycol-based smoke machines. For concert lighting, tobacco smoke gives a much better effect if all you want to see are the light beams, glycol is a bit coarser and not as smooth-looking in comparison.

You can get a fair bit closer to that look by using an oil-based cracker. Those have finer particles than glycol-based, but they have their own drawbacks as they rely on an air compressor that's either noisy or needs to be placed somewhere far away, and the oil tends to get on every light fixture and surface in the venue. It looks fantastic though.

When they introduced a smoking ban at the concert venue I worked at, I noticed that we had to run our smoke machines a lot harder to get the same looks we previously got "for free" from the punters smoking tobacco.
I should give KDE another chance. Last time I tried it was like a decade ago.
> The author is a sociologist. She's not criticizing working men's behavior.

It's not particularly necessary for the article. It reads more like elite signaling- "watches more TV," "does not contribute to housework," are there to remind you that you shouldn't feel empathy, that the subject is low status and low value.
TECHNOLOGY QUARTERLY NEW MATERIALS FOR MANUFACTURING
I hadn't taken it that way, it just seemed like an opportunity to express the vague unease with and choice to continue with that sort of comment.
Eden is hiring a full-stack engineer
A patent for an early 3-inch disk and drive mechanism was filed in 1980 [1]. The inventor was working on it since the early seventies [2].

[1] https://www.google.com/patents/WO1981001906A1

[2] https://en.wikipedia.org/wiki/History_of_the_floppy_disk#The...
> Good grammar is something that helps large groups of people understand each other quickly and clearly. It helps those armies and navies succeed.

Sure, but this has little to do with perception of good grammar (in the US at least).
Yes. I'd highly recommend making `git pull --rebase` the default behavior of your `git pull` operation. I'd thought that the Git folks were going to make this the default behavior at some point. It really ought to be.

`git pull --rebase` is a much better conceptual way to integrate changes from your upstream when working together collaboratively. The rationale is this: a newly released change should be, in the ideal case, simply an incremental diff against the head of the branch. It may have been developed by forking off at some point in the past, and incorporating changes over time, but those are implementation details of how the diff has been constructed. Once the diff is ready to go, ready to be committed, it's just an incremental change to the head.

By working in a branch and using `git pull --rebase` to incorporate upstream changes, you keep your code in a constant state of being "an incremental addition" to the primary branch. Indeed, it's very similar to what happens with Perforce when one runs `p4 sync ...`, by comparison - your local code is updated to account for the new remote contents. Finally when you submit, your change looks like a single incremental commit, or series of commits. The resulting history is simple and linear.

Sometimes people object to this because they claim that source history should be the "true history of what happened", whatever that means. I believe those arguments miss the point of source history. Source code history is always an abstraction over what really happened. Imagine an extreme example: an IDE that generates a single source commit for every keypress you type while editing a file. That's the true history of what really happened. But is it useful to commit that history to a repository? Of course not - that history is kept locally in your IDE as undo buffer. Similarly, it's often not useful to pollute the commit history with implementation details of how you developed the change (sometimes, but not often).

When you develop changes locally and push them upstream, you rightfully make a judgment call about what level of detail about the development process should be exposed in the history, and what level of detail should be hidden. For example, you might hide detail by combining many keypresses into one commit, as is conventional, or by squashing multiple related commits into a single commit. You might hide the detail about how your change was developed over time by using rebase to make it appear as if it's an incremental change to the head, even if it was developed over time and involved several integrations from the upstream. Sometimes these history-abstracting changes are not appropriate, such as if you truly need to develop a branch in parallel with the main branch, that many people are collaborating on. In that case, a branch may be appropriate. Most of the time, it's ideal to develop changes directly on the master branch, as an incremental change to it, using `git pull --rebase` to keep local changes up to date, which will result in a simple, linear history.
Our (Bare) Shelves, Our Selves
Can't wait to see Porsche's charging network. It's going to be as extensive as Tesla's Superchargers, right?
Yeah the interior of the tesla is the biggest gripe most people have with it.

There was a tesla promo in the business center i work at and I got finally a chance to sit in one and considering the 100k> GBP price tag it has in the uk it didn't feel like a luxury car at all.

Even tho the display model had their best interior the leather didn't feel as good as entry level German cars and the nice carbon fiber inlaid dashboard just felt cheap and squeaky.

The interior of the tesla is to me pretty much the same quality of most higher end sedans like the accord and the Passat not anywhere close to luxury car levels.
Heh. Here's a story. The book is long out of print but sought after - the non-microfilm version from Rutgers University Press retails for several hundred dollars in the second-hand trade.

You call up Rutgers, and RUP tells you that they have no idea who owns the publishing rights. Copyright protection lasts far too long, and something really needs to be done about orphan works.
RIP all other JS charting libraries.
A process supervisor (foreman, monit, etc. ) is just one of the things an init system starts. The set of items you want to ensure are always running isn't usually the same as the set of items you want to start with the system.
Addition still takes time though doesn't it? The idea is I could start an addition operation, and then be notified in some way when it's done.

I think the idea most similar to what the grandparent wants is instruction-level dataflow, where programs are DAGs, and instructions are only run when their inputs are ready, rather than when a program counter reaches them.

Physical dataflow machines were built that did this in hardware.
This is really cool! I'll re-implement this in C or Python this weekend if I have some time.
> (it's undefined for unsigned integers in C):

No, unsigned integer overflow is defined to wrap around in C. Only signed integer overflow is undefined.

> I wonder why Go doesn't just define signed integers to be in 2's complement representation

It does: "The value of an n-bit integer is n bits wide and represented using two's complement arithmetic" (from https://golang.org/ref/spec#Numeric_types)
They might use that infrastructure which will allow tesla to become what better-place failed to do - a service provider.

Supercharge is free for tesla owners afaik why can't they charge other ev owners, this seems to be both lucrative and savvy as it will solidify their tech as the standard which will give them the edge since they control its life cycle.
> Hence the word "poised" as in it will at some point compete with Tesla.

Yes, but since it's scheduled for 2019, it will compete with Tesla's 2019 lineup, not their current 2015 lineup and models.

> Given that (a) the Tesla S has a pretty cheap looking interior, (b) Porsche is a premium brand with exceptional design sensibilities and (c) Tesla has limited distribution channels I suspect Porsche will easily be a match for Tesla.

Agree, but in the same way that Porsche has four years to figure out how to get the thing working, Tesla has four years to improve interior quality.
Totally agree, the length of copyright protection is absurd. Doesn't mean we should use HN to pirate stuff though.
Those examples are similar to my music/dance and etiquette/dance examples from the Renaissance -- dance scholars are much rarer than music scholars.
git config --global pull.rebase true
I think such security issues are similar to the ones author described. They require decent language-level abstractions to disappear as well. Some sort of lightweight processes to deal with trust boundaries explicitly and easily.
Zuckerbergs $45B Loophole: Using an LLC that he has absolute control over
Going back to 2010, there have been 182 fatalities[1] in the United States due to mass shootings.

In the same amount of time, there have been about 158 fatalities due to being struck by lightning.[2]

In 2013 alone, there were 611,105 fatalities due to heart disease and 56,979 due to influenze and pneumonia.[3] The stats are a bit out of date, but from 2005-2009, ~3,500 people drowned each year.[4]

If you're worried about yourself or a loved one dying, don't worry about dying in a mass shooting. It's about as likely as being struck by lightning.

[1]:http://www.motherjones.com/politics/2012/12/mass-shootings-m...
[2]: http://www.lightningsafety.noaa.gov/fatalities.shtml
[3]: http://www.cdc.gov/nchs/fastats/leading-causes-of-death.htm
[4]: http://www.cdc.gov/HomeandRecreationalSafety/Water-Safety/wa...
I think what copperx is talking about, and certainly what I was talking about is not your ability to speak and communicate at a native level in the languages you speak, but your inability to achieve a very high level of competency i.e. talk with the clarity of a Steven Pinker or Noam Chomsky or generally anyone you consider to be highly articulate. IMHO this is largely due to actively speaking multiple languages on a daily basis. Its wierd because I can't really explain the types of mistakes but its things that second language learners won't ever do, like starting a sentence in one language and finishing in another, or adopting a verb from one of the languages you know, for instance in DE/EN, "gimme den ball" or "er hat gesagt he's sold.". It requires active concentration to not do this and can often lead to slight pauses where you are searching in your head for the X language equivalent of the term in language Y (only then to realize you should have started the sentence in a completely different way to articulate the same sentiment).

Given there aren't many people in general that attain a high level (Novel Authors, Great Lecturers, Debaters, etc.) of linguistic competency, still the few that do attain this, seem to almost always be monolingual or do whatever they are best at in only one language.

For me, with one side of my family everything is german/polish, with another english/spanish, and its very easy to casually speak in whatever language for daily tasks because if you are with family you can just use whichever word comes to mind regardless of what language it is in, and if not the vocab is so common and easy there is no difficulty just saying everything in the one language (even though your grammar is at times influenced by your other languages like copperx says - ahh). But once you go to writing an essay, giving a lecture or presentation, especially in one of the languages you don't usually do that in - you immediately realize how segmented your vocabulary is (or at least that happens to me :).

Not to mention that in informal settings with family, you are constantly mixing stuff up because your mother in law is speaking polish your wife is answering in german and you're asking you're wife something in spanish.
This isn't a patent on the Space Shuttle. It's a patent on an "improved" space shuttle where the External Tank is placed in front of the orbiter. (I didn't read why, but I assume it's to minimize various losses.)

Given the problems with foam shedding on the actual ET, it's probably a good thing they didn't adopt this configuration.

I checked, and it's actually somewhat buildable - if my back-of-the-envelope math is right, it's shorter than a Saturn V.
Well, since magnetic media has a very finite lifetime, you don't have much longer to worry about Zip disks -- they'll all be unreadable soon.

Which brings me to another fun story. My girlfriend runs a book conservation lab, and she was wondering if she should try to read the bits on a floppy disk associated with a book on numerical methods -- it costs $$ to try to read the disk, and given the age, it was unlikely to work. I know one of the book authors, so I told her I likely could probably find a copy of the software on the Internet, if she found some pages that listed the names of the software functions. Turned out that it was a copy of LAPACK, which is available at NETLIB. Only one checkin to the code since the book was published in 1986...
curious - I remember when modules were first proposed I thought Apple was heading up the initiative, based on their work with Objective-C. I remember reading slides someone at Apple prepared describing the likely syntax and everything...
The comments on the NPR story are amusing.
If this court can throw out a settled, century-plus-old understanding of the Second Amendment, then another one can certainly restore it.
I wonder if there is any overlap with Ayasdi's topological data analysis "similarity maps" (which are network representations of datasets).
No, that's just a very basic implementation of macros. Even C can implement max that way.

What distinguishes templates from macros is that templates deeply interact with and are instiantiated at the time of typechecking. Macros, on the other hand, are expanded at parse time (or, in more sophisticated implementations, at name resolution time).
Does this work because there is massive redundancy in the DNA soup? So if some strands of part of strands are contaminated, there are 100s or 1000s (millions?) of cloned DNA molecules floating around?

Or is a single DNA molecule capable of long term data data storage and retrieval? I realize of course that scientists pull DNA from long dead things all the time, but for example there is of course hundreds of trillions of cells in a large mammal with copies of the DNA.
Good comment. You almost have me convinced.

But what is hip hop? Poetry or music?
Clump – A library for expressive and efficient service composition
"According to MS' blog post, this is based on the current modules proposal that the committee is working on. Isn't Clang also following the same proposal?"

The blog post is just oddly written to make it seem like the proposal MS has implemented was approved.
Not sure why it was done, but it's confusing.
I was referring to this: https://code.google.com/p/android/issues/detail?id=62644

I'm not sure how the current status of that warning is, however.
for large projects, they help a lot.
I've seen large projects whose compile time has gone from 3 minutes to 10 seconds.
Is there a way to get just the DNA you're interested in sequencing in the first place? Eliminating the sequences that look out of place afterwards does not seem like a good strategy.
The performance is hard, but the bug-for-bug compatibility is what will kill you.