skysight-inc/HackerNews huggingface dataset:
And yet Apple extended the web platform with these APIs, shipped them in a production browser, documented them (without labeling them as experimental or proprietary), published web content that used them, and encouraged other web developers to do the same [1]. Other WebKit vendors followed suit and implemented Apple's APIs, including Android, BlackBerry, and Nokia. Then other browser vendors like Opera followed. Mozilla had our own independently-developed multitouch API [2] but earlier this year we implemented WebKit-style touch events in Gecko and helped lead the standardization process at the W3C. They were already a de-facto standard; we had to implement them if we wanted mobile Firefox to work with popular sites like Google Maps.

If Apple had no intention of ever allowing other browsers to implement touch events, then they could at least have shipped them with a vendor prefix, as Mozilla did with our "MozTouchMove" events (and other experimental or pre-standard APIs). Instead they polluted the global namespace, created a de-facto standard, and never gave a word of feedback to the standards effort that emerged around their work. Only at the very end of the process, after supporting the API in their production browser for four years, did they suddenly act to block the acceptance of a de-jure standard based on the de-facto standard they created.

Touch events are not just for novel multi-touch scenarios; in browsers like Safari they are necessary even for single-touch drag and drop handling that has been possible in desktop browsers for over a decade. If the W3C and Apple can't work out a royalty-free licensing arrangement for Apple's essential claims, then this seems very likely to fragment the mobile web even further by creating yet more "works only in Safari" pages. While we don't know the outcome yet, the path Apple has taken so far does not reflect the responsibility or stewardship toward the web that I'd like to see from a major browser vendor.

The mobile web is already in terrible shape when it comes to pages working across browsers. Do you think Google would ever push an update to Gmail that makes it not work in Firefox? Well they did exactly that to mobile Gmail this year, and didn't fix it until a month later [3]. It's like the 1990s browser war all over again. Keeping the web platform based on open standards is essential to keep it open to new browsers and technologies.

[1]: https://developer.apple.com/library/IOs/#documentation/Apple...

[2]: https://developer.mozilla.org/en/DOM/Touch_events_%28Mozilla...

[3]: http://bugzil.la/678150

(I work for Mozilla and I am co-editor of the W3C Touch Events spec, but these opinions are my own.)

EDIT: I think your comment is an accurate reflection of Apple's priorities -- I'm arguing against Apple's actions, not against your comment.
The original galaxy tablet looks about as much like an iPad as the second one, with the exception of the case color. The other major physical difference is that the buttons moved on-screen, which doesn't make it more iPad-like.
the conversions thing is true, but providing a wrapper class and an implicit utilizing scala.collection.JavaConverters makes that an issue you should only have to solve once.
Heaven help us if the author of this article does similar math for each engineer at Apple.
I was referring to more than their tablets.

The helm consoles are large flat touchscreens with black bezels and natural user interaction:

http://1.bp.blogspot.com/_XNPD380IpBQ/S8jnaB-iM1I/AAAAAAAAJx...

The iPad is absolutely a small version of that device.
The author doesn't seem that concerned with the patent applications themselves, rather Apple repeatedly throwing them at the standardisation process.

Every time that it's happened so far they've done it at the last minute and halted the standardisation process, only to find that the patents weren't even relevant anyway.

Given the insane amount of time that the standardisation bodies take anyway, Apple's approach is extremely unhelpful.
To succeed on tablets, Windows 8 needs to win on desktops too
I know NetHack[1] has been available for a while. It would be safe to assume that there are others.

[1]: https://chrome.google.com/webstore/detail/ladkaalcnedlcimjga...
Assuming someone was told to do a survey, and didn't care to make sense of the results or doesn't have the background to interpret them... happens in school all the time...
To illustrate how not-obvious the design is, compare the original kindle (released prior to the iphone) to the iPad. And now compare the Kindle Fire (released after the iPhone/iPad) to the iPad.

First of all, that's simply not true. iPhone first revealed in January of 2007 and Kindle in November. Those are very different devices with very different intentions. Apple building a high end phone; Amazon building a very affordable reading device.

Sure, the Fire will now compete with the iPad but it's a more general use tablet, not just a Kindle e-reader.
If you did a chart of how typical websites looked through those years, they would similarly change towards minimalism with rounded corners. Picking one and putting it in the middle wouldn't mean much. Popular design styles change over time. This diagram doesn't prove anything.
should they be unable to patent that invention

Of course not, they didn't invent anything.
Alternatif korek yamaha mio
Alternatif korek yamaha mio
riset menciptakan mesin yang lebih cepat berakselerasi untuk berpindah dari awal start menuju finish Terbukti motor matic lah rajanya pelibas motor
Few seem to realize that source code is but the most thorough "blueprint" of the product. That compilation - to wit construction of the actual product from the blueprint - is nigh unto instant and free means everyone overlooks it as the actual construction process, akin to actually building a bridge from detailed plans (except you get one shot at building a bridge, while you can recompile every few minutes). Ergo, "analysis", at greatest detail, _is_ coding. That we iterate so much comes from the continued newness of the technology and the relative complexity of the products; bridges are well-understood and iterating the design of one is minimal.

To the site's point (or missing thereof), the notion of "don't start coding until the analysis is complete" is a gross misunderstanding that coding IS analysis.

The inanity of reinventing the waterfall model is obvious to HN readers.
This was posted on HN so that we can make fun of it, and I think we're right to do so. You can be as wishy washy as you like about different situations requiring different processes, but have you ever seen somebody successfully isolate software engineering from coding and put them in sequence?
Create An Image Thumbnail Service Using Email Yak
Boomerang.js End user oriented web performance testing and beaconing
All of his (their?) work appears to be small-scale websites for small companies -- it doesn't look like he's built anything really substantial.
Native Client does not solve the portability issue. Portable Native Client is a research project trying to do that, but it is unclear whether it will succeed, and if it does, with what compromises (speed, security, etc.)

Native Client can in theory be adopted by other browsers, since it is open source, however no other browser has shown interest, the opposite in fact. Native Client is a nonstandard technology that will remain only in Chrome.
IPhone Emoji
There's an interesting question about where to draw the line, but in any extant country there are individual behaviors that can increase costs for the state, which doesn't necessarily mean we should ban them. For example, in countries with a state-provided fire department, one might argue candles, propane grills, and halogen lamps should be banned. In countries with a state-provided police department, perhaps we ought to ban controversial speeches and parades that induce extra police protection (not to mention enforce a strict nighttime curfew). And in countries with state-provided pensions, perhaps we ought to make various lifespan-reducing behaviors mandatory, to discourage people from living more than their fair share of years.
I agree with you. After a few years in the field, I'm now convinced that it is how most software is made. Even in the "Agile" startups and such, processes are often implemented as waterfall, or large parts of projects comply with the waterfall model.

While it fails sometimes, there are plenty of success stories about the waterfall model, like it or not.
Facial recognition is insecure, slow, and a wasted effort... for now
Totally -- I think that 0 (which is a perfectly valid value for a number to be) bites people doing lazy initialization all the time.

For this reason, CoffeeScript provides the existential operator, which asks: does this variable exist? (Is it not null or undefined?) You can use it in the same places you would use "||", as well as some others:

# In place of `||`
result = answer ? default

# Does `object.value` exist?
if object.value?

# Lazy initialize the speed of the car:
car.speed ?= 60

# Give me the value of `length`, only if `object` exists.
length = jsonResponse.list.object?.length
Thanks I really appreciate you taking the time.
Sorry to be harsh, but I have to agree with ovi256, I don't think your app looks beautiful. In particular, your fonts look boring (Arial?), there needs to be some small padding for the ingredients on the Random page, the neon-lighting on the borders looks a bit ugly, too many different colors seem to used on various pages....

I am not a designer, but you should get one to give you some suggestions. In any case, I just bought your app......happy to help out a fellow HN-er :) Hopefully this will help improve my cocktail-making skills.

PS> Check out a book called Tapworthy.
"How did the auto industry resolve this?"

Perhaps the auto industry's period of innovation and establishment happened during a more rational patent regime.
That they insert what amounts to a single early design iteration hardly rescues the inanity of "hey! I sliced bread! this is awesome!"
Not so fast. This isn't something new or strange at all. We are doing this for years with great success.

But maybe you know this method as these steps (which are the same):
Concept -> Functional design -> Graphic design -> Building -> Testing -> Deploy.

Nothing strange about that. Take a look at the IBM Rational Unified Process http://en.wikipedia.org/wiki/IBM_Rational_Unified_Process

I just think this is a hyped site trying to sell there book.
Demystifying the Common Methods of DDoS / DoS Attacks
Thin is not a patentable idea. If Apple's thinness innovations are truly patentable, then they should get a patent for the specific technologies they've invented and not a design patent for the idea of making something thin. People have wanted thinner computers forever.

Also, the article shows a tablet that came out before the iPad looking at lesst as much like the iPad as the Galaxy Tab.
This is not reliable at all. Look at the numbers for Oracle for database.
Doesn't look as terrible as "true" waterfall, but I think this is just marketing fluff to win people over by telling them about your rock-solid practices.

If they have an arrow that looped from Beta Testing back into Interface Design/Usability/Engineering/Coding, you'd probably end up with what most shops do anyways, speaking in broad strokes.
Airbnb Hires Former Yahoo Legal Eagle Belinda Johnson As General Counsel
The 8 Best Types of Video Promotion for Small Business
Watch barcelona vs ​​Real Madrid live stream online 10-12-2011
Florian has more insight, and in english: http://fosspatents.blogspot.com/2011/12/motorola-mobility-wi...
Poor guy...
Linux Mint Swap Banshee Affiliate Code, Take 100% of Profits
> If you can find me one C project out there which has headers with zero #includes and forces each compilation unit including the header to include all the prerequisites needed for that header I would be genuinely interested.

A whole OS does this: Plan 9 from Bell Labs :)

For details see the paper by Rob Pike: How to Use the Plan 9 C Compiler

http://doc.cat-v.org/plan_9/4th_edition/papers/comp

Also the Plan 9 libraries are much cleaner and leaner than those in 'modern' *nix systems, which makes keeping track of includes much easier: http://man.cat-v.org/plan_9/2/intro
Unfortunately you have to live your whole life to discover whether you're an exception or a statistic. I'll go with the statistics for my personal choices.
Autotranslation:
http://translate.google.com/translate?sl=auto&tl=en&...
Custom  without using JS
"Virtual" Cable Coming on the Web in 2012
Saw a chick on the train today with book 12 on patent law (can't remember if it was Germant or EU). It was about 7 cm thick, and the pages were real thin. Bureaucrats (the EU fuckers don't even pay tax), lawyers and politicians are just taking the piss now. I sure hope that is what the 99% are fighting against, and not the right for businesses and individuals to trade freely amongst themselves.

It is a wonder anything related to commerce can happen at all in well Germany at least
This might become more common when Proxy is supported more widely in JavaScript implementations.

http://wiki.ecmascript.org/doku.php?id=harmony:direct_proxie...
They are different, but both are true here, and they are related.

It's not truly open because it is not standardized, nor even proposed to be standardized, and it relies on other non-standard technologies (Pepper). Also, it is incompatible with the open web because it is not hardware-independent, which is another type of openness it lacks.
Alternate title:"Apple disclosing patents ahead of deadline in accordance with W3C patent policy, again."

The sense of malice seems to be inferred from Apple not disclosing these sooner, but I question what the point is of having a deadline if disclosures a month prior to it are going to be considered disruptive. If this was going undermine the process, shouldn't the deadline have been sooner?
From the headline I expected this article to be about over working and exhaustion, a topic I'm sure many here can relate to in some way. In the authorised biography of Steve Jobs, he comments on how he believes the exhaustive hours worked in 1997 when driving back and forth between Apple and Pixar were the cause for his cancer. In a similar vein, there seems to be a higher ratio of cancer sufferers in high pressured environments like financial trading. As a developer wanting to achieve amazing things, working what others consider crazy hours, the worry does occasionally cross my mind. I love what I do, but I do wonder how much harm can be caused by over working, regardless of the fact that there's nothing else I'd rather do with my time.
Obligatory insane animation explaining the issue:
http://www.youtube.com/watch?feature=player_embedded&v=j...
People don't work at Apple for the pay.

They work at Apple because they love the products, culture and people. Sure pay is a factor in the decision but I think the type of people who work at apple work their mainly because they believe in what Apple stands for. Challenging the status quo by thinking differently.

*I don't work at apple but I do have a few friends who do.
While there are many factors that point to the industry heating up, I do not believe that we are frothing yet. One of the things that many miss about the .com bust was that the infrastructure just was not there to support the application that where being built. Some of the .com bust was because the entire market moved too soon. Most people where on dial-up, commoditization of servers had not happened, and the toolkits we have today where not available. A lot of the .com bust where good idea's on paper but where just too unusable by the consumer in implementation.

Fast forward to today, and much of what is fueling the boom is mobile. The big difference here is that mobile is ready, the infrastructure was there before people jumped in and started to move the industry forward. I sometimes wonder if Steve knew that and kept the iPhone locked away from third party developers until it was ready to sustain the rush.

To me the mobile market's growth is a lot more healthy and a lot less exuberant than the .com rush was. I think what is throwing people off, is what I see as a new form of hiring, where a company of developers form around a product that has no hope of commercial success but yet they get acquired. This bothers some because it mirrors the bad ideas of the .com bust, but I tend to look at it as a new form of resume. The VC know good teams are in demand, so they can invest in keeping a team together, while the large players spend a lot of money identifying good candidates, purchasing ready made teams reduces that burden and has a higher success rate. Looking at the VC's as a form of headhunter that invest in keeping a team asset together to sell makes the picture of how that market works a lot clearer.

On a side note, after reading the first paragraph of that article, my bullshit meter spiked, I do not know what this paragraph says, other than they made a tool and are most likely selling it or the research from it:

in the context of a data-driven value capture and investability model. We have developed a tool called The KeyStone Compact method, which considers multiple corporate element interactions including the replicability of the nexus of a company’s capabilities (assets, networks, skills) relative to the nature and cost of acquisition of complementary assets required to capture value in the market (‘positioning for value capture – PVC’).
He's got to be trolling. Multiline ternary operators aren't in my book better than an if block.

He also completely misses the point about javascript's global-by-default variables and how easy it is to introduce them with typos, properly building classes, etc.
It's amazing how the interests of a very small yet powerful lobby representing the interests of such a marginal percentage of the population can get Congress to consider a bill that imposes itself so overwhelmingly on the other 90 something percentage of the population
Can we see a link to your LinkedIn profile?
Erlang SPDY
Chrome Web Browser Most Secured Against Attacks
It does feel that Apple is reaping the whirlwind here.

For a long time the major players have all held loaded guns pointed at each other's heads, with nobody willing to fire a shot because they knew it would be more trouble than it was worth.

And then Apple decided to take the first shot. The big question now, is whether the politicians will let this drag out, costing everyone a fortune, or step in and call an end to it by changing the patent system.
Right, there's always the option to just ignore PCI and live with the possibility of being fined if something goes wrong. But you're right, that's not always a big risk.
Give me my t-shirt
It sounds like you're saying something similar to this: http://www.developerdotstar.com/mag/articles/reeves_design.h...
"We've invented cigarettes", come buy a pack... everything that doesn't kill you makes you stronger...
The article title is inaccuarate. To quote the body:

"which could see an injunction placed on iPhones and iPads."

I would bet money on the iPhone/iPad not being banned. How many times have we seen this now? Product gets 'banned', company appeals, ban is lifted. World continues to turn.
"Unlike a traditional development process, ours establishes all the system's requirements before a line of code is written."

This is freakin' unbelievable. ROFL
Why on earth Europe doesn't have something like Stripe or WePay ?? This is such an amazing opportunity, and I can see lots of people who would invest in it.
http://www.ted.com/talks/jeff_han_demos_his_breakthrough_tou...

When did Apple file for its pinch-zoom patent? Jeff Han figured out a good way to commoditize multi-touch hardware, but the pinch-zoom multi-touch interface existed well before Apple made it mainstream.
and the best part:
Das ganze Fallobst weg vom Markt? > The whole case away from the fruit market?
Well Google earns, what, $1.1 million per employee?
> i'm not touching jquery

> plugin repository was deleted and everyone acts like no damage was done.

Your comments weren't about being wary of using random third party plugins that are likely to go unmaintained. I assume that everyone looks out and is cautious of that, as I do. I presume for example that when searching for django social-auth apps, a high priority in making a choice is the activity and last commit timestamp.

Your two comments above just seem to link the plugin repo to hating on jquery in general, which I don't really understand.

(for example, the top comment in this thread is basically "be wary of third party javascript", but it's actually phrased that way and it's been much better received)
Hynix produces prototype 15nm NAND flash memory
You think proprietary software is software that you can't use without license, but proprietary API is something other than an API that you can't use without license?
Both of these posts are completely opposite to what the system of production should be. OBVIOUSLY we would see the apple design as intelligent, and obviously thats how we think intelligent tablets should look now that they have been established as functional and successful, but that is completely the result of apple engineers hard work, not some universal tablet design that just makes sense. I can understand why apple would be so pissed. They created a novel (and initially, quite criticized for several aspects of it's simplicity) piece of technology, and because everyone likes it, they're claiming that it was barely designed at all. Apple made tough and meticulous decisions that allowed them to nail this design, and now, seeing that they are successful, other companies are claiming that those decisions were obvious and effectively unmade. And even if the designs were in fact "obvious," and impossible to do any other way, then why hadn't tablets taken this form before now? And even further, why do we patent things at all, if whenever someone releases a design seen as intelligent and novel, it can be declared as the industry standard and infinitely copyable? We patent so that apple has an incentive to make such a well thought out product, not so they can "shut out other designs that are simply following the same completely objective universal blueprints for the tablet computer."
I found this infographic worthless. Leading developers? How did they decide that? Minority Java and .NET? What kind of developers are they talking about?
Plus they usually get a stay during the appeal anyway, so the ban is never actually effected.
Dealing with all of the banks, currency, and laws sounds like an absolute mess. Each country does business differently.
For what it's worth, we don't have a marketing team currently and, no, these articles are definitely not ones that we made.
5.9% plus $.95 or 8.9% flat per order with a minimum of $0.75 is pretty steep pricing.