Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
gtunnel
Tunnel is a clean wrapper around native Go channel to allow cleanly closing the channel without throwing a panic.
-
RE2
RE2 is a fast, safe, thread-friendly alternative to backtracking regular expression engines like those used in PCRE, Perl, and Python. It is a C++ library.
-
FizzBuzz Enterprise Edition
FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.
-
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.
-
Github-Ranking
:star:Github Ranking:star: Github stars and forks ranking list. Github Top100 stars list of different languages. Automatically update daily. | Github仓库排名，每日自动更新
-
-
-
In fact, this was brought up in their github issues, a very simple change. In fact, the PR adds one line of code and one if statement.
you should try and read kubernetes codes sometimes. There's a reason why it's maintained by basically an endless stream of dev and yet still doesn't have basic function like disable liveness probe without restarting pod or resizing PVC in sts - even though they already supported resizing PVC on its own, as mentioned in the ticket.
The only thing I would agree with him is the nil/closed channels behavior. I hated that, and so I built my own wrapper to make behaviors more consistent, which you can bet I use all the time for production code instead of the native channels.
You made me look again and they finally removed the donate to BLM banner from the regex wiki page on GitHub! It took them some 18 months...
Counterpoint.
the project: https://github.com/DanteFalzone0/mudnix
I prefer functions returning errors over throwing exceptions. Whether it's Go's errors or ML-style options/results, they're both better than exceptions. I cannot remember the last time I had a bug from not checking an error in Go. There's also errcheck which I use as part of my linting that will catch unchecked errors, such that I cannot even commit the code.
That's part of the reason, in my opinion, why a lot of interesting high-performance FOSS software is written in Rust. It's easy to write robust code, and even more importantly, equally easy for others to write that robust code and contribute it upstream.
My point wasn't that the distinction isn't important. My point is that little things like that can trigger hours or days worth of learning semantics that - in some cases - are a productivity killer. The unofficial tutorial Learn Rust With Entirely Too Many Linked Lists is the a pretty good approximation of the Rust learning curve: every time you want to do anything slightly more advanced, you need to learn a lot about how to make the compiler happy.
One of the big reasons that the try proposal ( https://github.com/golang/proposal/blob/master/design/32437-try-builtin.md ) was abandoned is that people felt that simply returning without handling errors is't enough for such a language feature to be added.
Crystal.