Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Actix project postmortem

github.com

Post reply on HN
Print view View original

51–60 of 408 posts

Re: Actix project postmortem

#51

Post by kmike84 »

fraktl wrote: post #13

Open source maintainers have a hard time - especially when they're under criticism and receive zero positive vibes. Author mentions it, here's the excerpt: Be a maintainer of large open source project is not a fun task. You alway face with rude and hate, everyone knows better how to build software, nobody wants to do home work and read docs and think a bit and very few provide any help. This a big problem with open s…

A data point: I've been involved in Open Source for 10+ years, developing projects myself, helping to maintain very popular projects, contributing, and I don't see a trend like this. I've interacted with hundreds of people over the years, and the vibes are overwhelmingly positive; I haven't noticed any hatred or rudeness towards myself. I can't think of a single time interaction with OSS people afected me negatively, but there were a lot of positive (or neutral) interactions.

Over time projects I'm contributing to were changing, and so I was exposed to several different communities (Python web development, data science, web scraping), and all of them turn out to be awesome. Maybe that's just luck, but not all OSS maintainers have it hard - no idea why :)

+1 to recharge the batteries!

Re: Actix project postmortem

#52

Post by buzzkillington »

onli wrote: post #40
buzzkillington wrote: post #21

Earlier quoted context omitted.

The easy way to tell is to remember if you're paying them or not.

That's not true at all. You can pay for amateur bullshit, and you can get professional software and support for free (and free as in freedom).

My Ethernet is stuck in ipv6, professionally tell me how to fix it, for free.

Re: Actix project postmortem

#53

Post by UserIsUnused »

tannhaeuser wrote: post #39
teddyh wrote: 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…

Strongly disagree. For me, what's implicit is that any software, commercial or F/OSS, can be abandoned at any time - because that's just the way it is. A remedy would be to use software coded to a specification with mulitple implementations such that in case a project folds, you might be able to switch over to a different implementation. The Java EE ecosystem used to be like that until around 2012 or so.

Abandon is different from deleting everything.

Ofc, git is distributed, so someone should have a copy of the repo, even if it's not updated.

Edit: disregard post, apparently it's just moved to the personal account.

Re: Actix project postmortem

#56

Post by CapmCrackaWaka »

thrownaway954 wrote: post #36

I use to do a TON of open source back in the day. i quit cause of the same reason, people suck and feel they are entitled. i couldn't count how many times someone would yell, kick and scream about an issue they were having and demand that i fix it right away (ain't gonna happen dude). i finally got to the point where i told people that i would only participate in pull requests and nothing else. you could still file i…

Maybe it's because I work on more niche projects, but every time someone contacted me about an issue in one of my repos they were always exceedingly apologetic about "bothering me". My projects only have ~400 downloads per month, so I'm sure it's a matter of sample size. If anything, working through issues with the community has made me enjoy the work more.

Re: Actix project postmortem

#57

Post by jrockway »

teddyh wrote: post #23
tsukurimashou wrote: post #11

"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 think that's made pretty clear in pretty much every open source license: "Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND".

Re: Actix project postmortem

#58

Post by thrownaway954 »

qwerty456127 wrote: post #17

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?

You obviously have never participated in open source and are talking about something you had ZERO experience with. Go participate in a toxic open source community for a couple of months and report back about not only the experience but also you emotional well being. I can guarantee you'll be reading your comment and cringing at what you once wrote.

btw, there is and awesome life lesson in this comment i posted, if you can remove the emotional part of it ;)

Re: Actix project postmortem

#59

Post by Sharlin »

zzzcpan wrote: post #47
logophobia wrote: post #31

Earlier quoted context omitted.

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.

The reporter included a patch.
Post reply on HN