Live data from Hacker News

OxCaml - a set of extensions to the OCaml programming language.

oxcaml.org

121–128 of 128 posts

Re: OxCaml - a set of extensions to the OCaml programming language.

#121
post #7

The Janet Street folks, who created this, also did an interesting episode[0] of their podcast where they discuss performance considerations when working with OCaml. What I was curious about was applying a GC language to a use case that must have extremely low latency. It seems like an important consideration, as a GC pause in the middle of high-frequency trading could be problematic. [0] https://signalsandthreads.com…

I actually asked Ron Minsky about exactly this question on Twitter[0]: Me: [W]hy not just use Rust for latency sensitive apps/where it may make sense? Is JS using any Rust? Minsky: Rust is great, but we get a lot of value out of having the bulk of our code in a single language. We can share types, tools, libraries, idioms, and it makes it easier for folk to move from project to project. And we're well on our way to g…

Well on their way.. by having to write a ton of C for the interpreter. I think it’s really imprudent for them not to be using Rust yet for critical sections.

Re: OxCaml - a set of extensions to the OCaml programming language.

#122

Earlier quoted context omitted.

Error squiggles and ocamlformat stopped working for me after the first time I restarted VS Code, compared to regular OCaml. They do work fine through the Dune CLI though.

Hmm. Did you install ocaml-lsp-server on the OxCaml switch? I also tend to run dune in polling mode (-w), not sure if that matters…

Fwiw I had the same experience as debugnik with ocaml-lsp-server installed, irrespective of whether I built in polling mode.

Re: OxCaml - a set of extensions to the OCaml programming language.

#123
post #3

So this is "oxidized" because it tries to achieve the same features as Rust (e.g. "fearless concurrency" is mentioned, and avoiding GC)... Not because it actually uses Rust in any way right? Slightly confusing.

It's ironic of course because Rust (the language) is named after the fungus called Rust, rather than iron-oxide

[deleted]

Re: OxCaml - a set of extensions to the OCaml programming language.

#124
post #93
post #7

The Janet Street folks, who created this, also did an interesting episode[0] of their podcast where they discuss performance considerations when working with OCaml. What I was curious about was applying a GC language to a use case that must have extremely low latency. It seems like an important consideration, as a GC pause in the middle of high-frequency trading could be problematic. [0] https://signalsandthreads.com…

The problem is not a GC language per se, people keep putting all GC languages in the same basket. The real issue is being a GC language, without support for explicit manipulation of stack and value types. Want a GC language, with productivity of GC languages, with the knobs to do low level systems coding? Cedar, Oberon language family, Modula-3, D, Nim, Eiffel, C#, F#, Swift, Go.

.NET AOT compiles comically slowly. It makes C++ look like Ocaml. I have no idea how anyone uses it for anything serious.

Re: OxCaml - a set of extensions to the OCaml programming language.

#126
post #83

Earlier quoted context omitted.

If you follow the installation instructions on oxcaml.org, you’ll get a patched Merlin with LSP support etc. It’s not perfect, but does mostly work out of the box with VSCode and the OCaml Platform extension.

Error squiggles and ocamlformat stopped working for me after the first time I restarted VS Code, compared to regular OCaml. They do work fine through the Dune CLI though.

Did you change the opam switch that vscode extension uses? It needs to be set to the oxcaml switch - you can do this via the "Ocaml: Select a Sandbox for this Workspace" command.

Re: OxCaml - a set of extensions to the OCaml programming language.

#128

Earlier quoted context omitted.

Error squiggles and ocamlformat stopped working for me after the first time I restarted VS Code, compared to regular OCaml. They do work fine through the Dune CLI though.

Did you change the opam switch that vscode extension uses? It needs to be set to the oxcaml switch - you can do this via the "Ocaml: Select a Sandbox for this Workspace" command.

Yes I did, I'm used to working with opam, and when I first changed the switch it worked until I restarted VS Code. But since then I haven't managed to make it work again.
Post reply on HN