Codekit 2 is out
incident57.com
incident57.com
I actually can't believe what I am reading atm, has this industry really gotten to a point where nobody has a sense of humor or any congratulatory comments anymore? And everyone is force to pick apart every single thing?
Combined with the other population who don't like to see tools and projects that let "lowly" developers accomplish the same things they worked so hard to do the manual/complicated way, and you get this thread so far..
Such is life...
Oh and he's built an awesome product that makes my life so much easier... and he doesn't demand I pay the earth for it. #win
I LOVE the sense of humor in the testimonials section... LULz
My one concern is does CK 2.0 create standard config files for Bower, Grunt, etc... CK 1.0 did NOT do this and made collaborating with non Mac / non CK users difficult!
Compare Maven / Ant / Gradle for the Java world, instead of builds configured in the IDE; said IDE's often have a GUI component for major build configuration files.
I wouldn't mind a GUI for Grunt configs, without sensible code refactoring, those can be a bitch to maintain.
Maybe a little more configuration necessary though.
GruntJS and Gulp essentially do the same thing of course, but CodeKit I guess 'interfaces' all those text-based configurations and once it's configured, well, it's pretty much done and you can just let it run in the background and forget about it.
Highly recommend it!
Looks cool otherwise though...
The testimonials give the whola page a somewhat human touch. I - for one - am now pondering if there really is a story behind the "Mad at me since 2008" stuff about Apple's legal department :P
I'm guessing the app is being marketed towards hipster frontend devs.
Stuff like "Make Panic Jealous" target a really specific group of users (ye-olde average user doesn't know who/what Panic is) but really add flavour to his companies image.
Of course, to each his own. I don't like the writing style in Romeo and Juliet; does that make me a hater of the arts?
I remember the days when I thought tools like this were cool. Like Coda for example.
CLI tools don't need to parody themselves, they're usually free, cross platform and I can retire them quickly because I don't feel overtly attached to them.
- 2min and 54secondes of demo video to explain the localhost address. Sooo, boring.
- At first, it sounded like another text editor but it's not.
- It seems that's just a GUI skin to CLI toolsIn the same time, Dropbox is more towards less savvy user and when you use Dropbox is more for the Cloud hosting than for its rsync capabilities.
To me, they are not in the same league…
Is it really so hard to open a command window and run a single command?
"Effort vs. Result" is an important metric, and Codekit lets you just "get it done" without needing to learn how to install and set up grunt or gulp, node (edit: and uglify-js, bower, image optimization tools, sass, less, stylus, compass, etc).. It just works.
And when Codekit becomes no longer appropriate then one can spend the time required to learn and configure grunt/gulp.
1. Install Node
2. Figure out how to use npm and package.json
3. Install the Grunt cli.
4. Install local Grunt.
5. Figure out exactly which Grunt plugins you need and install those.
6. Create the basic scaffolding of your Gruntfile, hoping that the references you use aren't outdated.
7. Figure out exactly which options each of your Grunt plugins need.
8. Do some debugging when you got something wrong in one (or more) of the steps above. Problem is, since this is your first time setting it up, you don't know which step you got wrong.
For someone unfamiliar with the Node & Grunt ecosystems, this could easily be a multi-day project. If you're simply putting out some static brochureware sites, then it might make a lot more sense to just pay for a GUI tool to handle a lot of this stuff for you.
Sure it wouldn't take days to set up, but for someone who has never done it before, it will absolutely take more than 5-10 minutes to correctly set up and test node with grunt/gulp (and all the other tools you might need: less, sass, compass, uglify-js, bower, etc) to replace the various worklows that Codekit provides easily and painlessly.
Again I am not saying there's anything wrong with grunt/gulp, but as I said, "effort vs. result" is an important metric, and if a tool like Codekit gets me the same results faster and easier than spending time learning how to install and configure grunt/gulp and all the tools they automate, then that's a win for me.
To each their own though..
But I assure you that there's definitely a market for tools like this.
Did they really have to resort to a level that low?
This crap doesn’t even start. Sent it straight to the trash.