A code snippet would have been nice, or a link to the blog post that introduced them (in trio, another async library): https://vorpus.org/blog/notes-on-structured-concurrency-or-g...
A code snippet would have been nice, or a link to the blog post that introduced them (in trio, another async library): https://vorpus.org/blog/notes-on-structured-concurrency-or-g...
If Twitter survives this without any major harm it will have profound consequences for the whole software industry.
I submit that that aint "broke". You're "broke" when you have to decide whether to repair the car so you can get to work, or repair the heater so you can sleep and shower and stuff, or buy food. "Broke" is when you know all the places you can hit for free crackers on your way to somewhere else.
He then used the story to illustrate the fact that such things can become fond memories, and related _that_ fact to poverty.
At least, that is how I understand the text.
Are there any anecdotal stories about how Rust programs have fewer errors?
Facebook, for example, rewrote Messenger with ReasonML:
https://reasonml.github.io/blog/2017/09/08/messenger-50-reas...
And it had a lot fewer bugs:
"Messenger used to receive bugs reports on a daily basis; since the introduction of Reason, there have been a total of 10 bugs (that's during the whole year, not per week)! *"
In my previous gig, we had a premium website hosting platform, and our incoming clients would usually want their old inbound links to keep working. Over time, this meant a few hundred thousand autogenerated rewrite rules in Nginx. This was causing Nginx to use about 10G of memory, so restarting it, which we had to do every time we added a redirect, was an issue.
I replaced this with a small reverse proxy written in rust that loaded all of the redirects from postgresql into a cuckoo filter. Adding a redirect was an INSERT, followed by a NOTIFY to let the proxy know to add the redirect to the filter.
Putting it all together took about 2 weeks of swearing at the compiler, but it never had an issue in production, and used about 1M of memory, while adding less than 1ms of latency, or about 4ms in case of a filter hit. Cuckoo filters can have false positives, so if a redirect was found, we still had to check in the db table before returning 301.
As far as I know it's still working fine, and I use rust whenever I can.
One that isn't snapshot images (docker, bundled java/ruby/libraries)
One that takes testing and integration seriously
One that takes security seriously
One that uses c-groups like they were intended
One that allows multiple versions
There are a lot of things that could come together for a new style and generation of package manager, but to do it right you would have to manage a whole lot of things
Because that kind of dogmatism is a complete show stopper for languages that want to be deployed on even medium term projects.
This is not to say that Elm is bad. O think it's great as a path into FP, and in fact _was_ my path in. But it does limit you in what you can do and learn.
Also, Purescript has this interesting property of being hard to learn (because it is powerful), but dead simple to use (because it compiles to JS). So you only really get stuck on figuring out how to do things in PS, as opposed to how to get PS working, and therefore every time you get unstuck, you have leveled up. So it's hard, but rewarding.
I'm probably off topic by now, but I do think that Purescript in the frontend is a better option for solid application development.
Maybe it's because rhe demo instance was reset way to often or something but I've never really seen a really working discourse instance. (I think both Mozilla and Canonical (has?) run one but they weren't to active either IIRC.
Anyone has examples of a working discourse community?
Like all delusions, this will continue to entrench itself against reason. When the negotiators fail to reach their delusional goal, the deluded will formulate a conspiracy narrative to protect their delusion.
You should be upgrading all the time since day one, adding necessary infrastructure gradually as your app grows.
Conversely, I was called by a company that I had built an app for previously. They had not upgraded the framework it was built with (Laravel), and ended up offering me consulting days to jump several versions. The irony is that the job ended up being quick and easy to do.