|
The Apple Launch was a bit lacklustre but we all knew what was coming, so the [insert company de jour] hating will be a little moreone-sided given that the faithful don't have as much oomph to defend.
Even so, Huawei released a camera last year whose camera bump looks pretty much the same as the iPhone, so people will just slam on whatever they can to feel important.
Having said that, Steve Jobs is spinning in his grave.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: Having said that, Steve Jobs is spinning in his grave. interesting, Chris, i personally don't have a dog in this race ... my rarely used mobile is (by choice) a lowest cost un-smart Samsung: no internet, no camera. i've lost track of what's what at Apple
of course, i am surrounded by a culture in which almost always-on mobile use, and constant messaging, is rampant. i see relatively poor kids sporting iKnockOffs, pretending to take selfies
"spinning in his grave" ? because of general lack of "insanely great" innovation ? because of losing the ability to define innovation by becoming just another horse in the optics race ?
while i think Apple doing tv/audio streaming services is weird, i wonder what Steve would have thought about that.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
BillWoodruff wrote: because of general lack of "insanely great" innovation
No, because of the dilution of focus. Steve was fixated on simplifying things.
First, we now have 6 different phone models to choose from. Instead of producing "a phone, the perfect phone" they are producing a Big Phone, a Not As Big Phone, and a "cheaper" phone. So basically a super expensive phone, large size / medium size, and then an entry level phone for those who can't expense this to their company. Except they are also still keeping the older, much cheaper versions because they want to offer a cheap phone without offering an actual cheap phone. A very passive way of saying "yeah, our phones are too expensive but we're not bold enough to say so explicitly.
Second, the design is complicated. It doesn't have that smooth, no features, no buttons, just a polished piece of perfection that Steve was always pushing. It's a compromised design of function over form (which is often how people, especially engineers think they want) that says "we weren't pushed hard enough to do better". They could have made the camera cluster be more elegant but they didn't. They focused on keeping the phone thin instead of keeping it beautiful. And the irony is the new phone is thicker. But who actually will notice? No one, but everyone will see that camera cluster.
When Steve came back to Apple the first thing he did was trim the bloated product line up that was massively confusing to customers and employees. Apple is drifting (maybe racing) right back to that point and it's like a slow motion car crash.
cheers
Chris Maunder
|
|
|
|
|
thanks, Chris, i see the points you are making.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
BillWoodruff wrote: a fear of clusters of small holes like those found in shoe treads, honeycombs and lotus seed pods.
Oh come on, they leave out the obvious - spider eyes! And yes, they lenses on the iPhone do look creepy. I wouldn't want that staring up at me in the middle of the night!
|
|
|
|
|
one of the recent seasons of American Horror Story used specific images to set off that phobia, in their intro (though not so much in the story).
Google[^]
|
|
|
|
|
i'd say a pock-marked human face is liable to get an instinctive disgust-fear-loathing-aversion response. not too long ago, in history, that was a distinct marker for smallpox ,,, or even leprosy.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
modified 13-Sep-19 12:24pm.
|
|
|
|
|
There are more phobias than you might be aware of. And some of them seem truly weird, such as Arachibutyrophobia- Fear of peanut butter sticking to the roof of the mouth.
Then again, others are rather easy to understand, e. g. Hippopotomonstrosesquipedaliophobia- Fear of long words. I think there was someone being overcreative ...
Both can be found at ThePhobia List[^] . However, that list doesn't include my favorite, Anatidaephobia (Urban Dictionary)[^], the fear of being watched by a duck . I think *that* one was a hoax though.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
Is Mississippi a hippie's wife?
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Actually, it's what they say about an exceptional poor shot who couldn't hit the broad side of a hippopotamus.
That being said, I'll begin my Maine reply: Is Maryland the original "happy place"?
Is Illinois when someone bothers you so much it makes you sick?
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 seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Only if she is called Magnolia and does not have MS
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
Indeed, I was Delaware of that fact, Utah thunk everyone was.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Was California Caesar's wife?
(No, her name was Calpurnia)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Not sure, Alaska round to see if anyone knows.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Can Ada help?
Message Signature
(Click to edit ->)
|
|
|
|
|
She's not here, she's either sick Oregon on vacation.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
O. Hi! O.
(I live in Xenia, Ohio[^])
Software Zen: delete this;
|
|
|
|
|
Someone here, I believe it was honey the codewitch, mentioned they "develop very iteratively". It made me think about styles of coding vs. debugging. Where I work, some people tend to code much more than others before compiling. I like to err on the side of caution- compiling much more often to see that what I think I did, actually worked the way I think it did.
Maybe some of it is confidence in your code skills? You can certainly code more if you don't check your work every two seconds, but if you embedded a bunch of bugs, they may be hard to find if you wait too long.
...Just curious what you guys think? Is it a matter of style, or is there a right or wrong way? How often do you like to compile?
|
|
|
|
|
Sander,
I'm talking about coding vs. not coding, whether it be compiling or testing.
Regards,
Rob
|
|
|
|
|
Then my original answer still stands, depends on what I'm doing.
Writing a new feature requires less testing than the testing of that feature and fixing bugs
The writing to testing ratio depends on the feature.
If it's a front-end thing I like to add a line of HTML/CSS and then check how bad I messed up in the browser (but this doesn't require recompiles).
When doing back-end code I can better predict what my code will do and I can test the entire thing in one go when I'm done.
|
|
|
|
|
why was your original thread with same title closed? interesting.
|
|
|
|
|
I actually compile when I run my code before sending to patch (to QA)... Save every second but compile as less as possible...
I see no need for that...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
You're not concerned about dealing with a pile of bugs at once?
|
|
|
|
|
What bugs are?
Seriously, no. What I'm writing is always connected to a single issue (new feature or bug fix), which makes it somehow monolithic, and for that easy to fix (because a single bug may open a chain effect, but also closes it)...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|