skysight-inc/HackerNews huggingface dataset:
I guess this makes sense if you look at it from a phone/tablet manufacturers perspective: A manufacturer wouldn't necessarily have the desire to implement their own browser on top of webkit so they want a company (rules out Mozilla) that will support a web browser on their phone without also being a competitor.

The problem I think is that the non-aligned phone manufacturers are going the way of the dodo. You have Nokia committing to WM8, Apple on iOS with Safari and most others committing to Android. In theory a manufacturer could go Android + Opera but why license Opera when you can get Chrome for free?

That being said: Opera has always done a great job fighting against massive odds. I hope this move gives them the breathing room they need to keep going.
The source shows quite clearly why the HTML community needs try to address the adoption of namespaces in HTML5 ASAP, maybe not in the current form but in some simplified form.

I feel uncomfortable with the use of non-namespaced tags and squatting on common terms. For example, cmx.io uses tags like <scene>, <label>, <drawing> and so on. I really would prefer it used something like <cmx:scene> or <c:scene>, so that it would be possible to mix CMX tags with other libraries that use similar tag names.
Just to give a counter-anecdote: Live in East Germany sucked in the 90s, after the euphoria of reunification wore off.
Where I live shops are within walking distance, and since we have a kid we switched to having lots of food delivered once a week fresh from the countryside.

I am especially bullish on that delivery service. Sure, they use a car, but one small truck making the rounds seems a lot more efficient than lots of small cars driving to the store.

Shopping is a very trite activity, owning a car doesn't make it much better. In fact driving out to some shopping center seems to make shopping a day trip, which is one wasted day. I prefer to just pick up a few things on may way home from the tube, and ordering more complicated stuff from Amazon (plus the weekly food deliveries).
I don't think it has to do with servo, which is really just a research project.

Gecko is a lot harder to embed (so yes, legacy is and issue here), and webkit is compatible with more sites (as sites are now often "designed for webkit" and use specific webkit-only extensions)

Makes the choice very easy and logical IMO. Not really good for the web, but maybe not a bad idea for Opera. Time will tell.
First to invent can screw the first inventor too, because the very notion of "first inventor" is kind of fuzzy. Suppose this is the time sequence:

I come up with an idea.
You come up with the same idea.
We separately work on implementing the idea.
We encounter serious problems with making it work.
You solve the problems and actually get the thing to work.
I solve the problems and actually get the thing to work.

Which of us is the "actual first inventor"? I had the idea first. You solved the practical problems necessary to actually make it work first.

In the US under first to invent the way it works basically is that your invention date is the earliest date such that you were working on the invention on that date and you worked diligently on the invention from that date through filing the patent.

So, in my earlier example, if you and I both worked diligently from the time we conceived the idea to the time we solved the problems in making the thing work and both filed patents, I would win.

However, if the timeline was this:

I come up with an idea.
You come up with the same idea.
We separately work on implementing the idea.
We encounter serious problems with making it work.
I take a few months off to work on unrelated things.
I resume work on the invention.
You solve the problems and actually get the thing to work.
I solve the problems and actually get the thing to work.

You would have priority under first to invent now. Since you were working diligently from you date of conception, that is still your invention date. My invention date would now be the date I resumed working on the invention after my break.
It's kind of unfortunate that this had to happen. This will only further entrench the WebKit hegemony in mobile devices.
Building Nginx From Source On Debian Squeeze
"Steve" would have been better, as a nod to both men.
Many FF addons are now restartless.
Is a monoculture as bad as it might seem though? Front end web development is a clusterfuck. Webkit is open source, unlike the almost monoculture that ie6 represented. It can be forked and evolution can continue. Ditch -webkit -mos and -o. Like when the dinosaurs experienced a mass extinction event and mammals bloomed from a shrew into cats and humans.
None of that is going to happen.

Apple is horrific at the gaming business, and that isn't going to change any time soon. Why? Because it's not a priority, and isn't going to be any time soon.

The substantial infrastructure pieces that Microsoft, Sony and Nintendo have built up in gaming - Apple has none of that, and it isn't going to magically appear. Apple would have to make gaming a top priority, and they will never do that.
That's the most scary thing of all. Although open-sourced webkit is mostly developed by big companies ( Apple, Google, Adobe .. ). Webkit is not perfect. There are a lot of bugs that nobody cares and will care less. Imagine what will happen if there are no competitor and webkit core engineers do whatever they want and still people use their engine. Prefixes like '-webkit-animation' will remain forever and w3c specs will not be a significant for them.
Interesting. Opera makes most of their revenue through licensing their rendering engine. That's how they've turned their ~2% marketshare into $180MM in revenue (compared to, say, Mozilla's ~26% and $300MM).

I wonder how this will affect that.

[EDIT: I mixed up currencies; fixed it.]
I think it is "safe" only in the sense that people are more expendable in third world countries. Probably poor people who don't have cars and have to cross streets on foot are even more expendable.
Maybe I'm wrong but my impression was that Apple never understood or cared much about gaming and largely lucked into their ios game success due to being a popular portable mobile device with opengles and a decent virtual application marketplace at the right time. I have a hard time seeing them get into consoles.
The problem of having the standard defined by an implementation is that it makes it almost impossible to have another implementation.

This is fine if we agree here and now in 2013 that WebKit is the only rendering engine we'll ever need.

That just doesn't seem like a smart bet to make. Opera was in some ways better than the WebKit browsers on mobile devices, except for broken Webkit only sites. That ain't going to get better now.
"Right DM, but what if somebody's parked there?"

"Penfold, shush."

I miss that show.
Just a headsup: I didn't sign up because you're asking me to before I even see what you're going to offer me. This is really how I feel about it, not trying to be dismissive.
I don't think Mozilla will ever switch. The reason why they've their own engine and try to keep a decent marketshare (which they do indeed have), is to be able to have a say on web standards, and the web in general.

Having a say ensure there isn't a single voice taking decisions that led us to things like IE6. And we're actually starting to see IE6-ish stuff happening with webkit, as it's nearly the only rendering engine for mobile.

One vendor != good for standards.

Oh also, their engine happens to be pretty close to webkit performance wise.
When Life Throws You S%&T, Make S%&T Chips and Set Those Mothers on Fire
7 Weight Loss Tips You Should Never Forget
And yet, within 100 years, horses completely disappeared from our streets. I think you underestimate the capability for change.

Even today, cities introduce pedestrian areas or limit the number of cars to certain areas, or they have special bus and taxi lanes. It seems likely that they would introduce special "only robot cars" areas eventually, as a first step.
Firefox for Android does this, and it's not like the underlying Gecko engine is different.
My Book | The Happy Academic Writer
A wise move for Opera. Now they can hire webkit-engineers from anywere without heavy training on their model.
Note that there's some fragmentation in WebKit as well. I think that developers that assume it will make their lives a lot easier will be slightly disappointed in the end.
"This is fine if we agree here and now in 2013 that WebKit is the only rendering engine we'll ever need." - this is a very smart way of putting it.
These are two different markets that we are talking about. I don't think the goal of the xbox, ps3 or steam box ever has been to distribute a bunch of low budget $1 casual games.

This is a potentially lucrative market, but it hasn't existed for 3 decades. I'm not even sure it has existed for 1. Changes in technology are only now making this possible, and tbh I hope all the console makers don't join this freemium casual game race to the bottom.

two and a half men and insert generic crime procedural are the most popular tv shows. Would you say CBS is disrupting tv right now by peddling a bunch of cheap garbage to the lowest common denominator audience.
I believe they've said never. They don't want just one major rendering engine.
I find those numbers hard to believe. Are you sure your currency conversions are correct?
>> I think bad developers will start to exclude other engines support if percentage of non-webkit browsers goes very low.

Bad developers are already ignoring everything except whatever single browser they [might have] tested in.

This move certainly is unsettling, but I think you can come up with a better argument about why.
Cool stuff. Just one suggestion, maybe add a place where people can sign up for a newsletter to receive updates. I quickly forget name of products, and as mentioned by others, the error tracking market is growing. I don't see myself using this yet, but I'd be interested in giving it a spin once JavaScript is supported (I assume Node.js won't be a problem?).
Not that I disagree but just so I can back myself up when I go repeat this to friends and colleagues where's the data to substantiate these claims?

In particular that 360 has made more money for 3rd party devs than Wii.

It doesn't really matter if Microsoft makes more money per gamer than Nintendo if Nintendo is still more popular. As a ludacris example I'd consider consider a company that sold a million $1 items more successful than a company that sold one $2 million dollar item. One has market. The other just as a customer.

I'm not suggesting Wii is more popular than 360. I have no idea since I have no data. I'm am suggesting that the profit of Nintendo vs Sony vs Microsoft is irrelevant. What is relevant, I think, is which console is making money for 3rd party devs because that's the console that seems like it would have the most support in the long run. I'd love to see real data as to which console that is.
The web may not be fully open, but it is far more open than the closed world of "apps".

(Of topic, perhaps...)

I hear this a lot, and I think, for the most part, web applications aren't remotely open (in general). While I can use any computer to connect to a web site, very few sites actually allow me to get my data out of them. In short, in my opinion, open access to data trumps open access by various clients.

On the one hand, we have systems that I can connect to with any OS I want but where my data is completely out of my control. On the other hand, we have walled gardens where the data sits, literally, in the palm of my hand. Both situations are ugly, but in the former, if I want my data, I have to pray the developers left me a method to do so. In the latter, it may not be trivial, but it is almost always possible[1].

I wish we had truly open systems across the board. Until we do, I vote we stop calling web systems open, because they are only open in terms of access, and that's not good enough.

1. For example, jailbreak, log in, and scp a SQLite db. Certainly not trivial but at least doable. In no way would I actually call this "open". I just think it is less closed than most web applications.
Speaking of Mac/Windows, do anyone know the Mac shortcut for Swap Line up/down?

In Windows it's Ctrl+Shift+Up/Down, but I've been unable to find the Mac equivalent.

EDIT: Sorry, I spoke too hastly. Ctrl+Super+Up/Down in case anyone else wonders.
> Besides, how does one do CamelCase with speech-to-text?

My guess would be tight integration with the IDE and knowledge of the language being used; most of the time, the editor should be able to figure out that chained, non-keyword or existing identifier words should be CamelCase. You'd need some manual way to disambiguate when it gets it wrong.
Smart move.

I don't know a single web dev who tests on Opera anymore. I personally stopped worrying about it for any of my products when it hit 1.6% market share, and that was five years ago. They're essentially not supported by anybody, and haven't been for a long time.

... But that's never mattered, since they have always known it. And they went out of their way to make sure they rendered exactly like the dominant browser. For the longest time, they'd match Internet Explorer quirk for quirk, so if you supported that you supported Opera.

Now they see that Chrome is going to win, so they're switching to copying Chrome instead. And since Chrome has a nice drop-in "Chrome in a box" rendering engine they can use, it's going to be a lot easier to pull off this time around.

They'll continue to be the browser that nobody cares about (aside from six people who are no doubt here in this thread somewhere), but your site will probably render fine on it.

EDIT: Looks like those aforementioned Opera devotees have arrived. This comment went from 6 points and the top slot down to 1 point in the last ten minutes. Funny, since it's not actually an anti-Opera comment (or of course the sort of thing that down-votes here are usually reserved for).
You might be interested in reading the following article, titled "Are Psychedelics Useful in the Practice of Buddhism?"

http://psychonautdocs.com/docs/stolaroff_buddhism.pdf
If any HN users have specific questions about the countries, ask away!

I've lived in Japan and Singapore, spent time in the rest. And I'm sure other HN-ers can chime in too!
> Well, the theory behind a patent is an invention that is not obvious to one skilled in the art.

The requirement is that it not be obvious to one having ordinary skill in the art.
You might like mercurial and bitbucket. There is also TortoiseHG and though I find it a tad clunkier it's not too bad.
I'm not sure I should be happy or sad. Part of me is happy that I have one less rendering engine to worry about, other part of me fear that the fact that WebKit dominating the market (now with only three major players playing, WebKit, Trident and Gecko) means the start of "this website works best when viewed with WebKit-based browsers" era via the use of non-standard -webkit vendor prefix.
Great idea :-)

Flick me an email at jdtrask@raygun.io and I'll make sure you get our news! :-)

Oh, and no, Node.js won't be a problem :-)
True

Too bad it seems to get worse (or maybe more bland) with every generation.

Thankfully the Foo Fighters showed everybody how to do it (again) last year with Wasting Light
Rotating Locomotion in living systems: http://en.wikipedia.org/wiki/Rotating_locomotion_in_living_s...

Technically they are apparently not wheels because the whole animal/plant rotates, but I'd argue that nature worked out the wheel principle just fine. In fact it seems an incredible cool solution to the problem that there aren't roads everywhere: the whole animal can transform from wheel form to walking form and back. It's almost like a biological Transformer (TM).
If you are using jQuery and just need a simple generic event emitter, you may not need this library.

var emitter = jQuery({});
emitter.on('ready', function() { alert("Ready!"); });
emitter.trigger('ready');

...or if you're on Node, Node.js already has API for events:

var EventEmitter = require('events').EventEmitter;

var emitter = new EventEmitter();
emitter.on('ready', function() { alert("Ready!"); });
emitter.trigger('ready');

The reason you'd use LucidJS is for its other features that these solutions don't have, like `.set()` and `.pipe()`.
"rooted device" == "illegal install"? Even if the rest of the comparison weren't bogus, this definitely sorted this entry into the "contains: one blog, zero clue" category.
It's an interesting piece, but I have a problem with one thing that caught my eye - while explaining what drives the policies that hurt - in his opinion - the education, first thing he mentions is "wealthy corporations". It's a common trope, but I'd expect more from somebody who actually teaches Government - what "wealthy corporations" have to do with this and how comes they - and not, say, vast government bureaucracy or enormously powerful educational unions - supposedly set the agenda and ruin everything for everybody?
It isn't fair to compare server products with gaming ones, because server products are bought by people with big money, and the lock-in potential is much bigger. You need much more popular product, and you must be consistently good across versions.
I would think one vendor would be great for standards: it is the standard. It sucks for any kind of innovation, though, as IE6 shows incredibly well.

Out if curiosity, what IE6-ish things do you see WebKit doing?
This is cool. Not so sure about the practice of committing object files to source control, but I guess it makes sense in a "the more, the better" kind of way, at least.

As a side note, I must say that as a former (contracting) developer at an EA studio, it's a very interesting feeling to see the programmer (the programmer, as in "the one") of a recent release sit next to EA's boss and talk about the title.

Things have certainly moved on a bit, since then. :)
GUI, features? Users don't even know what is a rendering, or javascript engine. They don't care unless it's exceedingly slow.
> That just doesn't seem like a smart bet to make. Opera was in some ways better than the WebKit browsers on mobile devices, except for broken Webkit only sites. That ain't going to get better now.

But a de facto standard (ie one defined by a popular implementation) forces sites to be compatible or be ignored. More monolithic standard => stronger coding conventions => more robust web. Or am I being totally idealistic?
Python and Django: ImportError: No module named django.core -
And their first contribution is already attached to https://bugs.webkit.org/show_bug.cgi?id=15553!
There's a common problem (https://en.wikipedia.org/wiki/Goodharts_law) with proxy measurements, and issues with testing highlight this problem. However your description of what the math education looks like I think this is a lesser evil, at least until we find better measurable proxy for actual education that tests.
Because they want to share their code and participate in open source projects?
Developing for the console seems really harsh.

Somewhat related, an indie company managed to get a fighting game out on PSN and XBLA. It just got an update on PS3, but it can't get updated for Xbox because the patch is bigger than 4MB. [1]

Keep in mind, these are free updates that fix bugs and stability issues, not paid DLC. Even so, patching is really, really expensive. [2]

[1] http://shoryuken.com/2013/01/08/skullgirls-xbox-360-patch-de...

[2] http://kotaku.com/5884842/wait-it-costs-40000-to-patch-a-con...
nice! well done.
Razuna 1.5.5 and custom fields and indexing the complete folder path -
Npm cheatsheet
Here's a scenario: As a network provider I wish to subsidise the hardware on my tariffs further still. I can shape traffic, sell advertising and analytic's to achieve this. Now if only I could get a capable proxy service compatible with the common browsers on iOS and Android.

Is Opera's core proposition a browser or a service? What differentiates them from their competitors? I read this announcement as a candid admission that they can compete better with their proxy service than with their browser.

I suspect the future of Opera is as a SaaS proxy that happens to have a client ready too. A proxy for shaping or sniffing (mobile) traffic has many advantages to those in emerging markets and those who wish to push advertising down our throats cough cough Facebook and Google.
I have written a heavy JS proprietary Ajax app, and opera was very easy to get working.

Opera really follows the standards, and if I found any bugs they were often an indication of a fragile part of the code that needed fixing (Opera was very useful for finding dodgy areas of my code).

Of course it depends upon the features one is trying to use, not just the quality of the code :-)
Is that where babies come from?
But a de facto standard (ie one defined by a popular implementation) forces sites to be compatible or be ignored.

No, it's totally the opposite. They only have to be "compatible" with this one implementation, and are free to rely on all implementation-specific bugs or implementation defined behavior when doing so.

Think IE box model around the IE5/6 age. Or hell, supporting Office Documents. Even if you'd have the source, being compatible certainly wouldn't have gotten much easier.

Note that WebKit is open source and Opera is having problems being bug-compatible with it.
Likely, Opera Software had a revenue of NOK 900M in 2011, and USD 1 ~ NOK 5 yielding a ~USD 180M revenue. So his comment is only correct if you compare without conversion (Opera Software is indeed a billion a year in revenue, but that's a billion NOK)
Same as before for me; mouse gestures, awesome speed-dial, custom search keywords and possibility for a lot of customization.
Except that most of those costs (and lets include pollution) are externalities borne by other people, not by the actual car drivers. If people would have to pay the real cost for cars, things might look different.
You were already asked about Airbrake and exceptional, but what about differences from getsentry.com ?

Pricing seems to favor Sentry, depending on how one weights days vs event # history, they have a similar focus on multiple environments for error clients, many, many plugins for third party service integration, and the awesomeness that comes along with having their open source codebase.
Not Yet Shut Down. But thinking so.

I started a website called "mistrics". This was designed to help students to document their college projects and work together as a team from multiple locations. Also getting right guidance from teachers. BUT looks like no body is interested to help students. Basically in India. College admin and teachers have decided to not accept technology especially if it is free.

What i learned is there is time gap between technology in India and rest of the world. We in India are not going to change our legacy rules (In education, not at all).
It can be forked and evolution can continue.

Yes, but only on WebKit-derivates. To use your analogy, it's sort of like trying to make better dinosaurs and deciding that we might as give up on apes at this point, because they don't seem as powerful and get eaten by the dinosaurs anyway.
> Gecko is a lot harder to embed (so yes, legacy is and issue here)

Gecko embedding is also unsupported since May 2011: https://groups.google.com/forum/#!topic/mozilla.dev.embeddin...
Introducing The Paper Bay
Well, it's a monetary transaction. The same happens when anything is purchased with a credit card anywhere.