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.

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...

It seems to me like they removed the warning on SQLite, so I guess they tested it and it works fine. But I didn't research this any further so far.

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.

And I would assume it's the same on high sea...

You cannot possibly be serious. Wirecard happened only two years ago.

So, while the thinking might goes that all this is for something like FTX, it's obviously not succeeding.

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)

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.

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)

Sorry, I don't get this. Of course your opposition on something can be based on ideology. That is the case if your opposition is more based on your history and tradition than on current facts.

I personally think that there are enough facts to say that nuclear is not really a great option, but I also think that the Green's opposition is based more on ideology (i.e. because they have been historically against it) than on facts. For me, that is evident when they talk more about nuclear risks in general than about financial considerations.

That's interesting, because I almost wanted to make the exact opposite point. I'm actually right now in the process of revisiting my notes, and I think it helps me a lot. Not because they are super useful in and of itself (After 1-3 months have passed now, I understand the stuff deeper now, obviously) but because they help me piece the stuff together.

Anyways, the reason why they then get useful is because I have an extrinsic motivation to read them! (Exams are coming up)

That does in no way make it easier to read them, but it helps in actually reading them.

Then, reading notes and really understanding something will always be hard. I think there is also quite some research ouf there that finds just this: If you really want to understand stuff, you need to put in the effort. It kinda needs to hurt...

This is why I don't think these personal wikis / note -taking tools help too much, especially if one is, like me (and probably most people), more a person who in their downtime maybe likes to read something new and interesting, but better keep that on the light side - it's supposed to be downtime anyways, no?

That leads me then back to the extrinsic motivation: If for example you're a researcher and use Roam (or whatever) exclusively for that (that means restraining also from putting notes in there that have little to do with your actual research), I think the benefits would be much more clear. To be honest, though, that is just a guess. I'm not a researcher myself and I have n't been using note-taking systems for a while now, because of the points explained above.

Coming from Spring or Java EE:

> implementations that could literally be a lambda function (on receive message, write row into DB) are a festival of multiple tiers of objects, mappers, mediators, IoC frameworks, wrappers, Nuget packages, etc., etc.

Spring or Java EE is a strong convention, so IOC is one automatically as well (both make use of that heavily). Hibernate would be the next strong convention, therefore mappers are, therefore we will have multiple tiers of objects. Wrappers will also be needed in a language like Java. About the rest of this list I can't say much now, but I would argue that lots of what this person is doing is based on strong conventions in the enterprise world. And it goes on:

> Everything is in multiple projects. Simple constants (like: API routes - '/api/foo/bar') are indirected into files containing those strings, so there's a huge cognitive overhead and much clicking around to make sense of it. God help you if you don't use an IDE.

Coming from Java again, everything won't be in multiple projects, but in multiple Maven modules instead. AFAIK that is good practice, or, if you want: a strong convention. Stuff like API routes will indeed not be saved in a code file, but in an openapi file instead.

IMO then, what this person was doing was actually following strong conventions. Yes, these are often also specific patterns, but what is the difference, specifically for these things listed here?

It seems to me much more that the person was probably "limited" more by the language. I think there are fairly good reasons for all of these, especially when working with more than ten people - in a language like Java. And in this case you will have to use Java (or something similarly famous) because otherwise you won't find a replacement very quickly that is fairly cheap. Now, maybe the person would not have needed all this in such a small project that is just for one person. But who knows, maybe the project grows. Or maybe this person was simply familiar with this and could get this down fastest. All in all, I think there are many good reasons to decide to make a project with patterns/conventions like this.

For my own enjoyment I have however seen that the translation that I use is really important. I'm reading it in German, and the new translation by Susanne Lange is much more pleasant to read than some other older translation I have in digital form.