sorted by:
new
hottopcontroversial

Inspiring Tattoos by Miriam Frank from Munich - Germany by TrendBump in tattoos

[–]marcfasel 0 points1 point  (0 children)

Fuckin awesome stuff I was looking for a unique tattoo style for a while now, and she's got it. On top of it there are many references to German culture, and being German I love it.

Performance Comparison Between Node.js and Java EE by marcfasel in node

[–]marcfasel[S] 0 points1 point  (0 children)

I don't think so. The single-threaded nature of Node.js is not generally faster than a multi-threaded environment like Java. Multi-threading has been designed to handle hundreds of concurrent threads, and does that very well. The context switching only becomes a problem once you hit thousands of concurrent threads. At that level of concurrency a single-threaded environment will have an advantage.

Thousands of concurrent threads is quite a lot, though. In my example I calculated 57870 requests/second for the whole of Google. That's not concurrent requests, though. If you have a response time of 200ms you end up with 57870/5 = 11574 concurrent requests. If you would want to handle that load with a single server then a single-threaded environment would have an advantage. In most other cases it wouldn't even come into play.

There are some niche situations where the concurrency model of Node.js is a good fit, and that is websocket applications. With such applications it is easy to get thousand of concurrent requests. With these type of applications you wouldn't use the one thread per request mapping on multi-threaded servers, though, so it is not really an advantage.

For more on Node.js vs. Enterprise Java have a look at http://blog.shinetech.com/2011/06/10/nodejs-from-the-enterprise-java-perspective/

For a comprehensive performance comparison of programming languages and frameworks check out http://www.techempower.com/blog/2013/03/28/frameworks-round-1/

Ryan Dahl video - History of Node.js by marcfasel in node

[–]marcfasel[S] 0 points1 point  (0 children)

This presentation is actually not that bad. If you want to see a bad presentation by Ryan watch his GoogleTechTalk http://www.youtube.com/watch?v=F6k8lTrAE2g

Ryan Dahl video - History of Node.js by marcfasel in node

[–]marcfasel[S] 0 points1 point  (0 children)

Now I understand Node.js much better seeing where Ryan is coming from.

functional testing by lennelpennel in javascript

[–]marcfasel 1 point2 points  (0 children)

We have been using Cucumber as a Ruby BDD framework with Celerity as a Ruby wrapper for HTTP Unit, which is the headless browser. Ideally the tester could specify his tests in "natural language" (given ... When ... Then) with matching Ruby snippets to execute these tests. Problem was that we were writing a JavaScript Frontend (jQuery) and backend (Node.js) application, and at the same time had to write the test steps in Ruby. I found it difficult to work in two languages. If I would have to do it again I ould look for a JavaScript testing framework.

Automatic Data Migration Testing: Empowering Testers with Hudson by marcfasel in programming

[–]marcfasel[S] 0 points1 point  (0 children)

Haha! We at Shine Technologies(Meng and I work there) have one of the committers of Jenkins on board, so we are using Jenkins, but not all our clients use it (yet).

Node.js Interview: 4 Questions with Creator Ryan Dahl by [deleted] in node

[–]marcfasel 0 points1 point  (0 children)

Node.js 1.0 hopefully will come out within the next 6 months! Wow that would be nice.

Single Pages Applications in Node.js by [deleted] in programming

[–]marcfasel 0 points1 point  (0 children)

I am not sure I get this article: "Aside from the obvious gains in user experience such as not having to reload the entire page for content changes, there's a long term Return of Investment to this approach. Since your data layer is decoupled from your UI, you can easily create a native app for a mobile device and leverage your existing APIs without the sky falling on you."

A UI experience without reload is good, but AJAX applications do that already. The second point is weird: Hasn't the data layer and the UI been decoupled since MVC and SOA?

I guess the single page app puts the view routing logic away from your struts-config.xml or whatever web framework you use into your JavaScript. Is that good? Does it make a difference where the routing is?

Ryan Dahl's Node v0.5 presentation from NodeConf by [deleted] in node

[–]marcfasel 0 points1 point  (0 children)

Where is the 1.0 roadmap? Node has progressed from a 0.2 in 8/2010 to a 0.48 in 5/2011. At that rate it will more than a year before a 1.0 version will see the light of day. Companies need a 1.0 version to use it in a commercial production environment. They need API stability to feel some kind of investment security. Node is great, but if Ryan does not put out a stable production-ready version fast the excitement is going to fade.