Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #1897

M

Meteor Blog

Company blog · blog.meteor.comprogrammingweb

Meteor Blog is the company blog at blog.meteor.com, writing about programming and web. Since 2016, 40 different Hacker News readers have linked it 54 times, most often “A New Chapter for MeteorJS – Acquired by Tiny”. It is still writing: the last post was on 2026-08-24, and you can follow it by feed.

Visit the blog
54mentions?
40HN people?
2016–2026first – last linked?
Links on Hacker News per year · peak 14 in 2017

Too few sampled comments (16) to say how often HN recommends it.?

Why HN links it

HN readers link Meteor's blog for JavaScript closure memory-leak explanations and for framework release announcements such as Meteor 1.6, 1.7, 2.0 and the sale of Meteor to a new owner.

Summarised by Claude from a sample of 16 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Most-linked posts?

  1. A New Chapter for MeteorJS – Acquired by Tiny
    5 people · 5 mentions · first linked 2019-10-02
  2. An interesting kind of JavaScript memory leak
    4 people · 6 mentions · first linked 2017-09-13
  3. Meteor 2.0 Is Here
    4 people · 4 mentions · first linked 2021-01-29
  4. Meteor 1.6 released
    3 people · 3 mentions · first linked 2017-11-02
  5. Meteor 1.9 and New Roadmap
    2 people · 2 mentions · first linked 2020-02-03

What Hacker News says?

  1. wahern · 2017-09-14Recommends
    The fix is to implement the closures properly, by only closing over individual variable slots. It looks like the engines are implementing closures by closing over entire windows of slots--that is, if two functions have the same scope, they inherit the _union_ of the variables they reference as a single window/block of variable slots. The original article has a much simpler explanation and solution: https://blog.mete…

    Comment linking /an-interesting-kind-of-javascript-memory-leak-8b47d2e7f156

    on “How JavaScript works: memory management and common memory leaks”
  2. Submitted Meteor 1.7 and the evergreen dream as a story · 44 points

    HN discussion
  3. Yeah. I thought so too (and still think so). SO post: https://stackoverflow.com/questions/19798803/how-javascript-... Chrome bug report: http://crbug.com/315190 Meteor blog (linked in article): https://blog.meteor.com/an-interesting-kind-of-javascript-me... Live example (will crash due to memory leak): https://s3.amazonaws.com/chromebugs/memory.html --- The reason this exists in all JS engines is for performance; it…

    Comment linking /an-interesting-kind-of-javascript-memory-leak-8b47d2e7f156

    on “How JavaScript works: memory management and common memory leaks”
  4. Submitted Meteor 1.5 as a story · 34 points

    HN discussion
  5. The Meteor framework has been actively developed ever since it was released and continues to have a broad, enthusiastic user base. Mr Goldstein would have known this if he had visited the Meteor blog ( https://blog.meteor.com/ ) and Meteor forums ( https://forums.meteor.com/ ).

    Comment linking /

    on “None of my projects want to be SPAs”
  6. Submitted Meteor 1.9 and New Roadmap as a story · 13 points

    HN discussion
  7. Reminds of Meteor 2.0 https://blog.meteor.com/meteor-2-0-is-here-867b0ab4f8df

    Comment linking /meteor-2-0-is-here-867b0ab4f8df

    on “Blitz.js Now in Beta (Batteries Included Framework Built on Next.js)”
  8. Submitted How to stop Ubuntu Xenial from randomly killing your big processes as a story · 6 points

    HN discussion
  9. Official blog post: https://blog.meteor.com/a-new-chapter-for-meteor-7b684320be4...

    Comment linking /a-new-chapter-for-meteor-7b684320be4c

    on “Tiny Acquires Meteor”
  10. Submitted Meteor in 2017 as a story · 5 points

    HN discussion
  11. React is the heavyweight, no doubt, but it also feels heavy for smaller projects. VUE is a great option and believe it or not Meteor just announced 1.7 with at least one killer feature: Babel-free JS for modern browsers. https://blog.meteor.com/meteor-1-7-and-the-evergreen-dream-a... It's good to see Vue gaining steam as more options = better fit per project.

    Comment linking /meteor-1-7-and-the-evergreen-dream-a8c1270b0901?gi=c82300da60f4

    on “Has Vue passed React yet?”
  12. Submitted Meteor 1.8 erases the debts of 1.7 as a story · 4 points

    HN discussion
  13. It’s still fairly easy to have subtle memory leaks in JavaScript code due to the way closures can keep variables in scope indefinitely. https://blog.meteor.com/an-interesting-kind-of-javascript-me...

    Comment linking /an-interesting-kind-of-javascript-memory-leak-8b47d2e7f156

    on “On Apple's Love Affair with Swift”
  14. Submitted MongoDB queries don’t always return all matching documents (2016) as a story · 3 points

    HN discussion
  15. About the first part of the question, Meteor is still a thing for several reasons: * It's a project with a strong community (364 contributors) that still has traction among developers (+ 8 stars by day on average over the last month, check the numbers here https://bestof.js.org/projects/meteor ) * They keep moving in the right direction: moving away from their own package manager ( https://atmospherejs.com/ ) to NPM…

    Comment linking /announcing-meteor-1-6-abf30f29e2c6

    on “Ask HN: Is Meteor.js still a thing?”
  16. Submitted A New Chapter for MeteorJS – Acquired by Tiny as a story · 3 points

    HN discussion
  17. No. JS engines detect of eval in the AST. It's why you can't rename eval and reference the current scope. const eval2 = eval; (() => { const a = 1; eval2("a"); })(); // ReferenceError: a is not defined --- The reason JS engines choose to share the closure record among all closures create in the function scope is purely for performance. function f() { const a = {}; const b = {}; return [ () => a, () => b, ]; } Both f…

    Comment linking /an-interesting-kind-of-javascript-memory-leak-8b47d2e7f156

    on “JavaScript garbage collection and closures”
  18. Submitted Meteor 2.0 Is Here as a story · 3 points

    HN discussion
  19. Not being that is one thing, but (at least in the past?) they implemented updates as non-atomic delete and insert, which is just crazy bad. It's one thing not to be ACID but having a query not return some entry at all because it's being concurrently updated is... an interesting design choice. Edit: link https://blog.meteor.com/-654b6594a827

    Comment linking /-654b6594a827

    on “Why you should never, ever, ever use MongoDB”
  20. Submitted Meteor Free Tier Is Back - Introducing Meteor Cloud as a story · 3 points

    HN discussion
  21. Some of the criticisms of Meteor are out of date. Last year Meteor added exact code splitting, making it a cutting-edge and industry-leading JavaScript build tool. Also, the criticisms of Meteor as something that doesn't scale are out of touch with the current state of the product. Pre-2017 Meteor had difficulty scaling due to its method of oplog tailing wiht Mongo. But last year Redis-Oplog made that a thing of the…

    Comment linking /modernizing-the-real-estate-industry-with-meteor-an-interview-with-qualia-founder-lucas-hansen-b3b70d2f5dea

    on “Ask HN: Is Meteor.js dead?”
  22. Submitted Meteor 1.9 (Node.js 12) and new Roadmaps as a story · 3 points

    HN discussion
  23. What older version of node? it support Node 8, please get your facts straight https://blog.meteor.com/announcing-meteor-1-6-abf30f29e2c6

    Comment linking /announcing-meteor-1-6-abf30f29e2c6

    on “Ask HN: Is Meteor.js dead?”
  24. Submitted Dynamic imports in Meteor 1.5 as a story · 3 points

    HN discussion
  25. It's a live and kicking :) You'd think majority people of at HH can do basic objective research and look beyond the FUD, but it seems not. Well, let me give you some facts, over the last two years Meteor added support for: - Out of the box dynamic import https://blog.meteor.com/dynamic-imports-in-meteor-1-5-c61304... - Importing NPM packages - React, Vue, and Angular as view layers - Latest release of Node JS: https…

    Comment linking /teaching-software-engineering-with-meteor-lessons-learned-after-three-years-793d8a16077

    on “Ask HN: Is Meteor.js dead?”
  26. Submitted Use GraphQL to load from any database in your Meteor app as a story · 3 points

    HN discussion
  27. > The browsers struggled with this for years. Arguably, they still do. function f() { var some = []; while(some.length < 1e6) { some.push(some.length); } function g() { some; } return function() {}; } var a = []; var interval = setInterval(function() { var len = a.push(f()); if(len >= 500) { clearInterval(interval); } }, 10); uses a very large amount of memory in all browsers. function f() { var some = []; while(som…

    Comment linking /an-interesting-kind-of-javascript-memory-leak-8b47d2e7f156

    on “Mjs – An interpreter for ECMAScript 1st edition written in C++17”
  28. Submitted How to use GraphQL with Meteor as a story · 3 points

    HN discussion
  29. > With most of the original Meteor Development Group team having moved on to Apollo GraphQL, it’s time to pass the torch to a new corporate sponsor that will make the promotion and growth of Meteor their full-time business. https://blog.meteor.com/a-new-chapter-for-meteor-7b684320be4... Meteor got sold to Canadian company TinyCapital (Dribbble, WeWorkRemotely), so it's under new leadership/management.

    Comment linking /a-new-chapter-for-meteor-7b684320be4c

    on “MeteorJS Releases v2.0”
  30. Submitted Meteor 2.0 Is Here as a story · 2 points

    HN discussion

Search all of HN for blog.meteor.com

Linked by the same people?