Sacha Greif

medium.com/@sachagreif · Personal blog · on HN since 2014

Sacha Greif writes on Medium about JavaScript, design, and startups, and runs the State of JavaScript survey.

What HN saysHN cites his State of JS survey results, which one commenter calls valuable despite delays, and his post on the quality of $5 logos.
28HN people shared it
6linked it in comments
30stories submitted
286story points
1 year agolast shared
2014people per year2026

Most-shared posts

  1. 1
  2. 2
    A Study Plan to Cure JavaScript Fatigue
    5 people · 38 points · first shared 2016 · 1 comments on HN
  3. 3
    What Kind of Logo Do You Get for $5?
    4 people · 155 points · first shared 2014 · 81 comments on HN
  4. 4
    The State of JavaScript: JavaScript Flavors
    3 people · 6 points · first shared 2016 · discussion on HN
  5. 5
    Why Crappy Developers Are More Productive
    2 people · 19 points · first shared 2015 · 4 comments on HN
  6. 6
    Marwan’s Story: From Developer to Refugee
    2 people · 4 points · first shared 2017 · discussion on HN
  7. 7
    State of JavaScript (2018)
    2 people · 4 points · first shared 2018 · 1 comments on HN
  8. 8
    The 5 Things You Need to Know to Understand React
    1 people · 12 points · first shared 2017 · discussion on HN
  9. 9
    Monetizing the Unmonetizable
    1 people · 4 points · first shared 2016 · discussion on HN
  10. 10
    I Know Nothing
    1 people · 3 points · first shared 2014 · discussion on HN
  11. 11
    “Life is a marathon, not a sprint”
    1 people · 3 points · first shared 2015 · discussion on HN
  12. 12
    Open Source Lessons Learned: Two Years of Telescope
    1 people · 3 points · first shared 2014 · 1 comments on HN
  13. 13
    Survivorship Bias
    1 people · 3 points · first shared 2015 · discussion on HN
  14. 14
    Push and Pull
    1 people · 3 points · first shared 2014 · discussion on HN
  15. 15
    Diary of a Launch
    1 people · 1 points · first shared 2015 · discussion on HN

What HN people wrote when they linked it

hobofan · 2025-08-08
I think this blog post may provide some insight: https://medium.com/@sachagreif/an-open-letter-to-the-new-owners-of-met… Roughly: Meteor required too much vertical integration on each part of the stack to survive the strongly changing landscape at the time. On top of that, a lot of the teams focus shifted to Apollo (which at least from a commercial point of view seems to have been a good decision).
FLGMwt · 2017-12-13
FWIW, Sacha posted a "sorry for the delay" post a while back: https://medium.com/@sachagreif/the-state-of-js-2017-results-preview-ac… Agreed on wanting it earlier, but the results are still super valuable.
wsc981 · 2014-10-11
Please read "What Kind of Logo Do You Get for $5? [0]" when considering this service. Though prices may differ, I wouldn't be surprised if the end result would be more or less the same. --- [0]: https://medium.com/@sachagreif/in-the-past-couple-years-startups-have-…
sgdesign · 2014-08-12
Relevant: my post about my experiences hiring logo designers on Fiverr from last week: https://medium.com/@sachagreif/in-the-past-couple-years-startups-have-… (HN thread here: https://news.ycombinator.com/item?id=8152631)
dm2 · 2014-08-08
This link from the same site is on the front page of HN today: https://medium.com/@sachagreif/in-the-past-couple-years-startups-have-… It's a decent article and fairly interesting (though not surprising), but the layout is like navigating a minefield, it's still better than the multi-page layouts that are common on some sites. Try to print this article though, 17 pages. 17 pages. Their main business is offering content in a format that is readable and accessible to users. One solution would be to have an alternate layout with normal sized text, no giant header image, and thumbnails rather than half-page images, and that layout preference would be both saved in a cookie and settable via a URL parameter.
catshirt · 2016-12-18
"In fairness, your question hardly reads as a question and much more like a halfhearted sigh from someone who hasn't given it much thought." the connotations are your own. :) the problems with Angular have been beaten to death and i didn't think i needed to include them to foster a conversation. i'm sure i'm not the only one surprised by the graph in the post [0]. even the article that OP links to- "The State of JavaScript: Front-End Frameworks" [1]- would beg the same question. if we take it's research seriously- more people want to learn React. less than half of surveyed Angular users say they would use it again. there is a discrepancy between that survey and Angular's popularity. i think my question is fair. i think dismissing it requires less thought than asking it. in any case, i didn't say that Google's involvement discredits it. quite the opposite really. a lot of people will admit it's the only reason they've taken it seriously. [0] https://cdn-images-1.medium.com/max/800/1*gmYPusm1EjWu713tmVCd8A.png [1] https://medium.com/@sachagreif/the-state-of-javascript-front-end-frame…

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close