> sqlite is in the public domain and not copyrightable, for example.
And therefore is not licensable under the GPL; because no license is needed at all. Ardour's goal isn't to be "compatible with" the GPL (in the sense of allowing binaries to be built containing both GPL-licensed code and their own code); their goal is to be covered by the GPL license for the purpose of constraining what actions users can take. This requires the code to be copyrighted, because copyright law is the mechanism that allows them to require users to agree to a license.
> I wonder why they couldn't just be more like a car seat, with some thigh support. I'm not sure I've ever been in a car seat less comfortable than the _best_ economy airline seat.
This very much depends on the simulation. CFD historically used 64-bit, with extended precision used internal to an extremely small number of poorly conditioned operations, or with very stiff equations; today it's not at all unusual to use single precision or (strategically) mixed precision, depending on the problem. I think the strongest statement you could make about simulation workloads, rather than them "needing" a specific precision, is that they are usually properly analyzed to determine the needed precision, and then run at that precision.
That seems like the distance to go from having 100k people in front of you to having 100k people behind you. The distance you'd have to go to run into them properly would depend critically on the width of the vehicle you're in. With about 30k people running the Boston marathon and 60k people running the NY marathon, if you can source a vehicle wide enough to cover the course, it seems like you could pull it off in just a bit over 52.4 miles... assuming that the bodies didn't produce enough drag to slow you down so much that runners were managing to stay ahead of you on the course. (And assuming that marathon runners prioritize completion of the course over running sideways away from obvious danger, but they're marathon runners, that seems like a safe assumption.)
There are a lot of workflows where cache is likely to be consumed exactly once (e.g. anything chat-like where a single thread is extended; if a prefix cache hit is found, and a set of new longer prefixes is inserted in the cache, it is unlikely that the original shorter prefix will be consumed in later turns). I could see allowing each session key a small number (1?) of 24-hour cache entries, where inserting a new cache entry (perhaps the maximum-length prefix, perhaps an API-tagged specified-length prefix) consumes that slot and either boots the rest of the items from cache, or demotes them to 5 minutes or something. Basically: workflow awareness, not uniform handling.
Wonder what the price will be like on the 64-core high-frequency version... if it's comparable to existing Epyc pricing, this might be the obvious answer for a CFD rig in 2027. Finally something with memory bandwidth way greater than a Mac Studio…
I assume this is what's up with the NordVPN ads flooding YouTube and stuff. No idea who the buyer is, but if I was in the market for a VPN I'd presumedly do a web search, skip NordVPN as having poisoned the well of good will, and choose whoever's next.
There's no way these are using a significant amount of compute. I'm not 100% convinced they're actually LLM-generated rather than an old-school Markov model. Both the relevance and accuracy numbers of the responses flirt with 0%. It's possible they just have a few million stashed responses and choose one at random, from what I can tell as a user.
Civ 7 still isn't good, but Test of Time made it somewhat better. It took a long time for Civ 6 to get good after release, but I'd argue they got there. Still frustrating, though.
Booting on what? Are BIOS calls (if allowed) considered a library? The overhead of managing a framebuffer etc without an OS (which would be a required component not included on the disk) feels like it would dominate.
My recollection is that Civilization (1) came on 5 (? 7?) floppy disks for Mac, but only the first disk was needed for the full game in black and white; the additional disks were needed for color and some add-on assets like improving your palace.
"Build a game that stands the test of time as well as Civilization" is a pretty high bar. 1.44 MB is huge.
That's a real risk, yes. There's definitely a difference between cases where the code is the artifact being built, and cases where the code is being built to generate an artifact that is independently valuable and assessable. I'm happily in the latter case -- but I definitely share your fear of those who think current LLMs are valuable in the former case.
> It's hard to say if this code is structurally better or worse than before, but it's certainly voluminous and as far as leadership could ever tell, with their flawed metrics, that is all that matters.
Hah. I've been working with ChatGPT-5.6 Sol and a lot of guidance to port a particular geometry from 2800 lines of Python-scripted Rhino3D (basically a custom parametric CAD kernel in there, plus use of it) to Python-scripted OCCT/FreeCAD (an existing CAD kernel) and it's up to 36,000 lines and only about half way there. And I've been setting goals and targets for duplication minimization, code size reduction, etc. The results are fine for my purposes, but if I put a positive value on "voluminous" I'd be super impressed; with my actual negative value assignment on lines of code, this is more "absolute crap but still useful to me."
I think "absolute crap but still useful to me" is a pretty high value and not worth neglecting, but I'm definitely scared by leadership who sees the toilet overflowng and assumes that means that value has been maximized.
meet.hn/city/37.0481715,-112.5285237/Kanab