[pkolaczk]

> Which is why when folks nowadays say "you cannot use XYZ for embedded", given what most embedded systems look like, and what many of us used to code on 8 and 16 bit home computers, I can only assert they have no idea how powerful modern embedded systems have become.

Yet, I still need to wait about 1 second (!) after each key press when buying a parking ticket and the machine wants me to enter my license plate number. The latency is so huge I initially thought the machine was broken. I guess it’s not the chip problem but terrible programming due to developers thinking they don’t need to care about performance because their chip runs in megahertz.

[tialaramex]

There's no pressure to make a good product because nobody making this decision has to use the machine. Everywhere I've worked purchase decisions are made by somebody with no direct contact to the actual usage, maybe if you're lucky they at least asked the people who need the product what the requirements are, otherwise it's just whatever they (who don't use this product) thought would be good.

"Key presses are 15x slower than they should be" gets labelled P5 low priority bug report, whereas "New AI integration to predict lot income" is P0 must-fix because on Tuesday a sales guy told a potential customer that it'd be in the next version and apparently the lead looked interested so we're doing it.

[miki123211]

Not just that, nobody chooses their parking spot based on the UI of the machine.

Banks and phone manufacturers now care about UI, because some of them started to do so, and people started switching to them en masse. US carriers were bleeding subscribers left and right when the iPhone was only available on AT&T, which was the first time people started switching plans to get a specific phone instead of the other way around.

People usually choose their parking based on where they want to go and how far it is from that place, and that trumps all other considerations. Paying more for programmers or parking machine processors would be a waste of money.

[littlestymaar]

> There's no pressure to make a good product because nobody making this decision has to use the machine.

Most software sucks, even when people have to chose using it. Everything is buggy and slow, people are just used to software being bad.

[jimmydddd]

I worked at a purchasing dept. where each commonly ordered part or service had a six digit item number that had to be entered. The CFO picked some company to do the new version of the software, and they decided to randomly assign new different item numbers which included 13 leading zeros to each item number. So now everyone had to learn the new item numbers and type in a the 13 leading zeros each time.

[ryandrake]

While this is a decision-making problem, it is also an engineering incompetence problem. No matter what pointy haired boss is yelling about "priorities" ultimately software developers are the ones writing the code, and are responsible for how awful it is.

When it comes to priorities about what to write and what to focus on, the buck stops at management and leadership. When it comes to the actual quality of the software written, the buck stops at the developer. Blame can be shared.

[csomar]

Everyone was locked out in a building am staying at (40 something stories) for several hours. When I asked the concierge if I can have a look at the system, it turns out they had none. The whole thing communicated with AWS for some subscription SaaS that provided them with a front-end to register/block cards. And every tap anywhere (elevators/doors/locks) in the building communicated back with this system hosted on AWS. Absolute nightmare.

[sofixa]

> Absolute nightmare.

Yes, but still probably a million times easier for both the building management and the software vendor to have a SaaS for that, than having to buy hardware to put somewhere in the building (with redundant power, cooling, etc.), and have someone deploy, install, manage, update, etc. all of that.

[exikyut]

I wonder what happened to the building when us-east-1 went down.

[lallysingh]

My first guess was debouncing. They assume that the switches are worn out, deeply weathered, and cheaply made. Each press will cause the signal to oscillate and they're taking their sweet time to register it.

When the device is new this is an absurd amount of time to wait. As the device degrades over 10, 20 years, that programming will keep it working the same. Awful the entire time, yes, but the same as the day it was new.

[scrumper]

I was late for a train at my local station and the parking machine was taking ages to respond to keypresses. I could see the training pulling up to the platform and I was still stuck entering the second digit of seven. In my shameful frustration I hit the machine fairly hard. While the button presses might take a while to register, the anti-tamper alarm has really low latency and is also quite loud.

[ssl-3]

Debouncing would be smart, sure. But sometimes, these sorts of embedded machines are weirder than that.

At Kroger-brand gas stations near me, I get to interact with the buttons on gas pumps to select options and enter a loyalty ID.

Those buttons have visible feedback on a screen, and also audible feedback consisting of a loud beep. And there's always delays between button press and feedback.

Some combination of debounce and wear might explain that easily enough.

Except... the delay between pushing a button and getting feedback is variable by seemingly-random amounts. The delay also consistently increases if a person on the other side of the pump island is also pushing buttons to do their own thing.

It's maddening. Push button, wait indeterminate time for beep, and repeat for something like 12 or 13 button presses -- and wait longer if someone else is also using the machine.

I can't rationally explain any of that variability with debounce.

[philipallstar]

That's a good point. When I use them I assume they're making API calls to a central server to validate (or something) them.

[smokel]

One of the more inspired design choices of the parking ticket devices in my area is the inclusion of a key repeat feature.

If you keep your finger on the touchscreen for just long enough, it helpfully repeats the keystroke while you're entering a license plate.

Given the inevitable hardware issues, this means that what should be a single tap frequently becomes a burst of identical characters.

The programmers who worked on this probably would've liked to be game developers instead.

[jwr]

That's programmer incompetence. Unfortunately pervasive, especially with devices like parking meters, EV chargers, and similar, where the feedback loop (angry customer) is long (angry customers resulting in revenue decrease) or non-existent.

[ttoinou]

It could be a management problem instead also, while developers are just following instructions sent by management

[graemep]

They also prefer you to use the mobile app so they can gather more data so they do not want the devices to work well in the first place.

[cmrdporcupine]

It's organizational incompetence driven by companies that see software development as a cost centre rather than a key asset.

It's usually clear when this has happened. Buggy bargain basement output.

[contravariant]

Give it some slack, it's probably doing its best to inexplicably run windows.

[mrguyorama]

Disagree. Windows for embedded runs extremely well, though can take a minute to boot.

My underpowered cash register that hadn't been updated in a decade could run POS on top of Windows 7 Embedded POSReady buttery smooth.

Occasionally they would start performing poorly, and it was always a network issue.

[stavros]

Or maybe they think they should be sending each keystroke to a server and waiting for the response.

[amelius]

A server on Mars?

[ZiiS]

Whilst I can not see a motivation I refuse to accept that parking machines are not advisarial design. Why do they have haf a dozen things that look a bit like tap n pay if they are not trying to make it eaiser for card skimmers.

[fennecfoxy]

And the self service kiosks/checkouts at supermarkets. So infuriating! Like I'd have to try to make something that slow myself on purpose!

Besides the fact that scanning a barcode seems beyond much of the general population, they do it so sloooow.

[Nextgrid]

Some of these are just dumb terminals with the entire state handled on a server. I've seen a bunch of them freeze at once where no UI would respond (but the interactions were buffered) and then when the network hiccup was over they all unfroze and reflected the input.

[jon-wood]

The self service kiosks are intentionally throttled when scanning barcodes, at a guess to prevent people accidentally scanning the previous/wrong item - I once had some problems with one and a staff member flipped it into supervisor mode at which point they were able to scan at the same rate you'd see at a manned checkout.

[theragra]

I found that checkouts in Belarus in cheap store are terrible. Checkouts in Latvia in cheap shop are slightly better.

Checkout in Rimi, premium Danish store are superb. Work well, UI clean and clear. No ads, no excessive clicks.

[itsamario]

Only in America. America is deigned to make you mad that public common life isn't keeping up with whats in everybody's pocket.

Gently forcing the individual to choose sapient or insentient.

[afpx]

Sorry to rant, but this kind of stuff is the only thing that triggers me. It's gotten so bad that my family makes me put a dollar in a 'complain jar' everytime I talk about how poor quality software has become.

Just one recent example: few months ago, I replaced a Bosch dishwasher with the latest version of the same model. Now, when I press the start button to initiate the cycle, it takes over 3 seconds for it to register! Like, what is going on in that 3 seconds?

How was it possible that even 'kind of good' developers like me were able todo much more with much less back in the 90s? My boss would be like, "Here's this new hardware thingy and the manual. Now figure out how to do the impossible by Monday." Was it because we had bigger teams, more focus, fewer dependencies?

[mordechai9000]

I think we've been trained to accept bad software at this point, and a lot of people don't know anything different.

I suspect that a lot of it is caused by shoving Android onto underpowered devices because it is cheap and seems like an easy button. But I don't know for sure, that's just an impression. I have no numbers.

Could there be an opportunity here, for a specialized kiosk OS or something like that?

[HWR_14]

It could also be intentional UX design. Or a result of the keyboard hardware.

[pjmlp]

What can you expect, when people assume as normal shipping the browser alongside the "native" application, and scripting languages using an interpreter are used in production code?

Maybe that ticket machine was coded in MicroPython. /s

[anthk]

- TCL/Tk slowish under P3 times, decent enough under P4 with SSE2. AMSN wasn't that bad back in the day, and with 8.6 the occasional UI locks went away.

- Visual Basic. Yes, it was interpreter, and you used to like it. GUI ran fast, good for small games and management software. The rest... oh, they tried to create a C64 emulator under VB, it ran many times slower than one created in C. Nowadays, with a P4 with SSE2 and up you could emulate it at decent speeds with TCL/Tk 8.6 since they got some optimized interpreter. IDK about VB6, probably the same case. But at least we know TCL/Tk got improved on multiprocessing and the like. VB6 was stuck in time.

- TCL can call C code with ease, since the early 90's. Not the case with Electron. And JS really sucks with no standard library. With Electron, the UI can be very taxing, even if they bundle FFMPEG and the like. Tk UI can run on a toaster.

- Yeah, there is C#... but it isn't as snappy and portable TCL/Tk with IronTCL, where it even targets Windows XP. You have JimTCL where it can run on scraps. No Tk, but the language it's close in syntax to TCL, it has networking and TLS support and OFC has damn easy C interops. And if you are a competent programmer, you can see it has some alpha SDL2 bindings. Extend those and you can write a dumb UI with Nuklear or similar in days. Speed? It won't win against other languages on number crunching, but for sure it could be put to drive some machines.

[eru]

Interpreters don't have to be slow.

Forth is usually interpreted and pretty fast. And, of course, we have very fast Javascript engines these days. Python speed is being worked on, but it's pretty slow, true.

[megablast]

Anything that makes the world worse for car drivers is a huge bonus for The planet.