hermes VS dayjs

Hermes is a big one as well: low startup latency, low memory

https://hermesengine.dev/

Hermes

InstagramBundle.js.hbc.spk.xz is likely a compressed version of Hermes bytecode (js.hbc)"

In React Native's case, it uses an engine called Hermes:

📜 I made JSON.parse() 2x faster: Radek proposes to improve the performance of Hermes by using very fast C++ libs based on SIMD instructions. Interesting to read even if you don't use React-Native. Ongoing discussions on the Hermes PR.

Thanks! There's a preliminary PR with a discussion here: https://github.com/facebook/hermes/pull/933 (and broader context here: https://github.com/facebook/hermes/issues/811 ). But we'll see if there's any interest on Hermes' side to merging it. They definitely want to improve the parser, but it's unclear to me if they want to take on the simdjson/simdutf dependencies.

The library is actively maintained with over 46k github stars and 330 contributors ensuring it remains up-to-date and compatible with the latest JavaScript standards.

Document address: Day.js Official documentation

In this code snippet, we use the Javascript date library Day.js to parse and format the date, which gives us a more powerful method for formatting our dates.

The fact that moment.js or day.js needs to exist in 2024 bothers me a lot.

Day.js (45.3k ⭐) — A minimalist library that offers an excellent API without much overhead. It is very similar to Moment.js but much smaller in size. It also supports plugins for additional features.

Day.js is a lightweight alternative to the now deprecated date and time handling library, Moment.js. It is written in JavaScript and uses a similar API to Moment.js. Day.js is sufficient for date operations such as parsing, manipulation, and display. It is designed for use on both the browser and the Node.js runtime.

Day.js is awesome for comparing dates! You just need to make dayjs objects from whatever dates you have. You can use the dayjs() function with different inputs and formats. Here’s an example:

Similar API to Moment.js: Day.js provides a familiar API, making it easier for developers previously using Moment.js to transition.

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.