3 ms·

Demo videos: https://next.atlas.engineer/#features https://next.atlas.engineer/#features I don't get the choice of Lisp. I don't mind it, I use Emacs, but a mo

Demo videos: https://next.atlas.engineer/#features https://next.atlas.engineer/#features I don't get the choice of Lisp. I don't mind it, I use Emacs, but a more popular language can have more complete platform bindings: > Sadly, the GTK bindings are not in a shape that is enough to fulfill our needs. We've tried to get Next running with CL-CFFI-GTK on GNU/Linux for many months, to no avail.

jmercouris 8y ago
Well, the Lisp part is for the reprogrammability of it all, the inspectability. You can on-the-fly edit a compiled version of Next, which is pretty cool I think!
- dmortin 8y ago
  Isn't there some popular language with the same capabilities? Is it a Lisp speciality?
  - jmercouris 8y ago
    It is a Lisp specialty, yes. Lisp has other facilities as well, such as meta-programmability, you can define new syntax, make macros etc, it is a very powerful language!
  - snaky 8y ago
    Nowadays it's usually called 'hot reload' and everybody hype about how cool is that in React Native and Flutter.
    - jmercouris 8y ago
      2hype4me
    - always_good 8y ago
      Well, those are GUI toolkits. A lisp doesn't compete with them. Any GUI that you build with a lisp still needs to support that sort of thing. Also, when people praise a feature that RN or Flutter have, they are really saying that it's nice that a tool that's practical today has the feature, not that it's never been done before. That something has been done before isn't all that interesting. If you don't realize this, you become the person running around unhelpfully reminding everyone that smalltalk or a lisp machine had a feature years ago, yet neither offers a practical way to build mobile apps today unlike RN/Flutter.
    - ericlewis 8y ago
      It’s is pretty cool, the alternative being compiling. I know there was a way to hot reload swift, when I tried back in like 2016. But it required strange swizzling, and still had a compilation lag (not that Babel doesn’t, but it’s usually faster)
ncmncm 8y ago
Lisp appears to be the whole point of the effort, so Lisp problems are just to be endured and, they hope, overcome. Not having a flagship modern application has kept Lisp on the margins. Emacs no longer suffices to maintain the language's edge, not least because Emacs Lisp is not a modern dialect. It remains to be seen what improvements to the language or its ecosystem will be needed to support this development, but there is no substitute for trying.
- jmercouris 8y ago
  well said! another hope is indeed to increase the popularity of Lisp by providing a "killer" application. Next is still in its infancy, but we have had barely any time at all, and it is on its 5th rewrite, and already it is quite powerful!

jmercouris 8y ago

Well, the Lisp part is for the reprogrammability of it all, the inspectability. You can on-the-fly edit a compiled version of Next, which is pretty cool I think!

dmortin 8y ago
Isn't there some popular language with the same capabilities? Is it a Lisp speciality?
- jmercouris 8y ago
  It is a Lisp specialty, yes. Lisp has other facilities as well, such as meta-programmability, you can define new syntax, make macros etc, it is a very powerful language!
- snaky 8y ago
  Nowadays it's usually called 'hot reload' and everybody hype about how cool is that in React Native and Flutter.
  - jmercouris 8y ago
    2hype4me
  - always_good 8y ago
    Well, those are GUI toolkits. A lisp doesn't compete with them. Any GUI that you build with a lisp still needs to support that sort of thing. Also, when people praise a feature that RN or Flutter have, they are really saying that it's nice that a tool that's practical today has the feature, not that it's never been done before. That something has been done before isn't all that interesting. If you don't realize this, you become the person running around unhelpfully reminding everyone that smalltalk or a lisp machine had a feature years ago, yet neither offers a practical way to build mobile apps today unlike RN/Flutter.
  - ericlewis 8y ago
    It’s is pretty cool, the alternative being compiling. I know there was a way to hot reload swift, when I tried back in like 2016. But it required strange swizzling, and still had a compilation lag (not that Babel doesn’t, but it’s usually faster)

ncmncm 8y ago

Lisp appears to be the whole point of the effort, so Lisp problems are just to be endured and, they hope, overcome. Not having a flagship modern application has kept Lisp on the margins. Emacs no longer suffices to maintain the language's edge, not least because Emacs Lisp is not a modern dialect. It remains to be seen what improvements to the language or its ecosystem will be needed to support this development, but there is no substitute for trying.

jmercouris 8y ago
well said! another hope is indeed to increase the popularity of Lisp by providing a "killer" application. Next is still in its infancy, but we have had barely any time at all, and it is on its 5th rewrite, and already it is quite powerful!