Hacker News new | past | comments | ask | show | jobs | submit | bentcorner's comments login

+1 it looks ok, although the stylistically I would personally prefer to split this file up into smaller parts (although maybe it's all related). I'm also not a big fan of macros but again without knowing more it's not too unreasonable.

Personally I wouldn't like to slog through this on a moment's notice but it seems named well and there are a lot of comments, and appears to have been through clang-tidy.

> it's much easier for me to order food online than to call a restaurant.

I feel like this is where bots would do well - you can say "order me a burger with extra mayo and fries for pickup at 5pm" and it should negotiate all the minutiae for you. Doing this all manually requires a bunch of menu navigation. Maybe a phone bot is still a bad fit but doing something like this using your on-phone voice assistant or typing it into a text window feels reasonable.

You can get more than 2 if you hit two in quick succession. I think the max is 5 (tested with blind double-clicks until I hit two in a row).

Love the mechanic where the more quickly you click the next one the more points you get.

There should be a timed mode to encourage rapid clicking (i.e., score the most points within 30s or 1min).

> This can be implemented basically with a fixed value of resistance, but because of the way resistance interacts with voltage, it’s actually very gentle on the battery. As the battery voltage falls, the current falls accordingly, so the delivered power falls even further. For modern appliances, this type of loading is not common.

Dumb question - is it at all possible to design a modern device which operates this way? (As battery voltage falls, device performance also falls? It's been a really really long time since my EE classes - are transistors just unable to operate this way?)

Apple did this with iPhones, where the CPU throttles itself when the battery can’t keep up with the peak demand anymore. They got sued for it (mostly because they didn’t tell anyone and people bought new phones when the old ones started mysteriously slowing down).

Have you ever used an old flashlight in the 80s or 90s?

As AA charge fell, the light got dimmer and dimmer. Today, we have devices that do the exact _OPPOSITE_, pulling the last bits of electricity out of the cells through boost-converters or whatnot (boost converters existed back then, but weren't as efficient or cheap as today).

Consumers demanded consistent and reliable performance no matter if at full-battery charge or nearly empty. People preferred their devices to suddenly "shut off".

Flashlight nerd here.

This behavior is still common in flashlights. Flashlights using three alkaline (or NiMH) batteries in series, or a single Li-ion cell can drive a white LED via a linear regulator (or occasionally just a transistor), and it will dim as the battery falls below the forward voltage of the LED at its maximum output. At higher price points, a single Li-ion cell and a regulated buck converter is common to see and much more efficient, but maximum brightness is still usually limited by battery voltage.

A flashlight using a single AA or AAA battery must use a boost converter because all white LEDs require about 3 volts. Even these often don't produce stable output as the battery drains, which is sometimes intentional because that behavior would produce terrible battery life with alkalines due to their high internal resistance. It's fine with NiMH.

Even Li-ion lights with boost converters don't always manage full output on a low battery because it's common to find overdriven components on a 20mm driver board (it needs to fit in a pocket) that's trying to push as much power as possible (lumens sell lights). Inability of the electronics to maintain full output isn't necessarily a significant limitation in the real world anyway; a 25x100mm aluminum tube pushing 40W gets hot fast, and there's almost always some sort of thermal-throttling mechanism. That said, full output on a low battery usually earns praise from reviewers.

> It's been a really really long time since my EE classes - are transistors just unable to operate this way?)

Yeah, most CPUs nowadays have dynamic frequency adjustment to maximize battery life. Lower frequencies also mean transistors can operate at lower voltages, so by reducing the operating frequency, you can reduce the voltage and therefore power draw on your battery.

Some LED flashlights with multiple brightness modes will drop to low brightness mode when cell voltage falls below a certain point.

Not sure I follow your line of questioning. It's a known fact that hospitals are overloaded. Anything we can do to reduce that load is a good thing. Hospitals are understaffed and overworked.

Masks provide positive ROI. Wearing a mask is really not asking a lot.

Hospitals were frequently overloaded by other seasonal respiratory viruses before 2020 but they just dealt with it and mandates weren't imposed on the rest of society. What's different now? It seems many physicians have a different perspective.


I use Keepass + Onedrive sync (Windows + Android). It's been working well for many many years and I see no reason to switch.

If I had to recommend a pw manager to someone I'd probably suggest they just save them in-browser, and use the same browser (Chrome/FF/Edge) across all their devices. Chrome has a pretty good password suggestion feature. Other browsers are probably not far behind.

I switched. Bitwarden just seems easier to use. Everytime I install Keepass on a new computer I have to spend 15 minutes remembering where all the options are to configure it. Bitwarden feels more like a vault of information while Keepass seems like you gotta fight it to be anything other than URL-username-password.

To be honest though I'm still not 100% moved over, and may never be. I doubt I'll need to transfer the login to the public library from a town I lived in 10 years ago.

Came here to say the same thing. Been using Keepass for years without any issue and won't switch. I started it using quite a while ago after someone on here recommended it and haven't looked back since.

Doesn’t chrome store passwords in plain text? Also, a proper password has the advantage of working outside of the browser on android/iOS.

As the sibling comment states, it's not stored as plain text.

You're right that external storage lets you use it elsewhere, but IMO using keepass has a lot of friction I personally don't mind but wouldn't initially recommend to most people. Browser password storage fills 99% of most people's needs.

Bitwarden is good for this. I use the browser extensions on desktop and the apps on mobile. It's my go-to recommendation.

They did at one point but not anymore. But either way any password filling is as secure as plaintext since it's pasted as plaintext, and you can just edit the DOM after it's filled.

Same, though I use Resilio Sync instead. Can also use SyncThing.

I think that's a more-or-less acceptable compromise for now.

Who knows, I wouldn't be surprised to see someone add on-board RAM back in to allow for cheaper expansion. Most operating systems support NUMA, this approach seems similar to that idea.

While I can't answer your question, just using a calculation like "box office receipts" - "movie making expense" is surely disingenuous. In that case every single direct-to-netflix release would be considered a money loser.

The developer ergonomics make more sense when you look at this from the VB side of things (positional or named arguments with everything optional), it's just the interop that is messy.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact