tcfhgj

20 ms·

1. 241.▲
   by tcfhgj 6mo ago

   You assumed > Likely more efficient than half the async runtimes out there. The benchmark shows the opposite: 2 (multithreaded async runtime) vs 7 (threads) * 10^8 ns per request for 2k requests/s. > non-linear scaling problems.
2. 242.▲
   by tcfhgj 6mo ago

   So once it's out of the experimental stage it won't be an intrusive hack anymore?
3. 243.▲
   by tcfhgj 6mo ago

   Would this be considered an intrusive hack? https://docs.rs/tokio/latest/%20tokio/runtime/struct.Handle....
4. 244.▲
   by tcfhgj 6mo ago

   Could you point out the issue here? Why does async make it harder to reason about when resources are released?
5. 245.▲
   by tcfhgj 6mo ago

   > Not all code written benefits from async nor even requires it. Running single threaded, sync programs is totally valid. Maybe, but is it useful to have sync options? You can still write single threaded programs
6. 246.▲
   by tcfhgj 6mo ago

   doesn't a async runtime have more knowledge about the tasks than the OS about the threads?
7. 247.▲
   by tcfhgj 6mo ago

   hardware from 10 years ago - do you have benchmarks for more recent hardware? https://vorner.github.io/async-bench.html
8. 248.▲
   by tcfhgj 6mo ago

   > If you are ten layers deep in a stack of synchronous functions and suddenly need to make an asynchronous call, the type signature of every individual function in the stack has to change. well, this isn't really true - at least for
9. 249.▲
   by tcfhgj 6mo ago

   bug or backdoor?
10. 250.▲
    by tcfhgj 6mo ago

    What different way of doing things? If I want sequential execution, I just call functions like in the synchronous case and append .await. If I want parallel and/or concurrent execution, I spawn futures instead of threads and .await the
11. 251.▲
    by tcfhgj 6mo ago

    I can't follow that it's hard to learn and unintuitive
12. 252.▲
    by tcfhgj 6mo ago

    oh I just love the replies
13. 253.▲
    by tcfhgj 6mo ago

    Typst
14. 254.▲
    by tcfhgj 6mo ago

    A lot of love for a company which doesn't even let you chose the apps you want to use.
15. 255.▲
    by tcfhgj 6mo ago

    at least you can still decide on the software you install
16. 256.▲
    by tcfhgj 6mo ago

    There is native to the OS and there's native to the machine. Anyways, I'm both cases you don't really have to write it twice. Native to the OS: write only the UI twice, but implement the Core in Rust. Native to the machine: W
17. 257.▲
    by tcfhgj 6mo ago

    Until? Just take what's out there - it's so easy to improve on Electron
18. 258.▲
    by tcfhgj 6mo ago

    hopefully not implying needing a gc for memory safety...
19. 259.▲
    by tcfhgj 6mo ago

    oh that would be a dream
20. 260.▲
    by tcfhgj 6mo ago

    > And if the alternative is a memory-unsafe language and if not?
21. 261.▲
    by tcfhgj 6mo ago

    It's 2^16=65,536 bytes for Firefox
22. 262.▲
    Debloat Your Async Rust(tweedegolf.nl)

    3 points by tcfhgj 6mo ago|1 comments
23. 263.▲
    by tcfhgj 6mo ago

    Telegram server operators can read message meta data and messages
24. 264.▲
    by tcfhgj 6mo ago

    you can have large groups and device sync WITH e2ee, see Matrix.
25. 265.▲
    by tcfhgj 6mo ago

    Matrix
26. 266.▲
    by tcfhgj 6mo ago

    Even more automation friendly than Matrix?
27. 267.▲
    by tcfhgj 7mo ago

    "they" is a German city, not Germany
28. 268.▲
    by tcfhgj 7mo ago

    Unforgiving?
29. 269.▲
    by tcfhgj 7mo ago

    Result<T> should work
30. 270.▲
    by tcfhgj 7mo ago

    https://typst.app/docs/web-app/export-and-preview/#html-prev...