In this weekly roundup, we highlight what we believe to be the most thoughtful, helpful, and/or interesting discussion over the past week! Though we are strong believers in healthy and respectful debate, we typically try to choose discussions that are positive and avoid those that are overly contentious.
Any folks whose articles we feature here will be rewarded with our Discussion of the Week badge. β¨
Now that y'all understand the flow, let's go! ππ¨
The Discussion of the Week
This week, let's give it up for Shameel (@shameel) for starting the practical and helpful discussion "Moment.js Is Now Legacy Project | Alternatives?":
Shameel provides us with some helpful context, pointing to the project status section of Moment.js's docs and highlighting specific quotes about Moment.js now being a legacy project in maintenance mode. Shameel plucked this quote that sums things up nicely "It is not dead, but it is indeed done."
Shameel then gets things rolling by suggesting a couple of alternatives and urging folks to weigh in with their own suggestions. And here's where the real fun starts...
@wraith weighs in with some info on TC39's new API, Temporal:
TC39 is working on a new API called Temporal that looks very promising. Itβs in Stage 3 so itβs worth having a look!
And, on a different note, @nikunjbhatt offers a reasonable counterpoint to the assumption that legacy projects need to be replaced:
This is what I don't like about software development. I am not talking about Moment.js. It's about the developers who think that a software is dead because no update is made. And since how much time? It depends on some random developers who think so!
There are objectives for developing a software. And when they are achieved, the software is declared dead!? There are many software which developers stop using for no logical reason, even when the developers haven't declared them dead, unmaintained, obsolete. But the wheel is reinvented, completely opposite of the reason behind making the software - that is, developers don't have to write the same code from scratch for every project they work on!
If a software has achieved its objectives then it is perfect for use. It is tried and tested. A lot of documentation, questions and answeres, solutions are available. Developers know its APIs. There are readymade code samples to copy-paste. Jumping to another software may require to create new code, new documentation, advertisement; and most importantly - a lot of time is wasted in developing, testing, debugging, learning, giving answers to questions.
I am seeing that new features are added in many software just because developers don't consider them dead. After a point, the newly added features are so odd that not even 0.00...001% developers use those features. Only their size increase. They become bloatware.
Many times it looks like the developers of the new software just want attention; it may be to be popular, add an achievement to their job profile, have money-making ideas, or any other reason.
It's a solid discussion, with folks dropping their suggestions for alternatives, people debating whether to replace legacy software, and others discussing the usefulness of the library and date conversion in general.
It's never too late to hop in there and share your opinions!
What are your picks?
The DEV Community is particularly special because of the kind, thoughtful, helpful, and entertaining discussions happening between community members. As such, we want to encourage folks to participate in discussions and reward those who are initiating or taking part in conversations across the community. After all, a community is made possible by the people interacting inside it.
There are loads of great discussions floating about in this community. This is just the one we chose to highlight. π
I urge you all to share your favorite discussion of the past week below in the comments. And if you're up for it, give the author an @mention β it'll probably make 'em feel good. π
Top comments (3)
Hi Michael,
I am glad that one of my blog got featured here.
Just wanted to know if "Discussion of the Week badge" would appear on my own profile (because currently it is not appearing) or it'll just remain here as part of the on-going series?
Hey Shameel! Happy to feature ya here. Really great discussion. π
And that was totally my fault, I must've forgotten to award you the badge... just hold one sec and I'll get ya covered.
Great!
Thank you very much! =)