freedesktop-sdk
ocaml
freedesktop-sdk | ocaml | |
---|---|---|
53 | 119 | |
- | 5,162 | |
- | 0.7% | |
- | 9.9 | |
- | 6 days ago | |
OCaml | ||
- | 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.
freedesktop-sdk
-
The Return of the Frame Pointers
I think I might have confused two unrelated posts. The one that references Polar Signals is this one:
https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/...
So not a perf issue there, but they don't think the workflow is suitable for whole-system profiling. Perf issues were in the context of `perf` using DWARF:
https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/...
- Finally mesa version 23.1.1 for fedora 38 has been published for testing 11 hours ago. It comes with quite important features like vulkan gpl for RADV to fight stutters in games and for better performance.
-
Yocto
But the fd-sdk https://gitlab.com/freedesktop-sdk/freedesktop-sdk and gnome build meta https://gitlab.gnome.org/GNOME/gnome-build-meta projects can prove as good references.
-
Rant: Desktop Sandboxing
With all of these hypothetical features out of the way and looking just at current release software, Flatpak allows you to do so much stuff that isn't accessible for a not-so-techy user. Custom installation folder? Yep. Running mesa-git GPU drivers? You got it. Any way to easily do this via GUI? In typical Linux fashion, nope. For a GUI focused packaging format this is a big letdown.
- Issue found for: Steam Deck Issue With Flatpak Hardware Decoding
- Steam Flatpak. Tried RADV_PERFTEST=gpl with proton-ge-54 but doesnt seem to be working when compared to using it with Bottles. Please see if I did it right.
-
Is there any way to force a specific Mesa driver for applications when multiple Mesa driver versions have been installed?
Link to (official?) how-to: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/wikis/Mesa-git
-
Fedora Workstation 38 Is Shaping Up To Be Another Fantastic Release
You can load up Mesa GIT using environment variables, see here. Honestly what I miss the most from flatpak Steam is properly working non-Steam shortcuts, but I've given up on that.
- Are all AMD GPUs equally well supported?
-
PSA: The new OBS update breaks VA-API encoding when used with the Flatpak
It was my understanding that the packages for vaapi are just put into the -extra version of the sdk so app maintainers can opt out, but they are still available if they want to use them. See https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/10616
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?
flatpak - Linux application sandboxing and distribution framework
Alpaca-API - The Alpaca API is a developer interface for trading operations and market data reception through the Alpaca platform.
Flatseal - Manage Flatpak permissions
VisualFSharp - The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio
argos-translate - Open-source offline translation library written in Python
dune - A composable build system for OCaml.
xdg-desktop-portal-gtk - Gtk implementation of xdg-desktop-portal
TradeAlgo - Stock trading algorithm written in Python for TD Ameritrade.
us.zoom.Zoom
melange - A mixture of tooling combined to produce JavaScript from OCaml & Reason
oneTBB - oneAPI Threading Building Blocks (oneTBB)
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266