HNHacker News
TopNewBestAskShowJobs

wtallis

22,096 karma · joined September 20, 2009

submissionscomments
wtallis··on Codex CLI installs a persistent, self-updating background daemon by default
Serious tools shouldn't do this. Sure, you can offer an opt-in rapid release beta update option, but if you can't go more than a month without forcing me into a "stable" update that changes the UI and behavior I'm getting used to, then I'm not going to consider your software stable and reliable enough to be worth developing expertise in using.
wtallis··on WSL3 Performance is about 5-60% faster than WSL2 depending on the workload
You say that Windows is fine if you have a whole IT department taking on the burden of fighting against the annoyances, but then accuse people who complain about those annoyances of regurgitating second-hand complaints!?
wtallis··on Python 3.15
You don't even need to upgrade your system. You just need to be willing to install another newer Python alongside whatever versions you already have, as a dependency of whatever newer tool you want to run.

If python interpreters masqueraded as versioned .so libraries, we probably wouldn't even be having this conversation, because having multiple versions of those lying around is ancient precedent.

wtallis··on Python 3.15.0
If you're writing or packaging software for a specific OS that bundles an old Python, then there's sometimes a reasonable argument for wanting to retain compatibility with that old Python. But now that uv has started bringing some sanity and relative ease to Python package management, it's not much hassle for end users to start running a Python newer than the one shipped by the OS when they want to use a tool or library that requires a newer Python or performs better on a newer Python.
wtallis··on The Forgetful CPU (Linux on M4)
> But I don't see any models with Iris and a dGPU

I don't remember exactly what the chip options were back then, but currently Intel enforces that by ensuring that the laptop chip with the larger iGPU doesn't actually have enough PCIe lanes to connect a dGPU.

wtallis··on The Forgetful CPU (Linux on M4)
Hot-swappable memory is probably much more common in mainframes than mainstream servers. A typical x86 server still requires you to power it off before replacing DIMMs. Meanwhile, NVIDIA and AMD have both recently done some rather Apple-like server processors that solder CPU, GPU, and RAM to the same package/module.
wtallis··on macOS Golden Gate Is a Buggy Mess
Does it really? When systems get 5+ years of supported OS upgrades, it doesn't seem like the annual OS release cycle is driving users to upgrade hardware in any meaningful way. If anything, the hardware update cycle is driving the software update schedule, because there needs to be an OS to run on the new hardware when it ships. This is especially apparent for the iPhone.
wtallis··on macOS Golden Gate Is a Buggy Mess
If Firefox isn't responsible for rendering the menu bar, then Firefox doesn't own the menu bar. It sounds like what you're describing is a process where Firefox tells the OS what items it wants the OS to put in the menu bar. Whether or not the app provides a new set of top-level menu entries during a window switch, it still seems to be entirely the responsibility of the OS to actually manage the rendering and respond to user interaction, including the OS keeping track of which top-level menu should be rendered as selected, and the OS should be enforcing that there's only zero or one selected menu.
wtallis··on macOS Golden Gate Is a Buggy Mess
> Firefox bugs are bugs in Firefox. (I also keep experiencing the stuck menu bug, but again, Firefox bug.)

Glitches in context menus could theoretically be just Firefox bugs. Glitches in the global menu bar can't be just Firefox bugs. Those pixels don't belong to Firefox. It shouldn't be possible for an application to cause the OS to lose track of which menu the user has open in the global menu bar. Even if Firefox is buggy here (quite likely), there's clearly a deficiency in the OS itself, too.

wtallis··on macOS Golden Gate Is a Buggy Mess
The problem with stating that 27 is an improvement over 26 is that it's ignoring the elephant in the room. It doesn't make any sense for the conversation to just stop there, and implicitly forgive all of the regressions 26 brought as water under the bridge. macOS 15 isn't just some nebulous hypothetical alternative, it's a readily-available example of what Apple actually shipped in recent history, and it should be a point of reference in discussions like this. Narrowly focusing on 27 vs 26 while ignoring 15 doesn't make any more sense than praising Windows 8.1 for fixing some problems from Windows 8 when neither was worth upgrading from Windows 7 for most people.
wtallis··on Plan mode is dead
I don't usually see Claude leaving comments that are obviously out of date compared to the code. The problem is that the comments are just a dumping grounds for Claude's stream of consciousness, verbosely recording random bits of history and context that are true and at least somewhat relevant, but without cohesively explaining why the code is the way it is. And some sentences in the comments will be beginner-style restating what's obvious from reading the code.
wtallis··on ReBarUEFI: Resizable BAR for almost any UEFI system
Source? I don't know what happened for the Linux drivers, but the Windows drivers definitely booted and ran benchmarks without ReBAR when the Arc A380 launched, because there were lots of published comparisons of the performance impact on workloads that definitely didn't fit in 256MB.
wtallis··on A brief history of Windows scroll bar shortcuts
"Feel" in the phrase "look and feel" refers to the behavior when interacting with the UI, as opposed to the aesthetic look. You asserted that literally nobody cares about a particular behavior that is the Windows equivalent to what has been a prominently-exposed configurable system preference in every version of Mac OS X/macOS.

Your weird hatred/obsession with Apple is preventing you from understanding that my argument wasn't even in favor of Apple's default behavior, but about software that doesn't respect the preference chosen by the end user who changes that setting away from the default.

wtallis··on A brief history of Windows scroll bar shortcuts
I go out of my way to avoid using applications that ignore the macOS system preference for what clicking in the scrollbar does. People who care about the "feel" half of "look and feel" genuinely do exist. Janky scrolling behavior drastically lowers my opinion of an app, and in a web page it prompts immediate closure of the tab.
wtallis··on A brief history of Windows scroll bar shortcuts
The ubiquity of mouse wheels and two-finger scrolling on trackpads drastically weakens your case for prioritizing the page up and page down behaviors in the scroll gutter. The mouse already offers a low-effort way to adjust scroll position at small to medium scales, generally much easier that repositioning the cursor from above to below the scroll thumb unless you really need to scroll by precisely one page (usually not possible on the web anymore because of floating dickbars).
wtallis··on ReBarUEFI: Resizable BAR for almost any UEFI system
Using an Intel discrete GPU on a system that lacks ReBAR support results in somewhat lower performance, not a complete inability to use more than 256MB of VRAM.
wtallis··on Apple M6 Pro Achieves the Highest Single-Core CPU Score in Geekbench 7
Note that Geekbench 7 no longer runs the same subtests in multi-core mode as in single-core mode, so any ratio calculated from the overall scores instead of from the individual subtests is misleading. There are a lot of subtests that it only runs in single-core mode and omits from the multi-core tests, seemingly to placate the critics that didn't like the inclusion of poorly-scaling tests in the multi-core mode. It's not as dumb as the Geekbench 5 strategy of just running N independent copies of the test, but it does seem like a dumb change to me.
wtallis··on Shapelearn Qwen 3.8 27B (13.1 GB VRAM)
It's equal parts memory clock and bus width: RTX 4090 is 384-bit wide at 21 Gb/s and RTX 5090 is 512-bit wide at 28 Gb/s.
wtallis··on Hister: A private search engine for the pages you visit and the files you keep
There was also Google Desktop Search for several years: https://en.wikipedia.org/wiki/Google_Desktop
wtallis··on Copying login keychains between Macs fails on Secure Enclave Macs with Tahoe
You're asking for the encryption key to be derivable by an unrelated system that only has the encrypted file and your password.
wtallis··on Copying login keychains between Macs fails on Secure Enclave Macs with Tahoe
I think it's time to update your expectations. Hardware security modules have been around for quite a while. You shouldn't assume that your chosen password is the only input to the key derivation, or even that the raw key itself will always be obtainable.
wtallis··on Rust is tier-1 language at Microsoft
I'm sure at least some of those macOS permissions prompts are spurious, but for the most part I think they're genuine red flags of poor software quality if not actual security/privacy threats. When a video game prompts for full disk access, it's probably because it wants to spray config and save files all over my home directory instead of putting them in a platform-appropriate location. When it triggers a permissions prompt about Bluetooth, it's probably using the wrong API to get input from a game controller or the wrong API for identifying what kind of input devices are present. If it triggers the "wants to control your system" prompt, it's probably trying to keep responding to input even when it's no longer the foreground application.

Sometimes the right API might not actually exist, but most of the time it's just lazy developers half-assing a port with no care for making the application behave appropriately for the platform. The prevalence of "Please don't turn off your computer while the game is saving" warnings is pretty clear proof that game devs in particular don't make any platform-specific adjustments they aren't forced to. (Game consoles usually require those warnings, but they're stupidly out of touch on a computer.)

wtallis··on iPhone Duo
> it is reasonable to assume that the point here is that a full-screen, unfolded image would scale exactly to a half-screen/folded image with no change in aspect ratio.

Sure, but aside from being interesting from a mathematical standpoint, there are no practical implications from that fact. When the user unfolds the phone and rotates it by 90 degrees, the fact that they're left with about the same aspect ratio (modulo whatever changes with status bars, etc.) means very little for UI design in light of the much more important fact that the screen doubled in size and thus the application's layout should be using the extra screen space to show more information, and should not assume that a majority of the screen is easily reachable by a thumb.

wtallis··on iPhone Duo
" you can open the phone and use the full-size camera with the outer screen, which results in much more flattering imagery than the wide-angle lenses selfie cameras use"

A camera held at arms length will have pretty much the same view of your face regardless of whether it has a wide-angle lens. A wide-angle lens just means the image will include more stuff around the edges, but only if the image/video isn't being automatically cropped to frame your face. The view the camera has of your face isn't more or less flattering unless the distance from camera to face also changes.

wtallis··on iPhone Duo
Size is even more important for UI design. If you don't think you need to re-design the layout of your app when the screen doubles in size, you shouldn't be doing UI design.
wtallis··on iPhone Duo
Most users would prefer to have adequately-sized text and controls regardless of whether they're using the smaller outside screen or the larger inside screen. Who would spend $2k on a dual-screen phone if they expected one of the screens to be mostly unusable for them?
wtallis··on iPhone Duo
You said: "If you unfold a square, you don't get two squares."

In the context of this discussion, it is reasonable to assume that any "square" available to be unfolded is something approximately like the folding phone, consisting of two layers joined by a hinge. When you unfold that, you go from having a square to having a rectangle equivalent to two adjacent squares, and usable as two adjacent squares.

wtallis··on iPhone Duo
You don't seem to be engaging with the point, which is that the space available for content after subtracting out the space taken up by other UI elements is not going to have the same aspect ratio folded and unfolded. A real UI doesn't actually get this supposed benefit. Only something like a full screen video player might (depends on what kind of keep-out zone you need for the front camera), and maintaining the same aspect ratio folded vs unfolded for video content isn't particularly helpful when the aspect ratio in question isn't popular so you'll have letterboxing regardless.
wtallis··on iPhone Duo
"larger version while keeping the aspect ratio" is of minimal benefit. You still need to present a different layout, because eg. any toolbar is going to be a different fraction of the available area depending on whether the app is on the small outer screen or the large inner screen in portrait orientation. Nobody wants a naive 2x scaling of the phone app on their iPad.
wtallis··on iPhone Duo
If the outer screen has dimensions X by Y, then you unfold it to have the inner screen with dimensions 2X by Y, which cleanly permits side by side apps at the original dimensions of X by Y. This is true for any ratio between X and Y.

If the user isn't going to be multitasking, then the app needs to additionally support the widescreen dimensions of 2X by Y, and the portrait orientation of Y by 2X. Both of these are so drastically larger overall that aspect ratio is a barely-relevant part of the UI layout problem, because nobody wants every button and text label to be double the size (which would mostly defeat the benefits of having the larger screen for anything other than multitasking).

← PreviousPage 2 of 34Next →