Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Today's Lisp

Name: Anonymous 2019-08-29 23:38

If you have been in touch with reality (yes this is /prog):

1. Is Clojure still alive for web application development?

2. What's today's most popular Lisp to develop on? Racket? Clojure? Common Lisp? Something else? Something new?

3. Any Lisp/Lispy translator that translates to JavaScript like Coffee/LiveScript?

4. When will people rediscover Lisp by trying to encode JavaScript programs in JSON? (It does lack a symbol type for that, but let's see if somebody thinks of this.)

Name: Anonymous 2019-08-30 1:03

Lisp is dead. All of the new Lisps are even worse. Just stick to SBCL or move on to Haskell like every other Lispcuck has already.

Name: Anonymous 2019-08-30 3:47

>>1
Any Lisp/Lispy translator that translates to JavaScript like Coffee/LiveScript?
JavaScript is "Scheme in the browser". Its widely available, million time more programmers than Clojure and most optimized JIT runtimes on the planet. Get with the times.

Name: Anonymous 2019-08-30 4:56

Scheduled reminder that LISP sucks

Name: Anonymous 2019-08-30 6:40

1. Is Clojure still alive for web application development?
yes
2. What's today's most popular Lisp to develop on? Racket? Clojure? Common Lisp? Something else? Something new?
Clojure is most common in greenfield projects. I haven't seen a new commercial CL project in quite some time, but legacy ones are still alive. as much as I like Racket, it isn't really used commercially much - the community is mostly hobbyists.
3. Any Lisp/Lispy translator that translates to JavaScript like Coffee/LiveScript?
ClojureScript is pretty good. there's also ParenScript which is a CL implementation, but I've only seen hobbyists and SLWs use it.
4. When will people rediscover Lisp by trying to encode JavaScript programs in JSON? (It does lack a symbol type for that, but let's see if somebody thinks of this.)
my bet is that they won't, at least not yet. Lisps will continue to live on as niche languages, but current momentum is now on typefaggotry so you'll see more stuff like TypeScript and PureScript. maybe a decent typefaggy Lisp will come along and shake things up, but the ones we have now are far from decent (Shen is overly complicated, Typed Racket quickly becomes confusing when you try to make an annotation for something generic and/or variadic)

Name: Anonymous 2019-08-30 6:59

(It does lack a symbol type for that, but let's see if somebody thinks of this.)
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol

Name: Anonymous 2019-08-30 10:59

>>3
How do you get around:
● The shitty type system (false vs Boolean(false) vs undefined which is a piece of shit vs null which is an object but has no properties vs NaN which is a number, shitty coercions in + and a lot of places... , etc)
● Broken in (use x.hasOwnProperty(y), fuck, this is ugly), typeof and most of the standard library up to ES5
● Shitty function names in API such as getOwnPropertyNames
● Myriads of competing class systems and module systems
● Convoluted prototype system

>>5
Thanks for the answer. I'll have a look at ClojureScript. I'm disgusted at the typefaggotry of TypeScript and similar (Microsoft's first big contribution, and I still feel like they're trying to sabotage the Internet and make development expensive, and it feels like embrace-extend and I highly doubt it'd gladly superset the next ECMAScript); the issue with most of this shit is that it doesn't really pay off over good documentation and good programmers. Lots of verbosity and faggotry for a small gain.

>>6
That's meant for always unique values. The name is incidental.
● Symbol('a') !== Symbol('a')
● It's not part of JSON
● It lacks syntax

JSON2 needs to consider the absolutely unnecessary and idiotic commas and also the colons as whitespace used for clarity, and an unquoted notation that evaluates absolutely anything that's not whitespace/number/string/list/obj/bool/null into LispFag(name) or Variable(name) or whatever. It would allow people to start rediscovering Lisp, and it would be very useful to allow it to represent other stuff such as dates as [date 2018 03 12] or whatever somebody agrees to, etc. Of course then JSJSON would also need reader macros so we can implement ' ` etc. I'll stop the circlejerk now; common people are too stupid to understand the beauty in this.

Name: Anonymous 2019-09-04 3:48

jax my janus

Name: Anonymous 2019-09-04 12:56

>>9
it's not January yet

Name: Anonymous 2019-09-04 13:30

check my doubles

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List