This surprisingly remind me of the last to birthday parties I organized for myself. Unexpectedly I managed to get much more people together than I expected. Simply by actually trying to ask as many people as possible. I was really happy about this. Both times.

Maybe that student was doing the same. Simply asking a lot of people. And other studends usually do not. I find it really hard to overcome my own shyness in this regard. And I wouldn't consider myself particularly shy. I assume a lot of people simply do not try asking enough people in order to get a decent amount of them to join.

Of course that guy might be simply cheating, but I just wanted to share the story.

If the whole script is run with sudo, then all parts of the script that wouldn't have needed suddenly become dangerous.

I really appreciate the reply and found another no-option. I would like to do something less... "abstract". I would definitly agree that crypto has meaningful usecases, but I guess it is not so easy to find those that are meaningful to me.

No problem. It sounds like you are in an experimental time of life. The author of this book encourages piracy:

https://www.resistance.money/research/library/to%20be%20orga...

Read it and maybe it will encourage you to rethink your disapproval of working in crypto.

Exactly this bothers me a lot. I do bare metal performance optimizations, but I worry to never find a job outside of academia in that field. as I don't want to do high-frequency trading nor develop games.

You could look lower in the stack, e.g. at compilers, drivers, and libraries for GPUs and other accelerators. That's not a huge field, but still a decent number of jobs to go around.

Like what is this comment? Why do people with an extremely narrow view of some political topic or politcal movement like anarchism/communism/immigration policies/etc. start posting something that dismissive. Like as if they where actually talking about the same thing, without realizing that they dismisse a delusional idea of something which has no to little to do with what the other person was talking about.

This was the whole point of Occupy! They refused to have any demands or talking points because they instead were going to live their truth by leading a better way of life in parks. And they had meetings with complicated progressive stack systems and looked for consensus in everything. It's theory compliant.

Well, this is not true. However, to be fair, most important use case of errno in my work is debugging in horrible code bases, trying to understand what has happened.

Yeah, Germany... For the current project I have so much overtime, needed to stop writting down my working hours officially and only record them off-the-record. This is with a mutual silent agreement with my employer to afterwards simply not show up for some time as soon as the project is done. Because... Laws. We are afraid to even talk about it.

But to be fair, my employer wouldn't mind to let the project fail (It may very well fail anyway, btw). I am doing it voluntarily. He's not at fault at all, except for maybe allowing me to do it. I just love working on the project and try to get it done somehow, against all odds. Nevertheless, German laws now make something shady out of it.

On the other hand, this is not the first time I am doing so utterly stupid and partly self-distructive shit at work. But for sure it is the last time. I am never ever doing this amount of overtime again in my life. Don't get me wrong, I don't mind occasional overtime. But that's simply to much for too long now. I will barely go to work for several months in a row just to get rid of all that overtime, to give you an impression. (I know there is professions where people literally die, if people stop working similar hours. I am not really forced to do that so I am not complaining.)

I am glad my significant other is fine with it, since I barely caried any other responsibilities I should have... for a long time now.

Edit: I am not sure if there is actually special laws in Germany to avoid mutually agreed overtime. But there is for sure some rules where I work. Our company has a kind of special situation and strange laws surprisingly apply to us. Also it important to mention that if low performance and mistakes because of overworked employees happen nothing terrible will happen. You wouldn't want to have your medical devise be programmed by some sleep deprived idiot, but that is not the situation our company is in. If projects fail, nothing of importance is at risk. Many projects are of high risk and failing simply belongs to the business.

I don't really see this as a downside to the German legislation. If anything it's ... good? It gives the employee a ton of control over whether they do overtime or not. Yes, it's a bit weird that it's technically illegal... but if neither side complains then it's fine?

The power imbalance is so high that normally any scenario where you can 'agree' to work overtime usually leads to employees always having to technically consent or face termination.

It's not perfect but I don't know that there is a better solution given the power imbalance and the game theory of these situations.

Did you consider that you might not have the right contract for this type of situation? There a lot of jobs (hospitals, consultancy, ...) that do not fit the standard work agreement (08:00-17:00, 1h lunch, 40h/week). The law is strict here for the case that it turns out that your agreement was in fact not mutual and your employer expects you to work normal after your overtime phase without rewarding you for it. The german law is convoluted and can be inflexible but more often then not there are solutions. I am also not sure why you would be afraid talking about it?

There is up to criminal liability (jail) for an employer who knowingly lets workers exceed the allowed time in a way that risks the health of the worker.

I assume the parent comment did not make fun of nushell advertizing this, but instead about the rust community advertizing itself all the time.

To be honest, they have good reason. Being written in a strongly typed, memory-safe language is a huge advantage. Obviously it's not the primary thing to look out for, but I do prefer tools that are written in it.

There are plenty of strongly typed memory safe languages. In fact I think those are the majority of popular languages.

Yet, almost all the basic tools in a Unix system are written in C.

Of course the person you're replying to is talking about languages without a garbage collector. Systems languages with zero cost abstractions.

But why? There is nothing about a shell that requires zero cost abstractions or no gc. It farms all of its work out to other executables. A shell could be written in literally any language.

Java, Scala, Kotlin, C#, D, Go, and TypeScript to name a few.

Of those only D and Go build self contained binaries (yes i know about Graal/Kotlin Native/.Net AOT). No snark intended.

This is moving the goal post a bit, since the person I replied to was considering JavaScript, but I don’t really think this distinction matters. You get most programs from a package manager.

I am curious though why you don’t count graal or .net aot? They are valid options to produce an aot binary and C# has been able to produce a self contained non-aot runtime for a long a time.

Even Python fits the bill.

> Being written in a strongly typed, memory-safe language is a huge advantage.

Great point, C# is a strongly typed and memory-safe language if you don't use unsafe. So this really is a huge advantage for PowerShell.

I do generally want a fixed commit. I often want to improve the code in the submodule possibly (voluntarily or accidently) introducing breaking changes without worrying about breaking repos that contain it as submodule.

5his is right in the spirit of: The Python community is a bunch of people learning programming together.

Someone else made this remark once, when the indroduction of type annotations was discussed as the python community discovering the benefits of static typing.