Adobe CSS privacy statement

dfs

macrumors 6502
Original poster
Sep 17, 2008
330
153
California
Hey gang, have any of you ever happened to read the lengthy and complex Adobe Creative Suite privacy statement (start at athttps://www.adobe.com/privacy.html and follow the popcorn trail)? At least if I'm understanding it correctly it's one of the most evil and outrageous documents I've ever read. It seems to boil down to "Adobe reserves the right to do whatever it damn well wants with your data whenever it damn well wants," with its subtext being "the huge amount we charge for a subscription isn't enough to satisfy our greed, so we've cooked up a way to make an even more indecent profit from your membership by selling your data to all comers (North Koreans not excluded), and if you imagine you have any right to privacy we think that's just plain humorous."

Which is why I (I only need Dreamweaver for my work) refuse to move on from the latest version I could purchase for a single once-and-for-all payment (even if DW6 does have a rogues' gallery of bugs that had been around for several versions that Adobe never bothered to fix). There's no way in hell I'm getting involved in a Web-based subscription service that allows me to use a bunch of software and other resources for which I have no need, at the same time forfeiting a large chunk of my privacy rights.

I realize that this is 32-bit software that won't run on the next Mac OS upgrade, but I can see a couple of workarounds (such as running Mojave on an emulator such as Parallels, or running my current version of DW on an older Mac and accessing it via a combination of Target Display Mode and Screen Sharing. But I'm never going to let these clowns get their hands on another dime of my hard-earned. I've paid for DW once and that's enough.

Or am completely misreading this thing?
 
Last edited:

DarthVader!

macrumors regular
Oct 3, 2013
134
75
least if I'm understanding it correctly it's one of the most evil and outrageous documents I've ever read. It seems to boil down to "Adobe reserves the right to do whatever it damn well wants with your data whenever it damn well wants,"
That doesn't seem any different then what google has.

If you don't want to abide by it, then find another app ¯\_(ツ)_/¯
 

dfs

macrumors 6502
Original poster
Sep 17, 2008
330
153
California
That's the essence of the problem, Darth. For Dreamweaver, and probably some other components of the CSS system as well, there simply ain't no other app. At least sticking to the Mac platform, if you want to do sophisticated Website development, it's Dreamweaver or nothing. So your response deserves to be filed in the "Let Them Eat Cake" category.

Saying "that doesn't seem any different than what Google has" is about as lame an excuse as saying "that guy doesn't seem any more evil than Vlad the Impaler."
 

ruka.snow

macrumors 6502
Jun 6, 2017
422
1,055
That's the essence of the problem, Darth. For Dreamweaver, and probably some other components of the CSS system as well, there simply ain't no other app. At least sticking to the Mac platform, if you want to do sophisticated Website development, it's Dreamweaver or nothing. So your response deserves to be filed in the "Let Them Eat Cake" category.

Saying "that doesn't seem any different than what Google has" is about as lame an excuse as saying "that guy doesn't seem any more evil than Vlad the Impaler."
Dreamweaver is a special kind of evil, but it you have to use something like it perhaps try Espresso which has a pretty excellent CSS editor built in. And of course you can use pretty much any text editor to do what Dreamweaver does.
 

Tech198

macrumors G5
Mar 21, 2011
14,824
1,898
Australia, Perth
That doesn't seem any different then what google has.

If you don't want to abide by it, then find another app ¯\_(ツ)_/¯

Perhaps, but if i had a choice: Adobe or Google... it would probably be Adobe.. because Google announces their business model up front in the way of 'free' services and advertising....

In fact, I wouldn't you any CC service today, but its flexible.. in how many devices you can use.. Plus, I wouldn't really say its Adobe's fault.... or anyone but the 'user' since you did give up and you are trusting them... So, they have every right to do what they want... even if it sometimes seems a bit shady...

Seems to me, that's where all business seem to go now-a-days, and its becoming more and more,, you gotta keep info yourself and tell companies fake info, if you wish to stay alive in *this* game.

Not saying they are bad, but users should also not blindingly trust any company, but that's what they are doing, thinking someone else will be 100% trustworthy....

The good think about CC is products are always kept up to date, and user can 'use and forget it'
 
Last edited:

InuNacho

macrumors 65816
Apr 24, 2008
1,469
640
In that one place
The good think about CC is products are always kept up to date, and user can 'use and forget it'
Hah, thats a good one. Back when I needed the "Cloud" for a project for a few months, I had a hell of a time actually getting work done when I updated from one version of the cloud to another. My Thinkpad X220's HD3000 was no longer supported under LR, Photoshop decided to start flickering for no reason, and Premiere just decided it was time to not launch.
As far as I know, most production houses that use Premiere use older versions of the software anyways as Adobe is more than happy to release buggy software.
 

jtara

macrumors 68000
Mar 23, 2009
1,957
509
Can somebody explain what (if anything) this has to do with CSS? (Or was that just a slip of the keyboard?)

I read the headline and I'm like: "All your CSS are belong to us".

Really?

As far as Dreamweaver. People still use that? I can never stop apologizing. I am partly responsible.

I rue the day I went to my boss in 1995 (at Mediashare Corporation, which was started by some people from Compton's New Media, and which later got renamed to Elemental Software, which got bought by Macromedia, which got bought by Adobe) and suggested that our catalog-publishing product could just as easily produce HTML as it did PDF for print or Director for CD-ROM from the goofy object-oriented database we used, by writing some different templates, and maybe somebody might want to publish catalogs on this here new WWW thing that I'd been experimenting with at home.

He gave me approval to spend a few weeks on it, and to set up a web server (under my desk, on our office network, connected to the T-1 line...) to demo. It worked. We did web catalogs for 3M, 3Com ("the threes") - for whom we'd already done CD-ROM/print catalogs, and Tesco (for which we hadn't). It was static publishing, like the print/CD forms, so really one of the first static site generators, if not the first.

Then some monkeys got in there are staring mucking with it and made it create awful inline Javascript, and started turning it into a more general-purpose web authoring tool. I wasn't able to stop that nonsense. And that eventually became the basis for DreamWeaver.

I think I have something like .007 shares of Adobe. What should I do with it?

What I am most sorry for is the awful inline Javascript. (I hope that's long gone?) But I swear that wasn't me! I just was not able to get across what a Bad Idea that was.
 
Last edited:
  • Like
Reactions: DRDR
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.