|
Greetings Lord David of Dalek,
My condolences on the passage of Ann B. Davis, but, you can take heart that your soul-brother, Chucky, is still going strong, and will, evidently, make another star-turn in the cinema in the near future: [^].
cheers, Bill
“I'm an artist: it's self evident that word implies looking for something all the time without ever finding it in full. It is the opposite of saying : ‘I know all about it. I've already found it.’
As far as I'm concerned, the word means: ‘I am looking. I am hunting for it. I am deeply involved.’” Vincent Van Gogh
|
|
|
|
|
Dalek Dave wrote:
Another bit of my childhood has gone.
Bit by bit, I remember her more from "The Bob Cummings Show".
R.I.P. Ann
If first you don't succeed, hide all evidence you ever tried!
|
|
|
|
|
Then you are really really old.
Like me.
|
|
|
|
|
GenJerDan wrote: Then you are really really old.
Like a fine wine! 
If first you don't succeed, hide all evidence you ever tried!
|
|
|
|
|
I've always avoided JavaScript programming like the plague as I find JavaScript to be a mess.
But I slowly realize that it's here to stay and that I need to get a clue about it.
The post below made me wonder not so much when to use which library, but rather when NOT to use a certain library.
I understand that JQuery is basically aimed at DOM manipulation, and Knockout is meant as a complement for doing MVVM binding, and AngularJS is trying to do both at the same time and is actually containing a subset of JQuery.
But there are plenty more JavaScript Libraries around, and I'm wondering not just when to use which but rather when NOT to use a certain library.
Discuss!
|
|
|
|
|
I DO JavaScript for over 10 years, started with plain (and messy) and go on with libraries (some of them home made). I think that the base is a deep and right understanding of JavaScript - including its flaws! Without that you will end up in Q&A asking stupid questions  ...
AS there are thousands of JavaScript libraries out there you can lost yourself easily. My advice is to go with the 'big' ones (not physically big but one with a big history/community).
As you have to understand JavaScript, you have to understand the library of your choice. Do not use JavaScript libraries based on copy-paste learning!
IMHO jQuery (directly or indirectly) is a must have for any serious JavaScript development and I do use it in every project I do (I even rewrote my libraries as jQuery extensions). Form there I chose according the project I do...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Dammit, that wasn't the answer I wanted. 
So what you're saying is that I need to read up on JavaScript as such, and JQuery in any case, no matter what library we end up using.
|
|
|
|
|
Learn JavaScript isn't optional! However jQuery can be exchanged with a lot of libraries or plain JavaScript too. I use jQuery for DOM traversing and even binding mostly as it simplifies that part very much...Also jQuery 'has my back' in a lot of ways (mature/community/extensible)...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: Learn JavaScript isn't optional
Never thought so, just want to avoid learning libraries unnecessarily.
I'm not one of those that finds everything new to be the best, on the contrary, I'm a late adopter.
|
|
|
|
|
Jörgen Andersson wrote: want to avoid learning libraries
IMHO you have to perfect your usage of the library, but also have to have a certain level of understanding of how the library works...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
We're on the same boat. Semi useful link - Clickety[^]
|
|
|
|
|
First thing I did, google for a comparison. 175 "Notes" and it does not mention Knockout at all. AAAAaaaaaahhhhhh
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
thatraja wrote: Semi useful link
Let me oppose you - these kind of list are totally useless...
When searching for JavaScript library use the same ideas that you use when you need something to nail a nail. You are looking for a hammer and not for a shoe with heels, but when the hammer is found you do not look further...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
|
Why would you bring a nail gun to a train wreck?
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
I didn't get any better all-in-one list. I should have mentioned there "little little .... bit" instead of "semi".
|
|
|
|
|
Some times I need a toffee hammer, but still end up grabbing a sledge hammer.
Javascript Libraries are the same thing!
My concern is often more, which ones can we trust!
When I look at NPM I find there is so much 'stuff' that I don't know what is good or bad in terms of design/functionality/security etc. I also get the same feeling sometimes with NuGet.
|
|
|
|
|
Same as in any environment, use a library when it makes your life easier and don't where it doesn't. Because of the flexibility of out-of-the-box JS I've always found that libraries are over-rated, apart from for fancy UI stuff which takes a long time to hand craft (so I've used jQueryUI in the past and it seems good).
|
|
|
|
|
The best way to decide when to use (or not) a library is when you have a definite project in mind.
When you have a good idea of what you are building, then you look for libraries and/or frameworks that may help you.
JQuery can be helpful just because it makes the code less verbose and offers nice, shorthand ways of achieving DOM manipulation - but I think it's better to be confident enough with the native JS before using this sort of shortcut.
I've found that (generally) when you are looking for a specific solution, it will come down to a choice between native and one or two libraries; I then tend to look at the couple of libraries and choose one and use it for the project I'm working on.
For example, if I'm writing a web app that is mainly displaying data with not much user input (say some sort of shop front) then the choice of libraries will be different to those I may choose if I am writing an enterprise application with many pages and database updates.
|
|
|
|
|
Interesting, a private group is attempting to reuse an old space probe. here[^]
Here today gone to Maui...
|
|
|
|
|
|
Article: Meeting these deadlines is pivotal, because the spacecraft won't return for another 30 to 40 years, team members say.
I hope the first thing they do is hire someone to do the calculations. 
A ten year approximation is a little vague.
Once you lose your pride the rest is easy.
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am.
JimmyRopes
|
|
|
|
|
They out sourced the math?
Here today gone to Maui...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
