skysight-inc/HackerNews huggingface dataset:
Could it be that this is an innocent mistake or a bug in the way that Google servers are sending HTTP. Chrome wouldn't be affected as it will be using SPDY for all Google services. As soon as Chrome switched back to the Firefox user agent it started using HTTP again and the same bug was found.

Besides, this just doesn't make sense. If this was an attempt to make Firefox look bad then it's a dreadful one. This just serves to make Google services look faulty as Firefox will still work for everything else. Because of this I doubt there is any malice behind this and it is just a bug.
dup: http://news.ycombinator.com/item?id=3923421
Not just cultural differences. Things like car accidents and murders also play a disproportionate role.

If nation A has 60 people living to 79, and nation B has 59 people living to 80 and 1 person being murdered at 20, A and B have the same mean life expectancy (of 79).

Though I suppose you could call things like murders and road safety "cultural".
if (document.querySelector('h1').innerHTML.match(/^Is .*\?$/)) { console.log('Probably not.') }
Why not buy Nokia for its patents and dump the rest of the business then?
so should we all buy nokia stock in expectation of a takeover?
It works fine here (Chrome on Windows) even if I log out.

I think it's a bug. Are you on a mobile browser?
I wonder if the problem goes away if SPDY is enabled on firefox (it ships off by default in v12)?
How to recover a lost file in Word 2007 or in Word 2003?
A laptop with a wired detachable touch screen
The original question was from March 2009. Deleting that three years later is bad internet citizenship -- it's removing internet history for no good reason.

Fair enough, if it was a new question asked today, no question, delete it, as it's clearly off-topic now, according to the rules they've clarified and developed over the years. But when these types of questions were asked originally they were on topic at the time. Deleting them retrospectively is poor form.
TypeError: Cannot read property 'innerHTML' of null

You should use UA sniffing to fix this bug.
I remember a saying for this kind of phenomenon. What was it, "Slow news day"?
Exception performance is pretty obvious: you need to unwind the stack everytime you catch an exception whereas checking an error return value is one instruction long.

It's not obvious at all. You need to unwind the stack anyway. If you do so using some form of jump table when an exception is thrown, you only have a single step to deal with instead of a whole series of returns. Moreover, on the non-exceptional path, you no longer need check-and-branch logic after the return from every function that might fail.

If you try to catch your exception at every statement, you're not using RAII correctly.

Sure, but that doesn't imply your conclusion that usually you would only want one try/catch per thread. Why can't we catch an exception at whatever level of our code knows how to respond to that situation? Why would we assume that the only levels of logic in our code are low-level work that might throw and a top-level oversight loop?

Returns values are less bug prone because behaviour is obvious (boost::system::error_code is a good way to encapsulate information).

C++ does non-obvious things all the time, and that can be helpful because it removes unnecessary details so that we can concentrate on the logic that matters. Would you also argue that using RIAA is bad because if we explicitly released all our resources before every possible return from the function it would make the behaviour obvious?

Exception is a goto statement because basically you're breaking the flow and saying "go to catch in case of error".

Except that you're not just saying "goto catch", are you? Like return, continue and break statements, exceptions can only transfer control to another location in a structured way, in this case, the equivalent of returning early from the lower-level functions and going back up the call stack. You can't escape the structured programming roots of the code using an exception the way you can with goto, and the semantics of unwinding the stack when an exception is thrown are well defined and widely understood.

For all these reasons, exceptions should be exceptional.

Use exceptions for abnormal behavior that you cannot properly handle in the program (out of memory, i/o error...).

Sure, that's one useful role for exceptions, but why should we limit our use of a tool based on what the tool happens to be called? I don't think they had modern C++ libraries and metaprogramming in mind when they added templates to the language.
> Many jobs have wearing a suit as a prerequisite. Would employers simply not hire anyone and close their doors if everyone refused to wear a suit?

You assume that bosses are rational agents. Years of idiotic decisions by idiotic bosses[1] shows otherwise.

[1] see Dilbert (1989), 'The Office', 'Office Space' (1999), etc etc.
Harr. :)
If you read the PostgreSQL docs you'll see that it only truncates spaces and throws an error if any non-space data is present. Apparently, this behavior is required by the SQL specifications.

So, in your example of storing "foobar" in a varchar(3) field, PostgreSQL will throw an error and not store the data. You could however store "foo " in that same field without any problems and you would get back "foo" in return.
Last ice age ended: glaciers in Canada slowly melted, forming huge mile-high lakes within the rotting ice.

One spring day the rotting ice broke, the lakes surged free, travelled downhill as they must, ending in the gulf of mexico.

Took all summer, carved the Mississippi valley. According to the storey in the interpretive center near Pike's Peak.
A round peg fits better into a square hole, until dimension 9.
3 Signs That It’s Time To Quit Your Job.
How did you set your self up for this unhappiness? Why did you go to Australia expecting to find something and turn out to find something so different?
Oops, didn't notice the second page myself.
Why buy it for at least $15 billion now (they'll have to pay a premium obviously), when they can wait say until the end of the year when it will be worth half of that? Nokia's share price is going down fast together with their revenues and market share. It will be worth a lot less 6-12 months from now.
Zynga didn't buy every other game this year and yet substantially all will have a growth curve shaped like that, with the main question being height at peak. I also think that zynga would lose in the poll "Who makes FarmVille?" to Facebook, Google, Microsoft, and Kim kardashian, even of you asked active paying players of it rather than regular people.
C♯ isn't much better, since IIRC search engines often ignored special characters.
I don't know why the other manufacturers haven't quit already. By staying on WP7, they're just helping Nokia, which at least was in the past one of their biggest competitors. All the credit for WP7 goes to Nokia right now, and Microsoft will also make sure of that.

If they didn't choose WP7 a year and a half ago, we wouldn't even be talking about WP7 right now, and they could've gotten rid of Nokia much more easily (which I'm sure it's something they'd like to see). But instead they sustained it until Nokia was ready to get all the credit for it, and now they'll get nothing out of it.
Technically Nice was never a part of Italy. Nice was most of the time part of the Duchy of Savoy (later called the Kingdom of Sardinia when the Duke of Savoy also became the king of Sardinia). Nice became French in 1860 while Italy was formed in 1861.

What used to be the Duchy of Savoy is now split between Italy and France.

EDIT: A map of Savoy in the 16th century: https://en.wikipedia.org/wiki/File:Savoy2.png
Interesting. But they didn't call it dot-net-dot :-)
True, but sneakernet protocols are more difficult to navigate and hack than any NAT. Why leave that attack surface exposed?
How to Succeed in Living the Entrepreneur Lifestyle
Stanford's course is often recommended. I just started going through it myself.

http://itunes.apple.com/us/itunes-u/ipad-iphone-application-...
<opinion> Probably Nokia would demand north of $20 billion to even be in the game. A few more bad quarters can lower the price, but still, it's Nokia.

MS has enough patents to scare the crap out of any rational company: they have been working in OS for decades and they patent everything. Long before the iPhone, MS came out with portable and mobile computers http://en.wikipedia.org/wiki/Windows_Mobile . The fact that their work never caught on, doesn't matter, the underlying tech is probably all patented. Add to that Nortel and Netscape patents (hello cookies, SSL and everything we take for granted now) and they are loaded with patents, especially since Android is an OS. Any win against MS is temporary; they don't mind opening their checkbook to license and to hire lawyers. As for Nokia's patents they can probably "buy" a few select ones to go after Motorola /Google instead of spending billions and billions

Edit to add: If not for Google, Motorola would have undoubtedly kissed the ring too, like Samsung and almost every other company did.

</opinion>
For your level of experience I would go would go with Kochan - Programming in Objective-C 4th edition.

There is also a free course for iPhone programming from Stanford (video lectures).

MonoTouch is a good alternative if you prefer to use C#, but you will need to pay 99$/year to Apple + 399$ for Monotouch. The good thing is that you can evaluate MonoTouch and pay after you are comfortable with the tool.

RubyMotion is too young to be used in a large application. Also learning Ruby and Cocoa in the same time can be difficult. I think RubyMotion is a good fit for an experienced Ruby programmer that wants to start coding on iOS. Another potential problem with RubyMotion is that it is currently developed by a single person, which can be problematic on long term.

That been said, muy advice is to go on the Objective-C route since you are already comfortable with C. Objective-C is a small language and an experienced C programmer can be up to speed in a matter of days.

The real challenge is in learning the iOS libraries and not the programming language.
I never get any errors with Firefox on Windows, so this was a interesting article. I will have to try it out some more on my Linux.

However, I got loads of "Connection was reset" when trying to use the powerbase site where this article was. Server seems very very slow or something is wrong with it.
Actually, that's a reverse problem to Wikipedia. Wikipedia article quality increases hugely, then as people fiddle with the article the quality rapidly decreases. Then it increases again... ad infinitum. Sort of like a sine wave.
You can use Jinja2 with Bottle:

> pip install Jinja2

from bottle import jinja2_template as template
This is the best iOS app out there. I have been using it for almost a year and I can't imagine owning an iPad without it.

This may sound like an ad for the app, but I have nothing to do with Alex (the creator) or his company. This app is just that good.

The kicker is that Alex is actually working on his own git library for the app, so in the next month or so expect to be able to have native git capabilities right from your iPad. Cannot wait!
It is common to have time on the x-axis, but that doesn't seem to be the case here. The dots on the line are equally spaced horizontally, but the number of years between each dot varies, sometimes it is 20 years, sometimes it is 40 years, so I don't think the horizontal location represents time.

I'd call this a parametric plot, useful when you have two quantities which vary over time, and you want to visualise how they relate to each other. There are some good examples of that on the Ladder of Abstraction demo, http://worrydream.com/LadderOfAbstraction/ The "Abstracting Over Time" graphic is a parametric plot of the position of the car, where x is horizontal position, y is vertical position, and distance along the line is time.
Because the probability of a success of Windows Phone goes down with every day they get bad press and unhappy customers. Nokia is the only handset manufacturer really pushing Windows Phone.
That would be short sighted. Apart from price, they do want to buy it when its in a relatively stronger position. In another year, with even lesser share, it wont be as attractive.
I know that Postgres does this the right way. I was referring to the initial comment that was suggesting that truncation happens, but of all the databases I know, only MySQL does that and it's totally wrong IMHO
Yes, the general opinion seems to be:

Use Objective-C with the new Automatic Reference counting mechanism.

iOS libraries - in your opinion - what are some good resources to get familiar? (Google-fu results in a lot of links to wade through).
On the other hand, how often do you type any search engine into the URL field? It's either bookmarked or it's automatically set as your search engine.
MySQL will silently truncate it without throwing an error however. And even when you know about it, you'll still get bitten occasionally and SERIOUSLY kick yourself when you realise the error.

Postgres is better for the little things, but when it goes wrong it tends to be harder to find the reason why. At least in my experience. That said, I'll still reach for Postgres over MySQL these days.
Do programmers encounter all sorts of algorithms when engineering software? In my experience, the only things I really need to keep in mind what are the consequences of certain data structures and algorithm types rather than their specific implementation, because often the implementations are built-in to the language, but the choice of which implementation of data structure and algorithm to use are more important. I use sorting algorithms very frequently. Usually it is just a call like "list.sort()".

Yet in interviews, the questions I get asked are more like "Implement <My favourite sort> in 20 minutes, no googling.

I mean, really?

The other day I was in an interview where I had to implement a queue in 30 minutes. The unit tests were already written and the IDE was eclipse.

I wrote the "correct" implementation for the queue in about 10 minutes but there was a bug I couldn't find; I've never used eclipse before and took a lot of time figuring out everything. In the last minute I finally tracked down my bug. I forgot to increment a variable. I fixed it and all the tests as well as the performance test passed. I didn't get the job because I took too long. (It was a graduate position and the last time I used Java was 2 years ago)

I was distracted with all the buttons on eclipse... Otherwise I'd never have missed the variable increment! I swear. Anyway the point is, if a programmer is ever implementing their own simple Java queue in production software it is not a good sign anyway. Why are you testing for that?
> ... by telling us Unicode sucks.

Could you tell us where he did this?

(I didn't notice it on the first time through; he did say to use Unicode everywhere inside your code, though, and to not do anything rude like converting Unicode to ASCII by stripping non-latin1 characters.)
Interestingly, the original iPhone 4 is a more attractive device than the iPhone 4S because it doesn't rattle when you put it down.

I can't believe that slipped though. It's a blot on the impression of the iPhone 4S as a solid thing.
As a Mercurial user who doesn't feel like learning git just for the sake of deploying toy Python apps, can anyone comment on whether hg-git or the like is a reasonable way of deploying to heroku?
Regarding #1: "Taking their beautiful hardware and subjecting it to Windows users must have been controversial inside of the company. It just didn't seem like something Jobs would do." -- Having read Jobs' biography, it wasn't something he would do: he argued against it, and even said that Windows users could use iPods "over my dead body." However, business sense prevailed, and Jobs realised that it made sense to open up the iPod world to Windows users.

Jobs was a proponent of porting iTunes to Windows, but Schiller didn't want this. As a result, Apple joined leagues with MusicMatch, and they made a music player, but Jobs said it was a terrible piece of software:

"To make the iPod work on PCs, we initially partnered with another company that had a jukebox, gave them the secret sauce to connect to the iPod, and they did a crappy job. That was the worse of all worlds, because this other company was controlling a big piece of the user experience. So we lived with this crappy outside jukebox for about six months, and then we finally got iTunes written for Windows. In the end, you just don't want someone else to control a big part of the user experience. People may disagree with me, but I am pretty consistent about that."

So Caldwell appears to be right in both points: it was understood that it would bring a lot of value back to Apple, but it also took a lot of smart people to convince Jobs to let it happen.
Actually, the use case is more for someone like me - I remember that I want to try DDG once in a while, so I decide to visit it, and then I can't remember the shortcut and am annoyed that I have to type in the whole name.

Obviously serious users of DDG don't have any problem with it.
T.H.I.S.

Most people don't get the 'schlep' as pg wrote about recently. Startup success stories aren't all about One Amazing Idea and the code that goes with it. It's about the whole ride.
> (and if you do not write in "pure" functional way - you will never see this problem)

Could you explain this a little more, please?
#2 is the reason why we'll be getting my Mother an iPad (2). She wouldn't appreciate the high resolution screen, so we'll save a few bucks and she can still FaceTime the kids.
The problem with PHP is that people is not used to languages/communities evolving so fast.

You should check Symfony 2, then tell me if you need a better structured or more feature complete framework.
Apple Legacy Filevault Hole
I think at one point .Net was going to be the next major brand for all MS products. At one point MSN Messenger was called ".Net Messenger" before it was renamed to Windows Live.

I imagine the branding didn't work for consumer products because nobody had any idea what it meant. Hell , I had no idea what it meant. I remember trying to figure out what .Net was because I had heard so much about it , but all I could get from MS' website was jargon and buzzwords about "enterprise web services".

It wasn't until I started writing C# code that integrated so seemlessly with old VB code and started being able to do things easily (like sockets , databases and GUIs) that I would previously have had to dig through obscure C++ APIs for that I "got it".
See also the (great) video by Adam of Heroku at the 2011 Startup Lessons Learned conference

"The Epic Pivot - Heroku's Story" (20mins): http://www.justin.tv/startuplessonslearned/b/286516447
7 Business lessons from Caine's Arcade
I'd say there's no quick way to do it, the message passing of obj-c is very different than the event-based slots & signals programming you are used to. And that's before the hell-which-is-InterfaceBuilder. Since you already familiar with programming, I'd suggest the Big Nerd Ranch guides at bignerdranch.com

Most online examples won't give you the details about the important stuff - single inheritance vs. categories, delegates and message passing in the runtime, extending a protocol, etc. You may see it in the code, but there won't be any theory or reasoning behind it to help you.

As a side note, you can track your learning progress by how much you hate XCode with specific examples of how it ruined your day.

Can't speak to clutch.io, but the other 2 just seem to get in the way of someone who already knows Ruby, C#, and obj-c. Do you really need another layer of abstraction if you want to learn something at a lower level?
rshetty: posting links to your own blog - which you do often - gets old.
YES! We need to get one of these disclaimers so we can stop the endless stream of needlessly pedantic comments that contribute nothing to the discussion. Of course, given the volume of those comments on HN, it would be a long, long disclaimer.

And we'd have to make sure to restrict pedantic comments trying to find workarounds to the disclaimer (by taking overly literal and meaningless interpretations of them of course) to one giant pedantic orgy thread.

In all seriousness though, I see this happening on every sufficiently busy thread on HN, it's annoying. It's not all bad though, as that kind of attention to detail is sometimes also what facilitates insightful discussions on the threads.
"Don't worry, migration from Python 2 to 3 is really easy. It'll take 5 minutes to learn."

"Migration for libraries from Python 2 to 3 is really hard. It's taken them a few years and counting."

??
Harga Samsung Galaxy S3 (SIII) Dan Spesifikasi 
Salah satu handphone pintar Samsung Galaxy S3 ahirnya Muncul di Indonesia dengan Harga yang sangat mahal di bandingkan dengan h
That video demo was quite impressive.

I've used video stabilizer filters on virtualdub but I doubt they could fix as much as was done in that demo.

Another interesting stabilization demo http://www.youtube.com/watch?v=_Pr_fpbAok8
Yea, Linode support both. Thanks.
Replace "Halo 3" in that example with any title (fictitious or real), and the broader point still stands: even big titles mostly have quick burnout rates. The analogy wasn't so much about Halo 3, specifically, vis-a-vis Draw Something. It was about any hit game vis-a-vis Draw Something.

The console and PC gaming business has largely been a franchise business, largely because of single-title burnout. And, in fact, it makes little economic sense to keep gamers playing your same, single title for years on end (unless they're subscribing to it, a la World of Warcraft). Big studios typically desire burnout, so that they can sell you a new title or sequel for $50, or a piece of DLC for $5-10, or what have you. EA doesn't want to sell you one game that you'll play for 12 months straight; EA wants to sell you 12 games that you'll play for a month apiece.

The iOS/Android app market has been different, though, and I think it's important to dissect why. First, a title like Draw Something will remain on the "shelf" on App Stores indefinitely. Nobody's holding physical inventory on limited shelf space that they've got to clear at the end of the month. Second, console gaming burnout is often the product of fairly direct substitution in the marketplace -- i.e., I'm going to stop playing UberSoldiers 25 because a very similar title, L33tSoldiers 14, just came out and has better graphics and features.

In the iOS app market, we don't see such direct substitution effects[1]. Nobody's burning out on Draw Something because Paint Something just came out with hotter features. In this sense, burnout on Draw Something might actually mean something interesting. It can't be accounted for purely by basis of comparison to the console gaming market and its standard-issue burnout rates. This is where I think the Halo analogy (really, the standard-issue gaming business analogy) doesn't quite hold up.

[1]Unless, of course, we do. A strong argument could be made that any casual iOS app titles are substitutes. So Draw Something competes with Angry Birds, the same way that Modern Warfare competes with Battlefield -- even though Angry Birds and Draw Something have fewer superficial similarities.
How nice of Mr. Gates to invite interns to his home, though.
That's very good advice, thanks. The usual problem, though, is that you don't know if it's worth building (so you aren't wasting your time), so you need to go with your gut if you consider that a market big enough exists for the sort of thing you're building.

I think there is a market, so I'll post here when the MVP is ready, and see if people find it useful. Thanks again!
True, but I think DDG is smart to pursue the bigger market of "people who want to find stuff on wikipedia, youtube, and google image search" and wait for DuckDuckHack to come up with a plugin that does skillful python searches.