-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
-
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
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
> More concerning is that un-named parameters are a compiler error
I've been ranting about it many times. Most recently: https://news.ycombinator.com/item?id=32145520
There is an upstream issue about it where we should probably get our voices heard, it's encouraging to see many people in that thread that are opposed to that change, but I don't think the core devs are considering any alternative to unused variables just being errors, which is disheartening.
https://github.com/ziglang/zig/issues/335
This is by far my biggest annoyance with Go, more than writing if err != nil or the lack of generics.
I feel I write code in a different way than other people. Some think a lot before writing, and can stop to fix errors, while I tend to experiment, throwing stuff at the wall and iterating quickly, and only then polishing. Stopping every iteration during my experimentation phase to lint my code because the compiler is pedantic and stubborn just slows me down immensely and turns me off a language.
The evcxr project https://github.com/google/evcxr is implementing what amounts to an experimental Rust REPL. (Though there's inherently something a bit weird about a REPL for C/C++-like languages, where the phase separation between compile- and run-time is so inherent to the programming model.)
I believe this tracks it: https://github.com/rust-lang/rust/issues/32838