879 karma · joined June 12, 2014
I tracked it down to my desktop wallpaper being on a rotation. Seriously... how bad does that have to be implemented in Windows to actually hang the mouse and keyboard?
This page quantifies it. https://github.com/jhallen/joes-sandbox/tree/master/editor-p...
I don't so much care about memory consumption. It can be 5 to 10 times as much as Sublime... I am RAM to spare. What I do care about is that a lot of these tests are 20 times SLOWER than Sublime (which can already be considered a heavy-weight editor)
... why is this good:
def dup(n):
for i in range(n):
yield i
yield i
... but this one better? def dup(n):
for i in range(n):
yield from [i, i]
... it would seem you're needlessly creating (1): another level of generators, and (2) creating a real listGo or Rust for example. Also, I watched a talk from DConf and saw that D is adding memory safety as well. You need to mark any part of code doing pointer arithmetic as "system code" or something like that.
I think it's a shame one couldn't have happened before the other. I wish something like D or Go or Nim or something else would have won. Then there would be this effort to get that language fast on the browser.
Is anything I'm saying making sense? I don't know enough about WebAsm, is it really tied tightly to C or could Go or Rust or some future version of statically typed Python become a first-class citizen?
Should have been dead on arrival because of that fact alone. For something that was trying to bring C/C++ and video games into a browser setting a 4GB max on memory should have been a non-starter.
I think organizing / refactoring a bunch of named tuples would be a mess. In one code base I maintain I switched a bunch of namedtuples to attrs classes and the code instantly became more readable / maintainable.
The downside to the namedtuple is that it's a tuple and can be unpacked as one.
for x, y in points: print x, y
# vs.
for p in points: print p.x, p.y
# ... now go and add a z to the point class and see what happens to your code.
This is probably a good practice anyway. I'm curious now how I can test and see if I'm taking advantage of this or not. I wonder if using the attrs module will also make use of this new feature.
Herb Sutter: Leak-Freedom in C++ by default
Looks like a design issue and not an overflow or something.
Now that it is somewhat proven, maybe Google will leverage GVFS on Windows and create a FUSE solution for Linux.