Wow, is that code terrible. I wonder if there would be a market for a "Flash Compactor" to remove all that dead code and speed things up?
Sure, it's exactly the same as PHP opcode cachers market.
Reaching the Limits of Adobe Stupidity
11–20 of 52 posts
Re: Reaching the Limits of Adobe Stupidity
#12Re: Reaching the Limits of Adobe Stupidity
#13One can only approach the limits of Adobe's stupidity, not actually reach it.
2 x 10^13 years: Estimated time for a self assembling system of the complexity of Adobe's software lineup to reach equilibrium, e.g. to balance out new bugs with fixed issues.
Re: Reaching the Limits of Adobe Stupidity
#14Now I know the reason why I felt uncomfortable about ActionScript. Flash folks were always convincing me that AS3 is perfectly fine and kickass language. Next time I'll just link this.
Given that you didn't have this information before, it's highly unlikely that this was why you felt uncomfortable. Most likely you just don't like ActionScript. It's OK — you're allowed to have personal taste.
Re: Reaching the Limits of Adobe Stupidity
#15I have lost faith in Adobe because they cannot get their products working on case sensitive HFS volumes. The problem has existed for almost a decade I think. The fact that one cannot install Creative Suite on another volume makes it even worse.
This may be somewhat irrelevant, but what is the motivation for having a case-sensitive HFS volume? I agree that Adobe should support it (and separate volume installation) because these are edge cases that should be accounted for, but I've never heard the reasoning for having a case-sensitive format.
Re: Reaching the Limits of Adobe Stupidity
#16I have lost faith in Adobe because they cannot get their products working on case sensitive HFS volumes. The problem has existed for almost a decade I think. The fact that one cannot install Creative Suite on another volume makes it even worse.
Slightly more sickening is that for some of their apps it can be fixed by simply renaming directories and libraries within the App bundle. I googled around for a bit a few months ago and got PS and InDesign working on a machine with Case Sensitive formatting. This sort of laziness just kill me.
One example of the tail wagging the dog: http://forums.adobe.com/message/3311504
Re: Reaching the Limits of Adobe Stupidity
#17I still like ActionScript because I like javascript, but in many cases I want to declare my types so I can get type checks at compile time instead of being surprised or having to write unit tests to be sure of myself. Also refactoring large javascript or python projects is my nightmare because getting it to 'compile' means nothing, so many bugs could be lurking still.
Re: Reaching the Limits of Adobe Stupidity
#18I have lost faith in Adobe because they cannot get their products working on case sensitive HFS volumes. The problem has existed for almost a decade I think. The fact that one cannot install Creative Suite on another volume makes it even worse.
This may be somewhat irrelevant, but what is the motivation for having a case-sensitive HFS volume? I agree that Adobe should support it (and separate volume installation) because these are edge cases that should be accounted for, but I've never heard the reasoning for having a case-sensitive format.
I presume it partially is due to POSIX. Here's an errata from MS about that: http://support.microsoft.com/kb/100625
(TLDR: NTFS itself is Case sensitive even though the Win32 API isn't because NT was/is designed for POSIX compliance)
Re: Reaching the Limits of Adobe Stupidity
#19I have lost faith in Adobe because they cannot get their products working on case sensitive HFS volumes. The problem has existed for almost a decade I think. The fact that one cannot install Creative Suite on another volume makes it even worse.
This may be somewhat irrelevant, but what is the motivation for having a case-sensitive HFS volume? I agree that Adobe should support it (and separate volume installation) because these are edge cases that should be accounted for, but I've never heard the reasoning for having a case-sensitive format.
I just always have done it because I want my mac to act like a normal UNIX system. I suppose it was kind of a principle thing.
Re: Reaching the Limits of Adobe Stupidity
#20Earlier quoted context omitted.
This may be somewhat irrelevant, but what is the motivation for having a case-sensitive HFS volume? I agree that Adobe should support it (and separate volume installation) because these are edge cases that should be accounted for, but I've never heard the reasoning for having a case-sensitive format.
I just always have done it because I want my mac to act like a normal UNIX system. I suppose it was kind of a principle thing.
This is why I do it. To make my local dev system a bit closer to my (typically linux) deployment systems.
(I remember wasting a lot of time once on a rookie mistake where I had a Perl script with "use Strict;" in it instead of "use strict;", it worked fine on Mac OS (OS9, in this case), but failed in at-the-time-inexplicable ways when deployed on unix. I suspect my habig of insisting on choosing case-sensitive filesystem stems largely from that… And yeah, doing perl/cgi webdev on Mac OS9 was a really bad idea, I discovered.)