skysight-inc/HackerNews huggingface dataset:
http://www.runescape.com has been rewritten entirely in WebGL, they just released the beta and are upgrading the entire game in the next month or so.

It's pretty big news, as far as I know they are the first major MMO to swap to WebGL. They were using Java and had been building on it for nearly 10 years but they found that WebGL offered better graphics performance and easier programming than it's Java equivalent so decided to switch. It is slower, probably around 10 or 15%, but offset by all the new graphical features, longer draw distances, more vivid colours, etc.
Missile Launch Creates Weird Expanding Light Bubble in the Sky
You handle it honestly, openly, and by negotiation with the workforce.
Ecuador Pegasus satellite fears over space debris crash
My investment in Tumblr (11/2007)
I understand the problem of spam in notifications, but my question is, what's wrong with deleting an app that spams you, or not installing it in the first place if you don't trust their use of push notifications?
>Push notifications don’t need a permissions process.

Shouldn't happen and won't happen. You're arguing that you know better than the people who are actually using your app when chances are, you do not.
If a monarchy were better for the monarch and equally good for everyone else, I would favor a monarchy.

...the tendency is to see the privileged system constantly improved and the fallback languish into a horrible state.

I'm don't understand - how does the existence of alternatives prevent improvement? Could you clarify this point?

If Lenovo's customers were superior (in any relevant sense) to Apple's customers, would that cause apple to "languish into a horrible state"?
What do you need is a project that can disrupt the world. I wish I were in your position, I would make for sure the projects I'm design but well, someday I will be able to take it to the top by myself.
The Future Has Arrived With Spray-on Clothes
The only problem with "Greek Yogurt" is that there is no separate thing as Greek Yogurt. It's just a western marketing name for strained yogurt. Yogurt is a food of Turkish origin and even the words Yogurt and Chobani are directly from Turkish language. Yogurt and its derivatives are very common throughout the former Ottoman geography, from Balkans to Arabic countries. Does that really matter? Yes, if culture and history has any importance.
Your comment has made me curious. I tried to think of some examples of performance sensitive apps that aren't amenable to multi-threading and I couldn't, but it seems like they could offer interesting areas for R&D. Can you share some examples?
I have only two recipes: I get emails for reddit replies and messages, and any post I save in reddit gets added my to Pocket queue.
Both are fairly standard actually. I wouldn't call them creative. I often look at the website, and it makes me think of the awesome things possible, but I then realize I really don't need that much automation or mashups.
No.

http://www.joystiq.com/2013/05/21/xbox-one-not-backwards-com...
How Not to do a migration to a new version
Solar Impulse plane sets new distance record on Dallas flight
Am I the only one who's not all that surprised or inspired by this? We know we can print arbitrary 3d objects of different sorts of plastics, so if any human being needs something of that kind we can print it. That it saves a life is a cool and inspiring coincidence for sure, just like I was amazed when I heard about bad software causing deaths of real people, but it's not like any conventional tool couldn't have done the same.
I'm in the same boat. I think IFTTT is a great idea, but whenever I need something it does, I find myself using Cron jobs and web triggers instead.
When I was running for adminship on Wikipedia, I had it so every edit made to my election page was sent to me as an email.

This took an anxious week and turned it into full blown 24x7 nightmare. ;)
Volcano project scours Iceland for early warning signals
That's a little simplistic, don't you think? What about, for example, the minorities who are made to do things involuntarily?
Open-source end-to-end encrypted communications. Using it is not rocket science. You should not trust legislation and goodwill of service providers for your privacy. Take the power to your own hands.
Yeap. No chance. I agree with most, these are three items that won't improve the experience at all for user/dev.
>But I don't think you have to be lumbered with PayPal - there are lots of great options for taking payment for physical products through apps. Stripe even have an out of the box UI layer for iOS to handle credit card payments, and they'll only charge you 2.5%.

US only (and UK recently IIRC), so mostly useless for an international business.
Congratulations, this looks good.
On the main page you have a section 'Featured On' but since you've just launched I believe those listings aren't legitimate?
I have one where it grabs my Instagram photos and stores them in a folder in Dropbox and then my screen saver uses that folder as a photo source to display.
I suggest google employees should write "work for google" everywhere they comment or blog or say something about google projects. I bet half of the hype will just go away then
Awesome. Is there a video recording of your presentation anywhere online?

What strategies did you use to combat the lack of stack traces, especially in production?

I was happy to see that you are fellow Brisbanites. I'm a bit out of the "local loop", is there much of a local Brisbane start-up scene?
In Canada the Spark EV is (sadly) only available to fleet customers.
But i find the loading time of unreal engine very slow, their is more to happen
>But Apple – if a user doesn’t like their notificaitons, they know they can delete the app. Push notifications don’t need a permissions process.

So it never occured to the author that a user might like an app and STILL don't want push notifications from it?

Jesus...
Maybe I want to play that great game everyone recommends, and yet not receive their f*cking marketing push?
False analogy. The camera and microphone aren't readily available to non-running apps, whereas push notifications are. Push notifications can also interrupt other running applications.

Allowing them globally is a far greater burden on users than asking once when the app opens the first time. If your app cannot work without push it needs to fail gracefully, end of story.
Bitcoin gets another day in court- I had to testify for 30 minutes
I think the iOS model works a little better because you can defer requesting permissions until you actually need them. That way the user can get a better understanding of what the app is going to do with those permissions.

A game has a feature that lets you find people playing the same game nearby you. So in the app you click a button saying "Find players nearby", then the apple dialog pops up, asking for GPS permissions. The user is way more likely to understand why the app is asking for your location.

Contrast that with the android model, where you accept the permissions at the beginning, it may not be immediately obvious as to why the app wants your location, so you'll just deny it.

Also, with the Android model, it's all or nothing, and developers can assume that if an app is installed, it has all of the requested permissions. Whereas with iPhone, the developers is forced to cater for situations where not all the permissions are allowed.
I'd wager to say that I do. I'll give you a concrete example. People order goods, and I want to send them a "Your order has shipped!" notification. People who paid for something want to know that it has shipped and is on route to them. When I give them a push notifications permissions dialogue, they assume I'm going to bomb them with promotional material. I'm not, and they're missing out on a better experience.

One workaround is to better explain what notifications are for, but I've thrown days of work at designing better notifications permissions funnels. Lovely graphics, succinct messages that explain exactly what you're going to get, and it helps a little, but not enough. People are so negatively impressed by notifications, they often almost reflexively deny permissions.
Even though it might have been already showcased some time ago I haven't seen it yet. It's beautiful. I especially like the reflective water. Parallax effect in the diving mode is also a nice touch adding some extra depth.

Have any of you tried running it on iPhone 5? I wonder if there were any performance issues (if it worked at all!;).
Ditto however I changed the way I approach it, now Im hooked.

Instead of browsing recipes, just know the kind of things that are possible and leave. But, next time you run into a frustration †, hopefully IFTTT will be in your peripheral considerations and then you can set it up. Much more relevant that way.

---

† Like for example you wished you had a message the night before that it was gonna snow big time during the night, so you can set the alarm a little earlier. Or something like that.
And you can't 'just' have a small chip reader. The PIN can only be entered in hardware, so you end up with something ridiculous like this http://www.ingenico.com/en/products/payment-terminals/mobili...
what's wrong with deleting an app that spams you

If it already woke me at 3am, lots.

or not installing it in the first place if you don't trust their use of push notifications

How am I supposed to form an opinion as to my trust or otherwise in this company/developer before I've even installed their app?
Motivation/Money is a logarithmic curve.
Been to an Apple Store in the last month (In Australia, at least)? This is how Apple tackles it http://www.ingenico.com/en/products/payment-terminals/mobili...
Author here. Of course it occurred to me, but the problem is that users often can't predict if they want notifications or not, or how critical notifications are to the product. I'll give you a real world example from another permissions process - location.

One of the apps I work on is a neighborhood market place. It's all about seeing what people are selling around you, and requires location. The name of the app is roughly 'neighborhood', the marketing materials call it out in big letters, the permissions message clearly explains why the app needs location access. Still, people reflexively see a permissions dialogue and deny. Then the app doesn't work, and they contact support asking why.
Reddit discussion here:

http://www.reddit.com/r/haskell/comments/1etssw/haskell_in_p...
How to win a negotiation: have a positional advantage, wait for the other guy to realize it.
I'm not familiar with the precise aims of FWD.us but if it's coming across as to the public as wanting to ease the regulations so that they can "fire Americans" and "recruit cheaper software engineers from abroad", I think they might have a PR problem.
What Samsung's Flexible Display Might Mean To You As An App Developer
And you think allowing all pushes will fix this? I assume it will only make it worse. Not for your app, but by all the other apps that will send a million pushes.
Also Mozilla as these two browser are far better than Opera and IE, its good to have multiple browser installed in system for experiments and trial
> The thing is, a lot of apps can't work without push, or work a lot worse without push, and I think users aren't well equipped to decide in a few seconds.

Umm, No. For me, it's an easy choice. If it's productivity app, push please. If it's a game, nope. I couldn't care less if my friend need me to visit her farm in the middle of the day, while I might enjoy the game when I'm in the john.

I even wish the local notification follow the push notification rules.
How about discussing on merit, not finger pointing? (not a Google employee)
‘Something must have gone wrong with JAMB’s marking machine’
Why don't we err in favor of the user instead of the developer? It's bad enough that they cannot get apps from anywhere but the App Store, give them a break.
Thanks, you should have received an invite. Check your spam folder.
Not bragging here, but a while ago I used IFTTT to create a system where I created a quasi-alert system for a local legend/mentally ill guy who wanders the subway in my city. Everyone knows him, but sometimes he disappears for a month or two and people online start to talk about where he went.

I began wheatpasting a photo of him with a QR over his mouth (he often says the government/big corporations are trying to kill him) and the phrase "have you seen me?" around the subway stations he's usually on. The QR code went to an SMS #, which caught an IFTTT trigger to turn that SMS into an email (to an anonymous Gmail account) which, upon receipt, caught another IFTTT trigger and posted the text of their message to a Tumblr account -- one seamless workflow. This way, people could in more-or-less real time keep tabs on him and how he's doing.

It went well until the police took down the posters, of course. Haven't thought of a way around that, yet.
Using the GSM/GPRS_GPS Shield: call examples
The solution to this would be to put an explanation on why your apps needs access to, e.g, the contacts in your app description. Users shouldn't blindly trust you. If you provide a reason why you need all your permissions, the user are well better "equipped" to make those decisions.
"Categories" in Push notifications would help. The same as with most mailinglists. Let me check on/off what I'd like to receive and what I don't want so see. E.g. 'yes' for new functions, status and progress of the App and my order, 'no' for commercial offers and stuff.
I don't think it's a false analogy. I didn't not try to argue that the burden is equal, just that granular control can always come with benefits. For some apps, "failing gracefully" means not delivering a large part of the app's value, and that's a shame.

I believe that there are better ways to solve this problem, and that educating users to delete apps, and thereby educating developers to be conservative with their notifications is part of the solution.
Bingo. There's a reason why everyone advises you to 'consult a professional doctor' when dispensing medical advice.
It is a counterexample, because clearly untrue ideas also spread quickly, and history shows that untrue ideas stick far more easily - pursuing reason requires a lot of effort.
I archive Google Reader starred items to a Google spreadsheet by date, title, url and feed title.

On Fridays around 4pm I have an automatic tweet going out asking what's happening that night. Nothing too fancy.

I archive any Instagram photo I like to Drive also.
I think you're making generalised, quick calls because you've been burned by spam, which I get. Doesn't mean there aren't a ton of apps out there that would provide value with notifications but are hard to assess.
>Then the app doesn't work, and they contact support asking why.

Then the app, when loaded, should nag them to re-enable location permissions for it to work.
> besides paying the performance penalty because you have the hard-to-optimize JavaScript in the stack

Well the article proofs you quite wrong.
I appreciate the need some people feel to make modern-looking web pages, but the format of this really is just a triumph of style of substance:

* I have no idea how far through the content I am

* The lack of verbosity means I'm constantly having to apply guesswork to their statements (ie an explained point will tell the readers why Haskell gave them better communication. A slide show like that with just headings mean I have to guess the reason Haskell had those benefits)

* It's scales terribly (at least on Opera, some of the content fell off screen - so I had to maximize the browser. But this might just have been an Opera bug. In either case, this wouldn't have been a problem with a more traditional blog layout).

* The navigation requires guesswork

* And most annoying of all, it doesn't actually save the reader any time by displaying the content like that than it would have done with blog post as the jarring navigation presented with slides require the reader to pause before each page to understand how to read the slide, and then pause after each page to apply the aforementioned guesswork. With a blog post, the information is presented in a more natural communicative way which makes it quicker to digest the information.

It's a great pity I'm having to pick post a negative comment about the presentation of the submission rather than comment about the point being raised - particularly as I've been very interested in Haskell lately. But I found even my interest in the subject wasn't enough for me to put up with this slide show layout and thus I ended up closing the browser tab before the end. :(
I understand, and that's why it's tragic. I and my audience needs to suffer because other developers abuse the system. I'm calling into question whether there is not a better way.
I think i'm missing something. On slide 4 it says (the code) it has 0 exceptions and is robust, but then on slide 7 it says that (the system) it crashes without stack traces? Is that right?

What did the OP meant by being robust, when the code crashes unexpectedly?
Weirdly enough, I'm getting the same message on Chrome Version 27.0.1453.93.
While I lack the skill set to fully appreciate the paper, I must say that it is very refreshing to see innovative proposals on this kind of all-important foundational elements.

These are the kind of submissions that make HN worth visiting, for all its problems. ;)
A know a lot of Silicon Valley people who love The Economist; I'm actually a subscriber just so I can read it on the iPad. OTOH, I rarely read The New Yorker.

If the author of that article would like to visit Silicon Valley and see what it's like first-hand, I'd be happy to show him or her around. I promise no lame parties, and plenty of people who care deeply about policy, direction and magnitude of scientific, technical, economic, and social progress, etc.
Consider a single tab of a web browser, for instance. By specification, much of the code must run in the same thread. Keeping the semantics while getting code out of the thread is extremely difficult, often impossible.

I should know, that's my dayjob :)
The problem is, "value" is defined differently by the app maker and myself. "You got some coins!" at 4am isn't valuable to me.
Without knowing how many people saw and didn't follow, or followed and then stopped following - without the information that pushes the hypothesis back in the other direction - numbers alone are... well, they're not entirely meaningless - you can take some guesses - but they're not particularly useful.

Like -
If a superstar can get 30k people to follow them, it means less than some random artist getting all the 30k people who know about them to follow them. Because in the latter case you can guess that the weight pushing the hypothesis in the other direction's going to be quite small.

In semantic terms what you're really relying on in the former case to reduce the seize of the contrary hypothesis is the assumption that society is more or less uniform with respect to its interests along the relevant axis - which I find highly questionable.

Then think of where these stickers are going to turn up -you'd expect people to have better first hand evidence available.

So, I find it a bit odd. I'd have assumed it'd get discounted into irrelevance and people would just make up their own minds based on their knowledge of the person.
Another great thing about this demo is the movement of water, it always move in opposite direction of boat's movement which gives the feel that we are sailing in another boat with camera parallel to boy :)
Thankyou! Wow, that's some serious digging.

I managed to hunt down that the chance for divorce in Australia in 2007 was around 30%, down from a peak of around 50% in 2000. It was last around 30% in the early 80s.

I'm still hunting through some more recent papers on the ABS (Australian Bureau of Statistics) site devoted to "Family Formation and Dissolution"[1] but haven't found anything solid yet. I found many sites with unreferenced figures, and the only referenced figures all came back to the ABS, so I figure that their census data matches the marriage and divorce registrars pretty closely.

[1]:http://www.abs.gov.au/AUSSTATS/abs@.nsf/ViewContent?readform...
Interesting, it seems a little too bulky to get consumer traction but it's definitely a cool approach.
Your last two definitions don't fit unless you've a priori decided any government action is abuse - which is the wrong way to define things. Your first definition is so belaboured and tortuous that it sounds like libertarians have been at it.

And it's interesting to note that none of your definitions allow for natural phenomenon to be violent, yet we quite naturally talk about things like violent storms in English.
Do you have an example of such app? We keep coming up with examples of bad push notifications, yet cannot come up with examples of good ones. Genuinely curious.
Generators come to PHP
> That said Dart isn't that JS2.

To me, it is. Dart fixed everything which was wrong with JavaScript. There is proper lexical scoping, a lexically scoped `this`, no type coercion, build-in classes/inheritance, built-in dependency handling, built-in annotations/doc-comments, and good tooling is also possible.

It really does scale and it's very nice to work with. Plus, there are a bunch of nice features like lambdas, mixins, and named arguments.

> Javascript as web bytecode just doesn't sound right to me.

Yea, it's kinda icky, but there doesn't really seem to be a way around it. Fortunately, dart2js' output is reasonable in terms of size and performance. Unfortunately, it doesn't work in IE8.
Likely that is referring to the fact that when it crashes, it crashes in a way that can be interesting to debug. I took it as a comment about development vs one about production.
Let me detail tachyonbeam's answer.

All modern web browsers (I'll try not to troll about IE) support web workers. However, the semantics of web workers is message-passing (by copy, most of the time), which is the semantics generally associated to multi-process rather than multi-threading. Most developers using threads expect some kind of memory sharing, which is impossible with web workers at the moment.

Shared workers (not implemented in any browser atm, I believe) will take care of some usage scenarios. Other alternatives are being explored (e.g. [Parallel JS](http://smallcultfollowing.com/babysteps/blog/2012/01/09/para...). However, for the time being, don't expect any support from JS to do shared memory concurrency.

Note: I'm a Firefox dev.
Sure, take all benchmarks with a grain of salt.

However it's worth noting that deltablue has been used to benchmark polymorphism in Smalltalk, Self, the JVM, and V8.

Some of Nickolay's numbers are from a version of the code written at Sun labs, presumably for the very purpose of benchmarking the JVM.

I think it's safe to conclude that in many cases the DartVM already performs similarly to the JVM, albeit with a much better start up time.

Charles Nutter has some interesting follow up comments here:

http://blog.headius.com/2013/05/on-languages-vms-optimizatio...

Basically concluding that it's not static typing that matters, but predictable types.
In MINIX, afaik, you ship some drivers with the kernel in the same file. But those drivers runs in user space and separate from each other. The issue is not related with shipping.

IMO, loading the drivers at runtime is the easiest part of microkernels. It is really very very very tiny step. There are a lot more things to do, like doing IPC between operating system components, managing memory, scheduling, protection of the system & driver process running in the user space.

Finally, loadable kernel modules does not give you any security and reliability. Those modules still share the same address space with the kernel and each other.
Sure. As I mentioned elsewhere in this thread, I want to send users a "your order has shipped" notification, when an order they paid for shipped.
'The Internship' [at Google] Movie Trailer
A health guide for programmers: part one.