Three or four blank lines is probably the least hostile and most foolproof way to handle addresses.
But the cart software has distinct address-line-1, address-line-2, city, state, zip-code fields.
And the CRM they export into has similar fields.
Probably to be compatible with some further pipeline of tooling going back decades.
I suspect if you go back far enough it ends at pre-/semi-computerized data processing systems which would print addressed envelopes and documents from stacks of Hollerith cards, using extremely rigid fixed formats that were probably fine for their original buyers, likely US-centric and old enough that they were just getting it to the right city and letting the local postman figure out the nonsense on the envelope.
I went year-make-model many years ago when I did an autoglass website.
The filtering value is big as you said, and the model year as a first filter is easy to type in, and probably gets you reasonably close if you're off-by-one. Accidentally picking an '05 Sonata instead of an '04 probably has similar parts, but if you pick Honda instead of Hyundai, you're way off in Wonderland.
It looks suspiciously like a Kensington Slimblade.
That makes me wonder if the functionality could be done on random off-the-shelf trackballs in firmware or drivers, in which case you're not a product, you're a feature.
Creator here - yes, it's a mod of a Kensington SlimBlade Pro, mentioned on the site. Rotatrix is the hardware mod (added controller), firmware, and software stack that extracts 3DOF rotation and integrates into CAD and other apps. It's possible with firmware, but you need a trackball with dual optical sensors to do this (which very few have), and the system is patent pending. More on the architecture in the earlier Show HN: https://news.ycombinator.com/item?id=46990422
I got my General in late 2024, but haven't done much with it. Collected a few HTs, built one little 2m-specific antenna, but I'm a bit embarrassed to hit Transmit when I'm not sure I've got everything configured right to not intrude on other repeater users.
I had two atypical goals with it:
- If I could present a certificate that says "the Government admits that I know something about how RF operates" maybe my irritating brother would acknowledge me when I tried to explain that Wi-Fi multipath concerns no longer apply when we plugged his machine into a hard-wired Ethernet socket.
- Being able to brandish "the FCC allows me to build a 200-metre antenna tower in the backyard" as a counterargument when the local HOA hassles me about the weeds that apparently have evolved beyond vulnerability to the stuff they sell at the local home centre.
It feels very "bifurcated" as a hobby -- you either do 2m/70cm stuff with little $100 handhelds, or you start doing outright construction projects to deal with antenna sizes, and spending four figures to explore HF.
I understand the Fitt's Law concepts behind a top menu bar, but I wonder if this is a scenario with moving goalposts.
On a 1984 Mac, you had like 512x384 pixels and a system that could barely run one program at a time. There was little to no possible uncertainty as to who owned the menu bar. (Could desk accessories even take control of the menu bar?)
But once you got larger resolutions and the ability to have multiple full-size programs running at once, the menu bar could belong to any of them. Now, theoretically, you should notice which is the currently active window and assume it owns the menu bar, but ISTR scenarios where you'd close the window but the program would still be running, owning the menu bar, or the "active" window was less visually prominent due to task switching, etc.
The Windows design-- placing the menu inside the window it controls-- avoids any ambiguity there. Clicking "File-Save" in Notepad couldn't possibly be interpreted as trying to do anything to the Paintbrush window next to it.
The problem with the Mac UI is that the app's menubar can only be accessed by the mouse (can't remember what accessibility-enabled mode would allow).
Under Windows, one can access the app's menubar by pressing the ALT key to move focus up to the menubar and use the cursor keys to navigate along the menubar. If you know the letter associated with the top-level menu (shown as underlined), then ALT-[letter] would access that top-level menu (typically ALT-F would get you to the File menu). So the Windows user wouldn't have to move the mouse at all, Fitt's Law to the max (or is it min? whatever, it's instant access).
For the ultrawide monitors these days (width >= 4Kpx), if you have an app window maximized (or even spanning more than half the screen), accessing the menu via mouse is just terrible ergonomics on any major OS.
Since OS X 10.3 (2003) Control+F2 moves focus to the Apple menu. The arrow keys can then select any menu item which is selected with Return or canceled with Escape. Command+? will bring you to a search box in the Help menu. Not only that, any menu item in any app can be bound to any keyboard shortcut of the user's choosing not just the defaults provided by the system or application.
There's a very reasonable argument behind that, though.
"Sending" a file to another disc or on the network is non-transformative. At the far end, it's still a file.
But "printing" is inherently transformative-- you're expecting to get something clearly not a file (print-to-file pseudo-printers excepted).
I can see the desire for minimalism-- having seperate rows for "share/send" and "print" is, well, two seperate rows. But if you offer adaptable and configurable interfaces, I could see suppressing one or both depending on context or user preferences. (You have no external drives or registered share-recipients? No "Send To/Share")
Maybe I've been in Linux land too long but sending a file to a printer seems pretty obvious to me. Yes it's transformative in a way, but you could equally argue that my word document with A4 layout is a digital version of a document, and the print out is equivalent.
To me there seems to be more difference between sending and share. One is pushing something somewhere, the other implies making it available for someone/thing to pull.
I'm not particularly saying you're wrong btw. We are talking metaphors, and there's no 'correct' way to do it.
20 years ago, I used it a bit for my undergraduate work. Mostly as a "word processor that's prettier than... I suppose at the time, the old WordPerfect 8 for Linux"
The weird thing is that my family has started going to Red Robin recently. They started doing one thing right at least.
Their recent $9.99-with-drink special happens to be pretty exactly what most of our party wants when we go to a burger place. Who are the people who want the burgers with the 25 exotic toppings? It doesn't beat the local institution with the big wood-coal grill, but that place is 25km further away, and a few dollars per head more, so it's the "let's have an okay lunch and then finish our Saturday errands" choice.
It's not packed, but at least at the locations near us, the management seems to be very attentive-- like they're trying to at least keep an eye on the customer experience after blowing it up.
TBH, I think the meal special INCLUDING a drink is a very smart direction for for both RR and Chili's. I suspect that consumers are getting wise to the "hide the queen" pricing tricks, where they bury the costs of loss-leader entrees in the side or drink. There aren't many places our family of four can get a sit-down lunch for less than USD60 before tip, and RR is one of them.
There are also PATA SSD that are a bit more reliable, and fit the standard mount on older laptops. Because some models include several workarounds for older equipment (automatic wear leveling), these can last quite some time even with an OS that never supported SSD (turn off swap when possible).
If it is something important like old equipment, a CompactFlash SLC card with a PATA adapter is a proven solution.
Usually it is better to drop an old OS image into a 86box, and make the recovered backing image read-only. =3
Indeed, I also went through the ddrescue trial-and-error process with USB adapters to avoid large file corruption bugs, BIOS specific setup quirks, and proprietary controller remapping (seagate.)
Ultimately, it was almost always better to pull the disk image on the original hardware when possible, or use a legacy 32bit x86 PC to direct access the drive controller when BIOS doesn't support the drive. Best of luck =3
They didn't have to box themselves into "pitching electric cars to right-wing climate change deniers."
I've heard there are rumours there are least three or four countries outside the US. In several of them, EVs are selling like like hotcakes, or at least not with the current American militant hostility to the very concept.
I suspect they spent too long riding the horse they got here on though. Making an EV appealing to American premium buyers was a marketing coup. Selling it as a software-style "we'll continue iterating with OTA updates" was an interesting alternative to the model-year redesign when you're targeting an early-adopter audience used to regular software refreshes.
But now these things are a liability. Your product matrix is full of America-centric designs with iffy product-market fits in other markets (will a Model S or Cybertruck literally fit in some side streets of Europe or Asia?) You've failed to make a recognizable, exciting redesign of an existing model, so what you do have looks dated. You never really developed a reputation for quality or reliability. These are product problems that have nothing to do with politics. You could have addressed them and been a viable player elsewhere, even as the US continues to eat itself alive. (Of course, that might have involved not intentionally rubbing your brand all over a highly polarizing and toxic political scenario)
I was excited about Tesla back when they were a novelty. I can recall going to the mall with the Microsoft Store (remember those? They sold "bloatfree" PCs because it used to be the OEM who loaded them full of crapware instead of MS itself) to buy a Windows 8 tablet, and then looking across the aisle to see a Model S on display at the Tesla "not really a dealership" stall.
I bought like $2000 in shares back then, figuring one day, jokingly, they'd be worth enough to exchange for a new Tesla. It looks like I could probably get one now. But these days, I just want a BYD; they seem to be actually building a coherent product line and long-term vision.
Three or four blank lines is probably the least hostile and most foolproof way to handle addresses.
But the cart software has distinct address-line-1, address-line-2, city, state, zip-code fields.
And the CRM they export into has similar fields.
Probably to be compatible with some further pipeline of tooling going back decades.
I suspect if you go back far enough it ends at pre-/semi-computerized data processing systems which would print addressed envelopes and documents from stacks of Hollerith cards, using extremely rigid fixed formats that were probably fine for their original buyers, likely US-centric and old enough that they were just getting it to the right city and letting the local postman figure out the nonsense on the envelope.
reply