3 ms·
So here is my humble opinion: I discovered Capuccino two years ago. My first reaction was "This is amazing!". I need to learn another language, framework and st
by csomar 14y ago
So here is my humble opinion: I discovered Capuccino two years ago. My first reaction was "This is amazing!". I need to learn another language, framework and stuff. But I thought that's the price I pay. There were three things that pulled me off, though.
1. It's buggy (or was buggy). I don't remember the details, but I couldn't setup few things because of bugs and the community was not there to help.
2. It's SLOW. Unless things changed now, I tried a few examples and I can't see how it can work. This was a huge turn-off.
3. I'll massively depend on it. jQuery is broke? Replace it with another library. This xxx.js library sucks? We can use another one. When using Capuccino you are locked to their framework. Is there a bug pulling you off from shipping? You are now screwed.
So my humble opinion is that Capuccino was not successful, at least by the time I tried it. The founder leaving the project is another reason why no one should have used it.
- bunkat 14y agoIt was number 2 that just turned me off right now. Went to look at some of their demo apps and was met with a loading screen for 10 seconds before anything happened. Not sure about everyone else, but I know my users are not going to stick around long enough to even see the app.
- pooriaazimi 14y agoI have a slow machine for now (2009 MBP), and Cappuccino is dog slow on it. I'd try it again in a heartbeat once I get a faster machine, but for now, it's literally (and I'm using that word right) unusable. A 30+ second delay after I save a simple interface in Xcode and the changes compiling. It's just frustrating. But if the turnaround time was less than a second, I think I would love to use something as "well-thought-out" as Cappuccino.