5 ms·

Stable yes. Buggy yes. There are all sorts of problems it gets stuck on. solve() is terrible.

by ethernot 2y ago

anthk 2y ago
Which Common Lisp interpreter/compiler did you use?
- ethernot 2y ago
  SBCL shipped via homebrew. SBCL is fine. It's Maxima that is full of bugs.
  - ethernot 2y ago
    I love how I get downvoted for every negative comment about this rather than an actual rebuttal of the issues. It's fucking shit. I hate every moment using Maxima. I'd rather pay for Mathematica but my org is too cheap for that. There you. Enjoy :) Even better, I'd rather do it by hand!
    - anthk 2y ago
      Fricas it's another CAS based on Common Lisp. BTW, the current SBCL versions are much better than the stable/oldstable releases such as the ones for Debian or Ubuntu LTS. Try Fricas, you might like it too. On Maxima, beware, because your package manager might ship you a Maxima version built with generic and unnoptimized CL compilers. GNU CLisp's performance against SBCL it's abysmal. On an n270 netbook, MCClim widgets built from Ultralisp (QuickLisp repo) run in realtime with SBCL. ECL it's a bit beter, closer to SBCL than CLISP. CLISP fails to compile due the lack of threading support on 32 bit. And even if it ran MCClim, it would run visibily redrawing widgets like Win32 ones under a Pentium as they did back in the day.
      - ethernot 2y ago
        Thanks for the suggestion - will look into it tomorrow. Not performance heavy here. What I do require is something that is less buggy though. Maxima has zero to no test suite so there are regularly stupid regressions that break everything.
    - ketralnis 2y ago
      > I love how I get downvoted for every negative comment about this rather than an actual rebuttal of the issues. It's because you haven't mentioned any issues. Just said it's terrible and buggy. Nobody can debug that for you based on that description. If they haven't experienced the same "issues", the best they can say is "nuh uh".

Stable yes. Buggy yes. There are all sorts of problems it gets stuck on. solve() is terrible.

anthk 2y ago

Which Common Lisp interpreter/compiler did you use?

ethernot 2y ago
SBCL shipped via homebrew. SBCL is fine. It's Maxima that is full of bugs.
- ethernot 2y ago
  I love how I get downvoted for every negative comment about this rather than an actual rebuttal of the issues. It's fucking shit. I hate every moment using Maxima. I'd rather pay for Mathematica but my org is too cheap for that. There you. Enjoy :) Even better, I'd rather do it by hand!
  - anthk 2y ago
    Fricas it's another CAS based on Common Lisp. BTW, the current SBCL versions are much better than the stable/oldstable releases such as the ones for Debian or Ubuntu LTS. Try Fricas, you might like it too. On Maxima, beware, because your package manager might ship you a Maxima version built with generic and unnoptimized CL compilers. GNU CLisp's performance against SBCL it's abysmal. On an n270 netbook, MCClim widgets built from Ultralisp (QuickLisp repo) run in realtime with SBCL. ECL it's a bit beter, closer to SBCL than CLISP. CLISP fails to compile due the lack of threading support on 32 bit. And even if it ran MCClim, it would run visibily redrawing widgets like Win32 ones under a Pentium as they did back in the day.
    - ethernot 2y ago
      Thanks for the suggestion - will look into it tomorrow. Not performance heavy here. What I do require is something that is less buggy though. Maxima has zero to no test suite so there are regularly stupid regressions that break everything.
  - ketralnis 2y ago
    > I love how I get downvoted for every negative comment about this rather than an actual rebuttal of the issues. It's because you haven't mentioned any issues. Just said it's terrible and buggy. Nobody can debug that for you based on that description. If they haven't experienced the same "issues", the best they can say is "nuh uh".