4 ms·
I had a conversation with my wife, who's training to do front end development, just this morning. Our product is going to have Javascript. It's going to have JQ
by virmundi 10y ago
I had a conversation with my wife, who's training to do front end development, just this morning. Our product is going to have Javascript. It's going to have JQuery. After that, probably not too much. I explained to her the difference between an app and a web site (we're making a web site). There is only one app-like section. Even that is vanilla JS.
All that said, I told her to pay attention in the Udacity backbone class. General framework knowledge should let her generalize using JS.
- troncheadle 10y ago> I explained to her the difference between an app and a web site (we're making a web site) What did you say here? I've been thinking a lot about this lately -- In my opinion, a websites are a part of an 'app': the client.
- Spivak 10y agoFor me the distinction is what the JS is used for. * If you use FE JS to implement any of your sites functionality then you have an app. * If you only use FE JS for just presentation logic then you have a website.
- virmundi 10y agoI used an example. An app, that she's familiar with, is Gmail. I said our product is not a desktop application, like Outlook, but for the web. What we're going to do is mostly display static content, refresh the screen on navigation circa 2002, etc. So there are some parts where we need dynamicity, like our menu builder, but for the most part we don't need anything complex. As a result JQuery is fine.
- pault 10y agoWhen I have to explain my job to non-technical people I usually say I build apps "like gmail" not websites "like blogs and company websites"