Tokio focuses on being high throughput as default, since they mostly use yield_now backoff strategy. It should work with most application.
For latency sensitive application, it tends to have different purpose which mainly trade off CPU and RAM usage for higher low latency ( first ) and throughput later.
We shouldn't overestimtae the complexity of expressive language like Clojrue vs Go. Go is perfectly simple and easy to follow, even compared with Clojure. If you come from background of Computer Science or programming first, Go is easier to follow.
I do switch between Clojure and Rust depends on the problems I solve at hands ( prototypes vs building production ). And yes I need go through my checklist of each to switch from connecting data flows at high level to examine nuts and bolts at low level.
I really like the UI, it's exactly how I use and share notes within my colleges for years with my current system. Is there anyway that I can bring my own model ( integrating with my data stored on struct ) to answer my questions?
I just don't understand how Google communicates their product with customers. We have like multiple chat apps, and the history is repeating with Google AI? Make it simple, so we don't have to explain to the person next to us.
This is very nice, I hope we have a windows version soon. And this might encourage Sublime Text to do the same, it's one of the most responsive editor for now, let's see.
I have the same problem, I understand the enjoyment of sales / marketing team when it comes to using Notion, but for engineering team, it's just horrible, so slow.
it's true. The year MAC has the best new reliable, and fast chip, PC has AMD with broken, burnt CPU / motherboard, Intel has a chip so hot to cool down.
the UI is screaming speed. Actually most of the apps I use in Windows now, have that kind of UI, I hate that with the kind of hardware we have currently, we need to wait for a window to appear.
Apps I use daily: totalcmd, clipx, far, sublime text ( only for edit text, code with intellij )