ElCapitan

dewme said:

ElCapitan said:

dewme said:

As a developer, I'm sure that having to push out a patch (or a "supplement" if you want to obfuscate reality behind a sugary term) immediately after the general release is gut wrenching. 

It is not the first time around they push a major iOS version and then immediately an update. It has all to do with the logistics of getting millions of new phones into the market, and these obviously have to be produced a bit upfront if they are to be available in major geos at launch. So they inject these with the GM with known issues that they cannot get around to fix unless they stall the entire production pipeline. Which is why they immediately push an update with a batch of fixes that can be applied once the phone is in customer hands. 

But I agree, when there are multiple such updates in very short succession there are fundamental issues, and primarily a testament to a product release cycle that is too tight for quality work. 
Also, I am not entirely sure the public beta cycle is productive, as it will create a lot of noise and distractions for the developers.  

I'm not sold on whether the public beta program has a causal relationship with these late breaking bugs. 

Because of the way the beta program is run – despite all the instrumentation and automated crash reporting, the betas are commented up and down by just about every publication, blog and forum out there, and you force the developers into the scrum process of hell where they act on the comments (and possibly pressure from marketing and management) fixing what, at that time of the development cycle, are trivia and not fundamentals. 

dewme said:

As a developer, I'm sure that having to push out a patch (or a "supplement" if you want to obfuscate reality behind a sugary term) immediately after the general release is gut wrenching. 

It is not the first time around they push a major iOS version and then immediately an update. It has all to do with the logistics of getting millions of new phones into the market, and these obviously have to be produced a bit upfront if they are to be available in major geos at launch. So they inject these with the GM with known issues that they cannot get around to fix unless they stall the entire production pipeline. Which is why they immediately push an update with a batch of fixes that can be applied once the phone is in customer hands. 

But I agree, when there are multiple such updates in very short succession there are fundamental issues, and primarily a testament to a product release cycle that is too tight for quality work. 
Also, I am not entirely sure the public beta cycle is productive, as it will create a lot of noise and distractions for the developers.  

commentzilla said:

hmurchison said:

Nope. 

Based on past history of just abandoning anything that takes a modicum of effort 
it would be unwise for those who are not of the Apple Sheep cloth to put much faith 
in Apple being consistent with any product at this level.    You only need look at 

5.  OS X Server turning into a toy 

Apple’s spent their money on AI companies and other ancillary technologies but they haven’t spent much effort 
into growing their Pro apps beyond routine small features and maintenance updates. 

I’d trust Apple if I had a few workstations to purchase but I’d be wary with committing to anything more than that. 

All of OS X Server's functionality is still there via the command line. In fact, it's in every copy of MacOS.

Blatantly false.  - See post above.

Customers can get these same services directly from open-source providers.
Which for all practical purposes means a Linux distribution.

Looks like Open Directory is gone from 5.8 too, which cannot easily be swapped for a standard LDAP server. 

Andy.Hardwake said:

ElCapitan said:

It still keeps nagging to update Apple ID. 

Also Touch ID is erratic but now at least it recognizes the fingerprint about  70 percent of the time. 

Try another finger. Every time I restring my guitars and bases it stops recognizing my thumb. My wife couldn’t use Touch ID at all, turned up her index finger was constantly calloused by kitchen work, now touch ID works perfectly with her other fingers.

I have done that and it all works after I deleted the Apple ID and added it back again. 

A casual internet search will reveal others have had / have the same issues with the 13.0 and 13.1 update. 

StrangeDays said:

Gosh, I’d hate to see what happens when you find out Jobs accepted Microsoft investment  

He did not accept investment from Microsoft. 

Microsoft took a minor non-voting stock position as part of a much larger package to compensate Apple for stealing code from QuickTime and used in Video for Windows. 

Microsoft also paid a major amount (between $550 - $720 million - only SJ and BG knows the exact number), committed to port Internet Explorer to the Mac, committed to maintain Office for the Mac for a minimum of 10 years with an option for Apple to extend for a period (5 years if I remember right), let Apple get insight into and access to inspect all Windows code for a period of 10 years and let Apple use the portions of the code they needed, which was one of the reasons macOS server had Active Directory support for a while. There were other aspects to the agreement too.

The alternative for Microsoft would be that SJ took the theft as evidence to the case the DOJ had against Microsoft, and Microsoft would have been split. 

You have NO idea of the damage Microsoft both tried to inflict and inflicted to Apple, IBM and others around that time. It was a real battle.
Compaq was on the MS side of the battle.