Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Open Source Programming IT

Framework Developer 'Ragequits' Open Source Community, Citing Negative Comments, 'Very Few Provide Help' (theregister.co.uk) 122

The maintainer of the popular Rust web framework Actix has quit the project -- though he's backed off threats to make its code private and delete its repository, instead appointing a new maintainer. "Be a maintainer of large open source project is not a fun task," he'd complained last week on GitHub. "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...

"You felt betrayed after you put so much effort and then to hear all this shit comments, even if you understand that that is usual internet behavior.... Nowadays supporting actix project is not fun, and be[ing] part of rust community is not fun as well."

The Register reports: Actix Web was developed by Nikolay Kim, who is also a senior software engineer at Microsoft, though the Actix project is not an official Microsoft project. Actix Web is based on Actix, a framework for Rust based on the Actor model, also developed by Kim. The web framework is important to the Rust community partly because it addresses a common use case (development web applications) and partly because of its outstanding performance. For some tests, Actix tops the Techempower benchmarks.

The project is open source and while it is popular, there has been some unhappiness among users about its use of "unsafe" code... Safe code is protected from common bugs (and more importantly, security vulnerabilities) arising from issues like variables which point to uninitialized memory, or variables which are used after the memory allocated to them has been freed, or attempting to write data to a variable which exceeds the memory allocated. Code in Rust is safe by default, but the language also supports unsafe code, which can be useful for interoperability or to improve performance.

There is extensive use of unsafe code in Actix, leading to debate about what should be fixed. Kim was not always receptive to proposed changes... Kim said that he did not ignore or delete issues arbitrarily, but only because he felt he had a better or more creative solution than the one proposed -- while also acknowledging that the "removing issue was a stupid idea." He also threatened to "make [Actix] repos private and then delete them...." Since then, matters have improved. The Github repository was restored and Kim said, "I realized, a lot of people depend on actix. And it would be unfair to just delete repos... I hope new community of developers emerge. And good luck!"

The developer news site DevClass wrote that "The apparent 'ragequit' has prompted questions about the dynamics within the open source community." Over 120 GitHub users have now signed a sympathetic letter to Nikolay from "users, contributors, and followers of your work in the Rust community," saying "We are extremely disappointed at the level of abuse directed towards you."

"Working on open source projects should be rewarding, and your work has empowered thousands of developers across the world to build web services with Rust. It's incredibly tragic for someone who has contributed so much to the community, to be made to feel so unwelcome that they feel that they have no other choice than to leave. This is not the kind of community we want."
This discussion has been archived. No new comments can be posted.

Framework Developer 'Ragequits' Open Source Community, Citing Negative Comments, 'Very Few Provide Help'

Comments Filter:
  • everyone knows better how to build software

    Any developers who claim their work is "average" instead of gods gift to software is unmotivated and only looking for a 9 to 5 time sink instead of an enjoyable career.

    • by Brain-Fu ( 1274756 ) on Saturday January 25, 2020 @01:42PM (#59655608) Homepage Journal

      I must disagree. Many people who believe that their work is "god's gift to software" are actually just suffering from the Dunning-Kruger effect. [wikipedia.org] Objectively speaking, confidence is no measure of talent.

      In my experience it is also common that authentically talented people suffer from Imposter Syndrome [wikipedia.org], and they wind up being very unsure of their skills even though their skills are top-notch. I just deleted a long paragraph about my experience seeing this in some of our new hires. Long story short: they were over-receptive to criticism from people who knew less than they did....until they started getting some achievements under their belt and realizing what they were capable of accomplishing.

      People who put heart into their code tend to write good code....and are the most vulnerable to being hurt by harsh criticism from people who mostly just want to fling shit. Furthermore, in the domain of software development, there are WAY more ways than one to solve a problem. Some people get a religious-level of devotion to their favorite set of design principles, and they see as wrong anything that uses other principles, regardless of how well those other principles may actually fit the problem. Approach-absolutism has generated enough frustration that we have lost several employees over it. And the open source community may have just lost one over it, as well.

      My advice is always to judge every problem on a case-by-case basis. One size never fits all.

      And the need for a "thick skin" must be balanced by SOME kind of effort to police the on-line community for toxicity, and purge it.

      • Pretty sure the OP was being sarcastic.

      • I've been coding for 43 years and I'm well recompensed for it. My code still sucks donkey balls when I first write it.
        Good code takes time and effort to make good.

      • by Darinbob ( 1142669 ) on Saturday January 25, 2020 @05:24PM (#59656124)

        Different people have different ideas and goals about what is good software. Some write crap but think it's great because they solved the problem quickly and are able to move onto the next task. Others have code that works great but which is difficult for others to understand or modify, leading coworkers to be angry at it (and in my experience, 95% of all work I've done over 30+ years is code maintenance). Others inside on absolutely perfect code that follows that year's fashion, and end up with something over engineered and difficult for to follow, and more time is spent on making the perfect platform or framework than in getting a product out to the customers. And to be honest here, all of them are right, that's all good code for the view they come from.

        But I do wish more programmers understood that there are other people out there who will need to look at and modify their code in the future.

        • by rtb61 ( 674572 )

          It is "Open Source Code", everyone get's to see the code, whose is in and whose is replaced and whose it out. All professions are competitive, it is in the very nature of capitalism and those who code is best is worth the most, them and they code they could potentially create. So those open source code environments are competitive places, the code competes for inclusions to survive. You just need to take that into account when it set up the system for including code into the project, the coding referee syst

          • Didn't always be this way though. Before open source was called open source, there was a wide range of programs with varying quality, and it was accepted. A whole lot of "I learned how to program writing this" style of stuff. Not much competition because everyone had a day job or was a student.

        • by Bengie ( 1121981 )
          Pretty code and good code are only correlated. I've seen my fair share of projects where I thought the code was beautiful until I had to actually debug it. It was then that I realized that there can be too much abstraction. The idea of abstraction is that you don't "want" to have to know the implementation, not that you don't "need" to know. When something is going wrong, I have to know what the implementation is. When the implementation is buried in some obscure config setting, I can't quickly figure out w
        • by Bengie ( 1121981 )
          My personal definition of "quality" is if you spend less time supporting than developing. At all levels of abstraction, it should be difficult to do the wrong thing, easy to do the right thing, and intuitive for someone who understands the problem to use. For example. I was looking into an issue with someone's deployment. I noticed it made use of a project that I created nearly 10 years ago. Turned out they didn't test a case. But when I was troubleshooting the issue, I looked into the project I created man
      • by Bengie ( 1121981 )

        In my experience it is also common that authentically talented people suffer from Imposter Syndrome [wikipedia.org], and they wind up being very unsure of their skills even though their skills are top-notch

        They notice their own mistakes. I dealt with imposter syndrome for several years after graduating. But then I got several opportunities that changed my perspective. Now I'm a senior software engineer because of my constant "keep improving" attitude. I'm still my own worst critic. The worst part is few people can give me useful feedback about how to improve myself, and those people are always busy.

      • I've had issues with people in open source. You shouldn't always immediately take sides as it can be either maintainer or user. Sometimes it's neither but some external force bashing users and maintainers together like two conkers.

        The latter case is VERY common. You can say all these things are free and open source and take it or leave it but the reality isn't like that. Suddenly everyone insists on using this stuff, you get replaced if you don't or you don't get a job if you're not using this stuff. Oth
    • Re: (Score:2, Insightful)

      only looking for a 9 to 5 time sink instead of an enjoyable career.

      That's exactly what I want at this point.

      I'm nearing the end of my career and I have zero interest in hard work, death marches, meetings, deadlines, or working in a "fast-paced, dynamic, ever-changing environment" (as Amazon loves to describe their workplace). Fuuuuuuuuuuuck NO.

      Seriously, fuck that. I want a quiet, sleepy little place where I can come in late, leave early, screw off and do my work at a leisurely pace.

      And by "work", I mean looking at cat pictures, taking extended lunches, browsing slashdot,

    • I wouldd hazard guess that rust community is extra bad.

      Also. Checking it out i just gotta ask if rust is so good etc. .. . why is this project so essential?

      • I think it is maybe the fastest web server framework in existence according to various tests. I tried to use it myself to build a simple web server, but the documentation sucks (as he admits). So I gave up on it. Yet another case of a developer who doesn't care whether anyone actually uses his software. He wrote a great framework and so everyone should just figure it out for themselves or read the code themselves and no the code isn't commented. This isn't the 1970s.

        • Oh the âoeyou want better docs, write them yourselfâ guy? I go banned from a GitHub repo for asking for better docs on a part of an api. Actually I got banned after explaining that I would write the docs, but I donâ(TM)t understand the api. Apparently pointing out a fault in the project is a personal attack for some people.

  • by zotz ( 3951 ) on Saturday January 25, 2020 @12:56PM (#59655454) Homepage Journal

    and very few provide any help...

    I am not one to talk but...

    I consider the work people do on other projects that I make use of as "help"... When I look at it that way, lots of people help and hte amount of help is huge...

    all the best,

    drew

    • Comment removed based on user account deletion
    • by AmiMoJo ( 196126 )

      It's less about help and more about demands I think. People make demands of open source developers and don't help in any way, say by contributing code or even money. They just tell you that your work is shit but for some reason they are bent on using it so you absolutely must fix it for them, and are an idiot for not immediately doing so.

      I've had this a lot before and my projects were never anything like as big as this one so I can only imagine how bad it is for him. I've had people alternatively beg and de

      • People make demands of open source developers and don't help in any way, say by contributing code or even money.

        Yep. I donate to OSS projects to show my appreciation. Not tons of money, but $20 here and there helps. I can afford it and it's good to give back.

      • This is very common. Blame the internet and ignore them.

      • by zotz ( 3951 )

        It's less about help and more about demands I think. People make demands of open source developers and don't help in any way, say by contributing code or even money. They just tell you that your work is shit but for some reason they are bent on using it so you absolutely must fix it for them, and are an idiot for not immediately doing so.

        I hear you and do not doubt that happens and sucks when it does happen...

        On the other hand, I think that may be a problem I would not mind having with at least one of my projects...

        Let's try:

        http://www.vassalengine.org/wi... [vassalengine.org]

        https://sourceforge.net/projec... [sourceforge.net]

        https://youtu.be/0Xg-jYA_xsg [youtu.be]

        We shall see....

        Would you like to play a game?

    • So this framework achieved high performance numbers by using clever unsafe tricks. Does that mean that the code base is more difficult to understand? More difficult to modify, without introducing unsafe behaviour? To be honest it's not that surprising that few people want to help.
  • by Anonymous Coward

    From the "NIH" aspect of it all to the embedded comments on "Why would anyone need to make their code that small". It certainly is an entertaining.

    And good luck getting anyone to use any of your projects in the future. I'm not going to build a project on something where the author up and leaves if we don't worship them.

    • Yeah, and anyways, you're supposed to be eating your own dog food. In web frameworks that means running a web consulting firm.

      Like RubyOnRails. It was always something that they made to service their clients, and they also gave it away as open source because it got them a lot of free advertising, and also lots of donated work. If the lead developer isn't making money off it, how does he know it has the features that people need from a web framework? That's what web frameworks are for, people who make a lot

  • by Phillip2 ( 203612 ) on Saturday January 25, 2020 @01:03PM (#59655474)

    One of the strange things here is that this story actually shows quite a lot of good behaviour from the Rust community.

    If you read the comments on the original github ticket most of them were respectful; one or two were not, and the posters called out. Likewise the comments on the Rust user forum were moderated and generally respectful. The main place that it got personal was on reddit, and even there people tried to pull the situation back. Clearly there was a failing in the Rust community here, but this may be because the Rust community has set itself quite a high bar. Esepcially in comparison to many other parts of the internet, getting rude, abusive and even highly offensive responses is considered normal and something that you have to put up with.

    • Yeah the behavior was so good that the developer rage quit and deleted the repo after saying "[he] felt betrayed after you put so much effort and then to hear all this shit comments, even if you understand that that is usual internet behavior.... Nowadays supporting actix project is not fun, and be[ing] part of rust community is not fun as well.". So, um, yeah, completely the opposite of what you are saying.

      • by Anonymous Coward
        The developer is a prima donna. Never except anything good from an internet community and you will not be disappointed. Also do not allow the internet community to force you into anything. It is your project do with it whatever you like and if somebody disagrees then he/she can fork it. That is the way for happy hacking!
    • by Anonymous Coward
      Yeah, having actually read the original threads that resulted in his outburst the situation is quite simple.
      A bug got filed. He said it's not a real bug. Bug was demonstrated. He said the solution was boring.
      Some asshat insulted him, he deleted the bug report.
      In his retirement letter he explained that "boring" was really shorthand for "I want a creative solution involving the unsafe keyword and am going to work on it on my own, thanks for reporting this bug".
      Obviously at the time no one knew that's what he
    • > If you read the comments on the original github ticket most of them were respectful;

      And this exactly the problem with that: it cuts both ways.

      The moderation will catch up the rude, entitled, but /genuinely frustrated users/ who don't know how to behave, but all the agenda-driven "safe-practices" cargo-cult pushing trolls will breeze their way through with the "respectful comments", even if they're completely clueless or dishonest. And the poor dev doesn't even have the recourse the tell them to go fuck

  • Declining to engage with negative people is a great way to improve your life.

    You'd like to think entitled people with nothing to offer but complaints would learn. But when one of them finishes growing up, they seem to get replaced by someone new and even more entitled.

    • Yep. And to achieve it; turn off push notifications.

    • "Declining to engage with negative people is a great way to improve your life."

      Ironically, he works for Microsoft...

    • On the flip-side. Sometimes people need to learn to distinguish criticism about oneâ(TM)s work from personal attacks. All too often lone project maintainers take big reports way too personally. This is an easy no-hire indicator for me.

  • by Quakeulf ( 2650167 ) on Saturday January 25, 2020 @01:12PM (#59655494)
    Reads like a parody article headline.
  • The real world requires a thick skin. Especially when voices are unfiltered. People need to learn how to recognize and deal with bullies/trolls.

    The internet gave everyone a voice. It also gave you the power to easily block them.
    • People shouldn't be bullying other people who are giving them stuff for free.

      • by Cylix ( 55374 )

        Maybe if he didn't write such terrible code he would get more positive comments?

      • People shouldn't be bullying other people who are giving them stuff for free.

        Or course they shouldn't. I should be able to walk around big cities with wads of cash hanging out of my pockets. You can have laws and rules, but it is impossible to stop bad human behavior 100% of the time. The best course of action is to know reality and adapt to it.

      • by gweihir ( 88907 )

        There is a lot of stuff people should not be doing but are doing all the time. You have to find a way to deal with it, expecting people to change just because what they are doing is stupid, wrong, impolite, self-destructive, etc. is futile.

    • Bullies are people with power. Victims have none. You've got your power dynamics backward. It's impossible for users to be bullies as they have no power. The maintainers have all the power, by definition they are the only ones who can be bullies. FYI.
  • The wonderful thing about opensource licenses is that anybody can take code and fork it.
    It looks like it was released under the Apache 2.0 license, and I don't think there is anything that lets him revoke the license after he made it public.
    If he throws a hissy fit and deletes his copy of the code, I don't believe that he can stop anybody from just taking their latest copy and continuing the project from there.

    Life goes on. No matter how special some people think they are.
    • That's the only reason he changed his mind about that part of his hissy fit; he can't actually affect any damage. Funny as hell, IMO.

  • It explained everything.

    Thougj I should have already realized it ar "framework".
    (The difference between a library and a framework, is that a library is sharing and integrating into your project, while a framework expects you to integrate into *it*, and lock you in to have no other gods beside it. The latter mindset is fundamentally incompatible to open source, let alone FLOSS. Like open source versus closed source.)

    • by ffkom ( 3519199 )
      Indeed, Rust has a history of being advocated way beyond its relevance by people who think everybody needs to applaud their efforts. I am so much not surprised the same people quickly turn butthurt when others do not express as much love for their work as they think they deserve.
      And yes, "frameworks" are a plague, most of them are written by people who think their ideas are so fancy that it is beyond them to just write a piece of software that does a specific thing, so they "leave it to the audience" to pro
  • by PPH ( 736903 ) on Saturday January 25, 2020 @03:27PM (#59655880)

    Can't take this acrimonious atmosphere anymore. I'm quitting and going over to work on the systemd team.

  • That the Internet conclusively answered the question “Are people born good, and they learn to be bad, or are they born bad and learn to be good?”

    What we’ve done, is taken human nature, and amplified it ... allowing the effects to spread beyond one’s immediate environment.

    While the idea of the collaborative digital village was potentially a good one, we forgot to take into account human nature, which dictates that people spend most of their time thinking about themselves, and a neglig

  • by reanjr ( 588767 ) on Saturday January 25, 2020 @07:34PM (#59656404) Homepage

    There's no reason you have to read people's comments or accept pull requests. He did this to himself.

  • Years ago I developed a project called driver on demand for Linux which was simply an easy way to install drivers (this pre-dated ubuntu's driver project).

    The amount of BS you put up with is incredible..

    I had people telling me that they didn't want linux to be like windows and it wasn't needed because all the drivers were included, etc. If people are wondering what's holding linux back, sometimes I feel its the "elite" users from the non-development community..

  • I've seen many web forums and Usenet groups fall because of assclowns trying to be l33t, picking on all the new comers, and just being a childish, immature high school clique.

    Yes, if I was running a business, this would be enough for me to shun Open Source and bed down with M$. >:(

    • I want to clarify that it's all of the elitism and the shitting on "newbies" that scares people away. They need to put themselves in the shoes of a business executive: "Should I use software written by people who seem like middle school teenagers, or should I go with Microsoft whose software appears to be written by grown mature adults?" Why isn't Linux taking over desktop PCs? Look in the mirror.
  • Winter Sucks (Score:2, Offtopic)

    Is he up in the Redmond area? Somebody go be a friend to this guy - he might be having a month where nothing seems OK. He might need help taking things one day at a time until the sun comes back.

  • Been there, done that. The problem with being a maintainer is that you are responsible for juggling interests while ensuring that things continue to work. People developing feature A do not care about whether they break feature B, nor do the feature B people care much about what's being proposed by feature A. One way to limit this is, of course, to be more selective about what kind of changes you will take and which not. The downsides of this is that if you become too much of a barrier, someone will ultimat

  • " The project is open source and while it is popular, there has been some unhappiness among users about its use of "unsafe" code... Safe code is protected from common bugs (and more importantly, security vulnerabilities) arising from issues like variables which point to uninitialized memory, or variables which are used after the memory allocated to them has been freed, or attempting to write data to a variable which exceeds the memory allocated. Code in Rust is safe by default, but the language also support

Some people manage by the book, even though they don't know who wrote the book or even what book.

Working...