Can you please give one reason to name the project "Kashmir"?
Kashmir: A statically typed Lispy language compiling to Go
31–40 of 75 posts
Re: Kashmir: A statically typed Lispy language compiling to Go
#32Can you please give one reason to name the project "Kashmir"?
Why not?
Re: Kashmir: A statically typed Lispy language compiling to Go
#33Can you please give one reason to name the project "Kashmir"?
Love for Led Zeppelin?
Re: Kashmir: A statically typed Lispy language compiling to Go
#34Can you please give one reason to name the project "Kashmir"?
Pure guess: its beautiful? (in case its about the place in India)
Re: Kashmir: A statically typed Lispy language compiling to Go
#35What is the advantage of targeting go for a new language project? Could you explain about why this made sense for your project?
There are so many motivations for this (and so many lisp/go projects that are abandoned). This looks very promising and I hope it takes off. A few of the motivations: * A lisp with an amazing startup time * A lisp that can tap into a big and vivid ecosystem, like Clojure is tapping into Java's and its own * Cross compilation and self-contained binary (I've personally tried doing this with various lisps, and none of t…
"Go is the assembly language of cloud infrastructure"
People say this about JavaScript because to run code in a browser, it has to execute as JavaScript. As a result, there are lots of actual libraries or webapps that are written in other languages and compiled to JavaScript.
In contrast, you can do cloud computing in Java, C++, or various other languages. Go may have advantages, but compiling to Go would just be a choice.
In short, I really don't know what you meant or why you'd say it.
Re: Kashmir: A statically typed Lispy language compiling to Go
#36What is the advantage of targeting go for a new language project? Could you explain about why this made sense for your project?
There are so many motivations for this (and so many lisp/go projects that are abandoned). This looks very promising and I hope it takes off. A few of the motivations: * A lisp with an amazing startup time * A lisp that can tap into a big and vivid ecosystem, like Clojure is tapping into Java's and its own * Cross compilation and self-contained binary (I've personally tried doing this with various lisps, and none of t…
so why not just use Go? less complexity - same benefits. you're basically saying it's somehow an advantage to program in s-expressions...
Re: Kashmir: A statically typed Lispy language compiling to Go
#37Re: Kashmir: A statically typed Lispy language compiling to Go
#38Earlier quoted context omitted.
There are so many motivations for this (and so many lisp/go projects that are abandoned). This looks very promising and I hope it takes off. A few of the motivations: * A lisp with an amazing startup time * A lisp that can tap into a big and vivid ecosystem, like Clojure is tapping into Java's and its own * Cross compilation and self-contained binary (I've personally tried doing this with various lisps, and none of t…
"Go is the assembly language of cloud infrastructure" People say this about JavaScript because to run code in a browser, it has to execute as JavaScript. As a result, there are lots of actual libraries or webapps that are written in other languages and compiled to JavaScript. In contrast, you can do cloud computing in Java, C++, or various other languages. Go may have advantages, but compiling to Go would just be a c…
I don't think (s)he meant Assembly, but rather the language used to "assemble" an awful lot of the modern cloud infrastructure. If you use Docker or CloudFlare, which I would think covers a sizable portion of new projects, your code is passing through something written in Go.
Google did a pretty amazing job of walking back the "replacement for C" talk and positioning Go as the language for web/micro/cluster/distribution/cloud/interconnected services.
But maybe I misinterpreted and (s)he meant Assembly.
Re: Kashmir: A statically typed Lispy language compiling to Go
#39Earlier quoted context omitted.
There are so many motivations for this (and so many lisp/go projects that are abandoned). This looks very promising and I hope it takes off. A few of the motivations: * A lisp with an amazing startup time * A lisp that can tap into a big and vivid ecosystem, like Clojure is tapping into Java's and its own * Cross compilation and self-contained binary (I've personally tried doing this with various lisps, and none of t…
so why not just use Go? less complexity - same benefits. you're basically saying it's somehow an advantage to program in s-expressions...
Have you ever talked to a Lisp enthusiast?
That's said, the project states more flexibility as a goal - specifically supporting generics. Between code generation and the cross-language compiler, writing generics (but generating non-generic Go code) should be somewhat easy to reason about.
Re: Kashmir: A statically typed Lispy language compiling to Go
#40I understand this project, along with most of the other "Lisp compiling to ..." projects are just for fun, but it's still annoying to see so many of them announced. Half the time it's a stretch to even call them "a Lisp." It's a little silly to call your language a Lisp if it's missing a lot of the stuff that Lisp is associated with. Does this Lisp even support macros? Just say it's a new language that uses s-express…
Here here! It seems like every week someone posts their pet flavor of lisp. This doesn't have an substance. How about coming up with something new!