But equally noteworthy was what Adobe didn’t announce: an upgrade to Creative Suite 6, the conventional, boxed, pay-one-time version of its bundle of software. While the company will go on selling CS6 and issuing bug fixes, anything new will be available only to Creative Cloud customers, in new “CC” versions of the apps, such as Photoshop CC. It’s at least as striking a shift as when Adobe introduced the first version of Creative Suite in 2003, thereby winding down its era of stand-alone apps.
And even though today’s news is less about technology than it is about purchasing options, it’s still big — not just for Adobe, but for the software industry, period. It’s another nail in the coffin of the whole business model of software as it existed in the pre-Internet days. Even software that isn’t a web-based service is now being priced, sold and upgraded as if it were one.
This strikes me as nuts. As in delusional. Who is going to be willing to try to do expert media work through the crappy small straw that is what US ISPs call “broadband”? I’m still trying to get a decent internet connection on a regular basis. In fact, Comcast is so crappy and unreliable, we have a backup internet connection via DSL through CenturyLink, which is even slower.
Besides, what are cloud apps going to give me that I don’t have on my own computer? Hard drives are dirt cheap. I just bought a 2TB backup drive for $170, and that was at the Apple Store, not known for its bargain basement pricing. Why would I limit my ability to do my core business activity only when a) Adobe isn’t down and b) my internet access isn’t down or choked to a crawl, as it’s wont to do.
Decisions like these make the appeal of open source apps.
(Source: TIME)
(
)
Why? I don’t know. It’s not like it’s all that unusual. Sadly. Unfortunately. I guess that’s why: because it’s not unusual. Ugh. I feel fortunate to be involved in a tech community that does much better on this score. Not perfect, but better.
If talking freely about “banging chicks” or ogling women in bikinis is somehow critical to your professional function, you may want to re-evaluate your career.
Technology is propelled forward by creative thinking and motivated individuals, not by our cavalier attitudes towards dick jokes. Curbing that behavior does not make us any worse as engineers and entrepreneurs, so you can stop with that argument right now.
And this isn’t even delving into the bottom half of the internet.
(Source: chriszf.posterous.com)
1 note
(
)
I came across a pretty interesting article over at Slashdot about a guy who actually owns donotreply.com, and how he gets all that email from people who accidentally reply to those messages. Turns out he gets quite a lot of extremely private information (especially from banks).
Yipes!
(Source: blog.mailchimp.com)
(
)
MySQL co-founder David Axmark:
“we developed things [enterprise users] asked for, stored procedures, triggers, views, stuff which databases had for decades at that point, which almost no website ever used. the alternative of course would have been to develop it for the web users which would mean lots of simple queries, faster, and … oh … nosql. so if we’d have developed that way the big rush for nosqls might never have happened. but the question is we couldn’t figure out how to make money of it, and the people who paid us money wanted different features so. but we basically developed things that our biggest group of users didn’t want…”
This is something that has been on my mind much in the past few years.
h/t Darren Mothersele
1 note
(
)
I found this post to be very interesting.
There’s a fair amount of confusion surrounding css preprocessors like Sass and less, and I think some of it has to do with the fact that there are so many different ways you can use them. I thought I’d outline the different approaches, and some of the pros/cons to them.
Jeff Croft goes through 4 different approaches to handling using LESS/SASS in a web development project, with focus on how a team can work effectively together.
In comments, some folks mention that they commit their LESS/SASS files AND their CSS, but we’ve run into problems with that approach in terms of CSS conflicts. If you commit your CSS, then your LESS/SASS-generated CSS gets merged directly, which can be major headache time.
(Source: jeffcroft.com)
Tags:
front-end development
css
sass
less
(
)
button
