OK
ocaml
Our great sponsors
OK | ocaml | |
---|---|---|
12 | 119 | |
497 | 5,156 | |
- | 1.6% | |
0.0 | 9.9 | |
over 1 year ago | 3 days ago | |
Go | OCaml | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
OK
-
Looking for programming languages created with Go
- https://github.com/jesseduffield/OK
- [humour/satire] Just came across the "OK?" language, thought people here might appreciate it ."OK?s mission is to do away with the needless complexity of today's programming languages and let you focus on what matters".
- [RE: ternary operator] Disgusting, we agree. Einstein, Tesla, and Newton all died long ago, so there's really only a handful of humans left on Earth who are capable of parsing that stupifying syntax. What does the question mark mean? What does the colon mean?
-
The OK? Programming Language
I'm not certain, but this first example seems like they are joking: https://github.com/jesseduffield/OK#conditionals
Does anyone find the C ternary operator conditional expression hard to read?
And, in Lisps, all conditionals are expression special forms (there's no distinction between statements and expressions like in C), so it's even more comfortable there:
(if isprod "prod" "dev")
- "You shouldn't need to use juvenile word separators like underscores or camelCase because if you can't capture the meaning of a variable in a single word, that's a sign that you need to refactor."
-
Go'ing Insane Part Two: Partial Privacy
Your OK? language is brilliant. Our codebase rewrite is underway.
- OK? Programming Made Simple Again
ocaml
-
Autoconf makes me think we stopped evolving too soon
> OCaml’s configure script is also “normal”
If that’s this OCaml, it has a configure.ac file in the root directory, which looks suspicious for an Autotools-free package: https://github.com/ocaml/ocaml
-
The Return of the Frame Pointers
You probably already know, but with OCaml 5 the only way to get flamegraphs working is to either:
* use framepointers [1]
* use LBR (but LBR has a limited depth, and may not work on on all CPUs, I'm assuming due to bugs in perf)
* implement some deep changes in how perf works to handle the 2 stacks in OCaml (I don't even know if this would be possible), or write/adapt some eBPF code to do it
OCaml 5 has a separate stack for OCaml code and C code, and although GDB can link them based on DWARF info, perf DWARF call-graphs cannot (https://github.com/ocaml/ocaml/issues/12563#issuecomment-193...)
If you need more evidence to keep it enabled in future releases, you can use OCaml 5 as an example (unfortunately there aren't many OCaml applications, so that may not carry too much weight on its own).
[1]: I haven't actually realised that Fedora39 has already enabled FP by default, nice! (I still do most of my day-to-day profiling on an ~CentOS 7 system with 'perf --call-graph dwarf', I was aware that there was a discussion to enable FP by default, but haven't noticed it has actually been done already)
-
Top Paying Programming Technologies 2024
11. OCaml - $91,026
-
OCaml: a Rust developer's first impressions
> It partially helps since it forces you to have types where they matters most: exported functions
But the problém the OP has is not knowing the types when reading the source (in the .ml file).
> How would it feels like to use list if only https://github.com/ocaml/ocaml/blob/trunk/stdlib/list.ml was available,
If the signature where in the source file (which you can do in OCaml too), there would be no problem - which is what all the other (for some definition of "other") languages except C and C++ (even Fortran) do.
No, really, I can't see a single advantage of separate .mli files at all. The real problém is that the documentation is often worse too, as the .mli is autogenerated and documented afterwards - and now changes made later in the sources need to be documented in the mli too, so anything that doesn't change the type often gets lost. The same happens in C and C++ with header files.
-
Bringing more sweetness to ruby with sorbet types 🍦
If you have been in the Ruby community for the past couple of years, it's possible that you're not a super fan of types or that this concept never passed through your mind, and that's totally cool. I myself love the dynamic and meta-programming nature of Ruby, and honestly, by the time of this article's writing, we aren't on the level of OCaml for type checking and inference, but still, there are a couple of nice things that types with sorbet bring to the table:
-
What is gained and lost with 63-bit integers? (2014)
Looks like there have been proposals to eliminate use of 3 operand lea in OCaml code (not accepted sadly):
https://github.com/ocaml/ocaml/pull/8531
-
Notes about the ongoing Perl logo discussion
An amazing example is Ocaml lang logo / mascot. It might be useful to talk with them to know what was the process behind this work. The About page camel head on Perl dot org header is also a pretty good example of simplification, but it's not a logo, just a friendly illustration, as the O'Reilly camel is. Another notable logo for this animal is the well known tobacco industry company, but don't get me started on that (“good” logo, though, if we look at the effectiveness of their marketing).
-
What can Category Theory do?
Haskell and Agda are probably the most obvious examples. Ocaml too, but it is much older, so its type system is not as categorical. There is also Idris, which is not as well-known but is very cool.
- Playing Atari Games in OCaml
-
Bloat
That does sound problematic, but without the code it is hard to tell what is the issue. Typically, compiling a 6kLoc file like https://github.com/ocaml/ocaml/blob/trunk/typing/typecore.ml takes 0.8 s on my machine.
What are some alternatives?
automod - Pull in every source file in a directory as a module
Alpaca-API - The Alpaca API is a developer interface for trading operations and market data reception through the Alpaca platform.
vigil - Vigil, the eternal morally vigilant programming language
VisualFSharp - The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio
comet - A programming language implementation in Go.
dune - A composable build system for OCaml.
gojq - Pure Go implementation of jq
TradeAlgo - Stock trading algorithm written in Python for TD Ameritrade.
rye - homoiconic dynamic programming language with some new ideas
melange - A mixture of tooling combined to produce JavaScript from OCaml & Reason
slurp - Slurp is a highly customisable LISP toolkit for Go applications. 💻
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266