"flabbergasted" ? That's quite a strong reaction. It's somewhat normal for nerdy mc-nerdfaces, which the writer definitely is (in all the good ways), to tell people about their hardware. Or at least it used to be? Seemed pretty geek-norm to me even if it was jarring.
I chose not to write it earlier but my candid thoughts were that he seemed too old to still be doing this. Its just younger enthusiasts and professional gamers that do this, and the younger enthusiasts eventually get enough money for a mac and choose that.
The PSU is completely overkill, as if he was going to get GPU's. But then he has this completely outdated and old, power inefficient GPU in it instead, which is nothing to brag about and doubly warrants an explanation if the rig is to be explained at all. All while newer GPU's from the same company solve all of his driver and OS problems.
As web developers, we heavily rely OSS packages. One popular example is Day.js, a JS lib for parsing, validating, manipulating, and formatting dates. It's a widely-used alternative to Moment, with over 17mil weekly downloads on npm.
A critical bug was discovered in Day.js (see: https://github.com/iamkun/dayjs/pull/2118) causing incorrect date manipulation (add, subtract) when in UTC TZ. This could have severe implications for any project relying on Day.js for date-related functionality. However, the maintainer of the project appears to be unresponsive, leaving the bug unresolved and the future of the library uncertain.
This raises some important questions for our community:
- At what point should we consider a widely-used OSS project "abandoned" if the maintainer is unresponsive?
- Is forking the project the best solution, or should we first try to reach out to the maintainer through other channels?
- Are there established community guidelines around responsiveness expectations for widely-used OSS projects?
- What are successful examples of community-driven forks or maintenance after a maintainer stepped away?
I am very aware that many of these developers give their spare time for free for these projects, with little or no payment, and I am very thankful for all their work. This developer does get some money (a small amount?) through OpenCollective, and possibly also works for a company (in China?) that makes a UI library, which I think uses Day.js internally.
I understand that the fields page could be confusing, especially for people who are not already versed in databases. I guess this is one reason that the spreadsheet as database metaphor has taken off so well in recent years?
There are docs, but of course some kind of introduction video would probably help a lot? What do you think?
Again, thanks for the kind words and feedback. It is invaluable.
Nice. Already learned that I kinda fail at this. But learning.
Only comment I have is it is super hard with small islands. Not exactly sure of the solution. Maybe show a red circle around the actual location if you click the wrong one? So you can learn. I'm stuck on St Martin.
Looks super awesome. I was worried about where the data was stored, but it looks like you've already answered that.
Have you looked at adding Google Drive sync? I've done it myself (on a project you've just inspired me to post about on HN) and is a super easy way for people to sync their own data without having to do any kind of setup.
It seems you should be able to do this with other online storage using OAuth but I haven't found anything else that works frontend only.
Google drive sync didn't occur to me, but I'll check it out! Could be a nice option to add to the storage method suite if they have APIs that would be easy to integrate.
