nulltype

15 ms·

301.
by nulltype 11y ago
I agree that this doesn't seem to actually cover practical memory management. In Go (and perhaps most languages) this seems to mean avoid allocations, and if you have to allocate, avoid the heap. Maybe some information about how heap
302.
by nulltype 11y ago
What's the limit on limo medallions? Those use public streets.
303.
by nulltype 11y ago
I'm suspicious of some of these reasons though. Why did they have so few taxi medallions in NYC? Why are they allowed to be leased to drivers?
304.
by nulltype 11y ago
I haven't used Pusher or Socket.IO, so I don't know specifically what they offer. However, I have made a simple unidirectional websocket-type server and it was not a terrible hassle. With a go server on a GCE n1-standard-2 you sh
305.
by nulltype 11y ago
I don't think performance costs are that big of a deal in general. The real costs with those sorts of services is perhaps centralization and dependency on an outside entity. If we did manage to create some magical cross-language libra
306.
by nulltype 11y ago
Hilariously we seem to be getting code reuse mostly through network services these days instead of language specific libraries.
307.
by nulltype 11y ago
He's like the Uber of startup founders.
308.
by nulltype 11y ago
I think they should fix that bug where it's not actually looking at the comments. However, with the exception of that bug, I don't think I have ever made a comment that started with "//go:" and was not a direc
309.
by nulltype 11y ago
Yeah me too, and I can't recall that ever causing an issue with these comment directives.
310.
by nulltype 11y ago
I don't really agree. I don't see any substantial difference between //go: and #go: except that programs using the # syntax would not build on older versions of go. I haven't really run across any issues with the c
311.
by nulltype 11y ago
I like the vjeux thing, I think for dynamic sites if we replace static html and css with javascript the world will be a better place.
312.
by nulltype 11y ago
This is exactly where I am hoping reactive ui ends up. If you don't want to do 60 times a second you can render only on certain events like network call or mouseover. If you do the rendering in requestAnimationFrame you can batch thi
313.
by nulltype 11y ago
In the article you say you "Reuse through React instead of CSS" and that you have CSS files for the components and no global CSS classes. Do you mean that the CSS files are applied to the elements as inline styles by react, or ju
314.
by nulltype 11y ago
Seems like .observe() would fix that polling thing, right? http://www.html5rocks.com/en/tutorials/es7/observe/ Also you could just re-render whenever any event happens, which is probably when your state
315.
by nulltype 11y ago
I've been looking at reactive UI design, and it seems weird to me that React.js has this React.createClass and .setState stuff. It seems like it would be better to let the user manage the state and just re-render whenever the state ch
316.
by nulltype 11y ago
What are the legal consequences of path rewriting? And why would the sane world look down on npm?
317.
by nulltype 11y ago
I use specific versions of libraries in my app. If two libraries depend on some third library it's rarely an issue, and when it is an issue I often have to resolve it manually anyway. Ideally I think each library would have its own in
318.
by nulltype 11y ago
What if it's debug() instead of debug? That could be an expensive function that does a bunch of things to produce the debug output.
319.
by nulltype 11y ago
Thanks for the explanation! I'm not sure I personally want to rely on semantic versioning, but if you have a hierarchy of dependencies like that I see how that would be pretty useful.
320.
by nulltype 11y ago
One thing I've never been able to figure out about these package management systems: why do you specify a version range, and not just always specify a precise version? I don't like dependencies randomly upgrading themselves, and
321.
by nulltype 11y ago
While StackOverflow has a number of flaws, it is pretty good for finding things that I'm looking for. I've definitely found posts from the BigQuery team on there answering my BigQuery questions. As for Google's support plan
322.
by nulltype 11y ago
It's true, if Google wants GCP to be good, they will have to use it themselves. I definitely don't trust public bug reports to fix issues. At least if you have a support plan they are good at responding and sometimes fixing thin
323.
by nulltype 11y ago
urlfetch is the worst, at least MVM will be getting rid of that. I would just use the socket api instead of urlfetch, like I do here: https://code.google.com/p/googleappengine/issues/detail?id=6...
324.
by nulltype 11y ago
I like the gcloud-node docs! I remember the oauth stuff being a pain just because oauth is kind of complicated and the terms are weird and there was no guide that just says "go here and click this" you had to just figure that out
325.
by nulltype 11y ago
Even if that were not the case, I doubt the performance of the OS X image pipeline is tuned for non-Apple hardware if it supports it at all.
326.
by nulltype 11y ago
Unless of course you had to re-implement most of OS X's graphics framework on Linux, which could take both a lot of time and money.
327.
by nulltype 11y ago
http://gdcvault.com/play/1012210/The-Implementation-of-Rewin...
328.
by nulltype 11y ago
No I think it just means that we will not hit that level of usage again.
329.
by nulltype 11y ago
Salary is only one part of a company's compensation. For instance, in the Buffer case, they do remote working, so some people could find that to be worth quite a bit.
330.
by nulltype 11y ago
I think the things we want to conceptually do at least with code are not that complex, but the tools we have are. I don't know how to prove that without actually building better tools. One example might be that sync is a complex probl

More ›