Randy's probably right about how silly all the tiny reinventions of UI frameworks are. And, though I'm generally unsympathetic to claims that a project is a failure because people don't want to learn the tools, I think it's safe to say here that asking people to use a language that's only marginally less horrible than JavaScript is not going to be a win from any perspective.
But he fails to realize that doing UI in a Cocoa-like framework is totally fucked (to be clear, I do Cocoa touch for a living; I'm speaking from experience).
I'd be making an understatement if I said I was unexcited about Cappuccino because it fails to even approach solving any of the truly important problems of UI work, which are (as you hinted) less about "can I make the table scroll quickly" and more about "can I decouple this monstrous mess of data, dependent requests, and presentation". As you note, FRP looks like a step in the right direction toward solving that problem. Traditional Cocoa-like approaches are a step backwards in that area, not forwards.
I think he was simply pointing out the fact that we've stagnated at the same level of abstraction in the web space for a long time. Cappuccino is just the example he's using to point out where we were relative to where we are and in that light it's almost a regression.
For the purposes of his larger argument, the way that Cappuccino delivered its abstractions (Objective-J) isn't as important as what it allowed you to do with the web.
You have solutions like gwt, cappucino and extjs which build custom ui components that behave properly, ad the infrastructure to tie them together. This works, but only if you never step outside the framework, and only if you're willing to deal with bloat, which sucks. Then you have frameworks which just give you the infrastructure, not the custom ui components, like ember or backbone. That also works, but because html's core controls are horrible the only way to get a great ui out of that is to build really custom ui, essentially rebuilding what the complicated frameworks already provide out of the box, which sucks. And then you have one-shot solutions that try to bring just one or a few ui elements to the web, trying their best to fit into the raw platform. That also works, but because the raw platform is so painful to use, it doesn't scale.
Really, the problem is that html/css/js is the wrong base for building abstractions on. I have great hopes for shadow dom and web components, but that's only the beginning of what we need. The platform itself needs to evolve a great deal to make building high-quality ui something that doesn't lock you into a vendor's toolset.
Personally i chose extjs and am waiting it out until the platform matures underneath it. I'd like to see the extjs codebase evaporate as parts of it get replaced by native code, until it's nothing but syntactical sugar on top of a rich base platform. That's going to be a while though.
It pains me that Cappuccino has received so little interest, for despite all its possible drawbacks it represents a very interesting path for future web programming.
That applies in the opposite direction too. Native programming seems to involve jumping through insane hoops just to do simple things:
Like "put some text on the screen, this part is bold".
Or "open this web page".
Or "put these things next to each other, with 10px in between, unless the screen is a little narrower, then put the second one below with no margins".
Or "I want to play with the layout of this every day for the next month, have the new layout download every time someone uses this app".
I can write complete, ready-to-distribute web apps that do those things in 1-3 lines of code. Doing so in iOS takes many layers of indirection.
Look at something like Ember.js. The abstractions being put in place are fascinating. Or CSS. It's is an incredibly powerful abstraction on something that iOS just scratches the surface of.
The truth is, both the web and iOS have evolved to deal with specific pain points. Some things that are easy on one are hard on the other.
This idea that web programming is under-abstracted seems really narrow-minded to me.
Let's remember that even as recently as 2-3 years ago, top end phones and tablets were single core ARM processors clocked at ~1GHz. And devices of that spec are still in wide spread use even now.
The point of the HTML is that it's an open standard which should work on any internet device regardless of platform, patents and what not. While I admire the ambition of the guys who push the envelope of what the web can do, they often forget that everyday sites also need to cater for low end devices used by everyday folk.
The idea right now for telecoms and device manufacturers is more about getting their stuff in as many people's hands as possible, not about whether they can replace a screaming desktop with a handheld.
Let make information available to everyone; then we can worry about making those sites fancier than a strippers underwear draw.
Low end devices are a good point, my main gripe with all these frameworks is that they make it very easy to break many conventions of the web (URLs no longer work as intended, extra efforts is needed to make the pages crawlable etc.).
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? If you want a full featured enterprise SQL DB, why not just use PostgreSQL? And don't even get me started about Walyand/Mir as opposed to Xorg, or the whole debacle of disabling separate /usr because of rewriting things like init to use glib and other non-base system dependencies. The hubris, lack of knowledge of history, lack of foresight, and just plain lack of professionalism (to put it politely) are staggering.
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 Java, including using a tool that translates MIPS binaries to run under the JVM, allowing the use of libsqlite as 'native Java' code: http://nestedvm.ibex.org/
This is, however, not something you'd likely want to use unless you absolutely need to interoperate with sqlite's data format.
Fully native java and an in-memory implementation mean that we can very quickly implement it in our systems.
My objection is right here. No need to mix in the Objective-J at all.
Microsoft's ASP.NET tried to do this thing, to a surprising amount of success. The context then ofcourse was "Web 1.0" pre-Digg internet and the only other "big thing" being PHP.
Microsoft managed to take the whole "Draw a GUI in Visual Studio and it's a done app" thing and take it to the web, much like it originally defined Windows-programming with Visual Basic. It was an immense success and very cool.
Then Web 2.0 (as much as I hate that term) came and changed the game.
Then not working on the raw metal became an obstacle to making ASP.NET do all those cool things which everyone else was doing. It's killer feature (not having to know HTML) became it's Achilles Heel. It's abstractions became a hinderance to all the things you actually knew how to do once the framework got out of your way.
I may be a tad pessimistic and cynical, but I doubt a framework whose main goal is to give you a non-webby workspace will be a long term success when you're actually working on the web.
Microsoft learned that (too late?) and have tried to remedy the situation with ASP.NET MVC, but by the time that became useful, it seems lots of .NET developers went off to find cool stuff elsewhere.
A new framework like that, right now, seems like an utterly dead end.
I'm joining OP's web haters club, if he starts one.
Every time I hear a programmer condescend towards other programmers for using a higher level language, I also die a little bit inside.
How is javascript not the "metal" of the web? It's a core part of the modern web experience upon which many libraries and frameworks have been built.
I don't understand why that analogy is bad and is worthy of your condescension.
Are you just being condescending to the entire web paradigm in general?
A language interpreted at runtime, by an application that runs inside an operating system (which may or may not be virtualized) that boots into protected mode. Let me get this straight, you're ostensibly describing this as being "bare metal"?
Have you ever heard the terms "kernel mode" or "ring zero"?
Oh wait, you qualified it as "the 'metal' of the web"... so it's an "analogy". Sorry to be pedantic, but when people say "bare metal" in the context of platform virtualiztion, "bare metal" literally means just that. The executable code is compiled into binary that directly correlates to the copper wires (and etched semi-conductors, or perhaps even vacuum tubes) of the specific, real, tangible machine intended to execute the code. JavaScript is nothing like this.
Maybe the packets and datagrams of transmission protocols are the "bare metal of the web", but JavaScript most certainly is not.
Check out the Communication Systems OSI Model.
http://en.wikipedia.org/wiki/OSI_model
I'd contend that nothing above Layer 4 could be considered analogous to "bare metal".
You do realize it's been a while time since the ostensible instruction set and corresponding assembly language of most modern CPUs translated directly to the bare metal execution model of the machine. http://en.wikipedia.org/wiki/X86#Current_implementations Even on RISCier architectures, virtual memory, deep instruction pipelining, super-scaler dispatch, branch prediction, multi-layer caching, inter-core cache coherency, etc. introduce a huge amount of abstraction between the instruction you write and the actual execution on "bare metal".
On current chips, x86 machine code is as much a virtual machine as java byte-code. It's abstractions all the way down, you just pick different levels for different classes of work and "bare metal" is now just a label for one below where you landed.
I understand what you're trying to say, but this is way off base. x86 instructions may not align exactly a processor's primitive operations, but that doesn't mean abstraction makes x86 similar to the JVM, at least not anymore than it is similar to a Bible printed on papyrus. But nobody cares if ancient Hebrew is just as much a virtual machine as Java, so stfu.
"Sometimes writing markdown feels like working on the bare metalloid"
But! IN THEORY You could still construct a processor out of electromagnetic relays (springs, contacts, leads and solenoids only), if perhaps your goal was to never exceed 100 Hz.
(...at first I was going to point out http://www.bigmessowires.com but it turns out that beyond the wire wrap connections, he's still using modern semi-conductor packages)
It also brought in some clueless people who had no idea how HTTP, HTML and JS work, with questions like "why my button.hover event does not work" (this was pre-ajax, the event code was on the server and had no ways of knowing the user is hovering over the button).
Maybe it was OK for CRUD and internal applications but not for ordinary websites or sophisticated web apps.
.Net MVC is seen as a success: clean HTML, predictable things under the hood, jquery.
Eventually, yes. Which I addressed. But prior to the whole Web 2.0-thing, it was actually pretty successful by lots of means.
I'm not saying ASP.NET MVC is superior in most respects. There's no doubt about that, but it was clearly a late-started initiative which should have started much earlier. ASP.NET already had lost its respect and was a waning star by the time they got the first version out the door.
These days it's actually fairly pleasant to work with. The only thing I can say I really dislike about it is that you can still find the traces of all the old ASP.NET warts there, if you go beneath the hood.
Edit: Thanks for being the only one replying to the actual topic at hand, as opposed to doing inane discussions about what "real metal" is these days. And that's coming from someone with a degree in electrical engineering and design of digital electrical circuitry.
This style of thinking damages applications. Yeah you've made it easy to build a form with validation, but users don't need half the form fields, let alone the form itself. Also if you thought about it, you could have came up with a more innovative way to capture user data that would lead to more registrations, and thus more users.
Oracle are doing similar things these days too.
Some front-end devs are technicians that need to generate value quickly, and most can't afford investing time in a new complex system that may disappear tomorrow. If there are no clear advantages on the business side that justifies the investment, then there is no pressure to the front-end devs to do it.
Good engineering also means optimizing technical designs for the usage of the technology in order to reduce costs. That includes factoring in the skills of the technicians that are going to use the tech (and the cost of training them).
Is he saying that a product failing is the fault of customers? That's simply ridiculous.
No matter how you put it, one way or another it is ALWAYS you fault, I don't even know what it might be the problem, but it's your fault.
Web frameworks happen because people try to leverage their existing knowledge, skills or codebase in a web domain.
i.e. GWT & Vaadin are web frameworks where you use java and there is literally no need to know JS/HTML/CSS to create some really nice web apps that perform well.
I don't want to say that you don't need JS/HTML/CSS knowlede to build web app. But those frameworks allow people to be productive with almost no such skills.
Or when a change of behavior asked that is not supported by the framework out of box?
Seriously: being on your high horses and all is fine and well but your article is an oversimplification as to how the web works and as to what devs need and want.
For example lately I've been very interested in flapjax (FRP UI) and webfui (Clojure / ClojureScript with automated synchronization between the client and the server).
Functional programming and FRP UI may be the way forward. I'm not saying it is but I'm saying it may. What does Cappunico have to offer from the standpoint of determinism and reproducibility? Seen from a sufficiently distant paradigm, any web framework is the old, broken, inneficient way of doing things. Even your beloved Cappunico which you wasted so many time on.
Cappunico is a failure. It doesn't have to do with you being too intelligent and having figured out things earlier than others. It's just that there are many who devs do not want Objective-C / JavaScript and who want instead something really disruptive. As long as the one really disruptive thing doesn't come along, there shall be competition between lesser solutions (which Cappucino being one) Deal with it.