4 ms·
The Web IS a platform. The things TFA is talking about, angular.js, Play, etc., are just tools / libraries. The platform is TCP, HTTP, HTML, CSS, Javascript,
by mindcrime 14y ago
The Web IS a platform. The things TFA is talking about, angular.js, Play, etc., are just tools / libraries. The platform is TCP, HTTP, HTML, CSS, Javascript, etc. And what makes it beautiful is that you can build anything you want on top of that platform, without worrying about what Google or Apple or Microsoft or IBM or $WHOEVER thinks.
Curation? Beautiful app-stores? Feh. I'll pass on both if it means giving up the freedom to build anything I can imagine, which is what you get with the general "web as a platform".
Never mind nobody is forcing you to "play keep up" and constantly use the very latest and trendiest tools all the time. I haven't even touched Angular.js, nor do I have any overriding desire to do so anytime soon. Same for Ember.js and any number of other libraries. I'm sure they're cool, but I'm too busy building stuff to spend all my time evaluating libraries. But it's neat to know that they are there, and one day down the road, if I start to feel the right kind of pain, maybe I look at pulling in one of those (or whatever the "library du jour" is at the time).
- alttab 14y ago"I wish there was one straight-forward way to build awesome applications on the web like there is with mobile development. I want someone to hold my hand the whole time." On the internet, you keep 100% of the revenue you bring in. On the internet, you do 100% of the work, too.
- ebbv 14y agoWhile you're right about 100% of the revenue (minus Paypal, Visa/Mastercard, etc.) I disagree you do 100% of the work when compared to iOS/Android development. I actually love the tools we have available to us in webdev, and think it's actually quite a lot easier than native development for mobile platforms. It's so much easier to debug and work on a web app in real time in Chrome dev tools than it is to fire up the iPhone/Android simulator apps.
- rimantas 14y ago> "quite a lot easier than native development for mobile > platforms" I am going to bet that anyone claiming things like this did not ever half-heartedly attempted to look into native development and has no idea how much native frameworks have to offer.
- ebbv 14y agoYou'd be wrong. I have done quite a bit. They have a lot to offer, but I think web development is easier and faster.
- alttab 14y agoStill, you need to be way more qualified to build a successful SaaS or anything interesting on the internet. To build an iPhone app all you need is an Objective-C book, a mac, and $100.
- drawkbox 14y agoI agree, the plethora of platforms is a feature not a problem. The problem is when there is only one there is no innovation. The web is very healthy on innovation and iteration on how to do things better. In the end you build systems and products that work, using the best tools at the time, which isn't always the latest but sometimes is.
- 6ren 14y agoIt's striking how often new web libraries come along. Are they genuinely better?
- bjt 14y agoVery often yes, when you consider that the "better" question is not one-dimensional. Rails and Django are good at building traditional web apps where the logic and data live on the server. They have less to offer on the client side, where JS frameworks like Backbone, Angular, and Ember crop up. They also don't do async well out of the box, which you want if you're going to do streaming updates in real time. So node.js, EventMachine, and Gevent come along to solve that problem. There are some very young frameworks (Meteor, Derby) trying to solve all the above problems at once. I haven't used them, but my impression is that they're not really there yet. I think the underlying pain point from the article is that iOS and Android have the luxury of being able to iterate on the whole stack at the same time, which means they can move way more quickly than web standards, which can take years of argument and refinement, with disparate implementations in different browsers, which then get papered over in various ways by different client side libraries.
- TelmoMenezes 14y agoYes! Let's be honest here. If you had to chose between the web being gone forever and iOS+Android+whatever being gone forever, which would you chose?
- rimantas 14y agoIf you want to be honest you should rephrase your question and use "all native apps on all platforms" instead of "iOS+Android+whatever". And then you would understand, that question makes no sense.
- robmclarty 14y agoCompletely agree. The beauty of the web is it's plethora of choice (i.e., freedom). You decide what you want to make and how you want to make it. And nobody can stop you from doing it, or lock you down, or deny your request. You don't have to know every single tool to do good work either. But I feel a lot more comfortable on the web platform, knowing there is likely a solution to any problem I might encounter, than struggling to shoe-horn a single language/framework because that's simply all the platform-du-jour can support.
- rimantas 14y ago> "than struggling to shoe-horn a single language/framework > because that's simply all the platform-du-jour > can support." And in reality you just trying to poorly reimplement the stuff that platform-du-jour with decades of refinement has to offer. I don't want even to imagine what amount of effort is needed to replicate everyday stuff like Core Data + UITableViewController + UIFetchedResultsController and to make it even remotely performant.