anmonteiro90

5 ms·

1.
Reducing Latency by 83% with Esoteric Linux Process Flags(recall.ai)
4 points by anmonteiro90 2y ago|0 comments
2.
Melange 2.0: Compile OCaml / ReasonML to JavaScript(anmonteiro.substack.com)
10 points by anmonteiro90 3y ago|1 comments
3.
Ahrefs frontend now built with Melange (OCaml –> JavaScript)(tech.ahrefs.com)
2 points by anmonteiro90 3y ago|0 comments
4.
by anmonteiro90 3y ago
Thank you :-) You also make a good point. I didn't go into too much detail about ReasonML in another comment, but I know Jordan (@jordwalke) has plans for a ReasonML v4 [1] with slight syntax improvements. I don't currently know t
5.
by anmonteiro90 3y ago
Hi Paul, appreciate the kind words. Your perspective on the project is exactly how we think about it: Melange provides the tooling for fullstack (@davesnx likes to call them Universal) Reason/OCaml applications. I suspect my time in Cl
6.
by anmonteiro90 3y ago
ReasonML purely as a syntax layer on top of OCaml is still being updated and released[1]. Incidentally, I'm one of the maintainers of that project too :-) With this Melange release, we're hoping to somewhat revive ReasonML and cha
7.
by anmonteiro90 3y ago
Melange approaches the problem from the OCaml perspective. It inserts itself within the OCaml community, so you need the OCaml Platform[1] tooling to install and use it. This way, you get all the benefits of having a native toolchain and bu
8.
by anmonteiro90 3y ago
Melange and ReScript target different audiences. AFAIU, ReScript is a new language that offers an alternative to TypeScript. Melange approaches the problem from the perspective of compatibility with OCaml / ReasonML. We've focused
9.
Melange 1.0: Compile OCaml / ReasonML to JavaScript(buttondown.email)
195 points by anmonteiro90 3y ago|54 comments
10.
by anmonteiro90 7y ago
I don't wanna nitpick too much (I realize that's all I'm doing). I just wanted to caution against stating what you perceive as a fact without any backing references.
11.
by anmonteiro90 7y ago
That makes sense but it's not what comes across. The sentence immediately after says that "the language continues to grow". That's what I'm questioning.
12.
by anmonteiro90 7y ago
It'd be interesting to back the claim that "Clojure is (slowly) eating the world.". Interestingly, that's absolutely not my perspective and I don't see any sources for that statement in the post.
13.
Conduct Unbecoming of a Hacker (2014)(sealedabstract.com)
5 points by anmonteiro90 7y ago|0 comments
14.
OCaml Runtime for AWS Lambda(github.com)
4 points by anmonteiro90 8y ago|0 comments
15.
Autochrome – Structural diffs for Clojure source code(fazzone.github.io)
6 points by anmonteiro90 9y ago|0 comments
16.
Retroactive Data Structures (2007) [pdf](erikdemaine.org)
3 points by anmonteiro90 9y ago|0 comments
17.
Reason React's new website(reasonml.github.io)
3 points by anmonteiro90 9y ago|0 comments
18.
by anmonteiro90 9y ago
He was referring to these https://github.com/cljsjs/packages/blob/950064853c8391ac7a88...
19.
by anmonteiro90 9y ago
strings in `:npm-deps` should just work. I'm more concerned about the npm syntax for `@namespace/package@version` which I'm not sure is valid. If it doesn't work though, please open a ticket so we can fix it!
20.
by anmonteiro90 9y ago
We shell out to `npm` to install the dependencies you specify, so I don't see why it wouldn't work.
21.
by anmonteiro90 9y ago
Native CLJS libraries are regular JARs that you add to your classpath. Most people publish them to Clojars[1] (which also has Clojure libs). Maven Central may also have some. [1] http://clojars.org
22.
by anmonteiro90 9y ago
This functionality is opt-in, so you can still live on your island if you'd like :-)
23.
by anmonteiro90 9y ago
Just to add to this statement, even in cases where externs will still be necessary, adding CLJSJS packages[1] to your project's classpath will result in those externs being used even if you don't use the libraries that the package
24.
On Lumo's (ClojureScript REPL) Growth and Sustainability(anmonteiro.com)
1 points by anmonteiro90 9y ago|0 comments
25.
Requiring Node.js modules from ClojureScript namespaces(anmonteiro.com)
6 points by anmonteiro90 10y ago|0 comments
26.
Compiling ClojureScript Projects Without the JVM(anmonteiro.com)
13 points by anmonteiro90 10y ago|2 comments
27.
by anmonteiro90 10y ago
Why not?! Sounds like a great idea. Happy to see someone help me with that
28.
by anmonteiro90 10y ago
Just like you'd do in Node. Add deps to a package.json and npm install. Then just `(js/require "your-package")`
29.
by anmonteiro90 10y ago
Unfortunately, Node.js and V8 seem to be about 2.5X slower than JavaScriptCore for bootstrapped ClojureScript. I haven't found a way around it. I also don't mean to trick anyone and this is explained in the post.
30.
by anmonteiro90 10y ago
There are a number of pre-bundled libraries in Lumo. `cljs.nodejs` is actually part of ClojureScript so it's included too.

More ›