The stakes just aren't high enough for us to implement any of this crap for the Internet in the first place. Let alone an entire government-administered hardware supply chain.
Those are different circuit courts where this ruling doesn't directly apply. However anyone who wants to challenge those laws would be stupid to not bring this to the judge - even though it doesn't apply, the judge still needs to justify why they are ignoring it and on appeal the circuit court will mention this ruling (either why they agree, or why they think it is wrong) - assuming the appeal is accepted.
It will be fine to print a gun but there will be laws outlawing your ability to print an iphone case and printers will have to detect parts from any registered manufacturer. So we will get the worst of all worlds. printers only for guns and not for people to build useful things.
Unjustified cynicism aside, the same technical reasons that a ban on printing gun parts is infeasible apply to printing iphone cases. There's no feasible way to detect what a printer is printing.
Don't underestimate the state's ability to spy on what you (and your devices) are doing or their willingness to erode your freedom even with massive false positive/negative rates.
I very much wouldn't put it past this government from banning unauthorised part printing in some draconian DMCA-esque law bought and paid for by John Deere and Apple, but is there any current proposals for such a law?
You joke but phone mounts for firearms are a thing. People use them to record gun PoV videos and to make range estimation (such as dope charts) more accessible.
my bet it is that it only affects the states in the 10th circuit, but could be assumed to be the law of the land, until a case is brought in which case there is only an issue if a different appeals circuit rules differently
Correct, it's only /binding/ on courts in the same District but they are often persuasive when cited in other districts if the decision is well reasoned and less controversial. This one will likely be contested, the circuits have very different ideas about gun rights.
> Surely the precedent would have to be that a model trained on GPL code has itself been infected by GPL, and therefore must have all source/weights released
I don't see how this follows, unless we also agree that humans who have ever read any GPL code are themselves permanently tainted and therefore cannot produce anything that isn't influenced even slightly by said code.
Is it just because we think the robot does a better job at learning than we do? It's an impossible line to draw, I agree, but I don't agree that the answer is "well then everything must be considered tainted," I say the answer is "ignore a vestigial concern of a bygone era."
The robot does a better job at reproduction. I don't think there exists a definition of "learning" unambiguous enough to make the claim that it learns better than humans. Specifically, published models don't learn at all -- after the training phase, the model weights are fully static.
GitHub issues (well, PR comments specifically) is possibly the clearest example of developers not knowing how their users use the product. There are only 3 important user stories that matter for this workflow and none of them are done well:
- I want to review surrounding code and get context for a line level change. Can't do it without clicking multiple expanders and even that has a limit of 2 or 3. I also can't comment on surrounding unchanged code which is sometimes extremely relevant, like "copy this pattern"
- I want to see all the unaddressed issues. Ones that are not marked as resolved and not replied to, however you slice it, the issue filters simply don't work
- I don't want the PR author to be able to resolve issues without me getting indicated to verify them. The workaround is them commenting "fixed" on every issue. Make the button say "mark as resolved" and "verify resolved"
- Bonus: if you've got more than 40 comments on a PR, good luck finding some random subset of them. They're just unavailable and the UI unapologetically says "eh can't do it". Yeah small PRs but it happens.
Popup or inline i don't really care, the baseline workflow is completely uninformed.
I'd go long Google too if using Gemini CLI felt anything close to the experience I get with Codex or Claude. They might have great hardware but it's worthless if their flagship coding agent gets stuck in loops trying to find the end of turn token.
Gemini CLI isn't a great product unfortunately. While it's unfortunately tied to a GUI, antigravity is a far superior agent harness. I suggest comparing that to Claude code instead.
And the converse is true also. I mean, look at NVIDIA. For the longest time they were just a gaming card company, competing with AMD. I remember alternating between the two companies for my custom builds in the 90s and it basically came down to rendering speed and frame rate.
But Jensen bet on the "compute engine" horse and pushed CUDA out, which became the defacto standard for doing fast, parallel arithmetic on a GPU. He was able to ride the BitCoin wave and then the big one, DNNs. AMD still hasn't caught on yet (despite 15 years having gone by).
I make the mistake of thinking its 2020 as well. CUDA was announced 2006 and released Feb 2007. So its actually 20 years that AMD/RADEON hasn't caught on that they need a good software stack.
I wish it were otherwise but antigravity is also a distant third behind codex cli/app, and claude code.
3.1 pro is just fundamentally not on the same level. In any context I've tried it in, for code review it acts like a model from 1yr ago in that it's all hallucinated superficial bullshit.
Claude code is significantly less likely to produce the same (yet still does a decent amount). Gpt 5.4 high/xhigh is on another level altogether - truly not comparable to Gemini.
I use Claude Code all day and use Gemini CLI for personal projects and I don't see the huge gap that other people seem to talk about a lot. Truthfully there are parts of Gemini CLI I like better than Claude Code.
I agree. I like using Antigravity for some of my frontend work, and I find it does a better job than Claude Code - Opus 4.6. I’ve also found the Gemini Flash models to be good at legal defense research—I use them to help New Yorkers fight parking tickets (https://nyceasyparking.com). That said, the Claude models are still amazing at agentic work.
I don't use Gemini CLI- I use the extension in VSCode, and Gemini extension in VS Code is barely usable in comparison to Claude or GPT-5.4. My experience (consistent with a lot of other reports) is that it takes long time before answer, and frequently returns errors (after a long wait). But I think it's specific to the extension (and maynbe the CLI) because the web version of Gemini works quickly and rarely errors (for me).
Of the big three, Gemini gives me the worst responses for the type of tasks I give it. I haven’t really tried it for agentic coding, but the LLM itself often gives, long meandering answers and adds weird little bits of editorializing that are unnecessary at best and misleading at worst.
Same. The tone is really off. Here is a response I just got from Gemini 3.1: "Your simulation results are incredibly insightful, and they actually touch on one of the most notoriously difficult aspects of ..." It's pure bullshit, my simulation results are in fact broken, GPT spotted it immediately.
kind of sad that the CSS specification wound up with this clunky `light-dark(white,black)` thing instead of literally anything more extensible like, `themed(dark(black), light(white), retro(purple))`.
Then you'd be able to have a cool theme dropdown like sites used to have, fully CSS-driven with essentially no JS required, in a compatible and modern way.
The proposers of `light-dark()` themselves recognized that `light-dark()` was presumably a "stepping stone" towards (and then eventually just a shorthand for) a deeper `schemed-value()` function similar to what you are asking for, once CSS also picked up a way to define custom color schemes. (Often proposed as an `@color-scheme` rule or block.)
how your users' browsers choose to render `about:blank` while waiting on your page to be delivered is outside of both your control and concern
on Gnome i've got system-wide dark mode turned on and idk, my Firefox is dark gray until it gets any content. so users have the power and should exercise it to tailor their experience as they wish
> Could probably create exceptions for bullets used at the gun range, so you can become proficient and safe.
Amusing to imagine the red diesel of sport shooting - better hope the tax authority doesn't find any combustion-proof dye on the self-defense shell casings!
To be honest I was thinking more along the lines of you either store ammo at the range, with a checkin/checkout process, or you can receive a tax receipt for number of spent casings.
It's legal to go target shooting on most public lands, and on private property in rural areas (assuming you own it or have the owner's permission). People can easily burn through 1,000 rounds in a weekend in such places. Are they going to get a $20k loan and collect every casing for a refund? Of course people should pick up their brass on public lands, but if you have a private range, there's no need to keep it pristine constantly.
Also brass is often ejected forward of the firing line, meaning cease fire must be called frequently for individuals to collect their brass. And if multiple people are shooting at once, how do they determine who shot which casing? Considering the financial incentives, I could see frequent disagreements over brass ownership.
Then there's the issue of implementation. A proposed law and its implementation are often quite different. For example, California requires a background check when purchasing ammunition. Only California residents can buy ammunition in the state (which creates a problem for out-of-state hunters). This system is plagued with false positives. When I lived in California, I purchased multiple firearms but was unable to buy ammunition due to being incorrectly denied. This happens to 10-16% of legal firearm owners in the state. My assumption is that any sort of ammo tax/refund scheme would be similarly fraught with issues.
Honestly, I think such restrictions are a fool's errand. Both smokeless powder and automatic actions have existed for over a century. Given current US culture, effectively restricting such simple technology would require draconian laws & enforcement of those laws. This is actually a more difficult problem than previous failed attempts to restrict alcohol and other drugs, as the government needs a constant supply of firearms and ammunition.
reply