Prisoner’s dilemma: margins are razor thin. If your fellow farmers use better seeds then you are forced to use them as well. Otherwise you won’t be able to match their prices without selling at a loss.
That's true of any productivity enhancement. If your neighbors use more efficient tractors you're at the same disadvantage, but nobody argues that farmers should be able to steal tractors.
The parent has to do with permission, not stealing. Imagine if your neighbors could have an exclusive license to buy the new obviously superior tractor which you will never be able to obtain no matter what you do, simply because you're not them. This is legal today, the argument is that it shouldn't be because it punishes competition and lets the rights-holder wield too much power over the market.
Only if the cost of monsanto seed + roundup is less than the cost of regular seed per expected harvested bushel? Otherwise, no one would use the monsanto seed + roundup?
Who designs a signaling system where a ‘major disruption’ can be caused by a jumper cable applied at any point along potentially hundreds of kms? What about resiliency and fallbacks for something that critical?
Fear not! I’m sure the European Commission will promptly ban jumpstart cable ownership without a license.
The big bet is that the LLMs will get good enough to invent new frameworks or even branches of math. I hope it pans out. Otherwise we will get stuck in a local maximum for a while.
On the positive side We won’t get the cars, but our horses will be damn fast ;)
> Debian is a large and complicated project: the release announcement for version 13 says it has 69,830 packages, which take a total of 403 GB of disk, and contain 1,463,291,186 lines of code. So, suitably, it is a large and complex poll.
Surely these are not just Debian-owned packages. Whatever Debian decides won’t apply to packages not owned by Debian
Debian is huge - that's why so many other distros use it as a base!
So, yes, all those packages are maintained either by an individual Debian Developer or a team of them.
There are third party repos, but they're (currently) neither as widespread nor as commonly-used as those for other major distros. This vote won't affect them, and you might potentially expect to see their use grow if one of the harsher options in this GR were to pass.
Sure, this is (mostly) about direct contributions to Debian.
Proposal C does discourage use more broadly but acknowledges that many upstreams take a different view and that it would be impractical to ban them from using it.
I’ve been on a hunt for a perfect blank t shirt. After trying 10 different models either the fit or the material is not up to my standard.
I wonder how automatable manufacturing of T-Shirts is. Not sure if it is possible to automate sewing on a collar for example. Plus from what I’ve read a tubular t shirt is worse than front and back sewed at the sides cause it tends to stretch and rotate in one direction with time.
Anyway: continuous knitting is more automatable but introduces limitations just like injection moulding does. But the benefit of having a perfect fit might outweigh those limitations.
Particularly for finer gauge knits, I believe warp knitting is often used, where many strands are knit at once, crossing back and forth instead of a single strand going round and round (weft knitting) so there shouldn't be any issues with stretching or rotating. There's no reason a T-shirt can't be automated like anything else as far as I know, but I'm not in the industry at all.
I view it much like 3D printing, it's a tool that is well suited for some materials and tasks, but quite poor for others. Working around its constraints is part of the fun!
reply