I can see the argument for this triggering an eventual change, but having _both_ the chock of a CEO change _and_ 28% of the company being layed off at the same time seems unwise.
53 karma · joined January 7, 2019
I can see the argument for this triggering an eventual change, but having _both_ the chock of a CEO change _and_ 28% of the company being layed off at the same time seems unwise.
- I use zig as my build system for both rust, zig, C libraries and linking since the build system works really well for this purpose
- When I need to write applications or libraries that can benefit from compile-time code, I always try and use zigs since it's much easier to use comptime then a combination of rust macros and generics
- I like the zig async story a lot better. Or at least it's much easier to wrap my head around and write code in compared to rust + tokyo
On the other hand, sometimes I know a project will benefit from the borrow checker or I want to use some of the awesome rust crates that the community made and I'll use rust instead.
I understand the argument that in most situations a byte array might be what you actually want, but in practice it feels very dirty to be passing byte arrays around instead of expressing the underlying meaning of that byte array as a type (in this instance a String type).
Having a string type also makes any standard library functions on strings infinitely easier to discover.
Would you happen to have any actual evidence to back this up with?
The part after the schedule is weird for sure, but the schedule itself sounds fine.
I'd also disagree that adding a throws to the signature is much boilerplate at all. Especially in the ages of IDE's