Hacker Newsnew | past | comments | ask | show | jobs | submit | jolt's commentslogin

I love YouTube. I use it daily. I have some grief with the interface though. It seems like it doesn't want to be a webpage. So much of it feels custom-made as opposed to browser based. Navigation, scrolling, and image loading breaks for me all the time regardless of browser. So for me it feels risky to adopt their interface implementation.

I realize that YouTube is a crazy hard problem to tackle, and that is probably why stuff like this is necessary.


This reminds me of when i was learning to drive. In the beginning I was only aware of what was immediately in front of the car, and as such, drove very slow and had pay extra attention because a lot of important stuff was coming in to my field of view all the time.

Now, when i drive i look further down the road, i plan out how to follow the road, i see the intersection coming up, and try to anticipate the routes of the other cars/bikes and that requires far less energy, than only processing the immediate surroundings.


Well, all the sensory overload you experienced as a novice driver has become background noise that is handled subconsciously now. That lets you focus on more strategic planning of your driving. That's one reason I like countries that mandate a learner sign in cars for new drivers. It lets others around them understand that they are still getting to grips with that sensory overload and allows them to act accordingly.


I see, is there an equivalent for robots? Like putting part of the algorithm in to hardware or something? Or is my "algorithm" still "there", I'm just not as aware that I'm following it?


I'd say it's still there, it's just running on a background thread. :)


If only more people drove like you and knew who was behind and on the side of them accidents would happen at half the rate.


I was thinking exactly the same thing. I'm always amazed at how many times a lyft or uber driver does not see a "situation" a little further down the road, resulting in the need to swerve to avoid it versus changing lane early to avoid the last second reaction.

I've noticed it in cases where I'm a passenger in a friends car also, but I've always chalked that up to the conversation being a distraction.


Another reason for keeping the commented-out-code, could be if reverting to a previous version of the code is more work, than checking in a new version. Or when the old commented-out-code is used as an explanation as to why the current code looks as it does.


A great idea. And very well executed! One thing though, for some reason emails from the same list does not group together in my Outlook 2013, like "RE:" and "FW:" mails do. (In other words: The "Show as Conversations"-option doesn't seem to work on emails from Planleaf)


Is it only on Mac it shows the actual status codes on the network tab? On Windows i have to hover the little icon in the first column, which is really annoying when I'm trying to figure out if my caching is working correctly.


Sounds like your windows copy of firefox might be the main release channel. The numeric status codes have been in since 30 (currently Beta). You can hop on Aurora (or Beta, or Nightly, but Aurora is generally best for web devs), or just wait about 6 weeks for the next uplift.

https://bugzilla.mozilla.org/show_bug.cgi?id=972054


Is there an Ubuntu repo for Aurora that I'm missing or do I need to use the tarball.



I see. Thank you!


That is an excellent idea! Make it cross platform, and able to install missing tools, combine it with speech to text and you would be able to talk to any device regardless of the software installed on the device.

    please open presentation X from my dropbox


A way to do this could be to use a kind of proxy address. That way you would not have to convince every postal service to adopt some new system. The problem with that, of cause, is that it most likely would take you mail much longer to arrive, and you have another 3rd party (4th party?) service provider involved to potentially make mistakes and compromise security.


Its easy when you are just dealing with "text elements" of equal size. But if you are loading images or injecting content in the list elements, the back-button starts to break.


Why is this so hard that even Google can't get it right? If a page has little to no other content than the content in the list, why is it worth the hassle?


Nice! Another idea would be to use events in stead of keys in the sequence, something like:

"click:#elem1 click:#elem2 keyup:13"

That would enable you to make slightly more advanced easter eggs or "cheets"


I went ahead and made this[1]. The implementation is a little different from the way you do it, and it uses jQuery to create the events, but it supports sequences of click events using jQuery selectors like in my original comment, other events could be added without much effort.

The implementation is not at all as neat as the original, and i haven't done thorough testing, i just had an idea and tried it out.

[1] https://github.com/jonlt/cheet.js


Good idea; I'd incorporate your changes but I'm trying to keep it dependency-free, for now.

I could support '#id' without any dependencies pretty easily, though...


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

Search: