I built a PC this year in a Meshroom S V2[1]. The NF-A14x25 G2 fans I used for the AIO didn't seem so expensive when I was spending $600 on RAM, and I was happy that they were available in black.
Not every quiet PC is built in a dense box. Good airflow with big, slow fans is working for me to cool a 9800X3D and a 5070 Ti quietly under load.
I held my nose and bought an RTX 5070 Ti for $100 over MSRP in January. The very next week the same model was up $200. It turns out that NVIDIA had been subsidizing retail graphics cards with its Open Pricing Program. Not the whole story, but it may help explain the relative flatness of the graph until the end of January.
The other part of it is that the MSRP already baked in a substantial increase from the previous generation. While RAM was near rock-bottom pricing when this hit, current-gen GPUs definitely were not.
An editor that tries to be layout agnostic is almost certainly going to be a nightmare for people like me who set the layout in the keyboard itself. I downloaded the editor (I'm on Windows at the moment), and tried it with my keyboard set to Dvorak, which was plainly broken. I'm sure there's a way to fix the mapping, but when software thinks it's smarter than you, you end up feeling pretty dumb.
The article links to a YouTube mini-review of USB enclosures from UGreen and Acasis, neither of which he loves.[1] I've been happy with the OWC 1M2 as a boot drive on a Mac Studio with Thunderbolt 5 ports.[2] I just noticed that there is an OWC 1M2 80G, based on USB4 v2.[3] I didn't know that was a thing, but I guess it's the USB cousin to Thunderbolt 5.
The article links to the opinion[1], which notes more than once that "the quoted language does not appear anywhere in the opinion," and "Goldstine appears to be a fabricated case." I don't know whether it's easy to get a copy of the complaint in question.
I found the idea of a password generator appealing, mainly due to vault anxiety. I didn't (and still don't) like the idea that I can't access a resource without this precious vault. If I'm home with my tools, great. Otherwise, give me the right hash function, and I can MacGyver my way to PBKDF2 and generate my password.
However, once you introduce metadata (e.g., to deal with password rules), the idea loses most of its appeal. I wouldn't feel any more comfortable posting such a thing publicly than I would a vault.
I don't see anything in the post or the linked tutorial that gives a flavor of the user experience when you supply an invalid option. I tried running the example, but I've forgotten too much about Node and TypeScript to make it work. (It can't resolve the @optique references.) What happens when you pass --foo, --target bar, or --port 3.14?
Although this is characterized as 1.0, it is governed by the Terms of Use for Early-Access, which are quite limiting, including: "You may use the Service solely for noncommercial purposes."
The video on Steam shows both first- and third-person perspectives. Speaking of LLMs, Gemini says: "Hypercharge: Unboxed is both a first-person and third-person shooter. You can switch between perspectives based on your preference."
> The thesis is predicated on the idea that people claim this is the result of some study. I’ve never once heard it presented that way. It's a rule of thumb.
Code Complete cites eight sources to support the claim that the average cost to fix a defect introduced during requirements is 10-100x if it's not detected until after release. My qualm with Hillel's original assertion is that "They all use this chart from the 'IBM Systems Sciences Institute'" (emphasis added). I haven't personally vetted Steve McConnell's citations, but I am skeptical that they all share this common origin.
Personally, I don't know what you mean about Rust being too massive. One thing I am wary of is using a truly massive language like C++ on a multi-programmer project without consensus on which features to use and how to use them. Maybe you have in mind something like that?
If you want the simplicity of C with more safety, maybe tooling like Frama-C, a MISRA C conformance checker, or just aggressive use of static and dynamic analysis tools like ASAN and UBSAN. You can also disable certain optimizations (e.g., strict aliasing) to steer away from some of the major pitfalls of UB.
When I read SQL for Dummies almost thirty years ago, it made a point of distinguishing "sequel" as a historical predecessor to standard "SQL." As I recall, the author even asserted that SQL is not an acronym/initialism for structured query language. I felt funny saying sequel for the next decade or so, because I wasn't an old timer experienced with this pre-SQL technology.
Now I usually say sequel because everyone else does. That and it rolls off the tongue better than S-Q-L.
For a while I used dired-sidebar-show-sidebar and dired-omit-mode to give me a list of files in a narrow window on the left. I kept messing it up with C-x 1, though.
Not every quiet PC is built in a dense box. Good airflow with big, slow fans is working for me to cool a 9800X3D and a 5070 Ti quietly under load.
[1]: https://ssupd.co/products/cases-meshroom-s-v2