Live data from Hacker News

Actix project postmortem

github.com

41–50 of 408 posts

Re: Actix project postmortem

#41

People should really learn to ignore the emotional channel of the comments they receive. Just try to figure out if the message contains any useful information with a quick glance, extract it if it does and ignore the rest. People have to shit - that's physiologically inevitable, and there are people who do it in the streets and there are people who shit in comments/messages. Why take them serious?

> I used to do tech support and some people (not too many) wrote right out rude or nonsensical (like concluding I hate their religion just from the fact our service failed to suit their specific needs).

This isn't at all the same thing. You were paid to do your job, and at the end of the day you could just joke about those weirdos.

When working on an open-source project, everything becomes much more personal because your motivation is fuelled by your own personal attachement to the project. Imagine you're helping elderly people cross the street every day, and every once in a while they yell at you for not doing it better, whatever that means. At some point is it still worth it?

And of course you can't just put that behind you once you're back home, because this abuse happens at home. I remember this time where someone literally told me to kill myself while I was fixing a bug - at midnight - in a project I handle. Or the time I woke up only to see that during the night someone public had decided to openly send me literal fuck emojis on Twitter to right a perceived wrong. Good times.

So yeah - building a shell is the right solution, but it's hard and we really shouldn't have to deal with that in the first place.

Re: Actix project postmortem

#43
post #4

Asking for a friend - could someone explain what happened there? The README doc is quite vague - it is more of a personal justification than a rationale (to me).

It seems like the overarching issue is that Rust is a house of cards. They added unsafe like Java has null. My favorite part is that you can declare a crate to forbid unsafe, but that then doesn't have to hold for it's dependencies.

The obvious implementation is for unsafe to be infectious like const. You have unsafe code, your crate is unsafe. You depend on an unsafe crate, your crate becomes unsafe.

Re: Actix project postmortem

#44

People should really learn to ignore the emotional channel of the comments they receive. Just try to figure out if the message contains any useful information with a quick glance, extract it if it does and ignore the rest. People have to shit - that's physiologically inevitable, and there are people who do it in the streets and there are people who shit in comments/messages. Why take them serious?

Should they ignore the negative parts or should people who comment be mindful of the fact that a lot of open source they use is created in someone’s spare time and that they have a human being, not a company? I’d think the latter.

Re: Actix project postmortem

#45
post #23

"Ok... So that was unprofessional. If you don't want to maintain a project anymore, you give it to someone else and link to that repo in your README. This just screwed me over big time." https://github.com/actix/actix-web/issues/1#issuecomment-575... These kind of entitled attitude is probably exactly why the guy just removed everything. More details / discussion here: https://www.reddit.com/r/rust/comments/epszt7/ac…

> These kind of entitled attitude If you offer code to the public – and present it as an active, dependable project – professional behavior is exactly what you implicitly promise and signed up for . If you can’t offer that (at any time, and for any reason), then you should immediately make that clear, front-and-center, to any current and future users. It isn’t “entitlement” on part of the users – the users are making…

[deleted]

Re: Actix project postmortem

#46
I'll save this link for the next time someone tries to argue that the Rust community is somehow "more welcoming" than some other X community.

All internet-based communities contain some assholes. All of them. Sadly some maintainers don't seem to have the werewithal to tell them to go away. I mean, when you get "asked to change coding style", it's the time to put the banhammer down, because there is no way to please these people without humiliating yourself.

Re: Actix project postmortem

#47
post #14

Earlier quoted context omitted.

The maintainer can choose whatever style they damn well please, if you don't like it don't use it. What is hard about this?

It's not coding style, it's refusing to investigate use-after-free vulnerabilities in code because it's "boring". Noone should care if a maintainer uses tabs or spaces, or has weird variable naming, but if "coding-style" leads to security issues (due to hand-rolling unsafe memory-primitives), then it is an actual issue, especially if it's for a popular web-framework. Don't like it, don't use it doesn't really apply t…

> it's refusing to investigate use-after-free vulnerabilities

Please investigate yourself, don't ask others to do the work you consider important for you for free.

Re: Actix project postmortem

#49
post #23

"Ok... So that was unprofessional. If you don't want to maintain a project anymore, you give it to someone else and link to that repo in your README. This just screwed me over big time." https://github.com/actix/actix-web/issues/1#issuecomment-575... These kind of entitled attitude is probably exactly why the guy just removed everything. More details / discussion here: https://www.reddit.com/r/rust/comments/epszt7/ac…

> These kind of entitled attitude If you offer code to the public – and present it as an active, dependable project – professional behavior is exactly what you implicitly promise and signed up for . If you can’t offer that (at any time, and for any reason), then you should immediately make that clear, front-and-center, to any current and future users. It isn’t “entitlement” on part of the users – the users are making…

I do not think these expectations are reasonable. This line of thinking is definitely the core issue of the problem.

Re: Actix project postmortem

#50
post #29
post #23

Earlier quoted context omitted.

> These kind of entitled attitude If you offer code to the public – and present it as an active, dependable project – professional behavior is exactly what you implicitly promise and signed up for . If you can’t offer that (at any time, and for any reason), then you should immediately make that clear, front-and-center, to any current and future users. It isn’t “entitlement” on part of the users – the users are making…

Or to put it another way: As an open source maintainer, you're perfectly entitled to just walk away. Hit that archive button on github so nothing new can come from the repo, and enjoy your life. Nobody could fault on you that. People would prefer you work out a clean transition to a new maintainer, but you have no obligation to do so. Deleting the repos is the equivalent of setting the house on fire on the way out (e…

If you want to rely on some code that it takes even a second of your day to think about your response to author deleting that public code, then you fork it and simply track author's repo.
Post reply on HN