skysight-inc/HackerNews huggingface dataset:
Apple hasn't innovated into market leadership for status or intangible satisfaction. They've done it because that's what you have to do to keep those "big checks" rolling in.

If Samsung gobbles up market share, a big check won't bring that back, and a check big enough to account for it would probably bankrupt Samsung (assuming you could ever calculate what that numer would be).

Let's pretend that Samsung drove Apple out of business by rapidly copying Apple's R&D and competing directly on price. Just how big of a check would be required to set things to right?

We can use an analogy instead of hypotheticals. Imagine I've stockpiled grain for the winter. Winter has arrived, and suddenly, so does the army. They commandeer my grain and promise to write a check for its market value. The next spring, I get the check in the mail. Unfortunately for me, my family already starved.
How have we not abolished patents yet? This is ridiculous, and everyone appears to know it except that judge.
Angular is fast and easy for development. Very ittle boiler-plate and comes with easy UI bindings. I feel it's perfect for smaller projects where separation of logic isn't as important. Angular has the ability to grow in complexity if you need it too.

Backbone comes with a lot of boilerplate, but honestly is worth it if you have a larger front end app. Being able to have your data trickle though your models and views in a concise structured way can make changes as well as fixes much easier in the long run. Backbone's persistence functionality is pretty phenomenal as well.

Ember relies pretty heavily on Handlebars. If you're game to use that for your client side rendering than it could be a good option. Ember looks similar to Backbone but makes a few things easier such as computed properties and bidirectional bindings. I haven't touched it much yet as I'm currently working in Backbone and Ember's current lack of an "official" persistence mechanism turned me off a bit.

All three of these are great frameworks. Angular is easier to pick up but Backbone has more users and more users means someone has probably ran into a problem that you possibly will and has already asked a question on StackOverflow. That alone can be invaluable.
ATV Wedge
This is starting to read like a Rod Serling original.
The potential was always there ever since Satoshi released the specs. The volatility is because of the nail-thin market depth, and the bubble was unavoidable (Hello 20/20 hindsight) because of that combined with some media attention and the first time occurence of a digital limited resource... Well, most people probably only thought as far as "OMFG the price is going up, I expect great returns on investment". Thankfully the price fluctuations are smaller now and we can all focus on building infrastructure and a market.

As for legitimate businesses there´s plenty. We´ve (mullvad.net) been accepting bitcoins for two years, but then again we were probably the first corporation and full-time business to do so :)
All of those problems with the Segway could be solved if people were determined enough to use them. The Segway didn't take off because PEOPLE LOOK RIDICULOUS on them.

"Wearable" computing has the same issue, and will only take off if it can be made to look stylish enough for fashion-conscious people. This is Google we're talking about, so it's safe to assume the product will be about as stylish as an industrial vacuum cleaner. Some other company will have to come along and fix it before it becomes popular.
I was replying to someone who said: "Are your products so terrible that you have to force people to buy them by preventing any other competition.”

I accept that you don’t say that their products are terrible. I certainly like their products while disliking the innovation-killing patent-circus. The eventual end-game is an oligopoly, and I think this is a net loss for humankind.
And guess what, you'd get stuff done more quickly and with less annoyances and bugs if you were using another language. The article is encouraging people to start programming with PHP. This is bad advice, because there are better options. If you already know PHP and you don't plan to program a lot, then learning a better language may not be worth it and staying with PHP is fine. If you're just starting you have no such investment and you're better off learning another language which is both easier to learn and more productive.
This is why open source triumphs in platform spaces: if your business relies on another company's intellectual property it can be destroyed at any time.
Prefetching just grabs HTML.

Chrome also does prerendering in some cases, which runs JS, fetches stylesheets, etc. The user may or may not ever see the result, of course.
Rather than cast aspersions on her credibility I think this actually bolsters it to learn this. At least she has deep expertise in a (very flawed) system.
HTML. Or some sort of managed CMS.

Something that doesn't involve any programming. Because getting all of the bits of web development together is hard work, and you're not likely to end up with anything decent at the end if you don't know what you're doing.
"PHP apologists"
-You've got to be fucking kidding
I'm only halfway through this, but it rings true to my experience. The circumstances are different, but the emotions and lessons I had to learn are much the same. Near the end of my PhD, when I knew that graduating was just a matter of time, I had difficulty explaining to people what the process had been like, and how to answer people when they asked if they should do it, too. In the future, I'll point them to this.
Introducing the New Microsoft
That's the problem -- how do you calculate the lifetime value of that? It's not just lost sales, it's a substantial shift in the position of a huge corporation.

Here's another example -- Imagine how different things could be today if the AT&T lawsuits hadn't temporarily paralyzed the BSDs just as Linux was also emerging.

I can't even begin to quantify the cost of what could have happened if the lawsuit hadn't been filed by AT&T.
This isn't new, this has been known for a very long time.
Why does apple take 5x as long to reject apps in situations like this?
As I understand it, a court ruling like this is based on an initial assessment by the Judge that Apple is likely to win, as the patent(s) are currently valid and it appears (to the Judge) that Samsung is violating them.
I first want to congratulate and praise these advances in optics. I think it's great that they have received so much funding to further their pursuits.

I don't think that the current application of their technology makes sense. The form factor is awkward and they are selling to prosumer / professional photogs. The technology makes sense for consumers - because consumers aren't making art - they are making memories. And memories can absorb the dynamism their technology provides (changes focus and even perspective (minorly)). So this tech on an smartphone would be amazing. (because other consumer level cameras are being fazed out obviously).

For professionals this tech would also be useful in DSLRs - but ONLY for fixing perspective or composition. I dont think most professionals want the general public messing with their art form. Some abstract artists that will be very interested in the interact-ability - but not most. As a photographer myself - I want complete control over my medium and that includes focus and perspective obviously -- but the tech would be useful for post-processing. If they want to sell this to the current market they are selling to (seemingly professionals/prosumers but with a consumer form-factor) -- then they almost need to say this isnt even photography - but a completely new thing.

I can tell the founder really cares about the technology - and doesn't just want this to be like a Cisco and sell tech to larger companies. I can totally appreciate that - I wouldnt want to run that sort of company either. I just don't know that it will work how he wants to make it work.

Maybe that's why this change is happening.
I think the definition of an "API" should be "can I, if necessary, replace it with my own implementation of the same thing?" If it isn't subject to the Liskov substitution principle it's something different.
"They are becoming what Microsoft was in the 90's and it absolutely sickens me." Once you become the dominant player your mentality shifts from cocky upstart with nothing to loose to fat cat incumbent that thinks of nothing but protecting your turf.

You might notice all of your friends who were liberal and poor in their 20's start voting conservative in their 40's once they have material wealth to protect - "less taxes! less government!"
Ok. That is helpful. I will refactor the landing page a little bit.
"The item you've requested is not currently available in the U.S. store."

This article was originally posted on June 6th. It's now June 29th. After 23 days, this issue is still not resolved.

I'm not a user of the app or a fan, but I find this incredibly curious and sadly opaque.
Internet Explorer 6 as a chat server with Bridge RPC
The last time I used make was when I was in school, about 10 years ago. I don't think I've ever used configure. The last time I used arithmetic was... every day. To me, make is closer to quantum mechanics than arithmetic.

I also dabbled in Haskell. Honestly, I struggled. There's a distinct possibility that I'm not that smart, but if I'm not, then there are a lot of people that aren't.
You first need to consider what kind of framework you want.

Backbone is a very light MVC framework that provides you a few minimal tools for structuring your project. It doesn't get in your way, and it won't have any performance issues. On the other hand, it doesn't hold your hand, and it doesn't help you solve any especially hard problems. A simple demo app tends to look very clean when implemented in Backbone, but anything more complicated will require you to write a TON of code. (By design; Backbone only provides functionality that everyone will need, regardless of the type of project.)

The other two you listed are heavier, and more opinionated. They will do a lot more to help you, if you're working the way they think you'll work. If you aren't, they can be counter-productive; it's not hard to miscode something to get a major performance penalty.

I evaluated every framework I could get my hands on, and settled on Knockout. It's quite similar to AngularJS and Ember, but feels more mature than either, and has great documentation. Its killer feature is it's two way bindings between the DOM and the JS models.

My project is basically a very complex CRUD app; I've got tons of complex, deeply nested records I need to display and let users edit; a good, fast, clean UI for doing so is crucial. My initial spike using Backbone bogged down in endless boilerplate to try and keep everything in sync, and tons of ugly JQuery code to manipulate the DOM. (And was buggy to boot, which I'm sure was my fault, but highlights that Backbone can have a somewhat rough learning curve.) Knockout, however, made it a snap. My code was shorter, cleaner, easier to write and maintain, and fast.

So, my suggestion: Backbone if you're comfortable with writing all the functionality you need from scratch, and just want a little structure for your app. On the other hand, if you want a very robust framework for writing CRUD apps with a rich UI, and want to make your life easy, go with Knockout.

(Ember and Angular are good too, but in my view they're too similar to Knockout. There's just no compelling reason to choose them, given that Knockout is more mature and polished.)
1 other way to look at it: We were excluded from everything and generally treated like crap. We formed our own cliques and we're happy with them. Why the would we want to let the people in who once shunned us? We don't want that kind of person around us.

And before anyone says, "Not everyone treated you that way," they did. The ones that weren't actively tormenting us were passively allowing it to happen while they were allowed into the groups. Everyone that wasn't against us was with us.

So yeah. We're a pretty closed group now. It shouldn't come as a surprise at all.
Google Maps is a pretty good example of why you should be wary of all platforms, free or not.
You can experience it from the other side.

Now, you will find it is rather harder than it looks. Maybe your father was truly lousy, there are some like that out there. But it won't hurt you to reserve the possibility of seeing him some generosity, at least until you have done better.

If someday you can say you've done better for your children than was done for you, you'll be saying a lot.
Ask HN: Best HTML5/CSS3/JavaScript books/tutorials for a kernel engineer?
So I've spent most of my years as an embedded and linux kernel engineer but I think I'd like to make a move to web-apps.

About me: My favorite books is either O'Reilly's Programming Embedded Systems in C/C++ or "An Embedded Software Primer". Perhaps even old, old, old issues of Dr. Dobbs.

I learned programming by doing, not reading endless amounts of theoretical material about it, so any kind of materials that emphasize doing is preferable. I've been going through Udacity's CS253 course and found it neat and very helpful. I've searched around for info about the web-app front end material but none of it really crystallized for me or I just found it to be really boring. Perhaps you know of some better ones?

Any help would be appreciated.
Well that's just weird.
IANAL, but as far as I my very limited understanding goes. Prior art isn't verified when a patent application is applied. Only after that, when someone files a suit trying to invalidate the patent. Which is a separate case from the injunction. So Samsung would have to file a separate suit to invalidate the patents. If then win that, then and only then, they'll be able to stop the injunction by saying Apple patents are invalid. Which of course, would cost Samsung a lot of money and time.

So you can file any bogus patent, the USPTO won't verify. They'll only check if all the paperwork is in order. It will only matter if your patents are bogus if someone tries to invalidate it.

Or am I talking crap? Please correct me where I'm wrong, I'd love to learn more.
The Home Depot stuff is way too thin. It will flex and bend when you try to write on it.

We got a bunch of 24" X 48" X 0.375" sheets from Online Metals (ironic, I know) and hung them up everywhere. They were a bit pricey and you could probably do with thinner but they look and work great.

http://www.onlinemetals.com/merchant.cfm?pid=7459&step=4...

Edit: Just for info: Lexan is a brand name for polycarbonate plastic sheets. Plexiglass is acrylic. Lexan/polycarbonate is much harder, scratch resistant and more or less shatter proof. Plexi is soft, scratches easily and snaps into big jagged shards when bent too far or hit with something.
I've been out for 7 years now (ended about the same time this guy started). I actually had some experience working at Dawson's bug finding startup a bit at the end, which was an interesting experience, but not what I was interested in, so I went to EPFL to work on Scala for my post doc. I can sympathize with the author's struggles!

I'm only halfway through this, but everything is true, especially about research agendas and insider academic sub-communities.
OP here: I have an ambitious goal of expanding each rule into full posts with examples so I'll see what I can do for ya
Reading your comment has reaffirmed my decision to drop Linux as a daily desktop OS.

I remember everything you're describing from 10 years ago, and if things are still operating that way, then I'm glad I'm not using Linux.

It's clear from your comment that you don't understand how to use OS X as a developer. I used the BSDs and Linux on the desktop for most of the 90s, and have stayed current with Linux on both servers and desktops (though I don't ever use it by choice on my own). I don't think you're equipped to make a fair comparison.
Farhad Manjoo at Slate Technology also asks almost all of the above questions: http://www.slate.com/articles/technology/technology/2012/06/... (don't be misled by the title)

To quote:
"But there’s one big problem with Google’s small tablet: It lacks a business model. As Amazon did with its Fire, Google is selling the Nexus 7 at cost. Amazon could afford to do so because the Fire is a gateway to its online store. After you get the Fire, you’ll buy a lot of books and movies from Amazon, and you might even become a subscriber to Prime, Amazon’s highly profitable subscription service.

But Google, unlike Amazon, doesn’t sell physical stuff, so it can’t justify the low price of the Nexus 7 on the expectation of huge e-commerce sales. Sure, the search company does sell media—you can buy books, music, and subscribe to magazines from the Nexus, but the selection is thin compared with what’s available in Amazon or Apple’s media stores. If you get a Nexus 7, you’re better off relying on other sources for media. For books, install the Kindle app and buy from Amazon. For movies, use the Netflix app. For music, use Spotify.

Well, what about advertising? Google makes most of its money from ads, and boosting advertising revenue is the central goal behind Android. The more Android devices Google sells, the more people use its services, and thus, the more people see its ads. So if Google sells a lot of Nexus 7s, couldn’t it make a lot more money from ads?

Not really. Google makes only about $4 per year in ad revenue from every Android device, according to an analysis by Asymco’s Horace Dediu. So if Google sells 10 million Nexus 7s—far more than anyone expects—it would make $40 million a year from the device. For a company that made nearly $12 billion in profits last year, that’s nothing to crow about. (What’s more, two-thirds of Google’s mobile advertising revenue comes through Apple devices. If people choose the Nexus 7 over the iPad, Google might not be making any more money than it would have anyway.)

Google’s real goal with the Nexus 7 can’t be to make money. Instead, the tablet is a marketing device. Google wants to hop on the tablet train before it’s too late. It’s been two years since the iPad was released, and so far no one has managed to create a plausible alternative. The Nexus 7 is an effort to get people to believe that Android tablets aren’t terrible. It’s good enough to be usable for most people, and just cheap enough to get a lot of folks to give it a try. And if you get the Nexus 7 and find that it isn’t so bad, maybe one day you’ll be willing to give other, not-so-cheap Android tablets a try.

It’s a circuitous plan, and it could well fail. In the meantime, though, you might as well enjoy Google’s pretty good, cheap tablet."
Care to name them? I've been looking for them, and can't find any.
In iOS 6 you can open up to 24 tabs. I have 18 tabs open right now :)
100% correct.

Much like someone learning a foreign language from an early age, or growing up in a bilingual house. Even if this was the case, we don't expect that the person is saying they were a great writer, orator or debater at age 11.

I started programming at 9. What I mean when I say that is I was able to think about problems, data, logical rules and how to break those down in to something a computer could understand, usually in BASIC (much later 6502 assembly). True, I wasn't programming enterprise apps, but the foreign language thing feels like it rings true to me.

If I was looking for a translator, I'd prefer someone who was a native speaker their whole life, or someone who'd been studying from an early age. Someone who took "spanish I" at a community college 3 years ago, and perhaps visited Spain last summer .... they might be able to do the translation, but it likely won't be as comprehensive and nuanced as someone who's lived with that language for a lifetime.
What is Google Nexus 7's Business Model?
not to people to whom he's not distributing a binary
Ask HN: Why doesn't Mac have an 'uninstall' function for unwanted programs?
Just got a macbook air and I don't understand why the OS doesn't have a simple removal tool to uninstall programs. Can anyone reco an app that removes unwanted programs - entirely.
Penn's second intro class is indeed in OCaml, mostly due to the effect it has of leveling the playing field. It really turned out quite well, and most of the students enjoy it.
Video: http://frontburner.dmagazine.com/2012/06/25/video-of-bill-fo...
They're doing exactly what they except Sparrow do if I'm not mistaken: run a server and push mail. There's no magic involved.
> Apple has managed to have a bogus patent issued - the patent, as far as I can tell, covers any sort of "search-as-you-type" system

Is this from reading the claims, or from reading the introduction (whatever that's called)?
Okay, maybe arithmetic is too basic. But it certainly isn't beyond basic trig! I bet you don't use trig daily, but it's hardly unreasonable for you to need to know what sin and cos do.

The first time I ran into the whole configure and make system, I just looked at the INSTALL file and followed the instructions. It was actually easier than some GUI stuff I had to do because I could basically copy the commands verbatim instead of having to look through a bunch of complicated screenshots.

It also took me a little bit of effort to get used to Haskell. But once I did, it was great. It really is a magical language; it combines all the benefits you normally hear about with a unique sort of expressiveness I haven't found in any other languages (even close ones, like OCaml, don't quite cut it, although they are awesome in their own ways).

The real breakthrough for me was implementing a simple Scheme interpreter in Haskell. There is a tutorial [1] that explains exactly how to do this; I found it very helpful. However, I am a little leery of suggesting it now because the code there doesn't always follow best practices. It's great for getting the right mindset, but you should probably not carry all the exact techniques over to your real code.

[1]: http://en.wikibooks.org/wiki/Write_Yourself_a_Scheme_in_48_H...
You don't have to be a huge threat to be worth squeezing money out of. Huge threat? I don't think so.

Samsung is the only other player making any real profit in the industry, so they are definitely Apple's largest competition at this point. Unless MS does something crazy with Windows Phone 8. They're important.

But I don't agree with huge threat. At this point, Apple may be able to take a year off from releasing a new iPhone (despite not having true 4G) and not suffer significantly in the long term. It's not a good idea, but I bet they could.