LispyScript • Hacker News Board

Re: LispyScript

#41

Post by rane » Wed, Jun 10, 2015, 11:43 AM UTC

amyjess wrote: post #12

1971genocide wrote: post #3

Also check out LiveScript. http://livescript.net/ and its awesome FP library inspired by haskell's prelude.hs http://www.preludels.com/ I have done all forms of projects using LiveScript - robotics, simple websites, blog, cryptography, computer vision. Its actually becoming silently fairly mature. It helps when it doesn't generate any hype like most languages. The community around is also very helpful ! And LiveScrip…

Why did they name it that? LiveScript was Netscape's original name for JavaScript, before Sun asked them to throw in some Java branding.

  > Name
  >
  > LiveScript was one of the original names for JavaScript, so
  > it seemed fitting. It's an inside joke for those who know
  > JavaScript well.

Re: LispyScript

#42

Post by swannodette » Wed, Jun 10, 2015, 12:32 PM UTC

moonchrome wrote: post #28

didyoucheckthe wrote: post #18

Earlier quoted context omitted.

> "again this is only relevant for advanced production builds" So, all real-life builds that anyone would care about.

Think about where you would use CLJS - my use cases would not have an issue with extra 100kb of code - you don't use CLJS to do jQuery animations on your web page - you would use it to build complex single page apps or write server side code/scripts. You don't use clojure for performance anyway, it's going to be slower by default (because of immutability/persistent data structures, and yeah I know about react benefit…

ClojureScript applications start smaller than jQuery so I'm not really sure what you mean. If you're already using jQuery then ClojureScript applications are not large in comparison.

As far as your experiences sounds like a lot of your problems didn't have anything to do with ClojureScript and everything to do with trying to getting overly complicated 3rd party setups going. I've only heard woes from people trying to get piggieback + Cider going. I now recommend that people avoid those entirely for ClojureScript anyway.

I admit ClojureScript did have startup time issues but these were addressed earlier this year. ClojureScript can now compile "Hello, world!" from cold JVM boot in ~1.5 seconds. Of course auto-building has be subsecond for ages. REPL sessions start similarly fast and can go for hours without encountering problems.

ClojureScript may still not be your cup of tea but your complaints are not the sort I hear from users much these days.

Re: LispyScript

#43

Post by swannodette » Wed, Jun 10, 2015, 1:04 PM UTC

zupatol wrote: post #39

swannodette wrote: post #13

Earlier quoted context omitted.

Some inaccuracies here. ClojureScript does not have to be compiled by Google Closure. That pass is an optional one for production builds. There is no "bridging" when using the Closure Compiler with non-Closure compatible code. The issue is that in production mode the Closure Compiler will make aggressive assumptions about what it can rename. So it's not about bridging it's about preventing renaming - again this is on…

It seems I got many things wrong about ClojureScript. If I don't use the closure compiler, can I use any requirejs javascript library without problem? Once you have the JavaScript version of the ClojureScript compiler, will it be reasonable to use it for compiling in the browser? That would be great.

There's very little in the JavaScript world that can't be made to work with ClojureScript. That said it could be made easier and official support for CommonJS and RequireJS is underway thanks to Maria Neise's Google Summer of Code work.