Top all-time · #6049
isolani: weblog
Personal blog · isolani.co.uk/blogwebprogramming
isolani: weblog is a personal blog at isolani.co.uk about web and programming. Since 2009, 13 different Hacker News readers have linked it 24 times, most often “Breaking the Web with hash-bangs”. The last post was in 2015, but the archive is still widely read.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link this weblog's post "Breaking the web with hash-bangs", which argues that #! URLs break how the web works. It was cited when Twitter moved away from hash-bangs.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Breaking the Web with hash-bangs5 people · 5 mentions · first linked 2011-02-08
- Breaking the web with hash-bangs2 people · 2 mentions · first linked 2011-02-09
What Hacker News says?
> It's even more relevant now with all the front end > JavaScript frameworks that so many web apps rely on > these days. Hardly. The number of people who chose to disable JavaScript is utterly dwarfed by the factors that get in the way of JavaScript successfully executing on the page. Very simply: A browser can not execute JavaScript it hasn't received: http://isolani.co.uk/blog/javascript/DisablingJavaScriptAski...…
Comment linking /blog/javascript/DisablingJavaScriptAskingTheWrongQuestion
on “"Disable Javascript" option removed in Firefox 23”Submitted Breaking the web with hash-bangs as a story · 287 points
HN discussionAnd to expand a little on what mbreese said, the basic, fundamental idea behind the URL is for a client to indicate to a server what resource it's trying to access. So it's totally broken by that #!. http://isolani.co.uk/blog/javascript/BreakingTheWebWithHashB... is a great article.
Comment linking /blog/javascript/BreakingTheWebWithHashBangs
on “Twitter to move away from Hashbangs”Submitted Breaking the Web with hash-bangs as a story · 41 points
HN discussion"Bustle actually uses PhantomJS to create static versions of the site, for serving to search spiders." What value dose using PhantomJS offer above what progressive enhancement gives you for free? This feels like a contradiction. Avoiding progressive enhancement, and then bolting on a hack for search spiders in a way that is less robust than the technique you're avoiding. "The advantage of using Ember.js for Bustle i…
Comment linking /blog/javascript/DisablingJavaScriptAskingTheWrongQuestion
on “Progressive Enhancement Is Dead”Submitted Why Atom was created as a story · 41 points
HN discussion"My point is that the percentages of disabled users are often far below what would make financial sense to support" Yet every dollar spent focused on web accessibility further improves the usability of the site for your entire audience too. I rebuilt the Legal & General's online home insurance purchase flow. That resulted in a doubling of the number of people completing an online purchase. http://www.w3.org/WAI/bcas…
Comment linking /presentations/wsg/
on “3% use IE9 and 14% have a disability. Why do we only cater for the former?”Submitted The Web Development Discipline as a story · 20 points
HN discussionIt looks like URL of that article is case-insensitive and page does not specify canonical URL. Both: http://www.isolani.co.uk/blog/javascript/BreakingTheWebWithH... and: http://www.isolani.co.uk/blog/javascript/breakingthewebwithh... render the same content, and <link rel="canonical"> does not exist in source code of that page.
Comment linking /blog/javascript/breakingthewebwithhashbangs
on “Breaking the web with hash-bangs”Submitted IE8 Blacklist: forcing standards rendering opt-in as a story · 17 points
HN discussionA user disabling JavaScript is only one piece of the no-JavaScript puzzle. Here are some more: http://isolani.co.uk/blog/javascript/DisablingJavaScriptAski... "To me it would make more sense to use that time to make the sites usable for visitors with disabilities by including screen reader support and stuff like that." That assumes the choice is mutually exclusive, and also that we live in a world of perfect deliver…
Comment linking /blog/javascript/DisablingJavaScriptAskingTheWrongQuestion
on “Ask HN: Why would you disable JavaScript?”Submitted Url hack for Lifehacker hashbang links as a story · 9 points
HN discussionFirst place I noticed it was "New" Twitter. This article was posted on HN a little while after Gawker changed their design which explains why it was implemented and why it shouldn't have to begin with: http://isolani.co.uk/blog/javascript/BreakingTheWebWithHashB... And it's discussion: http://news.ycombinator.com/item?id=2196160
Comment linking /blog/javascript/BreakingTheWebWithHashBangs/
on “Random defendant outlawyers P2P attorney, gets lawsuit tossed”Submitted Breaking the Web with hash-bangs as a story · 4 points
HN discussionI feel your pain, and I hit my threshold of frustration. Here you go: http://isolani.co.uk/blog/web/UrlHackForLifehackerHashbangLi...
Comment linking /blog/web/UrlHackForLifehackerHashbangLinks
on “How to Jump Ship from GoDaddy to a Better Web Host and Registrar”Submitted Disabling JavaScript: Asking the wrong question as a story · 3 points
HN discussion"If someone doesn't have JavaScript, he's either extremely paranoid (and belongs to a really minor minority) or using hopelessly outdated browser (a minority that most likely wouldn't be a good customer anyway)." With the trend towards mobile devices (as in not chained to a desk) this introduces far more complexity to whether client-side rendering is viable than whether "javascript is turned on in the browser". (Her…
Comment linking /blog/javascript/DisablingJavaScriptAskingTheWrongQuestion
on “On Client Side Templating”Submitted Web App Mistakes: Condemned to repeat as a story · 2 points
HN discussionClient-side templating has its place when used with proper progressive enhancement. That said, if your template rendering is what's bogging your server(s) down, you really need to reevaluate your choice of template engine. The problem with relying on the client to handle templating is one of robustness. JavaScript is an extremely fragile runtime, and one JavaScript error in a piece of third-party ad or widget code c…
Comment linking /blog/javascript/BreakingTheWebWithHashBangs
on “On Client Side Templating”Submitted Sacrificing the Open Web with H.264 as a story · 2 points
HN discussionSubmitted Breaking the web with hash-bangs as a story · 2 points
HN discussionSubmitted Flash's slide into irrelevance as a story · 1 points
HN discussionSubmitted Breaking the Web with hash-bangs (2011) as a story · 1 points
HN discussion
