I would really like to know other folks opinions on this point mentioned by the author: "The web will persist and the web will win."
It's not necessarily a conflict that has an end. Because web-based stuff is standards-based, you'll always have a lag between state of the art and what is available in a standard. IMO, that's a good thing -- it pressures the market to continue innovating. People at Netscape were talking about the web displacing native applications twenty years ago. That hasn't happened yet!
If you had to start over, what technologies would you learn in 2014?
151–160 of 182 posts
Re: If you had to start over, what technologies would you learn in 2014?
#152Earlier quoted context omitted.
>It's just JavaScript, JavaScript, JavaScript. No it's not. Because JavaScript the language is so bare-bones, you need to supplement language deficiencies with frameworks and libraries. So you go and pick from a menu of Backbone/Marionette, Angular, ExtJS, Ember, Kendo, jQuery or etc. - some of them work together, some of them don't. Most of those get you part of the way there, you may still need to pull in things li…
So... javascript, javascript frameworks, and javascript variants. I think "Javascript, Javascript, Javascript" was accurate enough. And Bootstrap is easy.
Unless, Dart, CoffeeScript, TypedScript etc.
Re: If you had to start over, what technologies would you learn in 2014?
#153Folks, the big point of this article is not that Hanselman likes C#, it's that his list of options does not include Objective-C or Java. It's that he thinks that the web will win (over app stores). I strongly believe that he's right there. At some point, app stores had "discoverability" as an advantage over the web. This has been one of the strongholds of native app proponents. These days however, with the enormous a…
I agree, but not for the technical reasons most people are mentioning so far.
I think there is a much simpler driving force: mobile app stores have set both the quality bar and pricing expectations so low that it's almost impossible to develop good, non-trivial software for them and make money.
On top of that, the app store platforms tend to want a big cut and/or restrict the use of other payment models and/or want developers to jump through hoops just so users can install their application and/or require developers to build in a specific programming language that produces executables for their specific platform and/or a bunch of other obstacles that web development simply doesn't have.
Meanwhile, the only major benefit native apps have to offer in return these days is access to a few native features. Given how much success many web applications have already enjoyed, it's clear that those features aren't compelling in many of the application domains where this kind of decision is being made. It's also clear that if performance was ever really an issue for most web apps, it's an ever diminishing one and mostly irrelevant by now.
The two major business models that have made serious money from mobile apps other than in outlier cases are in-app payments and advertising, which are probably the two most widely abused and consumer-hostile payment models in widespread use today. I suspect mobile apps in their current form were already dead as a serious software platform as soon as people were selling $1 gimmick applications and $5 puzzle games in app stores. The industry just hasn't quite realised yet because there's still too much hype from the (mostly now over) gold rush, but fortunately we have high quality and great value apps like Dungeon Keeper at the top of the promotions screens to show us just how good mobile apps can be if you want to make real money from them.
Meanwhile, as numerous HN regulars can attest, plenty of B2B web apps are making money like it grows on trees, and plenty more people are making a decent amount of money with other B2C business models that simply aren't compatible with today's mobile app world but work fine on the web.
Re: If you had to start over, what technologies would you learn in 2014?
#154Earlier quoted context omitted.
What makes you so sure Cordova is the future? Curious.
Code once, run everywhere. Discoverable, searchable, updatable, all the good qualities of a web app with the power and speed of a native app. Of course you need HTML, JS, CSS and the whole web stack, but the good thing is everybody already knows it. Standards are good. Apache is behind it, also Google, Firefox, Ubuntu, everybody benefits from a standard way of developing apps once, but very specially users, and coder…
"everybody benefits from a standard way of developing apps once ... and coders" - my feeling is that it's 50% of HN spirit is building things in different ways. Just look at all those awesome languages, libraries and frameworks coming out every week!
Re: If you had to start over, what technologies would you learn in 2014?
#155Earlier quoted context omitted.
Depends on your definition of inferior. I can count the number of desktop apps that I use on a daily basis on one hand, and they're all development tools. I have more than twice that number of pinned tabs in my browser that are open at all times.
Are those pinned tabs all running applications or merely displaying information (websites)? Are you sure the ones running apps would not run better were they written as a native/desktop version? Are the apps trivial (e.g. to-do lists)? There's a lot of context you left out.
Gmail - email client
Mog - Music player
Google Voice / MightyText - Messaging
TweetDeck - Twitter client
Confluence - Team wiki
Trello - Organizational tool
Toggl - Time tracking
Bitbucket/Github (I suppose you could debate that these are just websites)
Google Drive - Document editing and storage
Would these run better as native apps? Probably, if you're just talking about raw performance. However, I frequently jump between OSX, Windows, and Linux machines. When I open Chrome on any of these devices I can pick up right where I left off. Could I say the same with a native app? Probably not. For me, the performance of the web version of these apps is good enough, so cross platform compatibility becomes more important than raw power. That's what I meant when I said it depends on your definition of inferior.
I don't think mobile hardware or mobile browsers are quite there yet. But I don't see any reason why they won't eventually get to a point where they're "good enough" for people like myself, at which point other factors beyond raw performance will become more important.
Re: If you had to start over, what technologies would you learn in 2014?
#156SAP. It's not particularly exotic but it runs the world.
You mean ABAP ;) Actually SAP is at a very interesting crossroad right now. You don't have to know ABAP anymore. If you can leverage SAP Gateway and check out OpenUI5 - http://sap.github.io/openui5/ you can make a name for yourself. There is heavy demand for this area right now and not enough supply. EDIT- If anyone is interested in this area, let me know!
Re: If you had to start over, what technologies would you learn in 2014?
#157Earlier quoted context omitted.
If the point is to easily be able to find work (which was the parent's emphasis), then yes, you need to learn the popular frameworks. No, it's not required for building your own web app, but companies use them, so they'll expect you to be familiar with them.
Where are you based? It seems like in most places it's an employee's market right now (assuming you work for an employer). Given the diversity of front-end frameworks and how new most of the trendy ones are, I find it extremely hard to believe that anyone who's any good at front-end development and has a decent track record to prove it will be short of work any time soon, even if they don't have a full complement of…
Re: If you had to start over, what technologies would you learn in 2014?
#158If you're looking to maximize your choice of companies to work at, one piece of advice could be to focus on front-end instead of back-end. I'm equally proficient at front-end and back-end, but the last time I did a whole bunch of interviews, I advertised myself as a front-end programmer (since there aren't too many full-stack positions around). Why? As a back-end developer, you're limited to picking companies that ma…
most boss think front-end programmer as code monkeys, and back-end guys as architects. Good luck.
Re: If you had to start over, what technologies would you learn in 2014?
#159Earlier quoted context omitted.
Where are you based? It seems like in most places it's an employee's market right now (assuming you work for an employer). Given the diversity of front-end frameworks and how new most of the trendy ones are, I find it extremely hard to believe that anyone who's any good at front-end development and has a decent track record to prove it will be short of work any time soon, even if they don't have a full complement of…
Portland, OR. I think you're probably mostly right with regards to frontend development. All my experience applying for non-contract work has been for backend positions, and I know for a fact that I lost at least two potential jobs because I didn't have the right language/framework on my résumé. But just based on my limited searching for frontend positions, it seems like companies do expect you to know at least one w…
I certainly agree with that. I'd expect anyone claiming significant front-end development skills to at least be familiar with ideas like MVC and data binding these days. I just wouldn't much care which specific tools they used to implement those things, and I wouldn't hold it against them if they'd considered their options and then chosen different designs and/or tools instead.