4 ms·
This is my feeling, too. I do iOS development for living and whenever I have to do some web programming, I feel like writing in assembly, having to micro-manage
by zoul 14y ago
This is my feeling, too. I do iOS development for living and whenever I have to do some web programming, I feel like writing in assembly, having to micro-manage things I should not care about.
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.
- erikpukinskis 14y ago> whenever I have to do some web programming, I feel like writing in assembly, having to micro-manage things I should not care about. 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.