Hacker News new | past | comments | ask | show | jobs | submit | Entlin's comments login

Maybe they're wearing an invisible bicycle helmet.

Think such a thing doesn't exist? Well think again: http://www.hovding.com/en/how/


Wa. That is... incredible!

edit: http://www.cycle-helmets.com/imgs/yehudamoon1.jpg :)


I suppose it's Nintendo only at the author's home, then.


This breaks the back-button for me, despite the author claiming otherwise.

Steps to replicate: 1. Visit article 2. Click on logo to go to the home page 3. Scroll down until more content gets loaded 4. Click back button

Expected behaviour: Get moved back to the article page Encountered behaviour: Still at front page, scrolled to the middle.

Using Safari 5.0.5, OS X 10.6.7


This seems like intended behavior. You back button is not broken. Clicking back brings you back to the previous page... that page just happens to seem to be part of the current page.

For you, it would seem best to remove the previous page content when adding the new content. That way pressing "back" will be super fast, page loading will be fast, and the web will still be happy.


Well then that's bad intended behaviour. The back button should reverse the loading of a new page after clicking a link. It should not interfere with scrolling at all.


Your comments echo many others. I've since changed the behavior to respect traditional back button usage. Hope this helps!


Great job!


It's interesting that there is no mention of BFCache anywhere in this article. This is one of those fantastic features that (although unfortunately not supported in Chrome) allows for very simple infinite scroll and use of the back button.

Unfortunately this guy's script takes it a little too far for browsers that DO support bfcache and unfortunately breaks functionality a bit, or at least makes it confusing, despite it being intended functionality or not.


I noticed that on Chrome in Snow Leopard, too. Guess it needs a little more tweaking!


The difference is of course: with Apple, rooting a device is not an officially sanctioned thing to do. With Google, it is.


There is probably a huge amount of truth to this. Apple puts enough effort into stopping jail breaking that they can easily claim their movie blocking is done through those efforts.


I would suggest that the lack of a Netflix app on WebOS would corroborate this. You only have to enter a short key combination to unlock the phone (put it into dev mode).


Well, democracy is not everything. If the majority of the electorate wants to fight wars, or repress a certain minority, then you've still got a problem there.


What about people outside the US? Before Apple, the FBI couldn't track them. Now that the phones are sending their gps tracks home every 12 hours, they probably can...


Does it use military mode (the one that is even more precise than regular GPS)? Now that would be great reverse engineering project :)

Where was the GPS receiver mounted? These things need view of the sky, no?


I don't know the answer to either of these questions. It appeared to be a standard GPS receiver, but some investigation would reveal whether the manufacturer supports military mode. http://docs.google.com/viewer?a=v&q=cache:7hhk_GsNmTQJ:w...

I never saw it on the car, but the antenna mount had a hinge that would allow it to stick out from the side of the car. But that would be rather conspicuous—I think that's why the antenna is so large.


I often scroll down using space or the pagedown key. This has worked with every webpage I've encountered so far.

While I don't care about the styling, every single linked example on that page doesn't work with space or the pagedown key. I wish there was a bit more polish here...


The linked example, http://maxvoltar.com, works fine for me for the spacebar and pagedown. I'm using Chrome beta build.


It doesn't for me. I have to click on the page first to make them work. OS X 10.6.7 / Safari 5.0.5 here (basically the newest thing you can get from Apple).


"not permitted to publicly link a UDID to a user account"? Really? But that's exactly what Plus+ is doing:

Register in Plus+ game 1, then open Plus+ game 2 and it promptly recognizes your account.

Appalling.


The Apple document reads "publicly associate", which I read as "don't show the UDID under a user profile".

But it also says "Never store user information based solely on the UDID. Always use a combination of UDID and application-specific user ID."


John Siracusa wrote about this very aptly 5 years ago: Avoiding Copland 2010 http://arstechnica.com/staff/fatbits/2005/09/1372.ars

Then he revisited it 10 months in 2010: http://arstechnica.com/apple/news/2010/06/copland-2010-revis...

And then he talked about it 2 weeks ago in the Hypercritical Podcast: http://5by5.tv/hypercritical/14

Abstract: new language and new API go hand in hand. A memory managed combo trades execution speed for faster program creation. Was already needed 5 years ago. The recent garbage collection additions don't cut it. Microsoft started working on their successor (.net) 10 years ago and now it's starting to look good. Apple gained some leeway when the iPhone happened. With ever improving CPUs on mobile devices, Apple still risks losing ground down the line.

Great podcast episode, I highly recommend it.


You could also argue that, given the current success of iOS and Mac, Cocoa isn't a significant hinderance to Apple's platform's success.

(Not to say I wouldn't mind some significant advancements in Apple's preferred runtime, but there's strong evidence that the current runtime is actually quite suitable. If, as you say, .NET is only now starting to look good after a decade's worth of work, perhaps that wasn't the wisest investment on MS's part. Siracusa's been beating this drum for years and, like many of his crusades, I struggle to see how Apple suffers from not following his advice.)


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: