4 ms·
These JS developers would probably shiver at seeing many Common Lisp repos with a last commit like 12 years ago and still working like a charm.
by rootnod3 2y ago
These JS developers would probably shiver at seeing many Common Lisp repos with a last commit like 12 years ago and still working like a charm.
- kaptainscarlet 2y agoNode is bad but the worst I have seen is Android
- telgareith 2y agoHow about node on android?
- lpapez 2y agoDelete this comment right now, don't give them ideas.
- ian-g 2y agoToo late, we already have react native
- kaptainscarlet 2y agoIt's a double whammy
- plaidphantom 2y agoAnd Nativescript.
- abdisalan 2y agoI’m curious, how do you measure the pulse of a project that old? Do people still talk about it? Or that not even necessary — use it until it breaks and otherwise don’t think about it?
- toast0 2y agoIf it has an issue tracker, you can look in there for things that look like real issues and are unaddressed. If there's no issue tracker, you can YOLO and try it and see if it works, or you can look around at the code and see if it looks reasonable. Even if there are unaddressed issues, you can always use it and fix it when it breaks. If it's reasonable enough, it's a good start anyway. And at least my assumption with open source is I'm going to be fixing it when it breaks, so lack of a pulse is better than churn.
- swatcoder 2y agoWhy do you want your building materials to have a pulse? Ideally, in adopting dependencies, you should be looking for a mature utility whose design was clear and implementation is complete. If it's open source, you should be able to read and unserstand the code yourself, and you should make an earnest effort to do so, in case it has faults you wouldn't usually allow in your own code and in case you need to fork it at some point. This lets you you build well-designed, stable, maintainable, clear things yourself. The alternate, building your project on a random collection of "living" projects undergoing active development is how you banish yourself to perpetual maintenance, build failures and CVE warnings that have nothing to do with your work, surprise regressions when you update your referenced version (you are, at least, pinning your versions??), etc
- Macha 2y agoSomething like a HTTP 1.1 client is something you might expect would be a pretty stable thing that doesn't need too many updates, right? But I would not assume that a HTTP client that has been untouched in 12 years supports SNI, for example, which means that actually it might be totally useless for a lot of modern sites (certainly Android did not support SNI 12 years ago).
- popcalc 2y agoYou're going to put it behind nginx anyways, right? So why does it even matter?
- deleted 2y ago[deleted]