skysight-inc/HackerNews huggingface dataset:
Erlang's strengths (and they are pretty much unique for a production level language) are:

* Fault tolerance

* Concurrency

From fault tolerance comes isolation. Don't let a part of your program that crashes affect or crash other unrelated parts of your program. Memory heaps are private for each actor (+/- some refcouting for binaries).

Hot code reloading comes from fault tolerance as well. So do immutable data structures and functional aspects.

As for concurrency. Erlang emphasizes "liveliness" and low reduction over throughput. This is quite rare and is very interesting. It means under concurrent load, it still tries to be responsive. So if 100k clients are connected, and on is performing a CPU intensive job, the other ones shouldn't get socket errors or get blocked. This might come with a trade-off of slowing down that one CPU bound function with frequent interrupts.

Here is a good article on how Erlang's scheduler works:

http://jlouisramblings.blogspot.com/2013/01/how-erlang-does-...

Now Erlang is a tool and it there is no free lunch. All these features you saw above don't come for free. Erlang will be slower in numeric and sequential computational tasks (the language shootout type benchmarks, like finding the shortest path, computer determinants and so on). So in some cases it won't be the answer. You'll have to benchmark and decide for yourself.
Dividers? Oh, then you'd love the Trough o' Urine. Shoulder-to-shoulder while you let it flow into one big long shared container, no hang ups allowed, and no peeking. Available at finer concert venues and race tracks (and Washington state ferries, as I recall).
Everest launch in Australia
I wouldn't say better, just different. Thanks for posting!
We have the same problem with Bitcoin. On one hand we'd love a system that automatically collects a stack trace, memory dump, information about the environment on a crash and sends it to us (like Google Breakpad does). On the other hand it opens a whole can of worms if accidentally a private key is sent.
Encryption is no solution in this case; the data still is stored somewhere which could be compromised.
It's very hard to automatically collect diagnostic data without potentially collecting sensitive data...
The most important problem of our time is the risk of losing all privacy. We must work to make strong crypto widely accessible to the masses.
The important bit isn't the Maybe-types, but all types that are _not_ Maybe.

If types aren't non-nullable by default then any function parameter or return value can potentially be null and a robust program practically needs to have null checks _everywhere_. Otherwise, when your program throws a NullPointerException you'll have no way to know where that null originated from.

In Haskell, the types guarantee that you never ever have to check for null (in fact, you can't even) unless the function's type explicitly allows for the possibility of having a null. In addition, you have several ways to compose function calls that might return null in such a way that you don't have to check for each null case separately.
Dance in a Year
That live editing CSS thing looks awesome, but it's been a few months since the video was released. Is it still an active project?
I think the reason is because that really didn't work for some reason. Starbucks experimented that idea for a while. (I think it was something like 3 hours for buying a something using registered card, and that then they decided to open it up...)

My personal opinion about MAC address filtering though, if they become the norm, everyone will start using a piece of software that changes MAC address periodically... (As it's already trivial to change your MAC address...)
Google Analytics isn't perfect (not meant to do cohorts or track users), but it's free and it can be used as a comparison with your server logs and other analytics services. (If the delta is very small, it means you have a good implementation, if the delta is large, maybe there's a problem in the implementation)

Besides the ones you mentioned, if you want to host your own analytics service and customize it, you can look into Piwik or Snowplow.
Org mode?

http://orgmode.org/
Cleartrip: How we redesigned everything
Combination sink-toilets are very common, a wide variety can be seen on Google images.

https://www.google.com/search?q=combination+sink+toilet&tbm=...
not the OP, but here's an article: http://washington.cbslocal.com/2013/06/23/promise-of-price-c...
0 commits on master and 0 bugs fixed in 9 months, a handful of commits by a user who branched off of master a couple months ago (and no PRs)... I think it's safe to say that that the 'public' version has been dormant for 9 months.
When you`ll take alook at the Financial Reports at Torproject.org.. In 2009, 72% of their refunds were payed by the US-Goverment. In 2009 it was about 1 Million US Dollar.
And there were News years ago that tor must have a backdoor for the german BND, by law.
Go to Chinatown Coffee :)
Your actual parser there is the definition of frame_struct, which you left out; and, as others have pointed out, if you're putting ints in there, you need to ntohl them. Also, you probably need some kind of extensibility.

And I don't really think "H:news.ycombinator.com" is quite as illegible as your suggested 32-bit integer space — which, by the way, is small enough that you'll probably need a central registry to prevent header name conflicts — and it also occupies only two bytes instead of four for the header type. So, from my point of view, the "completely illogical" thing is to go from, "The header names currently in HTTP are too long!" to "Therefore let's replace them with 32-bit integers in a binary protocol" instead of "Therefore let's shorten the header names in HTTP", which solves the problem more thoroughly and with less collateral damage.

And what is this about "if you string it along enough"? We're talking about a parser (for RFC-822 headers without continuation lines) that fits into 110 characters, here, without the least obfuscation. Less than a Tweet. In fact, I just Tweeted it. And it worked on the first try.

> the completely nonsense argument that using netcat once a year is worth a ridiculously impractical protocol format.

You know, we did kind of try binary protocols already: the whole IPX stack, CIFS, X.everything, SNMP, TFTP, ICB, Sun RPC and thus NFS and NIS, and so on. A few survive in common use: DNS, TCP, IP, ICMP, SSL, SSH, BGP, and to some extent, SNMP. And there are lots of them working fine inside of particular companies, rather than between implementations by different vendors. But for the most part, they've been replaced with textual protocols, despite the lower efficiency and in many cases the first-mover advantage: HTTP, SMTP, and IRC, and previously FTP, Gopher, and Finger. You seem to be arguing that was an accident, or a mistake. It's not.
CC may only apply to the artwork/creatives, where MIT may refer to the code.. this is only speculation.
An optional<T> has two states: it either holds a T or nothing. There's no third state.

All pointers can be null, but unlike (for example) Java, we don't have to deal with pointers to objects all the time. C++ has value types and it's perfectly possible to pass objects that cannot be null.
"What happened to simple protocols?"

Answer: The Internet is still running on them, 30 years later.

Whenever I read something like "simplicity is hard", it makes me cringe. I hear that a lot, and I see evidence of gratuitous complexity everywhere I look these days. I'd hazard a guess the engineers behind SDPY would find simplicity (and reliability) boring.

Debugging binary protocols is either great job security for over eager engineers like the SPDY team or a great waste of our collective time. I'll let you all decide which.
Who's we? You and author/OP? Because I've got good news for you, Moore's law corollary has merely slowed, not stopped. It will stop, just not now.

I think Moore's law will work better on mobiles, because they are retreading known grounds and they are way further from reaching, real physical barriers than regular computers.
Actually I think it was more related to:

- sloppy programming, the same kind we see nowadays in JavaScript

- doing everything in the main thread

- not caring to learn how to use Swing properly

- not even taking the time to switch to the native look and feel

- not caring about users and providing a rich UI experience
Functional language people are like "Embarassingly parallel" enthusists.
Haha, that was my first thought too. Some kind of retro revival!
>> coupled with miserable weather

90°, 100% humidity, no wind, mandatory suits.

what do you mean miserable weather?
Anyone interested in optimising their mobile web applications should watch Apple's Safari tracks from this year's WWDC.

They have plenty of informative advice on how to improve general performance and how to use tools WebKit provides to measure performance problems.

Some key take aways:

Avoid using libraries (like jQuery). It will reduce memory consumption significantly.

Be careful how often you're invalidating style info and forcing recomuptation

Avoid using scroll handlers to do layout (especially when you're likely to inadvertently invalidate styles at the same time)
>> single laptoppers

Sit down with one of them, make a friend.
Yeah, the Datastores API does two-way synchronization. Also, offline caches are done for you and offline changes are propagated (with conflict resolution) when the internet comes back up.
I realize the phrase was a little awkward. As I was writing the comment I struggled with finding the appropriate phrase that would not sound diminutive. I thought awkward was preferable to diminutive.
That's great and all, but you didn't address the issue. We're discussing this new notification system that will only ever work properly on Chrome. The latest posts on that chromium blog are even worse:

1) Richer access to Google services and better OS
integration in Chrome packaged apps
- Identity API - Google only
- In App Payments API - Google Wallet only
- Analytics API - Google Analytics only
- Native Messaging API - The problem we are discussing

2) Dart - obviously a way to create a two-tier web with
Chrome being the only option for performance. (You can
bet it will be incredibly difficult for other browsers
to package/integrate the Dart VM easily).

Your roundabout answer to this question leaves me very concerned for the future of the web if Google actually thinks this isn't a problem. I do believe it's looking like the only responsible option for an open web is to ditch Chrome and try my best to lower Chrome market share.

We're going to look back on this in 5 years and kick ourselves over letting Google do this. I hate to say it, but Google is now the biggest threat to an open web.
I think the main issue is that those environment so far insist in a VM model.

Most likely if Android used native compiled Java, performance could be improved.

Microsoft went this route with Windows Phone 8, as they replaced the .NET JIT with a proper native compiler when targeting Windows Phone.
WikiLeaks: Snowden Has Not Accepted Asylum in Venezuela
Cloud storage shoot-out 2013 – performance and reliability
There's a widely circulated story about everyone being stumped about how dislodge a truck wedged underneath an overpass, then a child suggesting that they let air out of the tires. It may be apocryphal, but it used to be referenced pretty often.
As for Starbucks, my local one (it's one of few bigger "reserve" store) had this problem before they renovated.

When they renovated the store, they changed it so they have "bar" desk facing the two sides of the store facing the window with plenty (pretty much every seat) and also some in the very middle section of the seat.

What I have been observing is that people who need power for their laptop tend one of those seat -- while some people do use laptop in other seats, they are more transient.

Of course given this is all given there are enough space to do this type of arrangement, but sometimes these approach of actually manipulating behavior rather than being prohibitive is one approach those places can take.
That's nice fiction, but it's entirely unfalsifiable, making it a completely ineffective as a theory.
I read in the yelp reviews that they were singing in the middle of the nights, and throwing out parties during the week.

The apartment complex should write lease violations to offenders (or Google)
I don't think this is America against democracy. Democracy is mob rule.

I think this surveillance was originally a good idea, since all the data's out there and the bad guys are using it. It was abused when it was turned from "listen to all traffic and see if you can find terrorists" to "use this whenever we suspect someone of anything."
Free wi-fi? Free power? SOCIALISM!
Looking forward to typed channels. I always found it very unfortunate that a scala library would throw away the language's wonderful type safety.
It's in beta; don't want to nail down the protocol.
Gosh, a lack of hierarchy means that everyone is unstable because they might get climbed over by others. Who would've guessed.
I think the thing to do is just to write a function to keep stepping through the list until you find the right place to insert, and then just use container/list.

Sorry to be "that guy" who questions the question, but sorted lists aren't really a great data structure. As you probably already know, insertion is O(N), where N is the total number of elements in the list. It might be better just to use the GoLRB library, which provides some always-sorted tree structures.
The theory that it should be falsifiable in order to be valid, is not falsifiable.
Good thing that the author provided such an exhaustive list of arguments supporting his opinions. Oh wait. Between using pointers and the standard library, I think that I will stick with pointers.
Going to binary seems kind of silly at this point.

HTML is text. Javascript is text. XML is text. JSON is text. SVG is text. CSS is text.

Is it really worth the complication to save a few bytes on HTTP headers when you're just going to shovel out inefficient text data in most cases anyway?

I don't understand why they're trying to shove this down everybody's throat as a new version of HTTP.

There are a ton of ports besides 80. The better thing to do, IMO, would be to make a new protocol on some other port and add it to their browsers.
Legitimately excited to see Blink-based Chrome released. However, Chrome 28 still does not support un-prefixed CSS transitions, transforms, and animations. What gives?? http://www.chromium.org/blink#vendor-prefixes
Coffee and the Brain [video]
> Citation needed.

No idea regarding relative amounts/toxicity etc., but I presume they are referring to these issues:

http://news.yahoo.com/solar-industry-grapples-hazardous-wast...
>Dart - obviously a way to create a two-tier web with Chrome being the only option for performance. (You can bet it will be incredibly difficult for other browsers to package/integrate the Dart VM easily).

Doesn't the same logic apply to Mozilla's asm.js?
I think the really big changes to packaged apps are in Chrome 29, the current dev channel build.
Doesn't sound nearly as horrible as the censored world you propose. That fucking shitty world would be hell.

Carlin's Seven Dirty Words: Shit, Piss, Fuck, Cunt, Cocksucker, Motherfucker, and Tits

This should be required reading alongside Shakespeare in high school.
http://www.erenkrantz.com/Humor/SevenDirtyWords.shtml
Firefox adds add-on memory reporting
For your own peace of mind, please never put expensive gear in checked luggage. It is very likely to get stolen.
According to the shills employed by or rooting for Google, here on HN and elsewhere on the internet, it's not silly: It is paramount.

See, it allows the request for www.google.com, including all of Google's tracking cookies, to fit inside one TCP-frame, causing a 5ms improvement in load time, and Google has evidence that this means they make more money.

Never mind the open, exploratory nature of the internet and how text-based protocols was what made the internet into what it is today. We're going to throw away all that which the internet has taught us about that because Google says we should.

This thing is fucked up beyond belief.

Edit: found a link to the IETF discussion about this:

http://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar/...

It admits in plain sight that the only thing they care about with HTTP 2.0 is solving Google's massive-scale issues at the cost of everyone else:

> I finally admitted it was a dead end. At the moment the
challenges consist in feeding requests as fast as possible over high latency connections and processing them as fast as possible on load balancers

A good, open, self-documenting protocol didn't suit Google, so let's throw it away. It's a "dead end", after all.

Jesus christ these people need a bitch-slapping.

More emails on the subject can be found here:

http://www.w3.org/Search/Mail/Public/search?keywords=&hdr-1-...
Urine in your bladder is sterile. It passes through your urethra on the way out, which is definitely not sterile.
Author provides source code using non-monospace (!) slanted (!!!) font. I would have wasted a damn gigawatt to unsee that.
Amazon Quietly Tests Streaming Flash Videos to Kindle Fire Owners
I remember seeing on Top Gear a review of a car with a collision detection system that could detect pedestrians. (I think it was a Volvo.) I wouldn't be surprised if it also detects bicycles without active cooperation from the cyclist.
Can people comment if they down vote please? I see no errors above and this seems a little harsh.
FYI: In 2007 was hired as a new-grad software engineer at Google with a college GPA of 2.66

So Google didn't have any minimum GPA requirement. I certainly was asked about the low GPA during my interviews, but it clearly didn't stop them from hiring me.
Not answering your question, but developers can also use http://parse.com or similar.
I am with you on this one.

I only got dropbox installed on my PC because we needed to exchange some files with an external contractor that only used Dropbox.

As soon as the project was finished I removed it from my PC.
It strikes me that 'puzzle languages' are just languages with non-mainstream semantics. If we lived in an alternate universe where the dominant paradigm was entirely pure, then those odd languages where any bit of code can change any part of the state of the program would be puzzle languages.

Hague defines puzzle languages by referencing the experience of realizing you're going down the wrong path and having to completely restructure your code; I have had this experience in Python and Java in the past, and conversely, I program in Haskell more or less daily and therefore almost never have that experience there any longer.
I of course meant those four horrible days called "spring" and "autumn". :-)
It's live now. Sorry, I put the publish date a couple hours ahead.
If browsers did that they would break the Web. They must clamp to some low delay (4 ms, I believe) or else some pages will lock up.

See https://bugzilla.mozilla.org/show_bug.cgi?id=123273
I wasn't referring to residency spots at accredited medical schools.

I was referring to medical school accreditation itself.
This wasn't really possible until the addition of the Macro and enhanced reflection systems in the most recent versions of Scala. Type information isn't stable across all runtime environments. They had to come up with a way to generate proper types for distribution on the fly.

Someone correct me if I'm mischaracterizing this please. I'm only a little familiar with the new typed channels.
The 5-10x difference mentioned is the difference in raw hardware speed between mobile CPUs and desktop CPUs, not a reference to JS speed vs native speed.

JS speed as compared to native depends heavily on the nature of the code being executed, how type-stable it is, how polymorphic it is, what its allocation behaviour is like, and a number of other factors.
gcc is owned by Google? Someone should tell the gcc folks and Richard Stallman that.
See slide #5 onwards of:

http://www.cis.upenn.edu/~bcpierce/papers/harmonyslides-2003...

It explains the terms and explores the pros and cons of each approach.
In the meantime, Linux has (by default) an adaptable timer and will soon be fully tickless [1]. In other words there will be no fixed timer and the OS will calculate when the next wake-up should be scheduled and sleep until that time (or until an interrupt comes).

At the same time, PowerTOP [2] will nicely show you which programs or drivers are responsible for waking up the computer and estimate how much power each program is consuming.

[1] https://lwn.net/Articles/549580/
[2] https://01.org/powertop/
> Every time Firefox introduces a cool new feature, they emphasize how it's standard, or being put into the standardization process [...]

No, not really. They just added `let`, iterators/generators, destructuring assignment, etc in 2006 without asking anyone. Today, you can even use it without opting-in (via: type="application/javascript;version=1.7"). This stuff is supposed to be in ES6 in the future.

Same deal with APNG. They just added it in 2008. It also isn't standardized.

Firefox also supports "jar:" URLs for some reason. Here is a demo: http://kaioa.com/b/0907/jartest.html

Well, all browser vendors are like that and it's generally a good thing. If one of those experimental things turns out to be useful, other browsers will adopt it. Good examples for that are things like JavaScript, XHR, or text-overflow:ellipsis.
Do you inspect every single line of code? Or at least grep the file list to see if you find a suspicious looking name? Don't think so. Your default assumption should thus be 'everything is compromised' since you did not verify it :]
I agree. However parts of the nuclear industry would do the whole industry a great service if they cleaned themselves up. Up front honesty about mistakes and accidents might make a bad headline or 2, but it they look far worse when the retrospectascope is peering in after a big problem. A critical media and general population would (IMHO) be more accepting of accidents if major events (Fukishima being a big, unusual example) weren't followed by months of backtracking, half truths and lies.
Is it just me or are coffee shops turning up the music too? I'm having a hard time finding a coffee shop where I can have a skype or phone call. Loud music and/or noise is one way to discourage long-term telecommuters who need to stay in touch.
Shoot me an email, brianw.stearns@gmail.com. I have [very] limited practical admin experience, but I will try to scare up a friend who can devote some time to it.
How did this make the front page again? I don't get why anyone would care about this. If the company was Exxon, GE or BoA instead of Google, would this have made the front page once, let alone twice?
Perhaps it's not a theory. Perhaps it's an axiom.
Merging lock elision into glibc
DNS-LG - Multilocation DNS Looking Glass
McDonald's is increasing automation. Seriously, go in and order a smoothie; once the order is finalized, the smoothie machine will dispense the ingredients, run the mixer, and put the result into a cup (that it also dispensed). Some of the locations have automated soda fountains for the drive through as well. I have heard stories about call centers for drive through ordering too (although I haven't seen that in practice)
Would they expect your grades to change?
That would limit to some degree the gear that you could bring to the fight. Given that choice of tools in this situation is a valid differentiator I don't think arranging the challenge as "Backtrack5 at Dawn" is a realistic way to go about it. Clearly you could write or upload anything you wished if you sshed in, but the added convenience of BYOD seems like a net win.