Do you have adblock enabled?
 
If you can read this, either the style sheet didn't load or you have an older browser that doesn't support style sheets. Try clearing your browser cache and refreshing the page.

(Entertainment Weekly)   In Memoriam: iPhone 9   ( ew.com) divider line
    More: Sad, iPhone, dick-ish new iPhone, normal iPhone possibility, scrappy iPhone, Kristen Wiig character, afflicted middle child, clearer retina screen, gender-fluid younger sibling  
•       •       •

3130 clicks; posted to Geek » on 13 Sep 2017 at 10:20 AM (12 weeks ago)   |   Favorite    |   share:  Share on Twitter share via Email Share on Facebook   more»



32 Comments     (+0 »)
 
View Voting Results: Smartest and Funniest
 
2017-09-13 10:11:23 AM  
Samsung still gonna release the Note IX Plode.
 
2017-09-13 10:22:00 AM  
I like that they did the same thing Windows did. "9? Never heard of it. Look at this! It's shiny and expensive!"
 
2017-09-13 10:25:32 AM  
Well, 7 ate 9,

/sorry
//not sorry
 
2017-09-13 10:26:08 AM  
The God-Emperor has banned any reference to the heretic Ixians.
 
2017-09-13 10:33:53 AM  
They only made one iPhone 9 and Trump will get it.  It's exactly like the iPhone 8 but there's no wifi capability, although it does simulate a connection.  His staff came up with this design feature.  The iPhone 9 will be Trump's version of George W. Bush's Speak & Spell.
 
2017-09-13 10:52:29 AM  
Because if you hold it upside down, everyone will complain it is an iPhone 6.
 
2017-09-13 10:53:40 AM  
That's because the iPhone 7 8 9.
(Should've had the bacon.)
 
2017-09-13 11:19:16 AM  

Modified Cornstarch: Well, 7 ate 9,

/sorry //not sorry



Barenaked Ladies - 7 8 9 [Official Music Video]
Youtube x1cnJ_pOAdQ
 
2017-09-13 11:32:13 AM  
The answer might be here.  "Four" sounds like "For" in English and is hard to pass over.   It's also possible the earlier versions happened before someone though about it.    Of course, it could just be random coinkydink.

https://www.lingualift.com/blog/lucky-unlucky-numbers-japan/
 
2017-09-13 12:01:53 PM  

Arkanaut: The God-Emperor has banned any reference to the heretic Ixians.


First thing I thought of.
 
2017-09-13 12:56:26 PM  
NateAsbestos

I like that they did the same thing Windows did. "9? Never heard of it. Look at this! It's shiny and expensive!"

MS didn't use 9 because of a software issue, Apple is not the same OS and does not suffer from the same situation. So clearly the once leader in innovation is now copying who was once the back of the pack.
 
2017-09-13 01:07:08 PM  

Random Anonymous Blackmail: NateAsbestos

I like that they did the same thing Windows did. "9? Never heard of it. Look at this! It's shiny and expensive!"

MS didn't use 9 because of a software issue, Apple is not the same OS and does not suffer from the same situation. So clearly the once leader in innovation is now copying who was once the back of the pack.


Or more appropriately, software developed by lazy devs who would parse Windows 95/98 as "Windows 9" for version checking.
 
2017-09-13 01:26:15 PM  
if the article is suggesting that 9 died, because they named it 10....well.... then that means 8 died too.
 
2017-09-13 02:15:35 PM  
Nah, I bet the iPhone SE and 8 will be retired next year, and the 9 will be Apple's low-end phone.
 
2017-09-13 02:39:31 PM  

RyansPrivates: Random Anonymous Blackmail: NateAsbestos

I like that they did the same thing Windows did. "9? Never heard of it. Look at this! It's shiny and expensive!"

MS didn't use 9 because of a software issue, Apple is not the same OS and does not suffer from the same situation. So clearly the once leader in innovation is now copying who was once the back of the pack.

Or more appropriately, software developed by lazy devs who would parse Windows 95/98 as "Windows 9" for version checking.


Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?
 
2017-09-13 02:46:44 PM  

bdub77: Samsung still gonna release the Note IX Plode.


This post is the tech version of 'But what about Hillary's emails!'
 
2017-09-13 02:51:48 PM  

physt: Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?


Half lazy devs half MS being INCREDIBLY conservative about backwards compatibility.

MS bends over backward to maintain compatibility/not change things. It's kinda infuriating. Probably a godsend to all those idiots running a virus infested XP machine that controls a CNC machine or a medical radiation therapy machine. Just hope nothing screws up!
 
2017-09-13 02:54:08 PM  

physt: RyansPrivates: Random Anonymous Blackmail: NateAsbestos

I like that they did the same thing Windows did. "9? Never heard of it. Look at this! It's shiny and expensive!"

MS didn't use 9 because of a software issue, Apple is not the same OS and does not suffer from the same situation. So clearly the once leader in innovation is now copying who was once the back of the pack.

Or more appropriately, software developed by lazy devs who would parse Windows 95/98 as "Windows 9" for version checking.

Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?


Well, it was exposed by the "ver" command to the end user.  I know if WMI was installed (very common for win 95/98, and not unreasonable as a prereq for software installs)) that you you could get at it that way.  Ther was also the version API, but I'm not sure if that was availabe for win9x.
 
2017-09-13 03:15:36 PM  
Cirno inconsolable, just like when Microsoft skipped over Windows ⑨

img.fark.netView Full Size
 
2017-09-13 04:02:50 PM  
img.fark.netView Full Size
 
2017-09-13 04:23:11 PM  

RyansPrivates: physt: RyansPrivates: Random Anonymous Blackmail: NateAsbestos

I like that they did the same thing Windows did. "9? Never heard of it. Look at this! It's shiny and expensive!"

MS didn't use 9 because of a software issue, Apple is not the same OS and does not suffer from the same situation. So clearly the once leader in innovation is now copying who was once the back of the pack.

Or more appropriately, software developed by lazy devs who would parse Windows 95/98 as "Windows 9" for version checking.

Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Well, it was exposed by the "ver" command to the end user.  I know if WMI was installed (very common for win 95/98, and not unreasonable as a prereq for software installs)) that you you could get at it that way.  Ther was also the version API, but I'm not sure if that was availabe for win9x.


Yeah but even the version numbers were bonkers. Windows 7 still was listed as 6.something. It made no sense. Msft killing that and saying "henceforth it'll be 10.x" actually made a lot of sense
 
2017-09-13 04:30:32 PM  

NateAsbestos: RyansPrivates: physt: RyansPrivates: Random Anonymous Blackmail: NateAsbestos

I like that they did the same thing Windows did. "9? Never heard of it. Look at this! It's shiny and expensive!"

MS didn't use 9 because of a software issue, Apple is not the same OS and does not suffer from the same situation. So clearly the once leader in innovation is now copying who was once the back of the pack.

Or more appropriately, software developed by lazy devs who would parse Windows 95/98 as "Windows 9" for version checking.

Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Well, it was exposed by the "ver" command to the end user.  I know if WMI was installed (very common for win 95/98, and not unreasonable as a prereq for software installs)) that you you could get at it that way.  Ther was also the version API, but I'm not sure if that was availabe for win9x.

Yeah but even the version numbers were bonkers. Windows 7 still was listed as 6.something. It made no sense. Msft killing that and saying "henceforth it'll be 10.x" actually made a lot of sense


It made a weird sort of sense because Win 2000 was NT version 5, so XP kept the 5.X.XXXX numbering. Vista was a huge change in terms of APIs, so it made sense for it to be NT 6.0. Since 7 and 8 were relatively minor updates under the hood, keeping them at version 6 made it easier for devs to check for comparability. Win 10 being the clean break that it was provided a great opportunity to bring everything into alignment after years of wonky numbering.
 
2017-09-13 06:07:16 PM  

Mad_Radhu: NateAsbestos: RyansPrivates: physt: RyansPrivates: Random Anonymous Blackmail: NateAsbestos

I like that they did the same thing Windows did. "9? Never heard of it. Look at this! It's shiny and expensive!"

MS didn't use 9 because of a software issue, Apple is not the same OS and does not suffer from the same situation. So clearly the once leader in innovation is now copying who was once the back of the pack.

Or more appropriately, software developed by lazy devs who would parse Windows 95/98 as "Windows 9" for version checking.

Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Well, it was exposed by the "ver" command to the end user.  I know if WMI was installed (very common for win 95/98, and not unreasonable as a prereq for software installs)) that you you could get at it that way.  Ther was also the version API, but I'm not sure if that was availabe for win9x.

Yeah but even the version numbers were bonkers. Windows 7 still was listed as 6.something. It made no sense. Msft killing that and saying "henceforth it'll be 10.x" actually made a lot of sense

It made a weird sort of sense because Win 2000 was NT version 5, so XP kept the 5.X.XXXX numbering. Vista was a huge change in terms of APIs, so it made sense for it to be NT 6.0. Since 7 and 8 were relatively minor updates under the hood, keeping them at version 6 made it easier for devs to check for comparability. Win 10 being the clean break that it was provided a great opportunity to bring everything into alignment after years of wonky numbering.


Windows 7, to my way of thinking, is pretty much the way the successor to XP should have been (Vista was half-baked). And windows 10 was what the successor to 7 should have been.   Goes back to the old adage for  both Star Trek movies and Windows: every other one is good.
 
2017-09-13 08:22:36 PM  

Esc7: physt: Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Half lazy devs half MS being INCREDIBLY conservative about backwards compatibility.

MS bends over backward to maintain compatibility/not change things. It's kinda infuriating. Probably a godsend to all those idiots running a virus infested XP machine that controls a CNC machine or a medical radiation therapy machine. Just hope nothing screws up!


REEEELY? Tell that to my doctor friend who almost lost access to his billing database because the last Windows 7 update killed Windows XP Virtual mode.

"Ohhhh we're real *snicker* sorry.  Why don't you just upgrade to Windows 10?..where your app doesn't work?"
 
2017-09-13 08:32:47 PM  

netringer: Esc7: physt: Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Half lazy devs half MS being INCREDIBLY conservative about backwards compatibility.

MS bends over backward to maintain compatibility/not change things. It's kinda infuriating. Probably a godsend to all those idiots running a virus infested XP machine that controls a CNC machine or a medical radiation therapy machine. Just hope nothing screws up!

REEEELY? Tell that to my doctor friend who almost lost access to his billing database because the last Windows 7 update killed Windows XP Virtual mode.

"Ohhhh we're real *snicker* sorry.  Why don't you just upgrade to Windows 10?..where your app doesn't work?"


Who is this medical billing software company that is requiring a customer to run a DB on a consumer (not server) OS from 16 years ago?  It would be like trying to prescribe a medication that was discontinued in 2005 because of lack of efficacy and then complaining when you can't do so.
 
2017-09-14 12:15:06 AM  

netringer: Esc7: physt: Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Half lazy devs half MS being INCREDIBLY conservative about backwards compatibility.

MS bends over backward to maintain compatibility/not change things. It's kinda infuriating. Probably a godsend to all those idiots running a virus infested XP machine that controls a CNC machine or a medical radiation therapy machine. Just hope nothing screws up!

REEEELY? Tell that to my doctor friend who almost lost access to his billing database because the last Windows 7 update killed Windows XP Virtual mode.

"Ohhhh we're real *snicker* sorry.  Why don't you just upgrade to Windows 10?..where your app doesn't work?"

img.fark.netView Full Size

Is this your doctor friend?
 
2017-09-14 12:42:06 AM  

RyansPrivates: netringer: Esc7: physt: Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Half lazy devs half MS being INCREDIBLY conservative about backwards compatibility.

MS bends over backward to maintain compatibility/not change things. It's kinda infuriating. Probably a godsend to all those idiots running a virus infested XP machine that controls a CNC machine or a medical radiation therapy machine. Just hope nothing screws up!

REEEELY? Tell that to my doctor friend who almost lost access to his billing database because the last Windows 7 update killed Windows XP Virtual mode.

"Ohhhh we're real *snicker* sorry.  Why don't you just upgrade to Windows 10?..where your app doesn't work?"

Who is this medical billing software company that is requiring a customer to run a DB on a consumer (not server) OS from 16 years ago?  It would be like trying to prescribe a medication that was discontinued in 2005 because of lack of efficacy and then complaining when you can't do so.


There is a guy here who did work for BoA on a PC that singly handles large land deals.  He says 11 digits pass through it per year.  It is running on a specific version of XP that they had to stop updating because the program runs on a specific version off Microsoft.net that was released in to the wild for like 2 weeks before it was patched.  A zillion years ago, it was a program that worked, so why worry about it.  Now it is a keystone to billions of dollars that management is terrified of touching.
 
2017-09-14 07:52:21 AM  

Witty_Retort: RyansPrivates: netringer: Esc7: physt: Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Half lazy devs half MS being INCREDIBLY conservative about backwards compatibility.

MS bends over backward to maintain compatibility/not change things. It's kinda infuriating. Probably a godsend to all those idiots running a virus infested XP machine that controls a CNC machine or a medical radiation therapy machine. Just hope nothing screws up!

REEEELY? Tell that to my doctor friend who almost lost access to his billing database because the last Windows 7 update killed Windows XP Virtual mode.

"Ohhhh we're real *snicker* sorry.  Why don't you just upgrade to Windows 10?..where your app doesn't work?"

Who is this medical billing software company that is requiring a customer to run a DB on a consumer (not server) OS from 16 years ago?  It would be like trying to prescribe a medication that was discontinued in 2005 because of lack of efficacy and then complaining when you can't do so.

There is a guy here who did work for BoA on a PC that singly handles large land deals.  He says 11 digits pass through it per year.  It is running on a specific version of XP that they had to stop updating because the program runs on a specific version off Microsoft.net that was released in to the wild for like 2 weeks before it was patched.  A zillion years ago, it was a program that worked, so why worry about it.  Now it is a keystone to billions of dollars that management is terrified of touching.


Wasn't it a Vista machine?

/That story was a NCSB.
 
2017-09-14 07:56:51 AM  

Witty_Retort: RyansPrivates: netringer: Esc7: physt: Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Half lazy devs half MS being INCREDIBLY conservative about backwards compatibility.

MS bends over backward to maintain compatibility/not change things. It's kinda infuriating. Probably a godsend to all those idiots running a virus infested XP machine that controls a CNC machine or a medical radiation therapy machine. Just hope nothing screws up!

REEEELY? Tell that to my doctor friend who almost lost access to his billing database because the last Windows 7 update killed Windows XP Virtual mode.

"Ohhhh we're real *snicker* sorry.  Why don't you just upgrade to Windows 10?..where your app doesn't work?"

Who is this medical billing software company that is requiring a customer to run a DB on a consumer (not server) OS from 16 years ago?  It would be like trying to prescribe a medication that was discontinued in 2005 because of lack of efficacy and then complaining when you can't do so.

There is a guy here who did work for BoA on a PC that singly handles large land deals.  He says 11 digits pass through it per year.  It is running on a specific version of XP that they had to stop updating because the program runs on a specific version off Microsoft.net that was released in to the wild for like 2 weeks before it was patched.  A zillion years ago, it was a program that worked, so why worry about it.  Now it is a keystone to billions of dollars that management is terrified of touching.


Vista business: https://m.fark.com/comments/9587926/108971703

Sorry about that, on mobile, and the keyboard does not play nice with the Fark link UI

/Paging xaks, the white courtesy phone.
 
2017-09-14 08:05:23 AM  

agent00pi: Witty_Retort: RyansPrivates: netringer: Esc7: physt: Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Half lazy devs half MS being INCREDIBLY conservative about backwards compatibility.

MS bends over backward to maintain compatibility/not change things. It's kinda infuriating. Probably a godsend to all those idiots running a virus infested XP machine that controls a CNC machine or a medical radiation therapy machine. Just hope nothing screws up!

REEEELY? Tell that to my doctor friend who almost lost access to his billing database because the last Windows 7 update killed Windows XP Virtual mode.

"Ohhhh we're real *snicker* sorry.  Why don't you just upgrade to Windows 10?..where your app doesn't work?"

Who is this medical billing software company that is requiring a customer to run a DB on a consumer (not server) OS from 16 years ago?  It would be like trying to prescribe a medication that was discontinued in 2005 because of lack of efficacy and then complaining when you can't do so.

There is a guy here who did work for BoA on a PC that singly handles large land deals.  He says 11 digits pass through it per year.  It is running on a specific version of XP that they had to stop updating because the program runs on a specific version off Microsoft.net that was released in to the wild for like 2 weeks before it was patched.  A zillion years ago, it was a program that worked, so why worry about it.  Now it is a keystone to billions of dollars that management is terrified of touching.

Vista business: https://m.fark.com/comments/9587926/108971703

Sorry about that, on mobile, and the keyboard does not play nice with the Fark link UI

/Paging xaks, the white courtesy phone.


Holy shiat, it's a little scary when y'all remember so much, so well

Yes, it is/was a Vista business PC with a specific version of Visual Basic. It was *only* 8 or 9 digits of deals, though, not 11. But yea...

As of a mid-June of this year, it was still up and running!
 
2017-09-14 08:16:43 AM  

xaks: agent00pi: Witty_Retort: RyansPrivates: netringer: Esc7: physt: Were they lazy dev or did MS not give devs a decent farking way to determine what version they were running on?

Half lazy devs half MS being INCREDIBLY conservative about backwards compatibility.

MS bends over backward to maintain compatibility/not change things. It's kinda infuriating. Probably a godsend to all those idiots running a virus infested XP machine that controls a CNC machine or a medical radiation therapy machine. Just hope nothing screws up!

REEEELY? Tell that to my doctor friend who almost lost access to his billing database because the last Windows 7 update killed Windows XP Virtual mode.

"Ohhhh we're real *snicker* sorry.  Why don't you just upgrade to Windows 10?..where your app doesn't work?"

Who is this medical billing software company that is requiring a customer to run a DB on a consumer (not server) OS from 16 years ago?  It would be like trying to prescribe a medication that was discontinued in 2005 because of lack of efficacy and then complaining when you can't do so.

There is a guy here who did work for BoA on a PC that singly handles large land deals.  He says 11 digits pass through it per year.  It is running on a specific version of XP that they had to stop updating because the program runs on a specific version off Microsoft.net that was released in to the wild for like 2 weeks before it was patched.  A zillion years ago, it was a program that worked, so why worry about it.  Now it is a keystone to billions of dollars that management is terrified of touching.

Vista business: https://m.fark.com/comments/9587926/108971703

Sorry about that, on mobile, and the keyboard does not play nice with the Fark link UI

/Paging xaks, the white courtesy phone.

Holy shiat, it's a little scary when y'all remember so much, so well

Yes, it is/was a Vista business PC with a specific version of Visual Basic. It was *only* 8 or 9 digits of deals, though, not 11. But yea...

As of a mid-June of this year, it was still up and running!


I enjoyed hearing about Goatse level security holes.
 
2017-09-14 06:49:27 PM  

xaks: Yes, it is/was a Vista business PC with a specific version of Visual Basic. It was *only* 8 or 9 digits of deals, though, not 11. But yea...


my bad. I'll update my faulty memory accordingly.
 
Displayed 32 of 32 comments

View Voting Results: Smartest and Funniest

This thread is closed to new comments.

Continue Farking

On Twitter





Top Commented
Javascript is required to view headlines in widget.
  1. Links are submitted by members of the Fark community.

  2. When community members submit a link, they also write a custom headline for the story.

  3. Other Farkers comment on the links. This is the number of comments. Click here to read them.

  4. Click here to submit a link.

Report