|
|
Cute, but fourtey pounds! People pay that?
WTF am I wasting my time on computers for?
Installing Signature...
Do not switch off your computer.
|
|
|
|
|
Remove the upholstery and have them making out and maybe I'd be interested.
|
|
|
|
|
|
Seeing your other interests, perhaps I could interest you in crowd-funding my 'entry level' IoT market mover:
A rectal thermometer you can use to self-monitor on your smart phone and, with it's built-in camera, even post on Snapchat.* It's now up to you.
*insider information.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
|
Jeremy Falcon
|
|
|
|
|
The way reality TV is going they're such to have "Battle of the fridges"?
Someone's therapist knows all about you!
|
|
|
|
|
Most touch applications are developed using an emulator. The "touch" test is generally conducted on a real phone or pad. Are there any good reasons that developers need a touch screen dev box?
TOMZ_KV
|
|
|
|
|
I don't. Nobody had better touch my databases.
|
|
|
|
|
Quote: Are there any good reasons that developers need a touch screen dev box? Not a single one I can think of. Another bit of fluff to keep you from real work!
|
|
|
|
|
My box is 2 years old with a touch screen. With two regular monitors linked to it, I do not remember what was the last time I touched its screen.
TOMZ_KV
|
|
|
|
|
No body can select/insert/update your database?
TOMZ_KV
|
|
|
|
|
|
Nobody really does. That will find it's way to the top of the truth heap in time.
|
|
|
|
|
For daily business operation, not so much touch interaction on a computer is needed.
TOMZ_KV
|
|
|
|
|
Tomz_KV wrote: Are there any good reasons that developers need a touch screen dev box? An emulator is just that; it may not be an entirely accurate representation of what happens on the real hardware.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Do you think my boss would buy me an iPhone X?
TOMZ_KV
|
|
|
|
|
If you need to write software for the iPhone X, then yes, I'd recommend getting one. Most people reacting here in this thread are reacting before they read the entire question.
..if you don't need to write software for it, then the question would be simple; are you worth that iPhone X?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
It is a trade off. One shouldn't fully trust the emulator.
So for example one might suggest that QA should use the actual device.
But the emulator might be 'almost' good enough that one could leave it up to QA to find the small number of problems.
Not to mention that technically problems could come up on different versions of the device or different vendors. The solution to that is problematic for most places because it requires a lot of devices and a lot of testing. And that is simply impossible for a developer to do. At least one company does something like that as there was a story about it somewhere where there was a testing lab with something like 1000+ devices.
|
|
|
|
|
The way I see it, the best testing is done on the actual system the user is using, whereas emulators are best used for prototyping and debugging. I've had many problems only occurred when it was run on the actual system.
|
|
|
|
|
Agree. Even on actual systems, problems may still exist since there are so many different devices made by different manufacturers. Cannot test them all.
TOMZ_KV
|
|
|
|
|
Not until programming becomes as simple as pointing and clicking. At which time devs will make up about 2,000 fancy acronyms for left click and right click so we can still sound important in meetings.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: Not until programming becomes as simple as pointing and clicking
The day may come sooner than we expect.
TOMZ_KV
|
|
|
|
|