20,771 karma · joined June 1, 2018
Certain things like Sysinternals tools outside of their native platforms is somethnig I hope to see more of. E.g. I had a SumatraPDF and 7z GUI clone on Linux for a while just because I liked it more than the Linux PDF readers (now I have a home grown app which handles more formats). It looks like this one could use a bit more time in the oven though.
It's just a combination in the ambiguity of what "it discards the dot" should mean in GGP's message combined with the article already clarifying 3rd level domains are not available on .name anymore leading to a lot of confused comments.
And what I'm saying here is different from "you should not ever care to expand acronyms/abbreviations/initialisms", but that does not necessarily mean your goal should be that it's "fun" for every possible person (you'll never achieve that goal, under or overexplaining is never fun). It's about what's reasonably efficient for everyone likely to read the article. If 50%, 10%, 1%, and 0.1% of your audience will understand an acronym, abbreviation, or piece of jargon then it has different implications for what the right balance of reasoning is. Not every piece need target a generic audience, not every acronym need assume the reader can't be bothered to learn anything not spelled out for them in the page, and not everything is equally hard to figure out when it's not spoon-fed to the reader.
And, again, what is "Tensor Processing Unit" going to gain you if you don't already know that's what TPU stands for in the context of this article? I.e. who knows what a tensor is and why youd have a processor for them yet gains something by the acronym being expanded? People who don't know what a TPU is should start with a different article completely, probably several, and then read this one. Expecting every piece of writing should assume no knowledge blocks more knowledge than it helps share.
One thing I think the "lucky 10,000" XKCD gets bang on is that it doesn't frame sharing something with the 9,999 in mind as error any more than it blames the 1 for not knowing - instead the problem is dogging people for saying they've never heard of something. That's truly a golden rule, regardless the audience and so on, and doesn't require changing the way humans write to avoid problems like the one you ran into.
But yes, the rule about LLM generated text should at least be abided by and preferably enforced regardless if the intent was malicious.
Though, funnily enough, this kind of info and more is extremely easy to add to HN via a vibed extension. At this point, mine just stops HN from loading completely and constructs its own page (with a proper dark theme and the information I care about).
An MP3 decoder for a single target doesn't really run into that complexity, a UI components library for (Linux, Windows, macOS) * (x86-64, ARM64) suddenly has a 6x multiplier on what was already something with waaay deeper dependencies and integrations than MP3.
At least that's what I've noticed vibing my DE without external libraries. It went really fast when the complexity was small because most of the work was in adding code. Then it started taking longer to build and test, even with optimized builds and tests, than it took for the AI to do its part.
ASML -9% in 1 day
AVGO -10% in 1 day
MU -17% in 1 day
NVDA -9% in 1 day
SKHY -13% in 1 day
TSMC -10% in 1 day
As much as I think TSLA/SPCX are overvalued there is nothing unique about their drop compared to many other companies in the last day or two. I wouldn't even hazard a guess on whether the floor has fallen out on anything yet, it could just as well be a temporary reaction to the election results and volatility following the uncertainty of that for these types of companies.
Of course one can always pick a set of tickers and day ranges that make it seem like any trend if you filter the view enough.
This is a bigger jump, but it's also immediately after elections and other activity so I'd expect higher volatility than normal.
> accounts that should never take a password at all (root, your key-only deploy user, ldap users, the default user on alpine's aws and azure images) take any password longer than 256 characters.
But yeah, Alpine for persistant installs isn't unheard of - just not as popular as the container use case. They offer official VM, Xen, Pi, and bare metal images users deploy as well. I actually had a fleet of VMs to update!
Edit: The Alpine notice made it clearer to me that at least one other account has to have a password, it's just the target account that doesn't. So if you truly have no users with passwords in your container deployment then those passwordless users aren't vulnerable to this bug, but any of the image types which have a user will likely have root exposed.
> The attacker needs the name of an account whose password field is * (an account with no password set, which is normal for key-only accounts), and needs the machine to have at least one other account with a $5$ or $6$ password hash.
https://alpinelinux.org/posts/2026-11-05-openssh-password-au...
When you tell it to, you usually have good control around what kind of thing you want it to consider a problem, how much effort you want it to spend trying to prove that, and what should happen with code it can't prove that property for. Most commonly, people just use the "tell me if I've made an obviously dumb infinite loop which does nothing useful while it runs".
E.g. y-cruncher does something other than infinitely loop for no reason so it wouldn't trigger the loop detection logic on most anyone's compilation settings.
On the other hand, a loop which does nothing but run until the last digit of pi would either trigger the compiler to say this is a useless infinite loop or to say it isn't able to prove this loop stops (almost certainly the latter, as such a loop is a great example of going out of your way to fool the compiler).
A loop which sometimes terminates and sometimes doesn't depending on runtime input would depend on your compiler settings, but almost always nobody sets it in a way to say that's a problem (and when they do almost always it's not possible for the compiler to prove one way or the other) if their compiler even supports that kind of analysis.
> The basic algorithm divides points by a power of the time since a story was submitted. Comments in threads are ranked the same way.
> Other factors affecting rank include user flags, anti-abuse software, software which demotes overheated discussions, account or site weighting, and moderator action.
SRAM wise it doesn't seem too insane. About the same ratio of memory:SRAM as the 5090 (IIRC). Still more than I would have expected. I assume they found it helps process the current layer faster or something.
For a random non-software example: My mother has an HR job and absolutely loves it for working with spreadsheets, sorting through email, making mail merges, reviewing the policy documents for errors as she works on them, and so on. She spends less time in document hell and more time getting things done or talking to people.
Personally, I find the ability to quickly remove technical debt to be more practically valuable than the ability to quickly create software. A lot of the smaller shops I work with never had the time or money to properly manage, update, or retire their infrastructure. Now many are in a better shape than my own stuff has been because you don't need to be an uber nerd spending a weekend to upgrade an ancient & neglected MediaWiki box (or whatever) anymore.
The same is true of using any tool. If you just click a premade and generic "process photo" button in an image editor for every photo you get then you're doing no creative work (unless that whole action is a meta statement itself or something). If you mess with the different options and settings to find the one which matches your creative vision then you've played a part in the creative process, even if you weren't the one responsible for the code of how the pixels changed and paid for the software to do that part.
To LLMs directly, if you just say "make me some art" then you've done nothing creative as well. If you iterate and mess around with what you like until you get something you find interesting, then you've played, what seems to me, the biggest part in the creativity process of that output (which has nothing to do with where the code to match that vision of the output came from). I think LLMs and creativity can be confusing because "make me some art" will produce something that, at a glance, looks very much like we'd expect creative art to look like (regardless the reason or if it actually is), and we often falsely jump to the conclusion anything that looks creative out of an LLM must therefore only ever be able to source from the LLM. This would be like assuming because an image editor has that generic "process photo" button one can never do anything creative with an image editor.
Other targets and languages have portable SIMD targets that are a bit more advanced, but I think WASMs SIMD design is the best for generically getting your feet wet.
The underlying problem is Chrome exposes no (normal) setting to override the OS level setting at all, not necessarily that the preference shall always follow the browser's theme specifically.
I.e. just because Apple requires you to do things in 24 hour increments does not mean your billing has to expose it in exactly the same way.
For some, the degree is the destination and that's more than fine as well. It's a marker that says "others agree I learned x to a certain level, and I had fun doing it". This tends to overlap well with those who just liked university as an extra method of learning rather than going primarily to form part 1(a) of their career or something.