iPhone hardware wise is like an amazing alternative to rpi (way better hardware)
But the software makes no sense at all for a server, with screen locking due to inactivity and whatnot, not to mention energy and network priority is designed around a consumer use case on the move.
If you run Linux on it and take advantage from the Apple hardware like the light sensors and accelerometer - maybe it makes sense for measuring wave height, sky color, attached to a buoy or oil rig or something, you can even show it on a map due to its GPS. Assuming the oil rig has WiFi or a cell phone booster.
Idk though, maybe for something that important you just get the right stuff - cool hobby nonetheless.
Keeping it plugged in like that is going to harm the battery.
That and the fact that my Xiaomi 12 runs USB 2.0 ....
I'm stuck running stuff on MacBook at night when I don't use it because of that.
Electronic price need to become reasonable again, a 8gb raspberry pi 5 is about 200€ right now. It's absolutely insane.
My pi 4 did cost me 40€ a few years ago.
i'm thinking more about long term.
1) It's optimized for the restaurant first, and the patrons second or not at all, and it shows.
2) Someone thinks "hey, we could sell ads on this", and now it's even more a piece of garbage. (This is also what happened with all the little kiosk-tablets on the tables at some restaurants. We just set them face-down on their screen and talk to a human.)
3) Most of them never anticipate unexpected problems. They might have an "order X" button, but they often don't even have a "call server" button. And when they do, it often doesn't work, because the other end isn't hooked up to something that gets people's attention.
The much lower-tech and more enjoyable solution I've seen used successfully many many times is a call button on the table. Press the button if you want service. Bonus if it has a "press this other button if you want to be left alone".
People immediately see the cost of a tablet, the issues with charging, building the app and updating the data, customers not understanding the interface etc.
Yet, they don't seem to grasp all of these are basically the same for a QR code: you're now maintaining an online service just for your restaurant. People still need to understand your site. You'll be dealing with their browser, extensions, languages etc. And you still need the QR code somewhere on the table, visible, explain that it needs to be scanned (by one person ? everyone ? do they need to keep the tab open ? etc.). These will all be costs, you pay either upfront by hiring experts to make the experience good, or on the go with crappy customer experience, your staff spending more time than needed working around the system and explaining it to your customers, and those not coming back.
There are super cheap and simplistic ways to deal with all of that, and I assume GP has seen many of these.
PS: The weirdest experience I ever had was someone at our table scanning the code, to copy/paste it on the browser on their personal profile (default was work browser). They missed a digit in the url params and ended up opening the order menu of a table at the other side of the restaurant, and just started ordering, then waiting for a pretty long time while the other table was dealing with the mess.
Besides that, there are people who have no smartphone or an empty battery, can't use a smartphone (one of my grandparents can read a menu with a pocket magnifier, but a touchscreen phone is too cumbersome and so they don't know how to use that; another grandparent has memory issues and never learned how to use a smartphone), don't have signal (you need to provide WiFi), have an allergy and need to ask questions or ensure that some ingredient is really taken out, etc. I'm not against the option to order impersonally but a good kitchen communication system would go a lot deeper than slapping wetware with slopware
Having backup tablets on hand is a good hybrid.
Using QR codes to not having to talk to a human and to "optimize" humans out of the loop in a restaurant sounds like a great scenario for an episode of black mirror.
QR code menus are one the shittiest experience people going to a restaurant to enjoy a meal can have.
> Do you not like this option?
The entire world fucking hates it. It's totally dumbfucktarded.
Sorry to be blunt.
I run kube in a VM, and it was ressource constrained.
I hooked an old samsung to my pc and have let claude handle everything.
I only had to unlock the bootloader, flash the image claude uploaded.
It rebuilt postmarketos multiples times to enable various flag, and now there is a kube node running on it.
For me I have a 24x7 running intel gen 11 nuc, i am lucky to get it installed with 32G memory and two NVME disks years ago and cannot image add those memory and NVME disk with much higher price
Just run some docker and VM on that, use cloudflare tunnel or tailscale funnel if you want to expose some service to the wild internet
I recently even find a pixel 5 and passthrough it to the openclaw VM on that nuc, let it browse the X to find some posts and relax me from doom scrolling, though seems timeline still bad and no much valued post find.
Also if your phone has SD card slot you can try "industrial" SD cards. They are small in capacity but ideal for write load.
But the flash storage in a phone is going to be the eMMC variety which typically means a proper controller and TLC NAND. Not as robust probably as a "proper" SSD/NVME, but a lot more durable than most micro SD cards. And it'll have health indicators.
You can also just insert an SD card to do the write-heavy operations and swap it out when it wears out (you make backups, right? :D)
Would have been a fun load test had you hosted your blog on the phone.
Any efficient blog software will handle HN fine on anything that you can call a smartphone, so like maybe not a Nokia with GPRS and 6MB on-board storage, but something like the Samsung S2 from 2011 that basically shipped as a Linux box -- just need to adb push ARM binaries for PHP and a webserver