skysight-inc/HackerNews huggingface dataset:
I'm starting to think there must be 2 products on the market right now called the 'Amazon Kindle Fire' - this very enjoyable one I picked up and this other one that all these blog posts are complaining about.
Yeah, I was wondering what the hell the OP was referring to when it was claimed that web frameworks are stuck in the 90s. We use wicket both for our customer-facing sites, and most of our various departmental administration sites. It's a great, modern, component-oriented framework that doesn't have any XML hell.

My default reaction to HN hipster kiddos eschewing Java for web development based on hearsay/generational bias/fashion is to roll my eyes and simply not post, but in this case I'm glad to see there's at least someone else on this site that experiences the virtues of Wicket.
As being the same round with Rich, I couldn't be agreed more with him.
Replace every site on the internet with a page that says this site is unauthorized by the authority of a few people, nevermind who or you will be tazed.
I wonder if Amazon will do a trade-in program when the Kindle Fire 2 comes out for unhappy Fire owners. It's just the kind of crazy customer experience turn-around I could see Amazon doing.
+1 to Fastmail.fm (acquired by Opera a bit ago). Been happy with their IMAP/SMTP services as well as their web UX which keeps getting better.
The Facebook Platform Is A Trainwreck
There is none. No one is suggesting that. Bootstrap and Foundation aren't the be all end all either though. The reason there are so many frameworks out there is because of the myriad of ways people work. This is just one more. Most people won't want to use it but if just one person picks it up and makes it their own then it was worth it.
NO! No, no, no, a thousand times, no.

I spend all day every day troubleshooting broken things. Human readable logs are the very last thing that I have left that leaves me with any energy to keep troubleshooting things. If you take that away from me too, I swear I'm going to shoot somebody. (If I have any sense left when I go 'round the bend, I'll target a software engineer that thought it would be a good idea to fix what wasn't broke.)

Here's the thing: I can do anything with a human readable text log. I can scan it visually and look for anomalies; I can use my favorite text editor with it; I can grep it; I can cobble together some magic incantation on a command line to munge it to death until it cries out in mercy and gives me exactly what I'm looking for.

If I have to use somebody's special web-based woo-widget to view and search the contents of a log, if I'm restricted to the limits of their imagination when it comes to trying to get useful information out of the log, if I have to debug their dumbass invention while somebody's time-critical server is flopping around on the floor before I can even begin to figure out what in the heck is actually wrong with the server, I'm going to be stupid not to give up completely on support.

If you want to log information which is useful to you, you can do that without hardly any trouble at all without replacing perfectly good, reliable logging facilities which are the way they are for damned good reasons. Just write a Ruby whatchamacallit or a Python thingamajig or a PHP flibbedyfloo and log it to your MySQL database or your Postgres database or your no-sql nuh-uh-it's-not-a-database. I don't care.

But if I ever open up a server log and get blasted by a jillion lines of JSON that make it a thousand times harder for me to figure out how something broke I'm going to go on a shooting spree.
Ask HN: Has anyone deployed akka and redis based application on GoogleAppEngine?
Has anyone successfully deployed akka and redis based application on GoogleAppEngine? Is akka and redis are compatible with GAE?
Video: Android 4.0 Hacked Onto The Kindle Fire
This video is RIPPED from the computer museum site without credit.
Note that when these Anonymous clowns make charitable contributions with stolen credit card information, the net result is a loss for the charities. They will have to give the money back, and will also be hit by chargeback fees. They might also have their risk reassessed by the card companies and have their reserve amount increased.
Thanks so much for your input! A lot of your ideas are close to either things that are planned for the future or ideas that I have discussed with friends.

Badges, for instance, are something that I'm definitely going to implement. And although I think goal-achievement is important, it appears to me that it shouldn't be the only "metric".

For instance, I thought that it would be nice to let a user's friend verify if the picture posted is really compromising, and if it is, award a badge to the user.

Another feature that is definitely coming and that I think will improve "virality" (and that is also similar to something you mentioned) is the ability to set goals (and "bombs") for your friends. Of course they would depend on the friend's approval, but it would be a way to spread the word.

Oh, and honestly I don't think that failed goals are bad marketing. As I see it (and said earlier), I think that fun is our product, not productivity.
Accessibility is often ignored by website designer. That's very unfortunate.
Two reasons:

Easily read by human *and* by machine;

Highly compressible since it's full of repeating strings.

My Apache logs compress by about 94%. Chances are good that you wouldn't find much of a size difference between gzipped JSON and gzipped BSON (though parsing BSON would be faster).
It is simply amazing that something that is clearly a bug would be marked as WontFix without so much as a explanation of why.
Pretty spot on.

GoDaddy already has a bad reputation, and they're way easier to stop using than, say, the NFL or ESPN (for most people).

Also, GoDaddy is an internet company, supporting internet oppression. It's kind of like they're trying to throw their own family under the bus.
because GoDaddy's product was a commodity, there is absolutely nothing that differentiated it from the rest.

Meanwhile other companies offer unique products(or at least those that differ from their competitors)...so it's harder to give up things like that.

+ it's an internet company, so knee capping them will take off valuable support
Can't say i find myself very impressed: http://dl.dropbox.com/u/10190786/fractionless.png
Can anyone point me to a relatively easy walkthrough on transferring my domains away from GoDaddy (to namecheap, I guess)?
There are plenty of things that are wrong with Google App Engine. And there are plenty of bugs that exist that have cost me money.

Why don't you try filing a bug report/suggesting a warning and send an email requesting something of a refund. They tend to be a friendly bunch who give refunds to obvious problems.

Moving to AWS will of course save you lots of money in the longer term, depending on what your hosting requirements are.
Can't we get all this GoDaddy hysteria off of HN? Isn't there a /r/sopa this can go to instead?

I don't think this site was supposed to be about the latest breaking he-said/she-said drama - even if it is of marginal interest to hackers.
First off, welcome to Hacker News. Since you're probably wondering why you got downvoted, here's a quick crash course on how this site works:

Unlike a lot of communities you might have visited, Hacker News tries very hard to keep the debate intelligent and civil, which requires a lot of self-policing. Your comment was a little more brusque than most people here prefer. Here are a few tips:

• Please make your points politely. You don't have to tiptoe around with your pinky out, but just try not to be rude. Saying things like "First of all, get your facts straight, Android troll" and "Get off Android's nuts" will get you downvoted even if everything you say is correct. (I didn't downvote you, by the way — we can't downvote responses to our own comments, for fairly obvious reasons.)

• If something seems ridiculous, give it a second look and try to find a way that it might make sense. For example, in this particular instance, the first sentence of my comment was a pretty transparent joke. I expected anyone reading a nerdy site like Hacker News to realize that nothing in that sentence was true. The second half of the comment dropped the joke and stated my point directly: A good reputation can pay huge dividends.

• If I had in fact been trolling, this kind of angry response would be precisely the wrong thing to do. Please don't continue unproductive conversations — if you suspect someone is trolling, just leave it be. In fact, even if they're not trolling but just stubbornly wrong, leave it be. Let that thread die. Accept that sometimes people are wrong on the Internet. Fanning the flames will only drag the signal-to-noise ratio even lower than it already is.
Why Can't We Put a BASIC On the Phone?
Telecomix's efforts at anti-censorship and surveillance
Wonder why they didn't mention that in the blog post?
shareholder investment window is up to the shareholders. if shareholders push for short term profits at the expense of long term stability that is FINE. In a healthy market they get eaten. We have an unhealthy market where some get to maximize short term profit and then go crying to mommy when the consequences roll in.
We're back! Sorry for the downtime!
Having just received one for Christmas I too find the Kindle Fire quite enjoyable. Yes it could use some polishing, could possibly be the fact that it's running an older version of Android.
More debunking of Fingleton:

http://www.bloomberg.com/news/2011-12-26/women-beating-men-t...
They did this with EVERYTHING. The costs of manufacturing are roughly 1/3rd labor, 1/3rd raw materials, and 1/3rd power. China subsidizes power and raw materials (through various means). If it weren't for that, Chinese stuff would be about 70% the cost of US stuff (assuming 10% the wages, equal productivity, and the same material and labor costs).

Subsidizing stationary inputs (like roads, power, and pollution sinks) or stuff that's expensive to move (steel, coal, trained workers) is a way to force a country to industrialize. Subsidizing easily exported inputs (like rare earths) is less effective, as it just ends up in your competitors' final products.
Prohibiting voluntary victimless activities of the physical kind didn't even work very well in the 20th century. The technological kind in the 21st century? Downright impossible. It just moves outside your borders - and outside your ability to tax. Unless I'm ignorant of some industry-specific facts I think this would be a win-win for everybody (except, as always, the poor souls that willingly throw their money away...)

Edit: Good point by cellis below. Still, I think legalizing activities via connected interests is progress compared to fake illegalizing that exists currently.
please point to an actual historical example of this. the frictional costs never wind up being anywhere near as high as the pro-regulation crowd harp.
Wow! You really managed to help me see my problem much clearer!

I'll definitely spend some time trying to come out with mechanisms to achieve these 3 goals.

I think I can actually focus on the last two, since you need to register to vote (that's how we keep track of who already voted).

Thank you very much! I cannot even begin to tell you how much this "methodical" approach helped me to see my problems clearer!
8 Incredible Technologies used by the IDF
Not to mention treatment description apparently impacts efficacy. Here are two articles talking about this problem:

http://www.radiolab.org/2007/may/17/
http://www.wired.com/medtech/drugs/magazine/17-09/ff_placebo...
>Here's the thing: I can do anything with a human
>readable text log. I can scan it visually and look for
>anomalies; I can use my favorite text editor with it; I
>can grep it; I can cobble together some magic
>incantation on a command line to munge it to death
>until it cries out in mercy and gives me exactly what I'm looking for.

That's basically why the article is proposing using JSON: it's easily readable/scannable by a human, can be easily opened in a text editor, isn't all garbagy like XML, has near perfect support in every scripting language and is rumored to be Christ 2.0.

>But if I ever open up a server log and get blasted by a jillion
>lines of JSON that make it a thousand times harder for me to figure
>out how something broke I'm going to go on a shooting spree.

Are these really that different?:

>host.com:80 w.x.y.z - - [25/Dec/2011:06:07:42 -0600] "POST /page/open HTTP/1.1"
>200 1200 "-" "Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20100101 Firefox/8.0"

>{'host':'host.com', 'timestamp':'2011-12-25 06:07:42', 'method': 'POST',
>'path':'/page/open', 'protocol':'HTTP 1/1", 'response_code':200,
>'content_length':1200, 'user_agent': 'Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20100101 Firefox/8.0'}

There's a bit of extra verbiage, but the JSON version is perfectly extensible and would allow the devs to add additional debugging information to help you find issues. That said, I can see the downside to letting devs insert random crap, because you could get reams of garbage in the logs. As example of possibly helpful info it'd be easy to add db and app times:

>{'host':'host.com', 'timestamp':'2011-12-25 06:07:42', 'method': 'POST', 'path':'/page/open',
>'db_time':0.157, 'app_time':0.43, 'protocol':'HTTP 1/1", 'response_code':200,
>'content_length':1200, 'user_agent': 'Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20100101 Firefox/8.0'}
Web apps generally need to be accessible on port 80, and only a single service can claim an IP address and port combination. If web apps were distributed as services, each one would need to run on a unique IP/port combination. In order for outside users to access those apps through the default HTTP or HTTPS ports (80 and 443, respectively), you would still need to be running at least a reverse proxy server that could remap incoming traffic to the correct internal port. On top of that, your web app would have to include an FPM or UWSGI service, increasing the size of the distributed binary.

Frankly, it's much easier just to leave that aspect of things to the server admin, and distribute your web app as a PHAR or Egg or Gem or whatever.
I believe that their has been an update to the Fire that seems to have alleviated most of this guys problems.

The kindle that I received for Christmas has been a joy to use :)
"I tell her it’s less than half the price of an iPad, but the software will be almost as polished because it’s made by Amazon."

LOL. Because Amazon are known for quality consumer software, right?
It would help if you continue the very sentence:

After decades of global competition and collaboration, many solar markets around the world have reached grid parity—the point at which generating solar electricity, without subsidies, costs less than the electricity purchased from the grid.

No?
>>Migrated stored user passwords to a safer format (from salted sha1 to bcrypt).

I'm curious on how to do that? I'm guessing you add another field and wait for the user to log in and if it matches, you salt and hash the new password field with the new function.
Web search engines work
Fix your damn documentation, developers
tl;dr

his mom didn't like the kindle fire and over the holidays complained to him about it.
Well, all the kindles before the fire were pretty damn polished.
https://www.youtube.com/watch?feature=player_detailpage&...
Should Google refund developers when they make an uninformed decision that costs them money?

One could argue it is a bug in GAE that allows developers to make an expensive mistake when they don't fully understand how something (fairly complicated) works.

Someone else could argue that we are all developers and we should know the costs associated with the systems we are building. There is a real cost associated with PaaS systems like GAE.

What do you think?
Yeah, but I'm probably just used to it and since I was referring to BREAD, it kind of made sense. I guess it's one of those age old questions like "do we say 'your' or 'my'?".
Looks good. I'm noticing it uses highcharts, so there may be licensing costs under some scenarios, correct?
Funny that anybody can think there is a first mover advantage in this market when tablets have been shipping and failing for about 30 years now, the idea itself is over 50 years old, and some directly related patents are over 100 years old!

The secret to Apple's success is obviously their zen-like patience and restraint.

http://en.wikipedia.org/wiki/History_of_tablet_computers
Many of his main points are vacuous at best. "Adding insult to injury, it’s an extremely simple and ugly unlock-gesture, just the sweep of a mono-color bar from right to left." Since when is a function being simple a problem? And he's comparing it to a Windows phone, where the entire interface is based on "mono-color" tiles.

The Fire is a $200 tablet, and aside from a misplaced On/Off button (not sure how that got passed QA), the hardware you get for $200 is incredible. The software could use some work, there's no doubt about that. But here's the thing:

They can improve the software.

I don't love my Fire, but you can hardly say it is "downright terrible", especially when you consider the price tag.
The reason I've been more spurred to action over GoDaddy's involvement is twofold:

1) I'm not surprised that the record labels and movie publishers want this law. I am very surprised that a technology company who should be impacted by this law (but aren't, because of a special exemption) would support it, and it shows irresponsibility at best. At worst, they want to use it to stifle competitors. GoDaddy, as a technology company, has more reputation on technological matters to Congress, and is therefore in a position of severe abdication of responsibility. They aren't just a dying industry trying to legislate their survival - they're a traitor from "our" industry who have sided with the Bad Guys.

2) There are a lot of very easy-to-use alternatives to GoDaddy. I can't very easily just pick up and stop using Visa and Mastercard - I'm dismayed that they appear on the supporters list (and frankly, I'm a bit surprised; it increases costs and decreases revenues for them. Feels like they're being squeezed), but there aren't easy alternatives. To be clear, I'm not talking about credit cards here - I'm talking about my debit card, for which Mastercard is the processor. Carrying cash around is both risky and impractical in many cases, and I still have to do business online somehow. Compared to those, I can easily just pick up and leave GoDaddy and never do business with them again.

I wish that I could easily boycott every company involved in supporting SOPA. Many of them can't be as cut out as easily as GoDaddy can, but I'm happy to start with the low-hanging fruit and work up from there.

I was a GoDaddy customer for a very long time - back when they had decent geek cred (yes, that was a very long time ago). They've always provided good customer service to me, personally. The sexist ads were distasteful, but didn't bother me enough to cost them my business - sex sells, and it always has. Bob Parsons shooting an elephant was likewise distasteful, but that's Bob Parsons being a guy that I don't want to have over for dinner, not GoDaddy launching an initiative to hunt elephants to extinction. However, GoDaddy's support of SOPA, as a company is GoDaddy being an entity that I don't want to be involved with, and don't want to lend any financial means to. That's why I left. I wasn't looking for an excuse to leave, and frankly, it's financially costly and a pain in the ass to move a bunch of domains, but I couldn't ignore it, given the reasons enumerated above.
Yeah, I think a lot of people miss the anti-counterfeiting part of this bill in the noise about the dumber parts of it.

Petzl, the climbing gear manufacturer, showed up on the lists and released a statement clarifying their support.

http://www.petzl.com/us/outdoor/news-2/2011/12/22/petzl-amer...
Call me hopeless newbie, but I really haven't thought about people who may not sign up right on their first visit, but may do so later - and a way to "track" them.

I think the social buttons you've mentioned are good for this too - if people tweet/share and get feedback, they may be more likely to come back to the site.

I'm not happy with Addthis, the social solution I'm using. I chose them for analytics, but I'm starting to feel that sticking with the default buttons might generate more engagement.

I really have to put more thought & effort on social. Thanks for reminding me of that!
This falls under "good intention, but not well planned out" IMO. Single line logs are MUCH easier to process with text-oriented tools, which is why they've stuck around for so long.

This solves the encoding problem, but not the "how do I read/search it" problem, which is kicked down the line to other tools. And having a different format for every daemon is just a new problem.

I'd look at how others have dealt with the problem - for example, Logstash, which is a log parsing and movement engine:

http://logstash.net/docs/1.0.17/learn

Also, timestamps aren't recommended for storing time data - they're not human readable, and convey less information than something like ISO8601 which covers more edge cases.
> ...isn't all garbagy like XML...

I don't think it's fair to take something that isn't garbagy at all and then say that the proposed alternative isn't bad because it's not as garbagy as one of the garbagiest things ever invented. :-)

JSON may not be as garbagy as XML, but it's still garbagy. With logs in their current format, often my very first tool in log analysis is the scroll wheel on my mouse. It's so lovely because all the lines are unbroken, the columns line up so neatly, and the data in the columns are so distinct from each-other. JSON dicks all that up.

Now, OK, I'll admit it wouldn't be very hard for me to whip up something that will take a JSON-formatted log and turn it into something I actually want to read. And in fact that's exactly what I'd end up doing.

But, logs are already getting big enough that some companies are doing very stupid things to them. (Bluehost, by default, logs only the last 24 hours for all hosted sites; if you turn on their "extended" logs feature, their logs still have huge gaps in them.) JSON makes that problem a lot worse for those companies. And, if their log rotation isn't set up correctly -- and if they're doing vhosting I'll bet you a donut it's not -- then what would have been a silly amount of data to process now becomes nearly impossible to process.
Beginners Guide Pip and Virtualenv
Custom-Made Stairlifts for Your Building
DAY distributes a range of different stairlift models to match any staircase model and provide safe floor-to-floor transportation.
How can Scala be state of the art when it is so bad. They probably meant to say newest, in which case I nominate Dart to take Scala's place.
Think about it like this: Verisign manages the .COM registry, a database of domain names, what registrar controls that domain, their expiration date of the domain and its DNS servers.

Verisign makes available a few very simple operations that registries can invoke on this database in exchange for specific payments:

* Add X years to expiration date ($fee times X)

* Change registrar of domain and add 1 year to expiration ($fee)

* Change DNS servers of domain (free)

You paid GoDaddy to invoke the first operation, GoDaddy paid Verisign the fee, and the change was made in the database.

You are now going to pay some other registrar to invoke the second operation, they will pay Verisign the fee, and the change will be made in the database.

Your payment to GoDaddy was for a single thing (make this update to the database) and they already did it. There was not going to be any ongoing activity on subsequent years, there's no reason for any payment to move to anyone else.
It's bad for developers when a substantial proportion of handsets are running older versions, which slows down adoption of newer APIs.
Yo, dawg, I herd you like BASIC, so we put BASIC on your phone and now can write in BASIC while you read your SMS