My goal of closing 10% of Emacs bugs (2020)

#1

Post by goranmoomin » Tue, Sep 06, 2022, 5:55 AM UTC

My goal of closing 10% of Emacs bugs (2020)
lars.ingebrigtsen.no

Re: My goal of closing 10% of Emacs bugs (2020)

#2

Post by Animats » Tue, Sep 06, 2022, 6:49 AM UTC

After 39 years of EMACS maintenance, having over 3000 bugs is embarrassing.

Re: My goal of closing 10% of Emacs bugs (2020)

#3

Post by fantyoon » Tue, Sep 06, 2022, 6:49 AM UTC

This post should probably get a (2020).

Re: My goal of closing 10% of Emacs bugs (2020)

#4

Post by chuckledog » Tue, Sep 06, 2022, 6:57 AM UTC

Looks like since this was posted, the page author has closed another 10% of open emacs bugs: https://lars.ingebrigtsen.no/2022/01/20/13x10/

Re: My goal of closing 10% of Emacs bugs (2020)

#5

Post by andsoitis » Tue, Sep 06, 2022, 6:57 AM UTC

Animats wrote: post #2

After 39 years of EMACS maintenance, having over 3000 bugs is embarrassing.

It is not like there haven’t been any new features added or refactors done in 39 years… There’s an opportunity cost to fixing bugs rather than adding new capabilities or improving the code base for easier extension. Not all bugs warrant squashing.

Re: My goal of closing 10% of Emacs bugs (2020)

#6

Post by un_ess » Tue, Sep 06, 2022, 7:05 AM UTC

chuckledog wrote: post #4

Looks like since this was posted, the page author has closed another 10% of open emacs bugs: https://lars.ingebrigtsen.no/2022/01/20/13x10/

Last update is https://lars.ingebrigtsen.no/2022/08/19/19x10/

Re: My goal of closing 10% of Emacs bugs (2020)

#7

Post by AlchemistCamp » Tue, Sep 06, 2022, 7:10 AM UTC

Animats wrote: post #2

After 39 years of EMACS maintenance, having over 3000 bugs is embarrassing.

Just wait until you see how many bugs VS Code has!

Re: My goal of closing 10% of Emacs bugs (2020)

#8

Post by capableweb » Tue, Sep 06, 2022, 7:11 AM UTC

Animats wrote: post #2

After 39 years of EMACS maintenance, having over 3000 bugs is embarrassing.

Like that says anything about anything?

github.com/apple/swift has ~4000 open issues labeled as "bug" and has existed since 8 years ago. That makes about ~500 "bugs" per year while emacs by the same measure then have about ~75 bugs per year.

Tell me again how awful that metric is compared to others?

Re: My goal of closing 10% of Emacs bugs (2020)

#9

Post by makach » Tue, Sep 06, 2022, 7:16 AM UTC

AlchemistCamp wrote: post #7

Animats wrote: post #2

After 39 years of EMACS maintenance, having over 3000 bugs is embarrassing.

Just wait until you see how many bugs VS Code has!

I love VS Code, but I occasionally wonder;

should we be amazed over its resilience or in awe that it actually works?

I can't decide.

also, every time I think about the amount of CPU cycles that has to be executed just for the first pixel to appear on the screen, just, wow. what a time to be alive!

Re: My goal of closing 10% of Emacs bugs (2020)

#10

Post by sweetgiorni » Tue, Sep 06, 2022, 7:18 AM UTC

capableweb wrote: post #8

Animats wrote: post #2

After 39 years of EMACS maintenance, having over 3000 bugs is embarrassing.

Like that says anything about anything? github.com/apple/swift has ~4000 open issues labeled as "bug" and has existed since 8 years ago. That makes about ~500 "bugs" per year while emacs by the same measure then have about ~75 bugs per year. Tell me again how awful that metric is compared to others?

I'd say that Swift's 4000 issues are significantly more embarrassing given that it's developed by the most valuable tech company in the world.