Re:Show HN: Work for Performance – Open performance issues o...
by fn1 on Wednesday October 06, 2021 @11:36AM
(#28774414)
> This one is curious. The website appears to suggest that the list of open issues being presented was generated over 4 months ago.
It was generated today. 6.10, not 10.6. Fixed it.
> My second question is what is driving the short list of technologies?
I will add more languages.
Re:Show HN: Work for Performance – Open performance issues o...
by euphoria on Wednesday October 06, 2021 @12:46PM
(#28775257)
YYYY.MM.DD or YYYY-MM-DD is unambiguous if you would like to improve it.
Re:Show HN: Work for Performance – Open performance issues o...
by voiper1 on Wednesday October 06, 2021 @01:31PM
(#28775839)
ISO 8601 - https://xkcd.com/1179/
Because it's sorted better: https://www.reddit.com/r/ISO8601/comments/lkusca/improved_vi...
Re:Show HN: Work for Performance – Open performance issues o...
by david_for_you on Wednesday October 06, 2021 @11:36AM
(#28774403)
Given that today is 6th Oct, I am gonna guess 06-10-2021 means today, and not the 10th of June. More often than not American dates would use a 06/10/2021 format, I think?
Re:Show HN: Work for Performance – Open performance issues o...
by deathanatos on Wednesday October 06, 2021 @01:17PM
(#28775665)
> More often than not American dates would use a 06/10/2021
No, we use the nonsense MM/DD/YYYY ordering (usually without leading 0s). 6 Oct would be 10/6/2021.
ISO/RFC 3339 YYYY-MM-DD is really the way to go…
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?
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.