Facing the truth: Meteor became legacy in 2016 :-(

[a.com]

Blaze the front-end framework became legacy not meteor.

Is anyone’s quality of life going to shrink if they use meteor instead of feather.js or vice versa?

[efrancis]

For what it’s worth I did a combination of creating a cloaked version Simple Schema which pulls in the new one, and simply exposes it as if it were the old one, and selective updates to local packages (forks of various packages) to use the new versions of simple-schema and autoform.

SimpleSchema atmosphere package was deprecated in favor of an npm package by the same author awhile ago, just use that https://www.npmjs.com/package/simpl-schema

[captainn]

The problem is that many packages in atmosphere still reference the deprecated one. They are often still compatible with the latest one, but haven’t been updated. And things don’t work right when you have both of them in your project. So I created a local version which mimics the old one, and simply use that as a wrapper to the new one. That way, the old packages will use the new npm based version through my mimic package.

If anyone tries this, make sure to test thoroughly as this is certainly a hack.

[maxhodges]

Bash and the Linux command-line hasn’t changed that much in the past few years. Unix-based data storage is legacy in light of the strides Hadoop made in solving the problem of scalability.

@satya Therefore Unix became “legacy” a few years ago?