nimrody

35 ms·

331.
by nimrody 17y ago
Memory of course. I don't think there's much of a difference in runtime (ignoring cache misses, etc.)
332.
by nimrody 17y ago
While coroutines may help in writing more maintainable/readable code, they make for a very inefficient structure since they have to keep a separate stack. Having many concurrent coroutines is probably a bad idea. This is the classic trade-o
333.
by nimrody 17y ago
Making a good lens for these small sensor cameras is much easier compared to film or even APSC sized sensors (most DSLRs)
334.
by nimrody 17y ago
Besides recommending "Programming Erlang" which is a well written book, this article offers nothing new.
335.
by nimrody 17y ago
You seem to indicate that Japan's carriers has less strict certification process than AT&T's. My personal experience with NTT DoCoMo (one of the largest carriers in Japan) has been exactly the opposite. Certificaiton has been a very dif
336.
by nimrody 17y ago
Depends on the definition of "soft". Sometimes you have to be very optimistic (better term: aggressive) regard product features and schedule. This will drive you further and faster towards your goals. You can't always make all deadlines and
337.
by nimrody 17y ago
Many people still don't get it and use hotmail and similar services (Hey... they have cute icons :) Seems to me like gmail enthusiasm is mostly the realm of geeks. Some people even dislike the automatic threading.
338.
by nimrody 17y ago
Excel really took off on the Mac platform -- at first. So at least there they had no advantage. I agree that on Windows they always had an edge. But the truth is - everyone ignored the platform (everyone except users). Microsoft was heavily
339.
by nimrody 17y ago
Making a good product is not always about revolution. Many times it is about improving and refining. Remember the story of Microsoft and Lotus? Microsoft Excel won because it was a better product. Nothing revolutionary. Just better. Microso
340.
by nimrody 18y ago
It works, but is more difficult to debug and, of course, to integrate with existing libraries. I don't think many have taken this path - GWT has not exactly taken the developer community by storm. Even minimal approaches (e.g. QT extending
341.
by nimrody 18y ago
Nobody uses PHP because it is beautiful... Creating your own version would make you loose the one true benefit of PHP: easy deployment using many available hosting services. Unless, of course, you manage to make it popular as the original (