newLisp vs node.js

Featuring the Dragonfly web framework

newLisp vs node.js

Postby borgauf » Thu Feb 27, 2014 2:00 am

I'm a total beginner, but for a long time I've felt that a Lisp of some sort should be King. But then there's all this talk about javascript this, node.js that. Isn't newLisp capable of doing what node.js does, only better?
borgauf
 
Posts: 3
Joined: Thu May 09, 2013 1:55 am

Re: newLisp vs node.js

Postby Astrobe » Tue Mar 18, 2014 11:15 am

Node.js is popular because it's javascript. It let "web" developers reuse their knowledge, server-side.

Javascript itself is one of the biggest steal in CS history IMHO. The language design is full of WTFs (kind of the opposite image of Newlisp if you ask me), but it is the language of web browsers. Web browsers won, so JS won.

Browsers themselves are a poor technology. HTML, XML, CSS and JS are "resources don't matter" languages. You realize that when you have to fit the "web stack" in an embedded platform; you need far too much resources for what you want to do (except if what you want to do is really browse the web).
Astrobe
 
Posts: 38
Joined: Mon Jan 11, 2010 9:41 pm

Re: newLisp vs node.js

Postby cormullion » Tue Mar 18, 2014 5:20 pm

I've been trying out the new Node.js-based editor, Atom.io. There's a lot to like about it, but the central problem is that it's slowish - it struggles with loading new documents, for example. Perhaps we all spend so much time waiting in web browsers anyway, it's not a problem... :)
cormullion
 
Posts: 2037
Joined: Tue Nov 29, 2005 8:28 pm
Location: latiitude 50N longitude 3W

Re: newLisp vs node.js

Postby csfreebird » Wed May 21, 2014 4:47 pm

The answers will be different when asking different people?
For me, node.js is slower than C++, I can develop web site using C++, C++ has the best speed, so node.js is not my first option mostly.
Node.js is JavaScript based on V8 engine, JavaScript is a dynamic language, it provides more flexibility
than static language, i.e. Java or C++. You do not need to design a class and compile it, you can change it at runtime when using JavaScript. It's great! But if you can use LISP, you will find LISP can provide more flexible features, for example, macros!

So for me, if I want to get a flexible language to create some apps without considering performance, I will choose
newLISP.

But node.js community is much larger than newLISP or other LISP communities, that means you can get many libraries or frameworks to complete your job if you choose JavaScript. For example, I do not know how to interact with MongoDB using newLISP and do not get help currently.

You should make your decision, I still choose newLISP even if I face many problems.
csfreebird
 
Posts: 107
Joined: Tue Jan 15, 2013 11:54 am
Location: China, Beijing

Re: newLisp vs node.js

Postby obiTheOne » Fri Oct 07, 2016 10:38 am

Hi,

I'm a JavaScript and Lisp (Clojure) programmer, so I may give you an unbiased answer.

Node.js is great because is Js, and that means:
great community
huge ecosystem (someone already wrote an npm module with the functions that you need)
quite easy to learn
reusable skill all across the stack
JavaScript is a great language (despite all the WTF)

The bigger drawback is that Js was created to run in a brower, so if you need to use it in another environment, you basically need to embed the all "browser ecosystem"; and that could mean bad performances.

My advice is to learn pros and cons of every instrument you can use and choose the best fit for every project.
obiTheOne
 
Posts: 1
Joined: Fri Oct 07, 2016 10:22 am


Return to So, what can you actually DO with newLISP?

Who is online

Users browsing this forum: No registered users and 2 guests