drderidder

16 ms·

91.
by drderidder 10y ago
I like it, but it could use some refinement. Already a couple of years ago Dave Thomas, one of the original authors of the Agile Manifesto, wrote a piece called "Time to Kill Agile" (renamed "Agile is Dead")[1]. The &quo
92.
by drderidder 11y ago
Well said! Dynamic memory allocation is a really big performance hit, and in a lot of cases you can pre-allocate data structures on the stack for serious speed improvements. Avoiding DMA was one of the secrets for writing blazing fast real
93.
by drderidder 11y ago
The article is somewhat misleading. Keeping up with software evolution is something large North American companies struggle with as well, and while Japanese companies may be slower to adopt some software trends that are commonplace here, Ja
94.
by drderidder 11y ago
Hmm, that the acquisition would mean anything for node directly seems off. At least, the blog post seemed to indicate that this wasn't meant to be about IBM buying influence. I wasn't a customer and not particularly keen on the en
95.
by drderidder 12y ago
Well, that's true, the masters didn't forget about Bach even though the public mostly ignored it. Thankfully Mozart, Beethoven and Mendelssohn helped to keep an appreciation of Bach's work alive.
96.
by drderidder 12y ago
Bach, my all time favourite. An absolute genius; his work was almost forgotten, thank goodness it was rediscovered and preserved. Excellent performance of Prelude and Fugue in C Minor; two pieces I played back in the day for RCM Grade exam
97.
by drderidder 12y ago
What frightens me is that we don't seem to have come far enough as a society since those times. Benjamin Barber and Noam Chomsky have done a pretty good job of exposing current-day American exceptionalism. This article points out that
98.
by drderidder 12y ago
I feel like the techniques React uses to deal with state and performance are likely to be addressed in a simpler way by solutions that work better with the existing stack. I'm not an Ember user but I like the way they've approache
99.
by drderidder 12y ago
All the core team really lacks now is the node.js label. Joyent's trademark seems weak, since the term was in prior use for commercial purposes well before they came along. A trademark challenge might be one possibility. On the other h
100.
by drderidder 12y ago
I think it shows how important it is to maintain a healthy work-life balance. Hopefully he'll find a way to combine his technical aptitude with his new lifestyle in a symbiotic way.
101.
by drderidder 12y ago
I recently read this, worked through the examples, and was pleasantly surprised at the depth and quality. Subsequently we recommended it to our 800+ member meetup group as the top learning resource for new JS programmers. The content is en
102.
by drderidder 12y ago
What is a kicksled??? I want one already! [update] wow...found one, the kickspark! Awesome. http://www.goslide.ca/en/shop/kickspark.php
103.
by drderidder 12y ago
I just skated 13K on the canal in Ottawa - it's a blast. This year the ice is good but it varies, some years you get only a couple weeks of decent skating. For reliable self-propelled commuting in winter you're probably better off
104.
by drderidder 12y ago
Basically anyone who has a business model related to the node.js ecosystem would benefit by not having development under the control of a single corporate entity. Isaac was in a tough place back then. I think spinning off NPM was a good mov
105.
by drderidder 12y ago
About a year ago I posted "node.js needs a new home" on the mailing list. It started a minor s### storm and a couple of local IBM guys went down to talk to Joyent, which eventually led to the whole advisory board / foundation
106.
by drderidder 12y ago
I got a copy of Paul-Henning Kamp's critique "HTTP/2.0 - The IETF is Phoning It In" off the ACM website before the link went dead. Here's a bit of what he said about it: "Some will expect a major update to the
107.
by drderidder 12y ago
Why is this better than tshark?
108.
by drderidder 12y ago
Angular emanated some 'project smells' that have kept me at arms length. The size of the codebase was very large compared to alternatives. Lots of add-on solutions for various problems (ng-this, ng-that) kept cropping up. Articles
109.
by drderidder 12y ago
Node got forked because it got corped. When a corporation sinks their hooks into an active open source project, it's only a matter of time. Mysql, Maria, Hudson, Jenkins... same story. io.js is the way forward, and congrats to the core
110.
by drderidder 12y ago
I don't like the manager / developer separation. I've had better results using lightweight strategies to let projects be more or less self-managing. Basically just creating a shared vision, giving responsibilities to people,
111.
by drderidder 12y ago
Sure. First off, I should say that as the lead developer I took ownership of these decisions. Design by committee is certain death. I didn't ask for permission; I sought input from various stakeholders (often one-on-one) and made it cl
112.
by drderidder 12y ago
adj. of, related to, or characteristic of a Luddite. Luddite: one who protests against modern labor-saving technology.
113.
by drderidder 12y ago
There were a few alternatives on the client side. Not many, but they do exist: Java was supposed to be the alternative for building web based applications, but Applets didn't gain wide adoption. Flash did better but eventually became u
114.
by drderidder 12y ago
I'm thinking of things like TodoMVC. There's an abandoned list on nodejs.org that categorizes many of the earliest npm modules. A lot of those modules have matured and are still in use. MicroJS.com is another one I'd probabl
115.
by drderidder 12y ago
Okay. > JavaScript is an awful language This is a bare assertion. The same thing can be (has been) said about every programming language, ever. > the entire stack is more less broken. This is another bare assertion. > HTML and CSS
116.
by drderidder 12y ago
Wow, I have rarely encountered a more ludditic comment on HN. The number of bare assertions alone is bemusing.
117.
by drderidder 12y ago
Yeah. There's a great recent post by Jeffrey Ventrella on "Slow Programming"[1] highlighting the problem that comes from the "fallacy that all engineers are fungible"[2] and throwing a bunch of programmers immediate
118.
by drderidder 12y ago
Aw, come on, you really should. You know what happens when you publish something to npm? Approximately nothing. Your module gets in there with a bazillion others. Maybe someone will use it. Maybe not. Man if you could see the lame-ass libra
119.
by drderidder 12y ago
Exactly. Is there value in learning to code? Of course. Does learning to code mean you will be able to write quality software? Unfortunately no. Especially if you learned to code in a sort of crash course on web application development. To
120.
by drderidder 12y ago
What is happening with the web stack now is a sort of renaissance with an unprecedented pace of activity. It's easy to feel overwhelmed, which is why I started a local meetup group that has now grown to 800+ members, all wondering the

More ›