3 ms·

Good. A lot of developers justified doing it in their own projects because Twitter and Gawker were doing it. Now that one of the headline sites is no longer usi

by nikcub 15y ago

Good. A lot of developers justified doing it in their own projects because Twitter and Gawker were doing it. Now that one of the headline sites is no longer using it (and will hopefully condem it) we can file this episode to history and never speak of it again. Edit: wouldn't it be awesome if Google (they did start this, afterall) would allow sites using hashbangs to auto-update all indexed URls

simonw 15y ago
Do you know how long ago Gawker dropped them?
- nikcub 15y ago
  ~6 months ago IIRC they constantly had problems with their redesign and the last update involved removing the hashbangs
  - ianvanness 15y ago
    This sounds about right, if not a little earlier. Experimental work for this was done by me here: https://github.com/ianvanness/html5history https://github.com/ianvanness/html5history I believe there were further tweaks for additional pages that needed to be supported (whereas I had only solved, and most likely not very elegantly, the rudimentary issue) that took additional time before the hash bang removal was actually launched.
    - nikcub 15y ago
      Thanks - I was estimating off the top of my head - the site was in flux for a while at the time. They also went back and forward with keeping the story sidebar at fixed positioning and it seems they settled on it not floating. I check the site every couple of weeks because I was interested in how the redesign would work out. It seems they eventually got it right, I like it. A lot of the other blogs have home and article pages that are just too heavy and slow.
deleted 15y ago
[deleted]
marknutter 15y ago
hash bangs and push state are essential for creating single page apps.
AlexBucataru 15y ago
Hashbangs for state representation are just a tool, which can be used to make things better or worse for the users. Where content is the main purpose ("websites"), they are overkill at best. They can be useful though in functionality-first applications ("apps"), where the interface can be costly to build (too slow if you reload the whole "page" on each state change). Ideally, the app differentiates between fundamental states, represented in URLs, and transient states, represented in hashbangs. Anyway, this is good news for Twitter, if they are really going through with it.
- RegEx 15y ago
  I believe the best implementation of this patten comes from the trance.fm website. Trance.fm gets that people come to listen to their online radio, so avoiding a page refresh is priority #1. It's very quick and responsive, too. You can listen to the music as a non-member, become a member and rate the song you're listening to, all without the music stopping. I believe it makes for a really good experience.
kragen 15y ago
I'm particularly happy about this because I spent a bunch of time yesterday trying to get any of the current lightweight web browsers (Dillo and Links2; I couldn't get Arachne not to crash at startup, and I couldn't find the source to hv3) to log into either twitter.com or mobile.twitter.com, with no success at all. m.facebook.com worked, more or less, but no love from Twitter. Apparently you can't log into Twitter without 64MiB of RAM, which is what Midori uses. Dillo and Links2 use 6MiB. Hopefully this means they're switching to a more normal HTML interface and will become a web site instead of a DHTML application again.

by nikcub 15y ago

simonw 15y ago

Do you know how long ago Gawker dropped them?

nikcub 15y ago
~6 months ago IIRC they constantly had problems with their redesign and the last update involved removing the hashbangs
- ianvanness 15y ago
  This sounds about right, if not a little earlier. Experimental work for this was done by me here: https://github.com/ianvanness/html5history https://github.com/ianvanness/html5history I believe there were further tweaks for additional pages that needed to be supported (whereas I had only solved, and most likely not very elegantly, the rudimentary issue) that took additional time before the hash bang removal was actually launched.
  - nikcub 15y ago
    Thanks - I was estimating off the top of my head - the site was in flux for a while at the time. They also went back and forward with keeping the story sidebar at fixed positioning and it seems they settled on it not floating. I check the site every couple of weeks because I was interested in how the redesign would work out. It seems they eventually got it right, I like it. A lot of the other blogs have home and article pages that are just too heavy and slow.

deleted 15y ago

[deleted]

marknutter 15y ago

hash bangs and push state are essential for creating single page apps.

AlexBucataru 15y ago

Hashbangs for state representation are just a tool, which can be used to make things better or worse for the users. Where content is the main purpose ("websites"), they are overkill at best. They can be useful though in functionality-first applications ("apps"), where the interface can be costly to build (too slow if you reload the whole "page" on each state change). Ideally, the app differentiates between fundamental states, represented in URLs, and transient states, represented in hashbangs. Anyway, this is good news for Twitter, if they are really going through with it.

RegEx 15y ago
I believe the best implementation of this patten comes from the trance.fm website. Trance.fm gets that people come to listen to their online radio, so avoiding a page refresh is priority #1. It's very quick and responsive, too. You can listen to the music as a non-member, become a member and rate the song you're listening to, all without the music stopping. I believe it makes for a really good experience.

kragen 15y ago

I'm particularly happy about this because I spent a bunch of time yesterday trying to get any of the current lightweight web browsers (Dillo and Links2; I couldn't get Arachne not to crash at startup, and I couldn't find the source to hv3) to log into either twitter.com or mobile.twitter.com, with no success at all. m.facebook.com worked, more or less, but no love from Twitter. Apparently you can't log into Twitter without 64MiB of RAM, which is what Midori uses. Dillo and Links2 use 6MiB. Hopefully this means they're switching to a more normal HTML interface and will become a web site instead of a DHTML application again.