You can easily get compressed episodes of a TV show that are 250MB, so it's like watching a TV series at the rate of 2 episodes every 5 minutes. Obviously better quality is in the range 500MB-1.5GB for a 45-minute episode, so even being generous it's 20 minutes of compressed TV or 70 minutes of uncompressed music every 5 minutes.
Yes, as I understand it, the ~700 MiB "standard" was derived from the capacity of a CD. A rip is definitionally a copy that lacks some of the original data of the source media.
WebUSB is incredibly useful to flash firmware and update configuration on random devices.
The alternative is to install random software on your computer for every device (or, if you're a Linux user, you'll likely simply be excluded and whine about it).
Making device companion utilities WebUSB means that when the hardware maker goes belly-up and their site goes down, or just decides to stop supporting a device, it's now a brick. When they are native software programs, someone can preserve them.
Just look at all the old hardware like CNC machines still running just fine on old computers, and imagine if they were connected via WebUSB instead.
WebUSB is just a terrible idea if you're not an ad company.
Not if it's an Open Source project made by a bunch of people for the love of the game. Install a PWA and you have it even when the site is down, if not code available on GH. It's possible to do on a computer (write code and distribute an app not via an app store)...but not in the magical protected-profits land of mobile devices.
Your way of thinking is the reason why we now have a half dozen trillion dollar companies controlling the world.
You can move without disconnecting, you have to "drag" instead of move. Press G. Last time I tried it it just created a ratsnest of random angles wires though so you still have to fix them all one by one.
That's also why I ditched kicad, it's really a very very basic thing that every other software gets right. Wires should follow your part and do 0 and 90 angles only... Then all you have to fix are overlaps, if any.
I would recommend you both try recent KiCad in that case, because what you're asking for is how it has worked since KiCad 9 (and 10 will also warn you about overlaps visually)
I've not heard many people claim that LLMs don't hallucinate, however I have seen people (that I previously believed to be smart):
1. Believe LLMs outright even knowing they are frequently wrong
2. Claim that LLMs making shit up is caused by the user not prompting it correctly. I suppose in the same way that C is memory safe and only bad programmers make it not so.
AnonC doesn't seem to be upset that the journalist was fired. The disappointment comes from Ars trying to brush this entire situation away by deleting articles, comments, and making no statement on their website.
My understanding is that AnonC is upset at Ars not taking the mature approach by allowing this to become a learning moment for the employee and using it to double down and confirm their stance on AI generated content. There's strength in maturity. But I am doing some reading between the lines, and I'm possibly reading a bit too much into "There’s something to be said about the value of owning up to issues"
Reminds me of a story I was told as an intern deploying infra changes to prod for the first time. Some guy had accidentally caused hours of downtime, and was expecting to be fired, only for his boss to say "Those hours of downtime is the price we pay to train our staff (you) to be careful. If we fire you, we throw the investment out the window"
There is a difference between an error and totally misunderstand your actual task. I have absolutely no sympathy for journalists getting caught producing hallucinated articles. Thats an absolute no go, and should always result in that person being fired.
Same goes for engineers reviewing vibeslop. If you let that shit through code review, and a customer impacting outage results, that should be instant termination. But it won't be, because as an engineer you are supposed to be held "blameless" right?
I love vibe coding but you are absolutely right. We're at the stage where vibe coding is a fun way to produce sloppy software and that's fine if the intended user is just yourself and you're fully informed about what you're getting into. But actually shipping vibe coded slop to other people is wacky, anybody doing the needs to be manually reviewing every commit very carefully and needs to be prepared to accept personal responsibility for anything that slips by.
The problem is that reviewing code for correctness is harder than writing correct code. So these things will always slip through review. I'm a little bit divided here whether we can (or should) blame a reviewer too harshly for letting broken code through review whether it's LLM or human generated.
I've worked on teams with a rubber stamp review culture where you're seen as a problem if you "slow things down" too much with thorough review. I've also worked on teams that see value in correctness and rigor. I've never worked on a team where a reviewer is putting their job on the line every time they click "Approve". And culturally, I'm not sure I'd want to.
That said I think it's pretty clear we need mechanisms that better hold engineers to account for signing off on things they shouldn't have. In some engineering domains you can lose your license for this kind of thing, and I feel like we need some analogous structure for the profession of software engineering.
... and, also, improved processes. There should be no way an individual writer can damage the brand to this extent with absolutely no checks or oversight. This was just an error, but a bad actor could've put something far, far worse out there.
Even an automated quote-checker might have helped in this case.
Fact checking is a vital part of the editorial process and clearly that process failed here. Tech people often have a double standard when it comes to journalism--rules for thee but not for me. However the structure is fairly analogous, in that both professions ship under lots of time pressure where mistakes can be costly. I'm not sure, honestly, who is most at fault here or why only the reporter was terminated. But my comment above was to highlight that there shouldn't be a double standard--if you think a journalist should be fired for this kind of error it would be inconsistent to believe a software engineer shouldn't.
It's trying to prevent the server from caching the search. Thousands of different searches will cause high CPU load and the WordPress might decide to suspend the blog.
So by reading this article on PC gamer you've now downloaded the equivalent of a full-length movie worth of low quality code and ads.
reply