Re: Flashing twelves

Quoting Ivan Sergio Borgonovo ([email protected]):

> Because "supporting" Bluetooth/NFC costs as much as "supporting" the
> whole damn internet accessing your device and it is easier to sell
> to most people. It probably costs more in terms of development too.
> There are tons of framework for authentication + webview...
> controlling the hardware even with some good api is going to be
> harder even if just a little bit, but harder.

OTOH, even my pathetic OpenSprinkler box built on an Arduino and having
less grunt than my 20-year-old Casio watch has a built in, simple static
HTML 3.2 Web server to control every aspect of my drip irrigation
system.

The Arduino is only marginally adequate, but much better CPUs have been 
routine for many decades.  An embedded ARM7, wow, so much better, and 
if someone wanted to have a decent, clear, 1995-grade administrative Web
server built into an appliance, and also NFC (probably Bluetooth)
networking, I submit that that would not involve significant
development.

(I note Akkana's point about Bluetooth being a fiddly and unreliable
pain for her.  OK.  Hasn't been for me, FWIW.)

Point is, an "Android + iPhone API" is not required.  HTTP 1.1 + HTML
3.2 works just great.

> BIG TECH has no interest in changing this.
> And I don't think there is any force on the market that's going to
> change this unless something bad happen that is going to make
> apparent the cost of continuing in this line.
> 
> But you're perfectly aware that people are happy to pay hidden costs
> of stuff for decades even when they surpass the benefits.

Fair.