Axum is most likely to be supported long term since it has quite a bit of support and is a Tokio project but it's not nearly as batteries included as something like Rails or Django. I doubt any of the current batteries…
> with Bun leading the way Definitely leading the way in segfaults.
https://github.com/golang/go/issues/61901 https://github.com/golang/go/issues/61902 https://github.com/golang/go/issues/61900 https://github.com/golang/go/issues/61899 https://github.com/golang/go/issues/61898 Yes there…
I know. There are already proposals to add new functions to many of these packages that return iterators.
Basically every custom data structure right now has some custom implementation of iterators. This will set a standard and make them usable with range loops. Even simple library methods like scanner.Scan, strings.Split,…
They'll be used primarily by library authors but most people will end up consuming them a lot. They'll eliminate a lot of unnecessary intermediate slice allocations.
Python is the same but there's not nearly enough incentive to move to another slow language. A lot of people that are interested in using something other than Python want a language that doesn't require everything to be…
Erlang/Elixir are very slow for most computationally expensive tasks.
Axum is most likely to be supported long term since it has quite a bit of support and is a Tokio project but it's not nearly as batteries included as something like Rails or Django. I doubt any of the current batteries…
> with Bun leading the way Definitely leading the way in segfaults.
https://github.com/golang/go/issues/61901 https://github.com/golang/go/issues/61902 https://github.com/golang/go/issues/61900 https://github.com/golang/go/issues/61899 https://github.com/golang/go/issues/61898 Yes there…
I know. There are already proposals to add new functions to many of these packages that return iterators.
Basically every custom data structure right now has some custom implementation of iterators. This will set a standard and make them usable with range loops. Even simple library methods like scanner.Scan, strings.Split,…
They'll be used primarily by library authors but most people will end up consuming them a lot. They'll eliminate a lot of unnecessary intermediate slice allocations.
Python is the same but there's not nearly enough incentive to move to another slow language. A lot of people that are interested in using something other than Python want a language that doesn't require everything to be…
Erlang/Elixir are very slow for most computationally expensive tasks.