Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I would like to start a new Nodejs project soon, and I was wondering if I should try out Dart VM instead. I read that Dart VM is not finished yet, but I should already have everything I need (web server, sockets, files i/o), and I would enjoy discovering something new.
Does anyone have experience with both Node and DartVM, and can tell me what are the major differences/problems to expect, or if Dart VM is really not usable for real server side projects yet?
I'm not asking for your personal preferences, but for actual problems I might encounter based on your experience.
I worked on a small project, a few months ago, using Dart as a server side language. I really enjoyed it and didn't have any specific problem beside the occasional "there's no package for that" - there are way more packages for Node than for Dart. This could be something to consider for development speed (no need to reinvent the wheel). Other than that, everything went fine.
As a note, it is being used live by others: top 5 live websites already using Dart
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
At the risk of this question being closed I will ask anyway.
I have been looking at the different JavaScript Frameworks as most jobs roles seem to want:
angular.js
Knockout.js
Node.js
Whilst i can see Angualr.js and Knockout.js provides a MVC construct to the markup pages (though still not sure which one is best to use) I cannot see what is the case for node.js?
Whilst I appreciate node.js is good for real-time comms but so is Signalr as they both use long-polling.
At present I use signalr to update images on my clients.
is there any purpose to swapping this out for node.js?
Like I said this question could be voted to be closed as it may seem to be asking an opinion - and that would be an answer to me in itself as it would be down to developer choice but is there a DEFINITIVE reason to use node.js over signalr?
thanks
One reason to use node.js is code redundancy. Both the server and client run the same language, thus they may share a certain part of the codebase, meaning potentially less to write. With libraries like Browserify this process can be made a lot more transparent and writing the client-side can be almost indistinguishable from server-side development. Another opportunity this opens up is both client and server side rendering + MVC setups with, for example, rendr.js. So you can have both the fast load speeds of server-side and responsiveness of client-side rendering. If any of this will be useful naturally depends on what you are developing.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
OK,
I am setting up my first Azure VM, the only images available are basically windows server.
Why are their servers so low on memory until you get to pretty big $$$?
Are there any of us who would straight faced tell a client that they should run a windows server with .75 GB of ram?
Can I run basic applications on the small machines or should I not waste my time?
Thank you,
Joe
not sure where you're looking at, but there's definitely more than Windows images in there (Ubunto, CoreOs, CentOS, Suse...)
Not to mention that you also have the VM Depot
extra small instances make good for some light load like acting as a witness in HA setups, or even running small web sites...
depends on what you run on it.
you'd know better what your app requires.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Dont get me wrong people, let me clarify.
I would like to ask if I can trust node.js. I know its an amazing tool. But its a really young platform, to be honest. Should I start playing around with it (production, not just experimental use), or should I wait till it "grows up"?
Does it work fine on Windows? Because at the beginig it was not supported. Are there any stress tests that actually prove that its safe and can be trusted?
It demands to write a lot of code by hand, stuff that in other platforms are done by just one line of code. I know you are gonna say to me "that depends on your experience" . I agree, but does it worth "learning" node? What if its developing stops? Again, I'm only asking because its pretty young.
What of node's add-ons and modules are to be trusted about their safety/stability? There are so many out there.
Is it stable? And finally, what about node's interoperability? Does it work on every platform/browser? What about smartphones and mobile devices?
Again, dont get me wrong, I am not critisizing. I am just concerned because its pretty new, everybody is excited and I haven't see any cons, or safety/stability issues around.
Thanks
I don't understand why would anyone choose to use node.js to do backend: the statically typed code is easier to maintain and Javascript is not the best (a good?) language.
That said, there are situations, where it makes a lot of sense to have the same code running in the browser and in the back end. When you run into one of these, you will know. And then Node works just fine. We've had it in production for months exposing its functionality as an internal web service to our back end application and haven't had any problems with it.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We are using this server for almost a year now.
Last forum post seen in November, 2011.
Last server version released 28/03/12.
Just wondering if anyone knows whats happening inside the company?
Should we expect something or should we start looking for alternatives?
I did what you did not do: using email to ask the question to the people able to answer.
And they replied that:
the forum was closed because they could not cope with the amount of accounts created daily to publish junk
the next version will be the most important ever made for G-Wan, with new features like a caching reverse proxy and an elastic load-balancer as well as system replacements like a wait-free memory allocator.
With regard to such developments, a 3-month period without publishing releases sounds reasonable.
More reasonable than assuming that such an 'inactivity period' means that "the project is dead".
Would you say that for other Web servers like Apache which have much larger release cycles?
You should always be expecting something from G-WAN. It's a great piece of software. Here's the other thing too: G-WAN was expertly engineered. That doesn't mean that there are no bugs in it, or that features can't be implemented, but G-WAN is incredibly tight.
It has lean code, it does what it supposed to do, very well, and it is built for the developer to add in the functionality that hasn't been put in there yet.
That's the beauty of it, or one facet of the beauty.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I've heard that node.js is really fast for applications like chats and real time apps.
I was wondering if node is a good choice to develop a forum or a q&a site like StackOverflow?
Yes it's perfectly possible, you don't have to implement your own web server like somebody said, you can just create it using something like Express (as a framework) and Mongoose (as a MongoDB ORM) or whatever you choose.
I think Node.js is a good solution for such a case because of its high concurrency (and Stack Overflow is a site where thousands of users are online in the same time probably). So yes you can achieve this with PHP, Ruby and Python etc, but I believe Node.js is a better fit (that's my opinion, based on the success stories I've heard which were based on Node).
Node isn't just a solution for building small services, here are some good examples ( https://nodejs.org/en/blog/uncategorized/an-easy-way-to-build-scalable-network-programs/ ).