91–100 of 291 posts
Lets think about this from the opposite direction: Which projects on the web are the MOST successful? Facebook? Twitter? Gmail? Github? Do ANY of those giants use big, all-encompassing super libraries? NOPE
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.
Earlier quoted context omitted.
Second this; while I'm not a web dev, I do bump into it occasionally, and it pains me any time I see someone re-re-re-inventing the wheel, often badly. I don't know about Obj-J or Cappuccino, but just the OP's comments about modules had me nodding in agreement. Another related example, I recently learned of H2 ( http://www.h2database.com/html/main.html ) and I honestly had to ask myself, why is this needed? If you wa…
> Another related example, I recently learned of H2 ( http://www.h2database.com/html/main.html ) and I honestly had to ask myself, why is this needed? If you want an embedded SQL DB why not just use SQLite? SQLite is native C, H2 is Java. There are significant deployment and potential stability advantages to not using native binaries in your Java software. There have been some neat hacks to get sqlite running under J…
> The community has tossed out everything we’ve learned from the last 30 years of building applications in favor of being able to put something together quickly with complete disregard for maintainability or extendability. That's spot on. You can add in to that that all the lessons of the process of developing software have also been discarded and are slowly being re-learned. It is as if with the birth of the web the…
The web wasn't originally intended to be used to provide native like experiences and so the foundations for that just weren't there. So yes, people had to re-invent and re-discover all those desktop frameworks but this time in a javascript & html environment.
I think the obsession over desktop like frameworks in Javascript is due to the fact that there just isn't a clear winner yet and that is because the foundations required to support a clear winner just don't exist yet.
-We need the ability to scope CSS to a given section of the document. I want to be able to import someone's widget (or set of widgets) and not worry about style collisions.
-We need a better solution for storing templates (pre-compiling them into .js files or storing them in just seems awkward)
-We need a better way to bundle CSS with its resources. I.e., if I have a css file in "components/bootstrap/styles" that refers to "../img/pic.png" it is going to break when I concatenate all my CSS files into one and drop them in "/"
-We need a better module system. Yes, requirejs is good but I'd like to say I depend on "package.name.x" and not care where it comes from or who provides it. It should just get loaded for me (this has been solved for years in the Java world via OSGi).
-We need a better build system. Yes, grunt is good but I have to put in all sorts of logic to handle the above problems.
-I should be able to place custom tags in HTML and have the browser create my user-defined component for me. I.e., should find the correct template and backing javascript and construct the component.
There won't be a winner and the re-invention will continue until these foundations are put in place.
Why didn't I use it? - As a complete noob, I found it hard to start (despite having good objc knowledge) - I checked the objj github language page, and didn't saw a lot of activity - Last but not least, Atlas, a Cappuccino IDE was supposed to be released.
I tried contacting Tolmasky about where the language & IDE were headed but never got a response.
Earlier quoted context omitted.
> The web won. It fought a battle against many foes, and it came out on top. It won what , exactly? The war against Gopher for presentation of hypertext documents and information display? There's more to heaven and earth than data presentation and consumption. The examples of genuinely great web applications are few and far between, if not near non-existent. Are Google Apps really the best the web has to offer? Cappu…
There's more to heaven and earth than data presentation and consumption. I do my banking in a browser. I do my email in a browser. I manage photos in a browser. I manage relationships in a browser. I do my taxes in a browser. I order goods in a browser. I ship goods in a browser. I reserve items at the library in a browser. I watch movies in a browser. I listen to music in a browser. I push apps to my smartphone in a…
I'd be interested to hear how those tools stack up against their native (or cappuccino) counter-parts, because implicit in your argument is that all these attempts to extend the web into the application space are better (and have 'won') over traditional approaches to application development, which I can't say has been my experience, even for the 'best-in-breed' solutions such as Google Apps.
Personally, I've found the surge of interest in native development via mobile to be invigorating, since it has meant a resurgence in applications that put user experience ahead of dogma (or even cost). I can hope that this continues to carry over to the desktop and other spheres over the next 5 years.
Earlier quoted context omitted.
Something will come along and replace it when we finally pile too much on something that wasn't designed to do UI in the first place. The questions are "what" and "when" not "if".
Computers weren't originally designed to play music, video, or games. Yet, here we are.