Live data from Hacker News

Viewing profile — workhere-io

workhere-io

HN member
Joined
Fri, May 31, 2013, 12:07 PM UTC
HN karma
1,163
Public activity
371 items

About workhere-io

No profile information was provided.

Recent public activity

  1. comment
    Comment #7865257

    For PostgreSQL: RDS or Heroku Postgres.

  2. comment
    Comment #7832171

    Does this mean that all FastMail accounts are now hosted in Iceland?

  3. comment
  4. comment
    Comment #7819886

    Node's big advantage (some would say disadvantage) is that it uses JavaScript (or languages that compile to JavaScript). There's a good ecosystem around it. However, let's face it,…

  5. comment
    Comment #7809334

    Don't think you are gaining any SEO-benefit from one-page JS-only applications, just because Google made it possible for you to start ranking. No one is expecting to get any SEO be…

  6. comment
    Comment #7808854

    Which I emphasized in the post :)

  7. comment
    Comment #7807109

    If anything but almost all of your website is static, you won't be saving all that much time. Single page apps can easily be static (static HTML page + static JSON). The point of t…

  8. comment
    Comment #7806545

    But, have Yahoo or Bing or DuckDuckGo made the transition to be able to crawl the web with a full JS & DOM rendering engine? They can just use PhantomJS ( http://phantomjs.org/ ), …

  9. comment
    Comment #7806490

    What they were saying before was that you always need a HTML fallback for JS-generated content. Now it seems they're saying you don't necessarily need to.

  10. comment
    Comment #7806447

    For each new page on your site that your user loads, the benefit of single page apps becomes greater: Now she only has to load a bit of JSON, not a full page. So essentially single…

  11. comment
    Comment #7806417

    Author here. Some of you are saying that this will lead to bloated, JS-heavy websites. I disagree. The JS necessary for making a single page app can be done with something like 10 …

  12. comment
    Comment #7806353

    One potential problem here is that google will use this to widen the gap between it and the 'one page apps' web and other search engines (such as duckduckgo) that can't match it in…

  13. comment
    Comment #7806349

    I agree with you; developers definitely have to think about the URLs they're exposing to Googlebot. But this is essentially no different from how things were before. Your example w…

  14. comment
    Comment #7806256

    Those who claims that developpement is easier with framework on a single page have too learn programming, because for most case, the "old" way works very well and is incredibly fas…

  15. comment
    Comment #7806222

    The whole point is to make the experience better for the user: When going to each new page on the site only involves fetching a bit of JSON and not an entire HTML page including he…

  16. comment
    Comment #7806191

    Clientside rendering doesn't need to be heavy at all. In fact, you could do it with just $.getJSON('/api/users', function(data) { $('#users').text(data.content) }. Sure, that requi…

  17. comment
    Comment #7806169

    As I mentioned in the post, all these problems can be solved by using real paths/URLs and changing them dynamically using pushState.

  18. story
  19. story
  20. story
  21. comment
    Comment #7803977

    I see what you mean. However, given the large number of different CMSes, I'm not sure designers would appreciate having to re-learn how to design every time they use a new CMS. Rig…

  22. comment
    Comment #7803411

    Once you leave design and layout to non-designers/non-layouters, they will ruin everything, and you will get angry calls from the companies' designers, complaining about how their …

  23. story
  24. story
  25. comment
    Comment #7792494

    Braintree's checkout process is every bit as easy to implement as Stripe's. However, signing up for Braintree and getting approved takes longer (at least in the EU - I don't know w…