I'm glad "all-the-package-names" includes "all-the-package-names"
But what if it was "all-the-package-names-that-do-not-reference-themselves"?
Which NPM package has the largest version number?
71–80 of 80 posts
Re: Which NPM package has the largest version number?
#72Earlier quoted context omitted.
Yes you can set price caps. The cost of a query is understandable ahead of time with the default pricing model ($6 per TB of data processed in a query). People usually get caught out by running expensive queries recursively. BigQuery is very cost effective and can be used safely.
You can tell someone has worked in the cloud for too long when they start to think of $6 per database query as a reasonable price.
[deleted]
Re: Which NPM package has the largest version number?
#73Earlier quoted context omitted.
Yes you can set price caps. The cost of a query is understandable ahead of time with the default pricing model ($6 per TB of data processed in a query). People usually get caught out by running expensive queries recursively. BigQuery is very cost effective and can be used safely.
Running ripgrep on my harddrive would cost me $48 at that price point.
BigQuery data is stored (I assume) in column oriented files with indices, so a typical query reads only a tiny fraction of the stored data.
Re: Which NPM package has the largest version number?
#74> there are over 2800 legacy mixed-case packages, many of which have the same spelling as other existing lowercase packages This is insane
Sounds like a typo-squatter’s paradise!
Re: Which NPM package has the largest version number?
#75Incidentally I once ran into a mature package that had lived in the 0.0.x lane forever and treated every release as a patch, racking up a huge version number, and I had to remind the maintainer that users depending with caret ranges won't get those updates automatically. (In semver caret ranges never change the leftmost non-zero digit; in 0.0.x that digit is the patch version, so ^0.0.123 is just a hard pin to 0.0.12…
Isn’t vim or bash kinda like that? One of them publishes something like a few hundred patches on top the released tarball…
Re: Which NPM package has the largest version number?
#76Earlier quoted context omitted.
Shouldn't vulnerabilities be "data" in this context? You bump the vulns database but keep the code at the same version if the logic is the same.
The particular problem here is if you started out doing it wrong then changing your update behavior would break everyone's scripting around it. By changing the 'code version' everyones CI/CD system just keeps working the same way as any other package.
I understand, but you can just have a committed config file that tells which definitions version to use and/or URL to retrieve (so you can mirror it on your infra or serve a patched version for your use case).
Re: Which NPM package has the largest version number?
#77Earlier quoted context omitted.
You can also query for free at clickpy.clickhouse.com. If you click on any of the links on the visuals you can see the query used. The underlying dataset is hosted at sql.clickhouse.com e.g. https://sql.clickhouse.com/?query=U0VMRUNUIGNvdW50KCkgICBGUk... disclaimer: built this a a while ago but we maintain this at clickhouse oh and rubygems data is also there.
Here [0] is the partial query on the ClickHouse dataset, with different results due to a quota error [1]. [0] https://sql.clickhouse.com?query=U0VMRUNUIHByb2plY3QsIE1BWCh... [1] Quota read limit exceeded. Results may be incomplete.
We have mvs you can use to avoid this
https://sql.clickhouse.com/?query=U0VMRUNUIHByb2plY3QsIE1BWC...
takes 0.1s
Re: Which NPM package has the largest version number?
#78The Julia General registry is locally stored as a tar.gz and has version info for all registered packages, so I tried this out for Julia packages. The top 5 are: DiffEqBase 6.189.1 LoopVectorization 0.12.172 Reactant 0.2.161 Mooncake 0.4.159 Distributions 0.25.120 So, no crazy numbers or random unknown packages, all are major packages that have just had a lot of work and history to them. Out of the top 10, pretty muc…
This would seem to imply that the vast majority of Julia packages are 0.x?
There are many that are, but I feel like your comment is based on the same faulty assumption as your sibling comment - that this is an ordering of version numbers as a whole. It's not, the ordering is on the same basis as in the post, the largest single number within the MAJOR.Minor.patch trio.
Re: Which NPM package has the largest version number?
#79Earlier quoted context omitted.
Tangential, but I've only heard about BigQuery from people being surprised with gargantuan bills for running one query on a public dataset. Is there a "safe" way to use it with a cost limit, for example?
Yes you can set price caps. The cost of a query is understandable ahead of time with the default pricing model ($6 per TB of data processed in a query). People usually get caught out by running expensive queries recursively. BigQuery is very cost effective and can be used safely.
Can you actually set "price caps"?
Most of the cloud services allow you to set alerts that are notorious for showing up after you've accidentally spend 50k USD. So even if you had a system that automated shutdown of services when getting the alert, you are SOL.
Re: Which NPM package has the largest version number?
#80Earlier quoted context omitted.
Brief reminder/clarification that these tools are used to circumvent WhatsApp ToS, and that they are used to: 1- Spam 2- Scam 3- Avoid paying for Whatsapp API (which is the only form of monetization) And that the reason this thing gets so many updates is probably because of a mouse and cat game where Meta updates their software continuously to avoid these types of hacks and the maintainers do so as well, whether in a…
Considering the 18 billions price tag and the current mixing of user data between meta and WhatsApp I believe that meta has now revenue streams in mind than just the API pricing
The less people pay for software, the more companies are forced to look into other forms of monetization (and of paying engineers).
The idea of users paying (even 1$ per year) for whatsapp has already died, now we are normalizing companies not paying for it? Fuck that, software engineers should be paid. Stop normalizing stealing.