owickstrom

Yeah main workflow is over ssh into desktop rig.

Agree with the above. It's during the night time reading with backlight that the difference from E-Ink is most clear, IMO. There's like a slight sense of depth between the surface and the pixels, if that makes sense, which I don't perceive with E-Ink in the same way. As noted above, "the Daylight panel feels like a screen" in that setting. With ambient daylight though, it is close to the E-Ink feel.

Yeah I watched the Linus tech tips review of it and the color one doesn't seem good. I'd rather try the monochrome one.

That's sick, very inspiring!

Right, but I didn't submit it.

Author here. It's title is "How [...]", which sounds a little less weird. :)

Thanks, will do!

Looks awesome! Can you use it with third-party external keyboards? Bluetooth or USB-C?

Author here! Happy to discuss this topic.

Author here. Thanks for the share! :)

Author here :) It's inspired by Haskell, yes, but not a dialect. Syntax is very much open for change still and that's really not the most important bit. Semantics are not like Haskell, more Go + polymorphism.

Project renamed to Oden and moved to: https://oden-lang.github.io/oden/

There were a bunch of reasons to change the name and I was going to create a GitHub organization for it anyway. Kashmir was not a good choice for Googleability and it turned out there's some city or region in the Kashmir region called "Golang"... :S

Sorry about the confusion!

It does!

  (let (([x : string] "hello"))
    (fmt.Println (+ x "owickstrom")))

Got something up there now.

Probably not the best option in the long run, but I didn't want to focus too much on that to begin with. Hooking into the Go compiler would be nice, perhaps that's something to look at when the Kashmir compiler can be written in Kashmir. :)

Thank you for the feedback! I have deliberately not done any big work on the Go FFI yet because, as you say, I have not thought all stuff through. This is very valuable input, thanks again!

It's from the Led Zeppelin song.

I realize that it is missing some of the defining features of a real Lisp, that's why I wrote "Lispy" in the HN title. However, there's surely some parts in the documentation that says it's a Lisp, and that might be a stretch right now.

Anyhow, I wanted to get some feedback on this project and perhaps involve people early on, so not having macros yet is nothing that I'm ashamed of. I hope to implement them soon.

And yes, there are a lot of good compilers out there. Kashmir is not a replacement for any of them or any of the established Lisps. :)

Human-written is the purpose, but as it builds on the LISP syntax, which is just simple data structures, generating it would be simple. I guess one could do a more Haskell-like syntax front-end for Kashmir and transform it.

Currently not at all. :) Haven't gotten that far yet, but I have it in mind. There will probably be a 1:1 mapping to these concepts in Kashmir.

Cool! :) I'll add more examples as soon as possible. Actually there's not much you can do with Kashmir at the moment, I've mostly focused on getting the basic model up so there's no library functions available etc. I have an idea about how to read the type signatures from compiled Go packages to be able to do simple interop between Kashmir and Go - no extern declarations or anything like that.

Good idea, thanks! I'll try to come up with something representative.