OpenVi
Odin
OpenVi | Odin | |
---|---|---|
8 | 84 | |
151 | 5,684 | |
- | 3.3% | |
7.5 | 10.0 | |
7 days ago | 4 days ago | |
C | Odin | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" 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.
OpenVi
- Portable OpenBSD vi for Unix systems
- Genealogy of Vim (2017)
-
OpenVi: Portable OpenBSD vi for Unix systems
The behavior of the traditional vi is much different than vim and other clones. Nvi was a actually a re-implementation of the traditional vi for 4BSD (to be clean of AT&T code) and thus was originally intended to be bug-for-bug compatible, but breaking away where the original vi behavior was nonsensical or terrible.
For vim, `set compatible` or `set cp` is close, but still not traditional vi by any means.
A multibyte variant of the tradition vi is maintained - https://github.com/n-t-roff/heirloom-ex-vi/.
Nvi (now on version 1.8x) is also maintained - https://repo.or.cz/nvi.git
Nvi2 is yet another fork of Nvi, https://github.com/lichray/nvi2
Despite the very similar names, all of these editors have a variety of different features, and are structured very differently.
Nvi has a concept of a front-end and a back-end (which uses the BDB database). OpenVi uses the OpenBSD version of Berkeley DB which derives from 1.85. Nvi (1.8x) provides a minimal version of code also derived from that release intended from use with Nvi, and (IIRC) also provides support for using Db3/4/5. Similar situation for Nvi2.
Nvi 1.8 has been structured where a third library layer has been added, which doesn't exist in OpenBSD's vi or OpenVi. There is scripting support (Tcl, Perl, etc.) and GUI code in the other various forks ... all of these support various different options as well.
I should probably make a matrix of these, but you can get an idea by looking at the settable options implemented in each of the variants (as they historically include a comment to document from where the option originated):
OpenVi: https://github.com/johnsonjh/OpenVi/blob/22c2a7022e31d91e09e...
OpenBSD vi: https://github.com/openbsd/src/blob/master/usr.bin/vi/common...
Nvi2: https://github.com/lichray/nvi2/blob/5fcdc13656500a8c5b4c073...
Nvi1: https://repo.or.cz/nvi.git/blob/HEAD:/common/options.c#l52
-
Hacker News top posts: Feb 19, 2022
OpenVi: Portable OpenBSD vi for Unix systems\ (22 comments)
Odin
-
Zig, Rust, and Other Languages
There's also Odin[0] too. I tried using them all and Odin was pretty nice. Nim is also good too but a lot more features.
But - I concluded that language matters a lot less compared to APIs. Yes, the language should have enough good features to let the programmers express themselves, but overall well designed APIs matter a lot more than language. For example -tossing most of the C stdlib and following a consistent coding style (similar to one described here -[1]), with using Arenas for memory allocation, I can be just as productive in C.
[0] - https://odin-lang.org
-
Odin Programming Language
I highly recommend looking at:
* The Overview: <https://odin-lang.org/docs/overview/>
* examples/demo: <https://github.com/odin-lang/Odin/blob/master/examples/demo/...>
As for the first example: a basic lexing example is probably boring, but it does show some basic ideas of what the language is about. If people want to write better examples or just reorder the current ones, please feel free to make an issue or PR on the website's GitHub page: <https://github.com/odin-lang/odin-lang.org>.
-
babel tree
I use Odin primarily, it’s C-level but pascal/Go syntax and inspiration https://odin-lang.org/
- Botlib: Telegram Bots in C by Antirez
- "Odin is a general-purpose programming language with distinct typing built for high performance, modern systems and data-oriented programming."
- Austral Programming Language
- Small Joys with Odin
-
Can't decide what engine/library/framework I want to master
Website: https://odin-lang.org/
-
Download Odin and get started today! Includes binding to popular video game libraries
Get it from the website: https://odin-lang.org/ -- Odin includes bindings to popular gamedev libraries & APIs such as Raylib, SDL, DirectX, OpenGL and Vulkan.
- Check this odin file out for a demo of many of the language's features. It comes with the compiler inside the examples folder. I refer to it all the time when I need to figure out how to do something.
What are some alternatives?
nvi2 - A multibyte fork of the nvi editor for BSD
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
nextvi - Next version of neatvi (a small vi/ex editor) for editing bidirectional UTF-8 text
v - Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io
grist-core - Grist is the evolution of spreadsheets.
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).
src - Read-only git conversion of OpenBSD's official CVS src repository. Pull requests not accepted - send diffs to the tech@ mailing list.
rust - Empowering everyone to build reliable and efficient software.
heirloom-ex-vi - The Traditional Vi (vi with many enhancements from Gunnar Ritter)
carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
signify - OpenBSD tool to sign and verify signatures on files. Portable version.
Beef - Beef Programming Language