Ephera

Me, who practically only buys cotton and does not own an iron:

Yeah, it is literally just saying "active before something happens", so you can also omit the information that it's "before something happens", and therefore you do just express that you're being "active".

Yeah, same. Others will generate some awful code and get praise for how quickly they implemented a feature. And then I need to debug or modify that awful code at some point and it takes longer than rewriting it.

It just feels so wrong, too. We had the ability to quickly write awful code beforehand, too, and learned over a long time that it's not worth it. Now we have a different way of doing the same thing and it's treated like it's entirely different.

Maybe we can shift to an entirely different paradigm, where we don't need to understand code anymore, because we always just generate anew or something. But I'd really rather have any evidence of that being a good idea, and not just causing different bugs to be generated, before I risk a project to that.

Yeah, it's just wild to me, that we went full-force ahead with the whole 3D thing, when you lock out so many potential players with it.
With 2D games, you can chuck someone a controller and even if they're just haphazardly pressing buttons, they can still participate in the game. With 3D, no chance.

And even those who do have practice still struggle with it. Think of a difficult 3D game and I bet it's a valid joke that the true end boss is the camera.

The "pro-" is derived from Ancient Greek and means "earlier" or "prior". So, "proactive" means to become active before something (typically bad) happens. It's the opposite of "reactive", which means to become active after something (bad) happens, i.e. in response to it.

An example: To help with fighting fires, you can proactively remove flammable materials or buy fire extinguishers. But if a fire breaks out anyways, then you have to deal with it reactively, a.k.a. react to it, by then making use of the fire extinguishers.

In both cases, you become active, but one time you become active before something happens (proactive), the other time you become active after something happens (reactive).
Well, and the things you do in those situations are generally also different. Proactively, you try to prevent a catastrophe from happening and prepare remedies in case it still happens anyways. Whereas reactively, you use those remedies to condemn the damage and try to get things back into working order as quickly as possible.

What really frustrates me about that, is that someone put in a lot of effort to be able to write these things out using proper words, but it still isn't really more readable.

Like, sure, unsigned is very obvious. But short, int, long and long long don't really tell you anything except "this can fit more or less data". That same concept can be expressed with a growing number, i.e. i16, i32 and i64.

And when someone actually needs to know how much data fits into each type, well, then the latter approach is just better, because it tells you right on the tin.

You replied to the wrong guy, but I think they rather meant it as "unless you're using a password manager (...because password managers are generally capable of storing extra data)". 😅

I mean, even if it can't store extra data in one entry, you could still create multiple entries for a single account and just name the entries similarly.

And to give an example of a password manager intentionally kept so simple that, well, there is a solution, but it is somewhat choose-your-own-adventure: https://www.passwordstore.org/#organization
(You can get GUIs for it, which may have a premade solution after all, for example: https://f-droid.org/packages/app.passwordstore.agrahn )

Well, there might be other reasons to need them. For example, I once got locked out of an account, because I had lost the 2FA credentials (which I did not have in KeePass, incidentally). The webpage let me back in with a recovery question.

Well, technically, it was a recovery code which was just random symbols I had been provided upon account creation, but kind of the same thing in the end.

Well, I'd rather write down anything I enter, in case I do ever need it. But yeah, generally speaking you shouldn't need the answers.

Oh man, a zero byte long unsigned integer? Lots of languages represent it as an empty tuple these days (the "unit" type), but from quickly scanning the documentation, it looks like HolyC doesn't support tuples, so I guess you gotta get creative...

You can also store these in a password manager like KeePass...

Selbst mit Ad Blocker und Cookie Banner Blocker, und nachdem ich deinen Kommentar gelesen hatte, habe ich mich trotzdem noch an dem selbstabspielenden Video erschrocken/geekelt und reflexartig den Tab geschlossen.

Dachte mir noch kurz "ah okay, mit Blocker kann man das ja ganz gut lesen". Tja, zu früh gefreut.