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

Slow Software

inkandswitch.com

Post reply on HN
Print view View original

251–260 of 272 posts

Re: Slow Software

#251

Post by RayDonnelly »

ggreer wrote: post #249
RayDonnelly wrote: post #247

Earlier quoted context omitted.

So it's not really an open source project in any meaningful way? Do you consider it reasonable for people to waste their time making PRs and working trying to help you to improve the silver searcher? Could you put something up describing this policy? Could you recruit someone who's proven themselves to be maybe somewhere near as good as you to be a co-maintainer? As I say I couldn't care less about my PR now since I'…

Other people want to modify my project, usually in ways that break it, and somehow I am obligated to provide my time and skills to them for free? I don't understand where you're coming from at all.

You don't want to waste your own precious time but are more than happy for many other people to waste theirs?

Also you merged commits starting from 24 Dec 2011 and ending on 18th August. Presumably you saw value in those commits?

Re: Slow Software

#252

Post by hutattedonmyarm »

robochat wrote: post #16

My least favorite type of latency is when you start typing and the application takes at least 1 - 2 seconds to catch up with you. This still happen to me often enough to be a normal occurrence on both my desktop computer and phone.

The Windows 10 Start Menu on my machine loves to eat the first one or two typed characters

Re: Slow Software

#253

Post by burntsushi »

RayDonnelly wrote: post #247
ggreer wrote: post #246

Earlier quoted context omitted.

Years ago I disabled github notifications and ignored pull requests because honestly, 95% of them are crap. So many of them degrade performance, break unrelated features, or are incompatible with certain platforms. I don't have the time or inclination to sift through them all to figure out which 5% are good, especially since I'm not getting paid for it. Sorry.

So it's not really an open source project in any meaningful way? Do you consider it reasonable for people to waste their time making PRs and working trying to help you to improve the silver searcher? Could you put something up describing this policy? Could you recruit someone who's proven themselves to be maybe somewhere near as good as you to be a co-maintainer? As I say I couldn't care less about my PR now since I'…

As the maintainer of ripgrep, I'd like to respectfully ask you not to harass other maintainers of open source projects about how they spend their free time. I've been where ggreer is and it's not pleasant. I completely understand their position, and a little empathy on your part would go a long way. In an ideal world, the maintenance status of a project would be mentioned in the project README, but speaking from personal experience, this is seemingly difficult to do in practice.

Re: Slow Software

#254

Post by RayDonnelly »

burntsushi wrote: post #253
RayDonnelly wrote: post #247

Earlier quoted context omitted.

So it's not really an open source project in any meaningful way? Do you consider it reasonable for people to waste their time making PRs and working trying to help you to improve the silver searcher? Could you put something up describing this policy? Could you recruit someone who's proven themselves to be maybe somewhere near as good as you to be a co-maintainer? As I say I couldn't care less about my PR now since I'…

As the maintainer of ripgrep, I'd like to respectfully ask you not to harass other maintainers of open source projects about how they spend their free time. I've been where ggreer is and it's not pleasant. I completely understand their position, and a little empathy on your part would go a long way. In an ideal world, the maintenance status of a project would be mentioned in the project README, but speaking from pers…

I respectfully disagree with you. I wasted perhap 10 hours of my life or more on this PR (pointlessly rebasing it a few times). 95 other PRs are outstanding. There are many ways to improve this situation. I pointed two of them out:

    1. Declare that you won't accept (or even review) them, preferably at the top of README.md *
    2. Give a second person merge status.
I have some empathy for the maintainer but I also have empathy for the prospective contributors who spent a chunk of their free time working on https://github.com/ggreer/the_silver_searcher/pulls

I've done my bit here to stop wasting people's time globally, I don't consider a maintainer's time more valuable than a contributor's time. That's elitest nonsense.

https://github.com/ggreer/the_silver_searcher/issues/1284

* The likely side-effect is a unblessed fork (or people not wasting their time, or if they do, well, they didn't read the README.md and cannot be too annoyed at anyone but themselves).

Re: Slow Software

#255

Post by RayDonnelly »

burntsushi wrote: post #253
RayDonnelly wrote: post #247

Earlier quoted context omitted.

So it's not really an open source project in any meaningful way? Do you consider it reasonable for people to waste their time making PRs and working trying to help you to improve the silver searcher? Could you put something up describing this policy? Could you recruit someone who's proven themselves to be maybe somewhere near as good as you to be a co-maintainer? As I say I couldn't care less about my PR now since I'…

As the maintainer of ripgrep, I'd like to respectfully ask you not to harass other maintainers of open source projects about how they spend their free time. I've been where ggreer is and it's not pleasant. I completely understand their position, and a little empathy on your part would go a long way. In an ideal world, the maintenance status of a project would be mentioned in the project README, but speaking from pers…

In what way is updating README.md difficult? Please have as much respect for contributors and potential contributors as you seem to have for maintainers. They're all people after all and their free time is equally important.

Re: Slow Software

#256

Post by ggreer »

RayDonnelly wrote: post #254
burntsushi wrote: post #253

Earlier quoted context omitted.

As the maintainer of ripgrep, I'd like to respectfully ask you not to harass other maintainers of open source projects about how they spend their free time. I've been where ggreer is and it's not pleasant. I completely understand their position, and a little empathy on your part would go a long way. In an ideal world, the maintenance status of a project would be mentioned in the project README, but speaking from pers…

I respectfully disagree with you. I wasted perhap 10 hours of my life or more on this PR (pointlessly rebasing it a few times). 95 other PRs are outstanding. There are many ways to improve this situation. I pointed two of them out: 1. Declare that you won't accept (or even review) them, preferably at the top of README.md * 2. Give a second person merge status. I have some empathy for the maintainer but I also have em…

Come on dude, I just want to enjoy my long weekend. Please stop bothering me by creating spurious issues on my GitHub repo.

Re: Slow Software

#257

Post by RayDonnelly »

ggreer wrote: post #256
RayDonnelly wrote: post #254

Earlier quoted context omitted.

I respectfully disagree with you. I wasted perhap 10 hours of my life or more on this PR (pointlessly rebasing it a few times). 95 other PRs are outstanding. There are many ways to improve this situation. I pointed two of them out: 1. Declare that you won't accept (or even review) them, preferably at the top of README.md * 2. Give a second person merge status. I have some empathy for the maintainer but I also have em…

Come on dude, I just want to enjoy my long weekend. Please stop bothering me by creating spurious issues on my GitHub repo.

OK sure, but would you consider merging one PR that explains that people should not expect PRs to get reviewed? I'm happy to do the work if you'll review and merge it.

That way we can avoid unfortunate incidents such as this in future.

Re: Slow Software

#258

Post by phtrivier »

davedx wrote: post #150
icebraining wrote: post #112

Earlier quoted context omitted.

The author doesn't say you should use a language without GC, but minimize its effects. There are techniques to avoid GC churn by reducing allocations and the subsequent cleanups.

This. My last contract was working on digital TV UI software that was build using nodejs, so we did a lot of work optimizing our code and architecture to reduce latencies and load times. I ended up going down the rabbit hole of how v8, libuv and node's GC work. It was a great learning experience. You really can influence your app's performance if you have the attitude and determination.

Oh I absolutely agree that it can be done, I just wish the article had went into more details about how that's done...

Re: Slow Software

#259

Post by burntsushi »

RayDonnelly wrote: post #255
burntsushi wrote: post #253

Earlier quoted context omitted.

As the maintainer of ripgrep, I'd like to respectfully ask you not to harass other maintainers of open source projects about how they spend their free time. I've been where ggreer is and it's not pleasant. I completely understand their position, and a little empathy on your part would go a long way. In an ideal world, the maintenance status of a project would be mentioned in the project README, but speaking from pers…

In what way is updating README.md difficult? Please have as much respect for contributors and potential contributors as you seem to have for maintainers. They're all people after all and their free time is equally important.

In theory, I agree. But again, speaking from personal experience as the maintainer of several somewhat popular projects, it is actually emotionally difficult to update the maintenance status. It appears trivial from the outside, and to some extent I agree with what you're saying about being respectful of others' time, but we should nevertheless do our best to be kind to others. Calling out a maintainer in an off topic comment is not being kind.

Re: Slow Software

#260

Post by RayDonnelly »

RayDonnelly wrote: post #244

Can we talk about slow maintainers here instead? Can you explain why you never responded to https://github.com/ggreer/the_silver_searcher/pull/619 despite me asking you to several times over the course of many years?

ggreer: I have no grudge, hopefully ag will continue to be a success for its users but it'd be lovely if people could contribute to making it even more of a success. I believe there are some easy ways to achieve that (expanding the core team if you were ameanable or somewhere or shomehow ossasionally explaining why PRs are not getting looked at), and some not so easy ways (CI with good testsuites and benchmarks).

I apologise for my overly aggressive comments, I did not handle the fact I really hoped to help out on ag and got frustrated by the experience very well (at all).

Have a nice weekend.

Post reply on HN