Forscape VS gleam

And if you like mathematical languages, you should check out Forscape :)

You can use the free GitHub runners to execute regression tests on Linux, Windows, and Mac. I recommend testing with 32bit compilation as well as 64bit- it has a way of smoking out bugs. You could take a look at the GitHub actions on my Forscape repo in the .github folder, although it's probably not the most idiomatic runner scripting, but it is a C++ project like yours.

When I was developing a typesetting text editor for Forscape, I struggled to get traction until stumbling on the following plan: 1) Implement the document data structure and get it rendering to the screen 2) Support non-mutating interactions, such as clicking to move the text cursor, selecting, copying, etcetera 3) Support mutating interactions, such as keyboard input, deleting, and pasting. You'll probably use the Command pattern to support undo/redo of mutations

The project is Forscape, although the language part is made a bit complicated because a goal of the project is creating an editor that supports typeset code with IDE interaction

Finally adding multi-file support to Forscape. The frontend UI aspects are completed and I'm quite happy with the result. The app is Unicode heavy and QString's UTF-16 encoding is an annoyance; I would much prefer if Qt relied on std::string even. But the signal/slot mechanism lets you achieve some complicated behaviour with minimal complexity, and Qt looks great.

Here's an example from a project. The first step installs Qt, the second step clones my repo on the runner, then a bit more setup with Conan, then building and running.

I've been working on the Key CAS project (Imgur Screenshot), CAS being an acronym for Computer Algebra System, and "Key" a judiciously chosen title. This was my third time attempting CAS- this iteration was a huge improvement, but I still find it to be a damn hard problem. The GUI comes from the open source project Forscape, a scientific computing environment written in C++.

It gets fun when you go beyond flat symbols and start supporting 2D notation, like fractions and matrices. Probably not worth the hassle for most things, but I think it makes matrix expressions more compact with better readability.

I've been working on a mathematical programming language, Forscape. Currently it's entirely numerical, but I'm building a CAS separately which I hope to use in the language.

Forscape is a scientific computing language in development. It supports first-class matrices and common matrix operations. The language reached a milestone when it achieved similar performance to other prominent scientific langs on a computationally involved numerical problem from my graduate school years. At this point, I am unsure where the development should go next and I would appreciate advice. What do you find missing in scientific computing languages? What are essential features that you need/enjoy?

Want a friendly language for building safe systems at scale? Gleam is here for you. It features modern and familiar syntax, that's reliable and scalable. Gleam runs on an Erlang virtual machine, and can run plenty of concurrent tasks. It comes with a compiler, build tool, formatter, editor integrations, and package manager all built in so you can get started right away. Congrats to the team on shipping your first major version 🙌.

While I love Clojure, I have to agree about tooling. I recently started using Gleam* and was impressed at how easy it was to get up and running with the CLI tool. I think this is an important part of getting people to adopt a language.

* https://gleam.run/

If you use languages that compile to WASM (such as Gleam https://gleam.run), and can also run Postgres via WASM, then it opens very interesting offline scenarios with codebases which are similar on both the client and the server, for instance.

Recently, Gleam has gained more popularity, and a lot of developers (including me) are learning it. At the time of this writing, it has exceeded 14k stars on GitHub; it grew really fast for the last month.

Oh, strange that github had a date of 2016 on this one: https://github.com/gleam-lang/gleam/issues/2

I was just going by that, though I do remember checking out gleam 5 years ago or so.

Re: macros, I really do think they’re a big deal and all the other newer languages I’ve used, such as Rust have some kind of macros or powerful meta programming features.

For older languages, a few, like Ruby have enough meta programmability to make nice DSLs, but many others don’t. Given the choice, I’d much rather have Elixir/Clojure style macros than other meta-programming facilities I’ve seen so far.

I had been only following this language with some interest, I guess this was born in gitlab not sure if the creator(s) still work there. This is what I'd have wanted golang to be (albeit with GC when you do not have clear lifetimes).

But how would you differentiate yourself from https://gleam.run which can leverage the OTP, I'd be more interested if we can adapt Gleam to graalvm isolates so we can leverage the JVM ecosystem.

I don't think the implementation itself is at fault, but yes, I do think that the design of dialyzer makes it an (at times) faulty type checker. The unfortunate reality of a type checker that fails sometimes is that it makes it mostly useless because you can never trust that it'll do the job.

To be clear, I've had it fail in a function where I've literally specced that very function to return a `binary` but I'm returning an `integer` in one of the cases. This is a very shallow context but it can still fail. Now add more functions, maybe one more `case`.

I think an entire rethink of type checking on the BEAM had to be done and that's why eqWalizer[0] was created and why Elixir is looking to add an actual sound, well-developed type checker. Gleam[1] I would assume is just a Hindley-Milner system so that's completely solid. `purerl`[2] is just PureScript for the BEAM so that's also Hindley-Milner, meaning it's solid. `purerl` has some performance issues caused by it compiling down to closures everywhere but if you can pay that cost it's actually pretty fantastic. With that said my bet for the best statically typed experience right now on the BEAM would be `gleam`.

0 - https://github.com/WhatsApp/eqwalizer

1 - https://gleam.run

2 - https://github.com/purerl/purerl