Timeline for Use-cases for node.js and c#
Current License: CC BY-SA 3.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot | Commonmark migration | |
| Dec 29, 2012 at 5:38 | comment | added | jcolebrand | To be fair, MVC is more of a methodology than anything. You could do MVC with WebForms. In that regards, the real question is ASP.NET vs Node.JS. | |
| Dec 29, 2012 at 2:11 | comment | added | Matt Esch | I'm surprised nobody bothered to mention that Node.js isn't a web framework. | |
| Dec 5, 2012 at 17:03 | history | edited | jcolebrand | CC BY-SA 3.0 | added 186 characters in body |
| Dec 5, 2012 at 16:59 | comment | added | jcolebrand | At the time of this writing Node.js was not supported by IIS, it is now, however. | |
| Jan 15, 2012 at 22:34 | vote | accept | Chase Florell | ||
| Jan 4, 2012 at 18:08 | comment | added | jcolebrand | You lot do realize that MVC3 is open source as well, right? | |
| Dec 8, 2011 at 21:48 | comment | added | Raynos | @Carson63000 Ok, first-party open source project. Same thing | |
| Dec 8, 2011 at 20:57 | comment | added | Carson63000 | @Raynos: Razor is not some third-party open source project, it is the officially endorsed developed-by-Microsoft view engine for ASP.NET MVC 3 | |
| Dec 8, 2011 at 20:18 | comment | added | Chase Florell | checking them out now. | |
| Dec 8, 2011 at 20:04 | comment | added | jcolebrand | hahaha, there's that then I suppose. I keep getting told I should consider relocating ;-) ~ Have you seen the github joyent node wiki pages? That would be a great place to start. | |
| Dec 8, 2011 at 19:48 | comment | added | Chase Florell | @jcolebrand re: healthcare... I'm Canadian ;-) ... re: writing node apps... no I haven't written any as of yet... just looking into it. | |
| Dec 8, 2011 at 19:45 | comment | added | jcolebrand | C# does compile time checking of all the code paths. It won't throw until bad data blows it up. Node won't stop the build just because of bad code. Or I was using an old version and that's changed. | |
| Dec 8, 2011 at 19:37 | comment | added | Raynos | not all paths are checked at startup". What? Sure not all paths are checked at startup, but neither are they in C#. You still have run-time failures. | |
| Dec 8, 2011 at 19:35 | comment | added | Raynos | "Razor templating". You know razor is a third party open source module right? Just like all the other third party open source nodejs templating engines. Besides comparing ASP.NET MVC 3 to node.js on it's own is bullshit. | |
| Dec 8, 2011 at 19:30 | comment | added | jcolebrand | I'm sorry that you don't need health insurance and the benefits of having coworkers to bounce ideas off of (the reasons I work in an office). I've considered going independent, and I don't think I would do well managing the business aspects of running my own shop. Also, I would end up hiring talented people to work for me. But, I prefer teams. I'm glad you don't. Have you written any apps in node yet? I would be glad to peer review them with my commentary and questions, if that's something you would be interested in. | |
| Dec 8, 2011 at 19:29 | comment | added | jcolebrand | @Raynos why is it version 0.6 then? That's not what most people call "first release". I'm pretty sure even the core developers wouldn't call it "first release" altho they said (same as I did) that it's ready for production. | |
| Dec 8, 2011 at 19:27 | comment | added | Raynos | Node is not in it's alpha stage. It's not in beta either. It's stable live and running in production | |
| Dec 8, 2011 at 19:23 | comment | added | Chase Florell | I'm not in college/university. I've been developing solo for around 8 years and am doing quite well for myself. I can make better $$$ on my own than under another company. | |
| Dec 8, 2011 at 19:21 | comment | added | jcolebrand | My advice, go write three or four complex websites in node.js. Start small, then get larger. | |
| Dec 8, 2011 at 19:21 | comment | added | jcolebrand | maturity - check, they both are stable enough to deploy apps on them. scalability - check, because I bet you don't have 300 concurrent requests on a regular basis on ANY site you've helped develop yet. Scalability is a question that can only be asked when you have performance problems. performance - check, they are both rather performant, up to a point. You won't reach that point before mid 2012, even if you get really lucky. feature set - well, what features do you need? one-man-band indicates you're in college/Uni, and that you need more experience yet. | |
| Dec 8, 2011 at 19:16 | comment | added | Chase Florell | Thanks for the detailed response. I don't have a "reason" to go with one or the other. Just wondering about some of what you posted above... maturity, scalability, performance, feature set, etc. I'm not a "shop", I'm a "one man band". Also, for the synchronous goods, I've been looking at SignalR as well. | |
| Dec 8, 2011 at 19:02 | history | answered | jcolebrand | CC BY-SA 3.0 |