What the hell industry do you work in, then?
What the hell industry do you work in, then?
Whenever people ask why anyone makes open source software for free, I’m going to use this as a metaphor.
Dang, a whole dollar? I would sell origami tanks for 25¢ each, didn’t realize people would pay more than that.
I thought so too. I remember looking for alternatives for when it would be removed completely.
This ridiculous article is what led me to unsubscribe from his newsletter altogether.
Are we all looking at the same repository? I see 3 commits in August, all of which were squash merges of PRs. 2 other PRs have been opened in this past week alone: one by a maintainer, and the other has already been reviewed by the maintainer.
I’m so glad they remind me so I don’t forget and accidentally buy them again!
This will also hopefully limit the number of issues opened that are resolved with a “you must enable X feature.”
Output from an AI has just been recently considered as not copyrightable.
Where can I read more about this? I’ve seen it mentioned a few times, but never with any links.
You can download the code directly from crates.io still.
Did you just have a stroke
Yeah, I’ve noticed this happening elsewhere on Lemmy instances, too.
As far as I know, no one has yet been able to reproduce the binary with the source code, so I don’t think the contents of it are confirmed at all.
If someone does fork serde, can they at least make it so it actually follows semver?
You’re right, I missed that. That’s unfortunate.
Hey, maybe this will actually lead to standardization of feature documentation? It’s been in terrible shape for years. The fact that optional dependencies and features have been treated nearly the same by cargo, but treated differently by crates.io, makes it useless for discovering features for crates. Up until now, my go-to method is to examine the Cargo.toml
file directly, and if I can’t figure out what a feature does there I look directly at the source code.
I’ve always thought I would have a Meowth/Persian. Seems like a good companion.
Well said. I imagine that maintaining a project as ubiquitous as serde
is not an easy job, and I’m sure dtolnay is no stranger to holding his ground when people disagree with him. I’m therefore not that surprised to see him holding his ground on this issue, and I think people should still continue the discussion with him instead of immediately forking.
I personally think that proposing a PR to allow opting out of this (as is being hashed out here: https://github.com/serde-rs/serde/pull/2580) is a much better solution than forking. In my experience in open source dev, writing a PR often produces much better results than just complaining in an issue.
Get some extra so you can pay the extra few thousand a month more you’ll be paying on your mortgage