skysight-inc/HackerNews huggingface dataset:
I have taken that one step further - I don't pay anybody else and do all the work myself. Every single dollar stays in the local economy - nothing gets away to those dangerous foreigners. Sure I have to work 16 hour/day and have multiple injuries, but that is a small price to pay right?

In other words - if you think there is any benefit to "shopping local" then you should try to think what will happen if you took that to the extreem.
I think the implication is that if a user is trying to use Google Docs or other "advanced" features, then either they themselves or their support staff are likely to be willing and able to upgrade their IE client.

Search is more lowest common denominator, hence it's ongoing compatibility.
... by 0.000000125 seconds over the last 40 years.
That's why the GSM iPad isn't for sale, and, in fact, Jobs even said that at the keynote. That doesn't explain why you can't preorder a non-GSM iPad.
I wouldn't bet on it being a flop. In my opinion, the only unsuccessful Nintendo console was GameCube. NES, SNES, N64, Wii, all a success. PS1 was a success, so was PS2. I'm not really convinced of this industry rule you're talking about.

Wii reached an audience no console ever reached, thanks to the titles and controllers. I'm betting Project Natal will take over a big slice of that market, unless Nintendo really steps it up.
IMO, this argument is a red-herring: you can write bad code in any language.

Perl lit is awesome and erudite: the best idioms are described in the Cookbook. Programming Perl is a joy to read, Best Practices could be used as a standards guide.

I agree that v5 has some problematic constructs, but, all in all, what Larry Wall & Co did was awesome.
The customer didn't choose, install, nor maintain the drive-thru intercom. If it's insufficient for the business purpose, fix it, but don't blame the customer. They have a reasonable expectation that the intercom works as well as the average speakerphone.
But they exhibit at least two features the ipad lacks:

- sub $300 pricing

- fit in pockets
PHP is, essentially, a souped up templating language, so I'm really not surprised you prefer it.

Django's templates aren't bad though, even if a little awkward at times.
Agreed. All the locking mechanisms and codes are to prevent accidental and non-authorized triggering. After that you have to depend on guys with guns for security.
Yet another post about how technology will solve all of our problems
Excuse me? The book costs GBP40 or 30 for the PDF version. Don't tell me to relax. Relax is for free crappy blog posts, not technical trade literature.
The bigger reason why I cannot use my SIM in the iPad is because my networks 3G operates on AWS 1700. Which, thank you Apple, decided to exclude because they're whoring themselves to AT&T and blocking T-Mobile, and in subsequence Wind here in Canada.
The application you have just started uses 'flash' content, this will adversely affect your battery life.

Click <ok to continue> or <cancel to save your battery>

edit: way to go downmodder, getting modded down for presenting a possible solution to an issue is a new low for HN.

Congratulations. Now if you'd be so kind as to explain why you thought that was not a viable solution?
Same here: IE8 on XP, FF 3.5.7 on XP, FF 3.5.7 OSX and Safari 4.0.4 OSX

Edit: Ohhhhhh I get it now; you have to enter your search term, hit the search button, and then select which portal you want to search through.

I think the interaction needs some work, but I do like the paging between the search engines. I'm not sure if I would want to do that a lot, but it is kind of novel (to me at least).
Making changes to addressing problems only when they occur is part of agile development. The problem here is that the change is an extreme one, that generalizes from one instance to all. But how do you tell how much you should generalize?

A starting point is raw statistics: if you have 1000 customers, and 1 has this problem, should you fix it? Then, account for consequences: how serious is that one problem (what is its cost to you, to the person, to the community)? Finally, what are the knock-on effects, looking at the big overall picture: will addressing this problem improve your business overall, or undermine it? (sometimes, that 1 in a 1000 problem is a good excuse to fix something, or a signal to grow in that direction).

Then, you can think about the best way to address the problem. Nasty prohibitive signs probably don't help; even nice prohibitive signs probably don't help either. Sometimes, you can reorganize how you do things so that the problem cannot occur (e.g. when training animals to not do something, you can train them to do something that is incompatible with the undesired action; e.g. floppy disks are shaped so that they cannot be inserted in the wrong way).

The owner of a prominent software respository site told me that no matter what you write on forms - or how you highlight it - people will simply not read it.

BTW: Sometimes the sign has underlining and exclamation marks added in a different colour, apparently upon second and third infractions. Exasperation marks.
Like I said, it doesn't look at the account's tweets, just its profile. That account has a good follower/following balance, it's not brand new, it hasn't sent a ton of tweets in a short time, it has a profile image... basically it looks safe.

Yes feedback is definitely needed to improve it! And to identify spam for other users with the same followers.
Do you have any insights/opinions on why node.js beats Netty? It is something inherent in the JVM or is Netty's implementation flawed/not ideal for your scenario?

(E.g. I'm a node.js newbie, but my understanding is that it doesn't have the io thread/worker thread pool, pipeline/handler framework that Netty does. Still reading about it.)
More information: http://www.ioccc.org/1990/westley.hint
The biggest difference that stuck out in switching was the way PHP was effectively like markup language, while Python usually involves its own web server. This can be a difficult transition because instead of thinking in terms of requests to specific files, you have the option to handle all requests however you'd like. It allows for more flexibility, but you usually have a more difficult time with deployment since things like static files are better served with a traditional web server. Likewise, things like different applications need a little more thought than simply uploading a file. That said, there is a wealth of great libraries and the standard library that help not only provide functionality, but help promote better code.
I read this as, "As an owner of a restaurant, I expect an x% profit margin. My friends down the street, however, seem to be happy with less. This means that I now only get an x-y% profit margin, and that means I have to trade in my 767 for a Gulfstream V. Clearly those damn consumers don't know what's good for them, and this is going to ruin the economy again. I say this as a completely unbiased neutral party who is deeply concerned with society in general, and certainly not because I want to keep my artificially high profit margin and the luxuries it affords me."
Money, although a very objective method of quantifying value, is not the only measure.

In a literal example, why attend university and pay to do work? The answer is, there is value in learning something. Presumably, that is what this individual wants to do.
Easing Smalltalk compatibility with Grease
Shoulda-like Rails validation and association testing with RSpec
The next step is hardware-based key-value stores.

I believe this is called the TLB.
There’s also a thumbnail view that shows all your open pages in a grid, to let you quickly move from one page to the next. -- http://www.apple.com/ipad/features/
I got the regular size Kindle 2.0.
It does suck for unmodified PDF's, but i have yet to try: http://news.ycombinator.com/item?id=1089068

That said, I "bought in" intellectually accepting that I shouldn't expect to straight up enjoy all my PDF's on this thing. I decided e-readers would be something that would be worth it (for me) to take a hit with the early adopter tax.
Can someone explain to me advantage of the Ipad over ASUS EEE multi-touch
I looked at both, and Asus tablet seems infinitely more capable, having things like memory-card readers, USB, a proper OS, a keyboard, and all that at approximately the same price. Can someone explain to me, why the Ipad deserves a second look?

Edit:The EEE in question http://www.asus.com/product.aspx?P_ID=KIqtSJ1aVsmVpeqS
I'm currently working on a team that switched from PHP to Python+Django for web application development a little over a year ago. Since I've been writing Python code longer than PHP (8 years vs. 6 or so), I can't really speak personally about what the transition is like, but I can tell you about what I've observed and heard from other members of the team.

In general, the Python language and tools tend to steer you in the direction of writing cleaner, better-structured code. Working with Django also gives you access to a lot of decent 3rd-party applications that you can integrate into your project, and the Python stdlib absolutely dominates PHP in terms of scope, quality, and consistency. Having the bytecode compiler and libraries that provide better data structure and algorithm in app servers also opens up the door to a whole bunch of performance optimizations that are difficult to accomplish with PHP.

That's not to say that the Pythonic way is always better, of course. PHP encourages a very iterative approach to development -- at a basic level, you're creating a static page, then incrementally adding dynamic behavior until it does what you need. Python apps tend to put the code front-and-center, and output HTML (or JSON, or XML, or whatever) as a last step in the process. In the long term, that's usually a Good Thing, but it can make the prototyping and learning processes longer for some people.
tptacek, I wrote you an email a few days ago about a similar topic. Did you receive it?
If a smart person makes a dumb decision it was probably an impulsive one. If Steve Jobs is smart, the chances of him making a decision on something this big, this monumental would be unlikely. Plus, look at his track record. Even less likely now.
>IMO, this argument is a red-herring: you can write bad code in any language.

I would be delighted to see you cause a segfault in Haskell without taking advantage of an implementation bug.

The point isn't that you can or cannot write bad code in any language, it's not that simple. It's a matter of how difficult a language's semantics, type-checking, logical structures, and faculties make it to traverse the spectrum towards bad code.

Python has clean indentation baked in at the implementation. All major interpreted languages don't allow you to muck around with pointers.

Functional languages strongly discourage mutability. Object oriented languages are really just a foil for context scoping in various ways combined with somewhat sanitary code-reuse that is less likely to introduce type or memory sharing bugs.

It really bothers me when people say, "you can write bad code in any language". Of course you can, but that ejects the subtlety and reality of the matter into vacuum. You cannot disregard the effect of the programming environment on the code, and the supposed canard of Perl's write-once read-never is not false but rather, a tendency that it facilitates.

I mean, have you seen the number of operators in Perl?

http://tinyurl.com/badvbx (large 300 dpi jpg, Period Table of Operators in Perl)

While this makes Perl the king of golfing, the mental context it consumes to remember all the operators someone else may use in their code (but that you do not) makes reading their code a non-trivial task.

This is precisely the thing people complain about when comparing (unfavourably) C++ to C. There's just too much syntax and too many complicated interactions that make it nearly impossible to reason about what the code does, let alone any degree of referential transparency.

Potentially one of Lisp's most powerful attributes is as you may have heard, the lack of syntax. The one ever-present syntactic feature in Lisp (paren) is widely mocked as well by detractors!

Perl is awesome. It's erudite. It's a fantastic means of parsing and manipulating text (I vastly prefer Perl to awk/sed abuse except for in-line commands.) Perl documentation is really good too.

All the meta of what makes a languages pleasant to use, is mostly there for Perl, but the language itself is a syringe of heroin and rat poison, just begging you to abuse the power.

And don't mention CPAN. People who accuse Python libraries of being written by amateurs haven't seen the manifest horrors that exist in CPAN. Rubyists have it good by comparison.

Can we please drop the "you can write bad code in any language" line now?
I've used it for some simple stuff and that worked ok, but as soon as you get forms with ajax integration, auto lookup and auto-reject of fields based on pre-existing keys things get tricky in a hurry.

So I rolled my own forms, thinking at the time that it must be possible but not knowing how.

Now I hear - from someone in a HN comment - that AJAX and django don't play particularly nice.

Here is the thread, I dug it up:

http://news.ycombinator.com/item?id=1078743
By removing Flash altogether, Apple is encouraging web developers to upgrade to new web technologies (HTML 5). If the iPhone/iPad had the option of using Flash, then web developers wouldn't have an incentive to produce non-Flash content. I'm guessing that had the iPhone come with Flash at launch, Youtube would never have implemented MP4 and HTML 5 video tags.
This one is well worth reading. He doesn't just list his kit, he has quite a bit to say on writing and some very interesting ideas about a "dream setup".
I know my phone (Motorola) is capable of voice dialing, either by number or of a speed-dial, or I can record an input. Why would I need an additional input device when most phones are capable of voice dialing?

Edit: As the iPad is based on the iPhone's OS, it is already capable of handling voice-dial inputs, you just might have to jailbreak it to access it:

http://www.apple.com/iphone/how-to/index.html#phone.voice-di...
I've played with ruby on rails very briefly when it was very new, and I was disillusioned with how fast I ran in to the limitations of the framework. I presume that it has come a long long way since then, but I haven't looked at it since.

I probably should.
How would one go about doing this? Isn't all subscriber information locked?
You have to click one of the links below the search box after you run a query. The fact that people are confused means that is certainly a usability issue though.
As far as syntax, it's about as easy to pick up as it gets. ( http://diveintopython.org/ )

Web dev wise, it helps if you had some experience with PHP frameworks (though most of them are modeled more on Rails rather than Django or other Python frameworks). Also, the libraries aren't built in as in PHP and documentation isn't as good as PHP's (I'm not aware of any language that has online docs as good as PHP's. Django has great docs, though).

I recommend starting with Google App Engine. It basically takes care of the deployment for you, which is often a sore point in many environments. It's free and includes a basic framework that resembles web.py with bits of Django. In fact it's worth picking up Python even just for the sake of making use of GAE.
I don't think Flash is at all threatened by the iPhone and iPad not supporting it. The owners of those devices are a tiny but vocal minority who may never be able to use Flash on those devices, but that's the choice they make by buying a device they have artificial control over. Flash itself is absolutely entrenched in the internet and unlikely to disappear because however many millions, out of a billion, can't use it.

You only have to browse down as far as the #2 website in the world, Facebook, to see a site that has extraordinary use for Flash and revenue and businesses built around it - Zynga is practically printing money.

Go down to #4 and you're at YouTube, who are going to be using Flash for the next decade while HTML5 trickles down to an audience that doesn't care and won't even notice when it stops being Flash.

Further down the list you see MySpace at #15, a site which has ties to musicians (generous use of the word) and many millions of users who embed their own or others' music on their profiles in .. Flash.

#29 is a live cam streaming porn site, unlikely to be replaced anytime soon by a non-Flash technology.

Flash isn't "just" video, it's a richer platform than HTML/CSS/JS, both now and next-generation versions, and it's used prominently by some of the most-trafficked sites on the net and less prominently by most of them.

HTML/CSS/JS is an insanely slow moving set of standards. Everybody's holding their breath for HTML5 to "be everything they need" ... and it's going to do a lot and it will be, for a while.

But it's also going to be a standard for a very, very long time and technology isn't going to stand still just because the W3C can't keep up.
Creating a Better User Experience With Storytelling
Up until I bought Hearts Net, Hearts Solo was the best hearts game for the iphone out there (UI aside).

If you want to try and get some more exposure, maybe try getting some blogs to play your game.

Gizmodo, for one, has weekly "best of" posts for apps, so you could give that a try.

http://gizmodo.com/5459997/this-weeks-best-iphone-apps/galle...
Yeah, pretty sure that was a play on the CouchDB tagline.
Same, I've always heard purple. From there, you get: What's lavender and commutes? An abelian semigrape.
Joy.

That does it, I'm off FB for good. Not for any real feelings of invasions of my privacy, it's just because they're careless and/or practically malicious.
A complex query is one that hits several tables in several databases on more than one server.

You can simply forget that using django, you'll have to export all the stuff you want to query in a format that exactly matches Djangos field name magic.

And better not get any of that wrong or you'll be tearing your hair out, an underscore in the wrong spot and it will look just fine but it will never work and the error messages you'll get are much less than helpful.

Here is a comment from the models.py file in one of my little django applications:

# caveat, the related_name parameters of parent and thread
# should not be parent_id or thread_id, this leads to
# an 'add() argument after * must be a sequence' error
# when transforming the template. Apparently the names
# clash with the underlying field names that django
# uses for these fields.

So, effectively, what this is all about is that django names a bunch of fields in the queries as aliases, but does not check if there are real fields with those names.
Google Apps Script now available for all
File Naming Conventions
I'm confused, are you a cuttlefish or a scuttlefish?
>>interesting work over

I can most definitely vouch for that.
Also MongoDB support: http://wiki.github.com/orlandov/node-mongodb/ (bleeding edge, but is working well for my experimental project)
In future, could you link the alternative product in question? I understand that it sounds incredibly lazy but I tend to scan many threads at a time and going on a google-hunt for something you wish to discuss makes my panda cry.

Not to mention that finding obscure taiwanese/chinese products can actually be mildly non-trivial at times.
Apple Pulls Flash Content From iPad Promos
> in fact, I don't know if any language has online docs that come close to PHP's

MSDN and MSDN Social has some decent doc and comments.
There are some very neat fixes to the more glaring issues with Djangos templating language, for instance the if statement.

edit: more digging:

http://www.djangosnippets.org/snippets/1350/
Also, once the handshake is done, no back-and-forth of TCP/IP headers (which generate a lot of needless bandwidth).
z/OS doesn't ship with Flash because Adobe's runtime burns MIPs like nobody's business. Data Center Operations does NOT like having to bring additional capacity online because the Southeastern Division discovered Farmville in the middle of year-end batch.
gigantic ridiculous ad for Rosetta Stone
Well, one data point: "38% of homeless survey respondents reported that they first became homeless outside of San Francisco or were relative newcomers, having lived in the City for three months or less." And that's actually a significant decrease from the 2007 survey.

http://www.sfgov.org/site/uploadedfiles/lhcb/homeless_count/...
As the ratio of Flash-having to non-Flash-having devices decreases, more and more sites will have to consider how much money they're leaving on the table by not supporting them.

For some this will be "easy" -- if you're a video site, serve up your vids in HTML5 <video> in addition to Flash. We've already seen YouTube and Vimeo take their first steps in this direction; Hulu appears to be going this way too.

If you're Farmville, it's harder. But would it really cost Farmville more to have a team rewrite their app in HTML than it would to not support all the people on non-Flash devices that want to play their game and will instead play something else? Perhaps today... 2 years from now, I strongly doubt it. Keep in mind, Apple's devices aren't the only devices that don't have Flash: Flash availability is actually decreasing on the web. And you know Farmville's CEO's non-techy spouse is gonna get an iPad. If Farmville's CTO hasn't already priced out what a move to HTML would cost, they're negligent.
Roasting coffee beans with Python, a bread maker, and a heat gun
Wait, seriously? Coming from PHP you must be working in the web world. You don't strictly indent your HTML and CSS either?
Doesn't build with gcc 4.4.1 as shipped by Ubuntu.
The Japanese government is not unique here. Earmarks and pork are just as big a problem in the United States.
From my experience, going from .NET to Django/Python, the documentation on MSDN was superior.

I hate to say it, but that was what I encountered. The paucity of the documentation on Django is one of my primary irritations with it.

I still strongly recommend checking out Python and Django. Excellent and productive environments.
Think you are right there. The competition somehow get it soo wrong - they need to up their game.
Ggp mentioned battery life explicitly, that's why I addressed that.

I'm probably one of the largest flash haters on the planet, it took me all of 7 years to convert our video to flash, because I simply can't stand it that for basic functionality like that we need a plug-in.

That said, that particular plug in is now so widespread that even people that can't stand it also can't really get around it.

HTML5 is not here yet, flash is here today. So, for live content, where downloading and converting is not possible this move by apple limits their users uses of the web.

The best way imo would be to show side-by-side the same functionality, have a period of cross-over, dual implementation and to deprecate flash.

To simply not support it is not going to convince any developers to make HTML5 content, it's simply going to frustrate a lot of end users.

I just got an angry email from some guy ranting at me that since I won't support the iphone he will no longer be frequenting my site. I sympathize, my budget is limited, both in time as well as in funds so he'll have to go his way.

I don't like it when choices are forced, choices ought to be free. HTML5 video capable deployment still sucks, flash is, as annoying as it is, at this moment in time the only viable way of getting good coverage on the majority of platforms.

Battery life decisions should be up to the user, not up to the manufacturer. If you need or want to see that video and there is no very good technical reason why you can't (and shortening battery life is not a good enough reason, if that were a prime decision factor the display in the iPad would have been a more economical model) then you should simply be able to.