|
There's a particular fondness for it in the coding horrors thread.
|
#
¿
Feb 18, 2015 19:46
|
|
|
|
| # ¿ May 9, 2024 23:30 |
|
|
sarehu already covered the gamut is his rebuttal, but here's more.pigdog posted:I don't know much of Node but the tech lead of quite a successful local startup gave a talk about why they use it, pigdog posted:Most developers need to know Javascript anyway these days, so why not use it on server. Also, JavaScript is a terrible language. It's tolerated on the front-end due to necessity and the fact that there's nothing that can replace with the same degree of browser compatibility. That said, it's been around long enough in web browsers that frameworks have sprung up to make it suck less. In contrast, there's few constraints on which language/framework to use on the server, and thus, there exists a variety of mature, well-thought-out language/framework combinations. Here, node doesn't provide anything fundamentally new at all, aside from the novelty of "having the front-end and back-end in the same language!" pigdog posted:Very easy to create and integrate with JSON/RESTful services, because duh. pigdog posted:Compile times don't exist, so devs are more productive and deployment is easy. pigdog posted:NPM is pretty cool. pigdog posted:It's single-threaded but asynchronous, so you get many benefits of multithreading but without the complexity and caveats. So, the deal here is that mature languages support both threading and event-driven models, so you can write code using whichever approach is better suited for your purpose. Node only supports the event-driven model because V8 doesn't support multiple threads. Node hipsters spin the "async sauce" as an advantage, but honestly it's a major limitation of the platform that is, at best, a neutral point for folks who really believe that event loops are always superior to threads. ExcessBLarg! fucked around with this message at 01:20 on Feb 19, 2015 |
|
#
¿
Feb 19, 2015 01:08
|
|
|
Bruegels Fuckbooks posted:Node.js is stupid and the community is poo poo.
|
|
#
¿
Feb 19, 2015 01:11
|
|
|
Deus Rex posted:This issue is a doozy. tjfontaine posted:The way readFile works is to first to stat() the file and then read that size,  So at first I was worried (hoping) they actually do a stat on the file, then open it. But it turns out they were doing it the (kind of) right way from the beginning. Except, if they used to have a "slow", but compatible version of readFile, why did they dump the slow path?
|
|
#
¿
Mar 6, 2015 01:39
|
|
|
pepito sanchez posted:What's so wrong with node? In short, though, JavaScript isn't a very good language. It was an acceptable language in the mid-90s as its design goal of providing "light scripting" for largely static webpages didn't necessitate a more complex language. However, over the past decade it's been pretty clear that it's outgrown its scope as a frontend language for highly-dynamic sites, but folks still use it because it's the one language (or compile target) that all browsers support. But honestly, dragging it into the server-side where we've long had better languages of all sorts, doesn't make sense. Hence, benchmarks are a major selling point of node because, honestly, there's not many others. It's hard to explain (beyond what we've already done) where node falls short in practice. In my opinion, its three biggest flaws are: complicated code (due to forced async with no threading and many callbacks), performance issues (where blocking I/O introduces jitter to the event loop), and a relatively immature community and collection of third party libraries. On the surface, node might look great, but anyone who uses it for large/complicated projects ends up feeling the compounded effects of those flaws. I'm sure there's limited-scope use case for node that are just fine. Prototyping, templating, use as a test framework, simple proxies, can all be done in node quite manageably. But I'd really hesitate to use it as the basis of a large project with a 10+ year expected lifetime.
|
|
#
¿
Aug 13, 2015 23:08
|
|
|
|
| # ¿ May 9, 2024 23:30 |
|
|
pepito sanchez posted:What's the difference between using Django with a RESTful API in mind, and a fully JS app? Apart from the obvious. pepito sanchez posted:Would you recommend someone learn Spring instead for server-side code? pepito sanchez posted:I don't even care what kind of database it uses as long as it's secure. NoSQL databases may have their place in providing solutions to specific problems. But I wouldn't use Mongo "by default", but only when you have data sets that really don't mesh well with the relational model. pepito sanchez posted:Obviously for small projects I could just use anything, but I like imagining everything might become something huge.
|
|
#
¿
Aug 14, 2015 06:00
|
|