|
I contributed to Node.js in its early days (just a simple bugfix) and have regretted it ever since. See also What the hell is going on in webdev land FakEdit: Good god that thread is from 2013.
|
#
¿
Feb 18, 2015 19:59
|
|
|
|
| # ¿ May 10, 2024 08:07 |
|
|
El Marrow, what other tools have you used for web development?
|
|
#
¿
Feb 18, 2015 23:11
|
|
|
Avenging Dentist posted:
An appropriate number for that 16-bit opinion on a 32-bit language.
|
|
#
¿
Feb 18, 2015 23:36
|
|
|
pigdog posted:Javascript and node.js are made for and optimized for the web and networking from the ground up, rather than relying on libraries. Javascript is not optimized for networking at all. It's not optimized for the web either (not sure what you mean by optimization, but if you mean in terms of language design... from a web server perspective, it certainly is not). Node.JS is not optimized for networking either. It has a networking library, like anything would have. pigdog posted:Most developers need to know Javascript anyway these days, so why not use it on server. Because of reasons, such as callback hell being worse than using threads, and being dynamically typed being worse than being statically typed. pigdog posted:Very easy to create and integrate with JSON/RESTful services, because duh. Actually, it's because there's a JSON parser in the library, and an HTTP server, just like there is with other languages/frameworks you'd use for web development. Being Javascript gives it no special privileges to either aspect. pigdog posted:The runtime is very lightweight compared to JVM and that of many other languages. Compile times don't exist, so devs are more productive and deployment is easy. Or you could use other languages that are better, also have lightweight runtimes (except you're running a server so having the JVM is not a problem) and you have to hit a deploy script anyway, it's not like you're editing files in place. pigdog posted:NPM is pretty cool. If it's so cool what is Bower for, and don't Python or Ruby or Java and the like have ways to get packages too? Yes, they do. pigdog posted:It's single-threaded but asynchronous, so you get many benefits of multithreading but without the complexity and caveats. You get the complexity and caveats of event-based programming, which is what multithreading solves. Guess what caveats you get of multithreading: there aren't really any if you're writing a sane web app that only talks to a database and global caching stuff, and doesn't have request handlers sharing global state. pigdog posted:They said they design what components they can to be stateless and just run [number of CPU cores] instances of node (behind some kind of load balancer?), and if that works, then they can easily scale it to many servers as well. Etc. Which is not some Node-specific solution or good thing about Node.JS.
|
|
#
¿
Feb 19, 2015 00:04
|
|
|
let i hug posted:If you know you're going to want to start over again when your app hits ~40k lines of code, why would you spend that time writing in verbose, clunky languages? C# or Scala aren't verbose or clunky.
|
|
#
¿
Aug 14, 2015 19:08
|
|