sokol-odin
v
sokol-odin | v | |
---|---|---|
4 | 219 | |
61 | 35,299 | |
- | 0.1% | |
8.9 | 9.9 | |
6 days ago | about 22 hours ago | |
C | V | |
- | MIT License |
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.
sokol-odin
-
Odin Programming Language
* etc
There is also the second issue that C is technically TWO languages: the C programming language and the C preprocessor. People mix the two together and things cannot be easily translated. A good basic example of this is people using `#define` for constants, and thus that name has no semantic meaning in the language itself. A translator has to try and make some semantic meaning from the intersection of these two languages, even if people don't make a distinction when making APIs.
And Odin's `foreign` system allows [1] for a lot of really nice things that most other languages cannot do so tersely. Here are two examples of demonstrating bindings of C libraries that feel as if they were native Odin libraries WITHOUT any wrappers:
* https://github.com/floooh/sokol-odin/blob/main/sokol/gfx/gfx... (and the rest)
-
Nim v2.0 Released
I maintain auto-generated bindings for my C libraries for Zig and Nim (and Odin and Rust - although the Rust bindings definitely need some love to make them a lot more idiomatic).
I think looking at the examples (which is essentially the same code in different languages) gives you a high level idea, but they only scratch the surface when it comes to language features (things like the Zig code not using comptime features):
Zig: https://github.com/floooh/sokol-zig/tree/master/src/examples
Nim: https://github.com/floooh/sokol-nim/tree/master/examples
Odin: https://github.com/floooh/sokol-odin/tree/main/examples
Rust: https://github.com/floooh/sokol-rust/tree/main/examples
-
I think Zig is hard but worth it
I'm actually dabbling with Odin a bit in the scope of language bindings for the sokol headers:
https://github.com/floooh/sokol-odin
It's a very enjoyable language!
-
I like the Odin programming language
I recently wrote a bindings generator to Odin for my C libraries, and the FFI is very well thought out, down to defining things like linker dependencies in the code. For instance see here:
https://github.com/floooh/sokol-odin/blob/main/sokol/gfx/gfx...
The only minor downside (compared to Zig) is that Odin still requires a separate C/C++ toolchain to actually build the C dependencies. But I guess that's a typical 1st-world-problem ;)
(but AFAIK Odins FFI system isn't in any way related or depending on LLVM).
v
-
V Language Review (2023)
Their site is clearly showing the language is in beta. The V documentation also states that autofree is WIP, and to use the GC instead. This isn't a corporate created language, but looks to be a true volunteer open source effort from people around the world.
Their community, in comparison to others, even has their discussions open and open threads for criticism[1]. These
[1]https://github.com/vlang/v/discussions/7610
-
Towards memory safety with ownership checks for C
V also has this https://github.com/vlang/v/blob/master/doc/docs.md#embed_fil...
- Vlang Release v0.4.4
- Vox: Upcoming open-source browser engine in V
- Building a web blog in V & SQLite
- bultin_write_buf_to_fd_should_use_c_write
- The V Machine Learning Roadmap and Ecosystem
-
Show HN: A new stdlib for Golang focusing on platform native support
Goroutines was the selling point for me until they decided to introduce telemetry in their toolchain; that was what forced me to stop using Golang as a whole.
About GC, I would say: if you implement C++'s RAII mechanism to replace garbage collection, then I believe this project will have a bright future.
My final question is the following: how `pcz` compares to V language, from a syntax's perspective [1]?
[1] https://github.com/vlang/v
- Hopefully, the V developers will establish a relationship with Microsoft.
-
The V Programming Language 0.4
V has the right to exist, have its supporters, and do things its own way. The creator and developers of V, from what I have seen, has always responded well to constructive criticism. Their language has discussions opened at their GitHub, unlike those for various other languages. They even have a thread for what people don't like and want improved about the language[1], again, something many other languages don't have.
A lot of what was going on initially, was coming from obvious competitors, to include being uncivil, inflammatory, and insulting. The initial "criticism" was not so much that, but false accusations of the language being a scam, vaporware, fraud, or didn't really exist. To include attacks and jealousy about its funding and having supporters. This was not any kind of "valid" criticism, that the creator or contributors of the language could reason about.
The "criticism" never died down, but rather after V was open-sourced and established itself on GitHub. The initial series of false accusations could not stand nor could the support it was getting be stopped. So, the rhetoric and targets shifted to whatever could be found to go after on the newly released alpha version of the language and its new website. In that new mix of what was being thrown at it, there were indeed some very valid criticisms, as can be found with any new language.
Constructive and valid criticism, is not the same as insults, trolling, misinformation, rivalry, or false accusations. There is clearly a difference. It's disingenuous to pretend something from one group is the same as the other, or that the intent behind what is being done is not different.
[1] https://github.com/vlang/v/discussions/7610
What are some alternatives?
linux - Linux kernel source tree
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
wayland - Core Wayland protocol and libraries (mirror)
go - The Go programming language
mvb-opencv - Minimum Viable Bindings to OpenCV for Nim
Odin - Odin Programming Language
RFCs - A repository for your Nim proposals.
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
sokol - minimal cross-platform standalone C headers
debug-trace-var - You do not have to write variable names twice in Debug.Trace
hn-search - Hacker News Search