unstruktured

5 ms·

1.
by unstruktured 3mo ago
very cool! maybe make a soccer one for world cup?
2.
by unstruktured 8mo ago
Technically you are right but too much mutation for my tastes and probably many other ocaml developers.
3.
by unstruktured 1y ago
18 years ago? Holy crap I feel old. I remember how disruptive the very stable 3 to completely unstable 4 was.
4.
by unstruktured 1y ago
There is absolutely no reason to use double semicolons in practice. The only place you really should see it is when using the repl.
5.
by unstruktured 1y ago
Thanks for restoring my sanity. Was quite confused of the value added by the author.
6.
by unstruktured 1y ago
To F# from what previously?
7.
by unstruktured 2y ago
"Uh...the answer's not in the box, it's in the band".
8.
by unstruktured 2y ago
I don't think he touched on whether server side is a more valid use case, but was nice to read someone elses take on using it for a desktop. Thanks for the contribution. He did find functional programming to be sort of mystic so I don&
9.
by unstruktured 2y ago
I wish they would at least rename the company to "ClosedAI" because that's exactly what it is at this point.
10.
by unstruktured 2y ago
What, to you, is an ultra strong type system? Both OCaml and Haskell are used in plenty of non academic contexts. Do you mean something like Coq or F*?
11.
by unstruktured 2y ago
Oh that's a solved problem since 1969. It's called "unix". Everything is a file which can be processed as a byte stream. Composition is a breeze- can't be any more general than that! (I kid, mostly :)).
12.
by unstruktured 2y ago
I think when people say safest they mean the safest "C like" language with zero cost abstractions.
13.
by unstruktured 2y ago
Interesting point. I never inferred a strong connection between dependent types and the unification of records and modules. Maybe a real PL theorist around here can provide insights on that subject.
14.
by unstruktured 2y ago
F* + 1ml ( https://people.mpi-sws.org/~rossberg/1ml/ ) would be the ultimate experience. I was born too early!
15.
by unstruktured 2y ago
macros can help with this if you can narrow down the traits you want to support. https://doc.rust-lang.org/reference/macros.html
16.
by unstruktured 2y ago
If you use Jane street's base, core, and async libraries, you already have most of the tooling you need.
17.
by unstruktured 2y ago
Like matrix/element chat? https://matrix.org/
18.
by unstruktured 2y ago
decentralized approaches would be resilient to that.
19.
by unstruktured 2y ago
To me, implementing an async api using algebraic effects is the end game. Gets rid of the need of an async keyword and no monads required!
20.
by unstruktured 3y ago
Big fan of kdenlive. I switched to it after one too many openshot bugs. Admittedly I always want kde apps to be good but in this case it actually is. Openshot was easier to learn though, personally.
21.
by unstruktured 3y ago
While we are on the subject, there's also neovim-qt: https://github.com/equalsraf/neovim-qt
22.
by unstruktured 3y ago
Keep up the good work! I love KDE.
23.
by unstruktured 3y ago
pypy and cpython don't mix well with each other so you have to create a whole new universe of packages for pypy. Interop with c libraries also adds complexity to the transition. In addition, vanilla python is finally starting to tackle
24.
by unstruktured 3y ago
Not familiar with said regulations, but Ada was a good example of not using C++ for these very reasons in a military context.
25.
by unstruktured 3y ago
I like both OCaml and Rust, especially OCaml, but even after 2 years of Rust I'm still way more productive in OCaml. Unless it's absolutely essentially, I really don't want to have track the life times of my objects so explic
26.
by unstruktured 3y ago
Been using Kubuntu nearly since it's inception and have always loved it. For audio players I stubbornly prefer Clementine for it's lighter handed approach, although I guess I should give Elisa a shot now. Would be curious to know
27.
by unstruktured 3y ago
You don't need personal reasons to dislike JS.
28.
by unstruktured 3y ago
The author of that link references the top 25 bugs, one (#12) of which is Null pointer dereferencing- static typing outright eliminates that bug. Not to mention that range checking is also fixable by using optionals rather than assuming the
29.
by unstruktured 3y ago
Unfortunately the typed kwargs are NOT composable :(.
30.
by unstruktured 3y ago
This is the year of the linux desktop! Finally!

More ›