-
Puts Debuggerer
Ruby library for improved puts debugging, automatically displaying bonus useful information such as source line number and source code.
-
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.
-
F#
Discontinued Please file issues or pull requests here: https://github.com/dotnet/fsharp (by fsharp)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
I tried Go too, but call me crazy I just couldn't swallow seeing github.com all over the code when you need to import some package. Also, it seemed weird that I cannot just simply separate code into subdirs but that might be my not-so extensive Go knowledge or I am just too used to being able to do that. :P
Discriminated unions are amazing, (though C# might be getting that soon with any luck), and the ownership model allows the typestate pattern which would have been very useful for some APIs.
Because of that, I've found myself prototyping in Rust before porting to C# if I need to. As an example, I've also been writing a lot of parsers lately, and nom, along with Rust's enums, make parsing code fun to write. Once I've gotten something off the ground, I plan to port it to C# using Pidgin, and a cursory glance at the API seems like the C# port will end up being much more complicated than the Rust version.
F# also gets really far by just having the inline keyword. If you just inline the higher-order function on the IL level, you can also inline the lambda. See for instance Array.map
As an aside, you can inline 'lambdas' in C# if you do something horrible like this, because the JIT knows the exact type of F it can devirt and inline the call to Invoke().