> Because climate-change is eating the world. CPUs need power. Less CPU-usage equals less power-consumption.<p>Faster code might result in more CPU-usage not less, because the amount of real world value derived by the same amount of electricity increases.<p>That being said I'm all for more efficient & faster code.
This one is curious. The website appears to suggest that the list of open issues being presented was generated over 4 months ago. That made me assume it was someone stumbling upon it and then sticking it on HN, but the github name on the submission and the HN name on here are close enough it is probably the same person.<p>Shouldn't you regenerate the list at least nightly to be up to date so people are not reading over issues potentially closed months ago?<p>My second question is what is driving the short list of technologies? You include Typescript and Javascript as seperate entries but no Ruby, Rust or C++ all of which jumped out to me but no doubt there is a much wider list of relevant technologies I am not thinking about as well.
Personally I haven't had a great experience with opening performance-related issues, a lot of the times people don't care enough about performance, pretty often they feel kind of insulted that you are saying that something they have written is slow and should be made faster.<p>A lot of the times, especially if the library is small, I find it more useful to just rewrite the whole thing. Or forking it with the performance patches and submit a PR, trying to convince people to make something faster with an issue doesn't work very well in my experience.
I thought of this idea as well, but don’t think this is really the right approach.
Many of these issues relate to specific features which developers subsequently avoid using.
I think these types of initiatives should be more broadly targeted and probably curated by the maintainers/users of the software. E.g. the faster-cpython project is focusing on improving general Python interpreter performance: <a href="https://github.com/faster-cpython/ideas" rel="nofollow">https://github.com/faster-cpython/ideas</a>
The biggest performance problems with python involve the GIL, highly dynamic runtime and an extension API that exposes internals.<p>I believe moving python towards a more static type system, functional programming and transpilation to other languages is a good direction.
Neat idea! There's no C, C++, Perl, or MATLAB entry though, so my ability to help is limited... :/<p>Surely there's a need for "implement <foo> in better machine code" work, in other languages and projects, no?