A few thoughts: - 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 tools
[deleted]
Codekit 2 is out
11–20 of 56 posts
Re: Codekit 2 is out
#12The best thing on the page was the face palm user image.
Re: Codekit 2 is out
#13Reading the testimonies made me wonder if this whole thing was a joke or not. Looks cool otherwise though...
Are you kidding me? 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 had the opposite impression. My initial reaction was "how immature and technological incompetent are your users?".
I'm guessing the app is being marketed towards hipster frontend devs.
Re: Codekit 2 is out
#14I like what I'm seeing, however the main gripe I have is that it doesn't seem to be cross-platform; it looks like it's a GUI for Grunt configuration (it seems to have similar options) though.
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.
Re: Codekit 2 is out
#15A bit frustration that it is a paid upgrade for Codekit 1.0 users - doesn't seem like that much has been changed, and it's not as if the first version saw a ton of updates.
Re: Codekit 2 is out
#16"A Mac App for Cool People" Did they really have to resort to a level that low?
Seriously. An embarrassingly bad slogan.
Re: Codekit 2 is out
#17This URL crashes Chrome on iOS.
Re: Codekit 2 is out
#18“You don’t have permission to save the file ‘CodeKit’ to the folder ‘Library’.”
This crap doesn’t even start. Sent it straight to the trash.
Re: Codekit 2 is out
#19Another solution to the 'elephant in the room' - that frontend workflows have become too complicated for frontend developers.
Re: Codekit 2 is out
#20I really don't see the value of having the compile toolchain in your editor. If you are making a serious front-end project, you will have created a gulp/grunt based workflow so that anyone with node installed can compile it. If you rely on Codekit's features, surely you're locking people into that editor?
Is it really so hard to open a command window and run a single command?