HackerTrans
TopNewTrendsCommentsPastAskShowJobs

troppl

no profile record

comments

troppl
·पिछला वर्ष·discuss
Something I haven't yet seen mentioned, but that is going through my mind. To me, it doesn't even seem like OpenAI got any better at producing GenAI images. Instead, it seems to me like they now simply removed a whole bunch of guardrails. Guardrails that, for example, made AI images shitty on purpose, so to be "safe" and allow people to kind of recognize. Making all of this "safe" was still very en vogue a few months back, but now there was simply a big policy/societal change and they are going with the trends.

This then allows their pictures to look more realistic, but that also now shows very clearly how much they have (presumably always) trained on copyrighted pictures.
troppl
·3 वर्ष पहले·discuss
I have a question that maybe someone here knows. It has been noted multiple times in the comments here that at this point, one should just use tokio as the async runtime. (From my limited experience, I agree)

The async Rust book [0] says this about runtimes:

> Importantly, executors, tasks, reactors, combinators, and low-level I/O futures and traits are not yet provided in the standard library. In the meantime, community-provided async ecosystems fill in these gaps.

Notably, it says "not yet". My question is if someone knows if there are actual plans to incorporate any (existing) async runtime, and if so, whether there is a timeline? Also, is tokio in the talks to be the runtime, or is this still open?

[0]: https://rust-lang.github.io/async-book/08_ecosystem/00_chapt...