Peter Brawley
peter.brawley at earthlink.net
Fri Jan 9 01:06:38 CST 2015
On 2015-01-08 2:52 PM, Salakhetdinov Shamil wrote:
> Hi Arthur --
>
> Thank you for the link.
>
> I'd post here two comments:
>
> 1st ("agressive"):
> ==============
>
> "Ag ibragimov • 18 days ago
>
> Web developers should stop acting like bunch of sissies and be afraid of new things. One becomes a web developer by choice - no one forces anyone to be in that. Yes, web has become a messy battlefield and one has to adapt and survive and constantly learn new things. Whining and complaining only make things worse..." (this comment is from the article ("The State of JavaScript in 2015" http://www.breck-mckye.com/blog/2014/12/the-state-of-javascript-in-2015/ ) referred by the one, which link you posted)
>
>
> 2nd:(realistic, proven by commenter's JS real-life 15 year programming experience)
> =================================================================
>
> "JAMES EDWARDS 1 January 2015 at 4:35 pm
>
> Call me old-fashioned if you like (and it would be fair comment), but …
> I’ve been programming JS for 15 years, I still don’t know what NPM is, I’d never heard of Bower until I read this article. Each new project, for me, consists of an empty page and a text-editor. The standing assumption is no libraries or external dependencies of any kind, and that changes only as and when the project requires it.
An excellent description of a sound approach.
PB
>
> ... (read more online)....
> But I think the industry would be a lot less intimidating to new coders, if they didn’t feel compelled to navigate the minefield of libraries that now exist, before they can do anything. You can build useful functionality with nothing but a text editor and a browser."
> I like both :) But I'd follow the second one.
>
> BTW, I have just got purchased a Kindle Edition of
>
> "If Hemingway Wrote JavaScript" by Angus Croll
>
> http://www.amazon.com/gp/product/1593275854
>
> and I have started to read, and I like it a lot - it shows how rich and expressive JS is.
>
> Everybody here knows what are "Closure, Memoisation, Currying, Map-Filter-Reduce" (functional) programming concepts and how and what for they can applied in JS? I must admit I'm only starting to realize the power of these concepts...
>
> And while getting through JS steep learning curve it happens "my mind tells me I will never understand Javascript, and my heart tells me I am not meant to." :) (quoted text is from "If Hemingway Wrote JavaScript" book) Thank you.
>
> -- Shamil
>
>
>
> Tue, 6 Jan 2015 15:52:38 -0500 from Arthur Fuller <fuller.artful at gmail.com>:
>> Here's a link to a provocative piece on the state of JavaScript:
>>
>> http://manuel.bernhardt.io/2014/12/30/generation-javascript/
>>
>> --
>> Arthur
>> _______________________________________________
>> dba-Tech mailing list
>> dba-Tech at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/dba-tech
>> Website: http://www.databaseadvisors.com
> _______________________________________________
> dba-Tech mailing list
> dba-Tech at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-tech
> Website: http://www.databaseadvisors.com