So we have (A) Apple prevents the flash interpreter thats available everywhere else, and (B) Apple also prevents the flash compiler built specifically because of (A)
But when I worked on Wall Street in the late 80's, you had to enter zeroes to make a trade. None of this B or M bullshit. It's just a few extra keystrokes, but the trader's intent is always clear, they pretty fucking well know the difference between 6 and 9 zeroes.
They came second, so they should be required to support the tools of those that came first. Because the bottom line is, some notable exceptions aside, all carriers and phones prior to the iPhone had some kind of similar restriction for developers, like forcing you to use the Java interpreter present in the phone.
There's also very little crime in a facist country run with an iron fist, and there is (in theory) no inequality within communisim...that doesn't make it a good idea.
That's a pretty myopic view. Other app translation layers are going to be knocked out of the market too.
I've been writing code for a very long time. Twenty seven years. I have seen similar restrictions. You can't develop for a game console without using the certified tools from the console vendor, and paying out the ass for the privilege. Prior to the iPhone, there were plenty of phones and platforms with even more draconian restrictions. Any app for any phone on Verizon Wireless required code to be written in Java.
And I'll say it: god damn right this is a good thing. What I have seen in my multiple decades in this industry is layer upon layer of bloat added and added and added to each successive version of a package or OS. Even Linux suffers from this, albeit to a much lesser extent than some "other" operating systems.
The answer for most of the software industry has consistently been: throw more hardware at the problem. The end result: people get hardly any value for buying a new computer. It's about fucking time some OS vendor drew the line and said "if you use cycle burning bloatware, you're not welcome here". I think it would be a damn good thing if all OS vendors took the same attitude. But of course, they would have to lead by example...which Apple has done. Snow Leopard is the first OS release in the past 3 decades that delivered more features than its predecessor, and did it with a smaller footprint, and with tighter, faster code. So, for $29, I got a better computer upgrade than any I have spent $800-$4000 for in the past. And my upgrades have spanned all microcomputer platforms except BeOS.
Bottom line: Man the fuck up and write some decent code. If you're any good at it, your core logic is layered away from where it touches the OS and it's APIs anyway, so porting your iPhone app to another platform isn't much of an issue anyway. Unless the other target platform restricts you to Java.
The point of the investigation is to investigate if the point of Apple's restrictions is to create more or less an app store monopoly by preventing the approval of apps that would work on multiple platforms.
No, the point of the inquiry (not investigation) is to determine if an investigation into possible anticompetitive practices in the smart phone market is appropriate.
Here's how I see it: the iPhone delivers a superior user experience, on a lesser-powered chip than its competitors, because the code is heavily optimized. Requiring developers to bypass cycle burning translation layers, the way I see it, is Apple doing what it must to maintain its competitive advantage.
Slashdot Mirror
Are you talking about makefiles and scripts, or are you talking about a proprietary compiler used to generate the code? There's a huge difference.
Only one problem. No Y encoded in the data stream, so it has to be interpolated.
Reading is good:
So we have (A) Apple prevents the flash interpreter thats available everywhere else, and (B) Apple also prevents the flash compiler built specifically because of (A)
But when I worked on Wall Street in the late 80's, you had to enter zeroes to make a trade. None of this B or M bullshit. It's just a few extra keystrokes, but the trader's intent is always clear, they pretty fucking well know the difference between 6 and 9 zeroes.
Really? When did they release Flash for the Blackberry? PowerPC-based Linux distros? Solaris? WinNT/MIPS (okay, that's a joke).
They came second, so they should be required to support the tools of those that came first. Because the bottom line is, some notable exceptions aside, all carriers and phones prior to the iPhone had some kind of similar restriction for developers, like forcing you to use the Java interpreter present in the phone.
ZOMG! Sam Walton owns a monopoly on Walmart! Call the antitrust police!
Are you going to argue that a fool can speak without removing all doubt?
Oh fuck that, I want my Stallman-inscribed GNU/iPhone, the version with emacs as the home screen.
Really? Odd thing to do with less than a majority share of said market.
There's also very little crime in a facist country run with an iron fist, and there is (in theory) no inequality within communisim...that doesn't make it a good idea.
Way to invoke Godwin's Law.
Yes, Verizon+Droid is indeed a choice.
And from what I've heard, Verizon is giving the Droid away.
Yeah, well, that's just because Windows doesn't pulse subliminal messages to its users telling them to hate Blackberry.
That's a pretty myopic view. Other app translation layers are going to be knocked out of the market too.
I've been writing code for a very long time. Twenty seven years. I have seen similar restrictions. You can't develop for a game console without using the certified tools from the console vendor, and paying out the ass for the privilege. Prior to the iPhone, there were plenty of phones and platforms with even more draconian restrictions. Any app for any phone on Verizon Wireless required code to be written in Java.
And I'll say it: god damn right this is a good thing. What I have seen in my multiple decades in this industry is layer upon layer of bloat added and added and added to each successive version of a package or OS. Even Linux suffers from this, albeit to a much lesser extent than some "other" operating systems.
The answer for most of the software industry has consistently been: throw more hardware at the problem. The end result: people get hardly any value for buying a new computer. It's about fucking time some OS vendor drew the line and said "if you use cycle burning bloatware, you're not welcome here". I think it would be a damn good thing if all OS vendors took the same attitude. But of course, they would have to lead by example...which Apple has done. Snow Leopard is the first OS release in the past 3 decades that delivered more features than its predecessor, and did it with a smaller footprint, and with tighter, faster code. So, for $29, I got a better computer upgrade than any I have spent $800-$4000 for in the past. And my upgrades have spanned all microcomputer platforms except BeOS.
Bottom line: Man the fuck up and write some decent code. If you're any good at it, your core logic is layered away from where it touches the OS and it's APIs anyway, so porting your iPhone app to another platform isn't much of an issue anyway. Unless the other target platform restricts you to Java.
The point of the investigation is to investigate if the point of Apple's restrictions is to create more or less an app store monopoly by preventing the approval of apps that would work on multiple platforms.
No, the point of the inquiry (not investigation) is to determine if an investigation into possible anticompetitive practices in the smart phone market is appropriate.
See Psystar Ruling. There is no "Mac Computer Market".
It seems his argument is that nobody knows what private communications went on between Apple and Adobe.
How is this any different from developing for NES or PlayStation?
That's certainly one way to look at it.
Here's how I see it: the iPhone delivers a superior user experience, on a lesser-powered chip than its competitors, because the code is heavily optimized. Requiring developers to bypass cycle burning translation layers, the way I see it, is Apple doing what it must to maintain its competitive advantage.
Translation: time to man up and stop shoveling extra overhead onto an underpowered device just because you're lazy.
What do you expect from a sociopath that stole the idea from his clients?
404. And if you're going to knock off twitter's logo, at least learn how to make antialiased shapes in photoshop.
Not for a site with useless content like this.
That it is better to be a fool and remain silent, than to speak and remove all doubt.
...The whole interesting thing with AJAX is that you can interact with the web server while staying on the same page...
And without taking the pageload/parsing penalty.