Why users cannot create Issues directly

Post by IshKebab » Fri, Jan 02, 2026, 4:31 PM UTC

mitchellh wrote: post #65

eviks wrote: post #10

> This pattern makes it easier for maintainers or contributors to find issues to work on since every issue is ready to be worked on. How is this not trivially solved via a "ready-to-be-worked-on" tag?

Because I don't want my default view to be "triage." If GitHub allowed default issue views (and reflected that in the issue count in the tabs as well), then maybe. But currently, it doesn't work. I've tried it at large project scale across many (multiple projects with more than 20K stars and millions of downloads). Compared to that, this system has been a huge success. It has its own problems, but it's directionally…

Post by IshKebab » Fri, Jan 02, 2026, 4:33 PM UTC

Etheryte wrote: post #77

lijok wrote: post #69

A couple of big projects in the python space use this approach. Pisses me off as a power user. I find what are clearly bugs all the time, and am forced through a funnel that places the burden on me. Stinks of arrogance to think your project is that rock solid you should add friction for reporting bugs. Especially in “forever v0” projects. But, I am super lazy.

[flagged]

Post by samus » Fri, Jan 02, 2026, 4:36 PM UTC

abenga wrote: post #134

samus wrote: post #122

Earlier quoted context omitted.

There is no justification for that IMHO. The program text only needs to be in memory once. However, each process probably has its own instance of the JS engine, together with the website's heap data and the JIT-compiled code objects. That adds up.

I'd very much like a crash in one tab not to kill other tabs. And having per tab sandboxing would be more secure, no?

Post by [deleted] » Fri, Jan 02, 2026, 4:38 PM UTC

taneq wrote: post #174

twelvedogs wrote: post #153

Earlier quoted context omitted.

facebook literally obfuscates their UI to stop you turning off "features" they want to push on you it is a UI designed to be hard to use

You're talking about two different things here (and I'm not condoning either, to be clear.) 1) UI = a clearly documented way to configure all features and make the software work exactly how you want. 2) UI = load a web page and try to do the thing you wanted to do (in this case communicate with some specific people). FB is clearly terrible at 1 but pretty alright at 2.

Post by ikawe » Fri, Jan 02, 2026, 4:39 PM UTC

kreco wrote: post #214

To me this just shows that the Github issue concept is significantly flowed.