Technical loss:
- inviting crappy third party code decreases stability
Financial loss:
- decreased stability leads to increased support costs and loss of sales
Quote:
Originally Posted by TETENAL
Technical loss:
- inviting crappy third party code decreases stability
We've been through this. People are writing hacks regardless. Pro…
Quote:
Originally Posted by besson3c
We've been through this. People are writing hacks regardless.
But people know they don't have support from Apple and do it on their own r…
Quote:
Originally Posted by TETENAL
But people know they don't have support from Apple and do it on their own risk.But some will and Apple has no way to control the quality of t…
I think the more basic question is:
"Why does it have to be Mail and/or Safari that does this?"
Mail and Safari are not intended to be end-all/be-all apps, whether by design or b…
Quote:
Originally Posted by besson3c
Financial gain:
- more viability and value of Apple's bundled products in business and places where workflow is a little more complex, wit…
I see your points, and you have changed my thinking a little.
However, I still see some viability in aspects of my own thinking. I guess we'll have to agree to disagree.
My littl…
Quote:
Originally Posted by besson3c
I hope that you see a little viability in some of my ideas too.
In a perfect world where Apple has unlimited (or near unlimited) engineer…
Quote:
Originally Posted by Chuckit
Incidentally, WebKit is open-source. If you want to give Safari a plugin interface, knock yourself out!
Yeah, I know that Webkit is op…
Quote:
Originally Posted by besson3c
We've been through this. People are writing hacks regardless.
Right. And Apple doesn't have to support them.
If Apple adds an API for …
Quote:
Originally Posted by besson3c
Yeah, I know that Webkit is open-source, and where to get the source too. I'm happy with Firefox, but I probably would have stayed on Safari…
Quote:
Originally Posted by goMac
Right. And Apple doesn't have to support them.
If Apple adds an API for something, they have to support it. That's the difference. Apple doesn…
Quote:
Originally Posted by Chuckit
So then your problem is not that Apple doesn't have a public API for Safari, but that it's not Firefox.
It's not a problem really, I c…
Quote:
Originally Posted by besson3c
(And no, you don't have to answer that question if you will just be reiterating the points already made... I get them).
We'd stop using t…
Quote:
Originally Posted by besson3c
However, Apple has open sourced the entire damn kernel, Bonjour, iCal Server, Darwin Streaming Server, Webkit, Webojects, and provides devel…
Quote:
Originally Posted by Chuckit
A plug-in architecture adds complexity that Apple itself has to deal with. Accepting tested code from outside parties is much easier than mai…
Quote:
Originally Posted by besson3c
I just want to be understood.
As do I.
The problem is that you continue to make statements like this:
Quote:
Originally Posted by be…
Quote:
Originally Posted by besson3c
So you're saying that Apple would have to be somewhat accountable for these projects in providing the infrastructure the developers need?
…
Quote:
Originally Posted by Moose
As do I.
The problem is that you continue to make statements like this:
You make it sound like Apple is intentionally expending effort to anta…