Discussions Alternatives

Similar projects and alternatives to discussions

HomeBrew

1,281 39,303 10.0 Ruby discussions VS HomeBrew

🍺 The missing package manager for macOS (or Linux)
Babel (Formerly 6to5)

58 42,901 9.7 TypeScript discussions VS Babel (Formerly 6to5)

🐠 Babel is a compiler for writing next generation JavaScript.
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
npm

48 17,233 2.1 JavaScript discussions VS npm
enquirer

18 7,498 4.9 JavaScript discussions VS enquirer

Stylish, intuitive and user-friendly prompts, for Node.js. Used by eslint, webpack, yarn, pm2, pnpm, RedwoodJS, FactorJS, salesforce, Cypress, Google Lighthouse, Generate, tencent cloudbase, lint-staged, gluegun, hygen, hardhat, AWS Amplify, GitHub Actions Toolkit, @airbnb/nimbus, and many others! Please follow Enquirer's author: https://github.com/jonschlinkert
rfcs

7 44 4.6 discussions VS rfcs

RubyGems + Bundler RFCs (by rubygems)
isnan

1 0 10.0 JavaScript discussions VS isnan

Test whether value is NaN

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better discussions alternative or higher similarity.

Suggest an alternative to discussions

discussions reviews and mentions

Posts with mentions or reviews of discussions. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-05-10.

NPM Vulnerability Discussion on Twitter
7 projects | news.ycombinator.com | 10 May 2022

The question in that thread, and this later thread,[1] is how to know which keys are valid to sign a package.
For example: I go to release a new version and I've lost my private key, so I roll a new one -- this will happen often across npm's 1.3 million packages. Do I then ... log in with my email and update the private key on my account and go about my business? What process does npm use to make sure my new key is valid? Can a person with control over my email address fake that process? How are key rotations communicated to people updating packages -- as an almost-always-false-positive red flag, or not at all, or some useful amount in between? If you don't get this part of the design right -- and no one suggests how to in those threads -- then you're just doing hashes with worse UX. And the more you look at it, the more you might start to think (as the npm devs seem to) that npm account security is the linchpin of the whole thing rather than signing.
It's not just npm; that thread includes a PyPI core dev chipping in with the same view: "Lots of language repositories have implemented (a) [signing] and punted on (b) and (c) [some way to know which keys to trust] and essentially gained nothing. It's my belief that if npm does (a) without a solution for (b) and (c) they'll have gained nothing as well." It also has a link from a Homebrew issue thread deciding not to do signatures for the same reason -- they'd convey a false expectation without a solution for key verification.[2]
[1] https://github.com/node-forward/discussions/issues/29