glasser

7 ms·

1.
by glasser 8y ago
The incomplete items that this update is about are an extra set of keycaps that I honestly can't even find where on the Kickstarter we were promised them. The main product successfully shipped long ago.
2.
by glasser 8y ago
And they all are speaking at the GraphQL Summit today and tomorrow in SF!
3.
by glasser 8y ago
Darcs was easy to use? Are you referring to the same darcs whose manual tried to explain concepts by making analogies to the simpler and better-understood theory of quantum mechanics?
4.
by glasser 9y ago
Is the "import compatibility rule" (ie, `/v2` suffixes in package paths) implemented in vgo today?
5.
by glasser 9y ago
Yup: https://guide.meteor.com/security.html#allow-deny I just submitted a PR to the main Meteor docs pointing there: https://github.com/meteor/docs/pull/164
6.
How to stop Ubuntu Xenial from randomly killing your big processes(blog.meteor.com)
6 points by glasser 10y ago|0 comments
7.
by glasser 10y ago
Don't worry — you can find that code at https://github.com/chrislgarry/Apollo-11
8.
by glasser 10y ago
My goal in writing this post was not to convince people to use or not use MongoDB, but to document an edge case that may affect people who happen to use it for whatever reason, which as far as I could tell was inadequately documented elsewh
9.
by glasser 10y ago
If I understand correctly, this method says "only scan the built in _id index, not any other index". Which means that you will not hit this index-specific bad behavior, but also that you won't get the performance characteris
10.
by glasser 10y ago
This is not related to reading from secondaries. This issue can occur in single node systems.
11.
by glasser 12y ago
Oh, wow. This looks like a really easy way to get a "turn on lights slow then play music" alarm... and some dance party blinky lights... and whatever else I bother to program!
12.
by glasser 13y ago
Threadable is like Google Groups, except that whether or not the default reply-to is "all" is a user preference rather than a group preference, which made me so happy. (There are other features too, which I entirely ignore without
13.
by glasser 13y ago
Exactly. Doing that by mistake (and then being taught to set `push.default` to upstream or simple) has been a rite of passage for engineers at my company.
14.
by glasser 13y ago
Yep, as Arunoda says I'm actively working on it right now, currently hoping for an initial release this month. I really appreciate the work Arunoda has done on smart collections; my implementation and his package have both learned from
15.
by glasser 13y ago
I'm not sure what your problem with contributor agreements are; basically every sizable open source project has one. You know, like... Node: http://nodejs.org/cla.html
16.
by glasser 13y ago
Our understanding of the current level of browser support is actually in a big comment at the beginning of every file aimed at the browser we generate that has a source map :) If you are using Chrome, open the Developer Tools and clic
17.
by glasser 13y ago
That post predates `npm shrinkwrap`.
18.
by glasser 13y ago
Cool! A major reason I made this post was because I assumed that this must be something people had seen before, but I had trouble finding any references to it in the JavaScript context. I'll add a link to http://flint.cs.yal
19.
by glasser 13y ago
Yes, but you can statically determine whether or not eval is called. A world-class JavaScript environment like V8 is far past "the simplest thing that is correct according to the spec". In fact, the JavaScript spec doesn't ac
20.
by glasser 13y ago
Looks like Go optimizes this fully, as pointed out by https://twitter.com/nynexrepublic/status/350717895971586049 If you run these on your own machine and peek at the RSIZE, it stays constant (well, the first grow
21.
by glasser 13y ago
OP here. Several people have pointed out that of course I should expect a leak, since each `logIt` object is leaked. That's absolutely true; my point was just that we don't want `str` to leak. But the original bug that led to this
22.
by glasser 13y ago
No, actually, you literally have to call eval as a function called eval if you want to get the local lexicals. See sections 10.4.2 and 15.1.2.1.1 of the ECMAScript standard, or try it out: > (function () { var x = 5; eval("con
23.
by glasser 13y ago
Right, but according to sections 10.4.2 and 15.1.2.1.1 of the ECMAScript standard, you only get lexical bindings inside your `eval` if it's literally a call to a thing called `eval`. (Which I believe is what you meant by "direct `
24.
The Ardent Mobile Cloud Platform(kickstarter.com)
20 points by glasser 13y ago|2 comments
25.
by glasser 13y ago
I don't know how to look at memory usage in other modern JS interpreters like those used in FireFox and Safari. Anyone able to check to see if they have this problem? (And if they manage to avoid the memory leaks in the first two code
26.
by glasser 13y ago
To be clear: when you say "removing the call to doSomethingWithStr() doesn't change the unbounded memory growth" you do literally mean "removing the call" and not "removing the function definition", right?
27.
by glasser 13y ago
BTW, the original bug in the Meteor codebase wasn't a setInterval. It was that code to replace a certain type of object (a Spark renderer) with a new instance of that object accidentally ended up with a reference to the preceding rende
28.
by glasser 13y ago
The surprise isn't that the memory associated with `logIt` is leaked. The surprise is that `logIt` holds on to the giant `str` object in its environment, despite the fact that there is literally no way for the `str` variable to ever be
29.
A surprising JavaScript memory leak found at Meteor(point.davidglasser.net)
179 points by glasser 13y ago|104 comments
30.
by glasser 13y ago
We took inspiration from the great work Tom and Mike did on Meteorite; several of 0.6.0's features are essentially versions of what Meteorite let you do, except for much more deeply integrated into the core. For now, Meteorite is still a gr

More ›