As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I've been watching the development of Node.js and frameworks like Express for a while. I finally found some time to play around and am enjoying it.
Does anyone know why Node's current version is only 0.10.0? I know it doesn't really matter but it makes it seem like an extremely new and unstable project when in fact it seems that it's being used quite a bit and even by some big players.
Well, it is new, it's only been around since 2009.
That may seem old to you whippersnappers but I primarily program in a language from the '70s and sometimes on machines that have been around since the '60s.
But seriously, it probably has more to do with the numbering scheme than any actual immaturity. As you can see here, there have actually been quite a few releases.
If you wait a little while, the release plan calls for a 0.12 (code cleanup mostly) to be followed by 1.0 which, based on comments, will be the "final" product (though there will still be more versions since predictions aren't perfect). Many projects start with a (crappy) 1.0 and improve that. The philosophy for node.js seems to have been to approach 1.0 as the fully-polished end product.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I just read some news about Qualcomm launching an internet of things development platform on top of JME and I was wondering where is jme/j2me used nowadays. I know it was used for some old mobile phones and apparently you can still use for developing application for Bada and Symbian.
But besides that is there any other field where is it used? Can someone exemplify other areas where Jme is used or point to an updated list of embedded devices implementing a jvm compliant with jme?
The newest related inquire I saw around the topic was this forum discussion which did not bring that much light to the question.
I think it has spread, with feature phones, into places where smartphones are still pretty expensive. As an anecdote, my scripting language for phones, Hecl, does not get a lot of traction these days, by and large, but does seem to get a lot of attention in places like Indonesia.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Are there available somewhere numbers of how much time is needed to learn programming languages?
I do understand that this does, very much, depend on the person/learning-method. But I'm more interested in seeing some dynamics among languages, which I guess would be less 'personalised' - i.e. I would like to see division between HARD & EASY languages
Well generally speaking, a language is only as hard as the libraries it has. Take the Windows API for C. It's hard and at many times inefficient for making programs to do simple things. That's where .NET framework comes in. You can still use C++ with the .NET framework. The language isn't any easier, but the libraries you are using are easier to work with.
Learning Java takes quite a while, especially for a beginner. However after my first 5 minutes in java I understood the Swing library and could make a simple program. If I wanted to do the same with the Windows API it would take me a good month.
In the end, mastering and understanding the innards of languages is time consuming, but is directly proportional to the effort spent.
C++ can be learned in 21 Days (as the book goes) but it takes years to fully understand it.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
As a programming novice, I often run into trouble when trying to install packages, use virtualenv, and basically do anything even mildly complex using the command line.
What are some good references out there to help me UNDERSTAND things like my path, environment, shell scripts, etc?
Basically, I'm tired of copying and pasting. I want to really understand what's going on.
Thanks!
I used Linux in a Nutshell by O'Reilly. It helps you get past the initial beginners stage. Obviously there are a ton more links and tutorials, lists of keystrokes online, easily found with a Google search, but this will help you get going, and nice to read when you are on the bus or at lunch or whatever, to give you some ideas you might not just happen on in normal everyday life.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I recently watched the "Introduction to Node.js with Ryan Dahl" video on Youtube (http://www.youtube.com/watch?v=jo_B4LTHi3I), and I really like the look of Node.js. Unfortunately, in that video, Ryan described Node.js as "very much a bleeding-edge technology" (in so many words), and that means it won't suit my purpose in looking at servers/server-side Javascript in the first place - to find a stable, well-supported, open-source technology to use for our server-side purposes.
I'm pretty sure that Node.js's "bleeding-edge" status hasn't change - at least not much - since March, but can anyone confirm this for me? How risky would it be to include Node.js in our design for a large (1000s of nodes), enterprise-wide system?
Thanks!
Aaron
In general I would say "yes", but that has not stopped some cutting edge companies from using it production. I don't know of any that are scaling (clustering) to the level you're talking about.
I would say if you're asking here, then it probably isn't for you right now.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
The Go language is a new programming language from Google. It is still in an experimental phase and I am having trouble figuring out how stable it is. What sort of projects would you risk using Go for?
As you said, it is still an experimental programming language so I would only use it for experimental projects, for now. The implementation is still young but more importantly the ecosystem around it is also not very mature. In other words you'll probably have a hard time finding frameworks and libraries to help speed up your development and may end up needing to code a lot more than if you had chosen a more mature language.