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.
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?
There are no plans to incorporate a big async runtime like tokio. This does not matches Rust's vision of small, well-focused std.
There are possible plans to implement a minimal runtime that only allows you to execute futures. No I/O or such. Mainly for tests or examples. No timeline though, at least as far as I'm aware.
There are also plans to standardize the async traits, e.g. spawn a new task, AsyncRead and AsyncWrite etc.. I don't think there is a timeline, but they wait at least for async fn in traits.
I know it was merged, but currently there is only support for statically-dispatched async fn in traits. I believe we also need dynamic dispatch to compete with the current style of `poll_X()` functions in the I/O traits.
Here in the alps, if you have an injury hiking and need a helicopter ride then you are required to pay for the ride (normally a few thousand euros). I assume it's the same if you're lost.
yes, same in Canada afaik. seems quite plausible to me that some of these bills will be sent to OceanGate, we don't know. ofc their ability to pay is another question.
I think the other commenters here really don't get what you mean or have never been to a retirement home. For people that really don't understand how this is not a good example: retirement homes reek of death. Even if you yourself are still fit, most people there won't be. This means that even though you would have the (mental/physical) capacity to enjoy your time there, you first need to find the few people that have that as well. Compare that to a college dorm, where almost everyone wants to socialize...
It really isn't just about mindset! Sure, that will have something to do with it, but it's really a minor part, and even then, it will be much much much harder to have a positive mindset there then in a college dorm. (Again, I'm not saying it's not possible - I'm really just trying to make people empathize with older people that don't want to go into a retirement home. I think that it's a really reasonable thing not wanting to go there)
Are you really sure that is the case here? I think everyone that starts working with git is a bit hung up by its complexity at least for a year, if not more.
It seems to me that, as it should be, every professional SW dev has managed to work with git at some point in their life, then. Because git is simply what you will most likely use nowadays.
But still, everyone remembers how hard it was to start out. Which is why, I think, these blog posts about git are so popular all the time.
Not always, but if you only do some of those incantations a few times per year, and what you remember is that you tended to get them wrong... it's a bit of a pain. This is partially why I switched to GUI clients for day to day. Tower (and maybe others) have an 'undo' which gives me a bit more confidence to try/test out things, because I know if it's wrong I can hit 'cmd-z' and be back where I was (at least until I push!).
> But still, everyone remembers how hard it was to start out
I sure don't. I learned the commands I needed (branch, checkout, clone, push, pull and commit) and didn't step out of those bounds until much later. It's really no different than learning any other skill or platform. Nobody starts out a master, but that's no excuse to never start.
This is actually not such a good example I think. A better example would be that you have a small improvement to an existing algorithm, but you know that another group across the globe is also working on/with that algorithm and maybe they also found out the same improvement as you did. If that is the case, then it will be a race on who publishes a paper about that first.
If you're not first, there's no reason to publish a paper anymore. And you just lost a good paper... (And paper count is really almost all there is in academia, at least that is what it seems to me sometimes)
You do realize that it's the exact same way in the EU, if not worse? In the EU, a company can't even hire you if you're from another EU country where your company doesn't also have a seat there...
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.