Ephera

There's a condition where people may sweat less or not at all: https://en.wikipedia.org/wiki/Hypohidrosis

Not as great as it might sound at first...

I feel like the main problem with balenaEtcher is that it requires downloading 150 MB, for a software that many people will use only once before a reinstall.
If you're in a rich country, you might hardly notice, but for poorer countries, this is an insane ask, especially if it just improves convenience mildly.

But yeah, ultimately any such tool is going to face the problem that no matter how easy it is to use, you need to first install it, which needs to be explained.
The usage of dd also needs explaining, but you don't need to install it.

Well, and another factor is that dd has been around since the dawn of time. Software like balenaEtcher tends to go unmaintained after a few years, at which point any documentation referencing it, will need to be rewritten. And it's usually rewritten to reference dd instead, before a new convenient software emerges...

It's the way Markdown works. If you put two spaces at the end of a line
before hitting enter, then it will only do a normal linebreak.

What helped me a lot with pushing deeper down into the language innards is to have people to explain things to.

Last week, for example, one of our students asked what closures are.
Explaining that was no problem, I was also able to differentiate them from function pointers, but then she asked what in Rust the traits/interfaces Fn, FnMut and FnOnce did (which are implemented by different closures).

And yep, she struck right into a blank spot of my knowledge with that.
I have enough of an idea of them to just fill in something and let the compiler tell me off when I did it wrong.
Even when designing an API, I've worked out that you should start with an FnOnce and only progress to FnMut, then Fn and then a function pointer, as the compiler shouts at you (basically they're more specific and more restrictive for what the implementer of the closure is allowed to do).

But yeah, these rules of thumb just don't suffice for an actual explanation.
I couldn't tell you why these different traits are necessary or what the precise differences are.
So, we've been learning about them together and I have a much better understanding now.

Even in terms of closures in general (independent of the language), where I thought I had a pretty good idea, I had the epiphany that closures have two ways of providing parameters, one for the implementer (captured out of the context) and one for the caller (parameter list).
Obviously, I was aware of that on some level, as I had been using it plenty times, but I never had as clear of an idea of it before.

The longest was probably the vegetarian → vegan pipeline.
My position was that 'employment' of animals was humanely possible, if you genuinely treated them like you'd want to be treated.

It was until I read how cows need to basically be kept continuously pregnant, that I realized there was just no way.
I believe, you could have a bite of cheese every year or so, if we don't do forceful impregnation, but at that point, why even bother?

Fun fact, it was originally made from the roots of the marsh mallow: https://en.wikipedia.org/wiki/Althaea_officinalis

Always glad to be of help.

I don't disagree with you on a rational level, but on a human level, it just sometimes feels nice to walk a different route, to not be forced to walk in exactly a straight line, especially with a ridiculously narrow sidewalk like that.

And that's then where the opinion of cars comes in. I'm not supposed to do what I feel like, because some guy with a car decides to head on through. If I think cars are vital to humanity, I'll gladly do the rational thing. If I think cars are killing humanity, then sincerely fuck that noise.

Looks like a cool software from a usability viewpoint, and that machine learning recipe import is probably actually quite useful for archiving other people's recipes.

But for long-term archiving, I think just a bunch of Markdown files + images are a better choice.
To still get a searchable webpage, personally I'd use mdBook.

Well, in this case, it is actually Valve that does the licensing. I don't think the original companies have much to do with it, other than maybe being more willing to sell through Steam than e.g. GOG or itch.io.

But all in all, yes, it would be a much more useful law, if it declared such a licensing model void.
I'm guessing, they didn't tackle that problem, because there are more legitimate uses of a licensing model, like World of Warcraft only giving you access while you're paying the monthly fee.

Nothing unsolvable, but you need some solid laws and it'd be a lot less likely that you'd get support from enough political parties to carry this into actual law.

It informs customers, that licensing a game on Steam is not like buying a pair of pants on pantsshop24.org. That's what it's meant to do.

aber waren Sie