1,037 karma · joined May 13, 2018
If a car dealer advertises "free floormat with purchase", and they don't give you a floormat, you sue them. If it makes it all the way to the courtroom, it's an open-and-shut case.
Based on this advertising, I bet someone with the right lawyer could compel ZenDesk to release their source. In fact I hope this happens, then maybe companies will think twice before making false claims like this
What about module federation? Has any other bundler implemented that?
Imagine a web developer gets hired to build a landing page for a product. Yes please, charge twice as much for your work, sure. But say they tried to charge an ongoing 30% of all future revenue for that product. Do you think HN would be behind that?
Right. To mitigate that you would regularly run `npm audit` or even just `npm upgrade` – and test afterwards of course.
I'm not completely sold, but I do think it's a very interesting idea.
> Can I ask for a warning if I'm getting two different versions linked into the same binary?
Yes. That was the lint I linked in my last post. Alternatively, you can run `cargo tree --duplicates`.
> "I really, really don't think think you should be using 1.0 any more"
That's called "yanking". Personally I think it has limited usefulness, but it exists.
https://doc.rust-lang.org/cargo/commands/cargo-yank.html
> And what happens if both versions get pulled in, but the package in question uses an external data file whose format changed between 1.0 and 1.1?
If it uses something like `include!`, both copies will be compiled in (and maybe optimized later by the linker). If it's truly "external" like hosted on some website outside the package manager, then it just means the author broke their package. Maybe I misunderstood your question.
> one of my dependencies constructs a foo using X 1.0, is that value of a different type than a foo constructed by X 1.1?
I believe they are always different types. Cargo encourages but doesn't enforce semver, so anything can change between versions, including private fields or enum variants behind non_exhaustive, etc. So they're treated as different and you need to convert between them. Although this might only be true for major versions; I don't know off the top of my head.
To work around it you can convert the types at crate boundaries, or the package author can use the so-called "semver trick" [1]
For your second question, yes, Rust handles that well. If you depend on ">=1.0" and ">=1.1", you end up with a single copy of 1.1. If you depend on "=1.0" and "=1.1", you end up with both copies of the library. Every crate uses the version it requested. You can argue whether that's good or bad, but at least it's principled. There's a lint if you dislike that behavior.
https://rust-lang.github.io/rust-clippy/master/#multiple_cra...
colors@1.0.1-1.0.3
colors@1.0.1-1.0.4
With npm, you'll end up with 1.0.3 because it satisfies all constraints. OP wants to end up with 1.0.4 if at least one dependency tested with 1.0.4 (and reject 1.0.5). I don't know of a way to do this with npm today.
This wouldn't be a complete thread without someone mentioning Rust, so I'll do it. cargo-crev is a nice web-of-trust type code review system for Rust crates. https://github.com/crev-dev/cargo-crev
The author argues that version bounds should be treated as a maximum rather than a minimum, like Go does. e.g., if the latest version of colors is 1.0.3, and you have dependencies that request 1.0.1 and 1.0.2, you would end up with 1.0.2. The end result being, the exact resolved version will have been tested with at least one of your dependencies.
I must admit I like the idea.
On emissions, a quick google gives me this:
> most states provide some type of exemption specific to older cars.
https://www.hagerty.com/media/archived/emissions-and-your-co...
But classic cars are not a big interest of mine so I don't know the details.
> illicit transactions making up less than 0.5% of Bitcoin’s yearly volume in 2020
No adding required.
[1] throws a lot of numbers including/excluding different categories of drugs/etc. You can squabble about 7% or 12%, but the point is it's an order of magnitude higher than 0.5%.
0.5% of Bitcoin's volume is illegal activity. [2]
When will this crime meme finally die?
[1]: https://www.investopedia.com/articles/markets/032916/how-big...
[2]: https://ciphertrace.com/2020-year-end-cryptocurrency-crime-a...
I have no conclusion, just thought it was an interesting stat to look up.
[1]: https://www.internetlivestats.com/google-search-statistics/
https://gdpr-info.eu/art-22-gdpr/
> The data subject shall have the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her or similarly significantly affects him or her.
Quote this and maybe it will get you escalated, but who knows? A lot of companies seem to just ignore GDPR entirely.