Re:The Axis Of Eval: Why I ignore Clojure
by jacquesm on Monday September 20, 2010 @10:14AM
(#1708864)
> Where I currently work, for better or worse, the micro-development manager has forbidden the use of JavaScript libraries. The net effect has been that some developers have left/been let go and thous of us that have stayed have had to learn to roll our own.
I don't think that kind of 'NIH' is very productive in the longer term but it must be a great place to work if you're encouraged to re-invent the wheel.
Most places would try to avoid such a waste of resources. Maybe there would be a way to convince him of rolling your own company specific OS?
Re:The Axis Of Eval: Why I ignore Clojure
by shawndumas on Monday September 20, 2010 @10:57AM
(#1709031)
As we are now discussing my current employer and boss's decisions third party -- and given the accessibility and permanency of the web -- all I am comfortable saying is that, in the long run, having stronger developers that throughly know their code-base can be a huge win.
Re:The Axis Of Eval: Why I ignore Clojure
by jacquesm on Monday September 20, 2010 @11:00AM
(#1709047)
Yes, I agree, it can be. It very much depends on the circumstances though, for most companies rolling your own ORM, framework, javascript libraries, database and so on are simply not an option, they'll be hard pressed to keep up with the demands of running their business.
Great stuff can come from that though, for instance, Django.
Re:The Axis Of Eval: Why I ignore Clojure
by shawndumas on Monday September 20, 2010 @11:20AM
(#1709128)
Maybe that's why a lot of things like 20% projects, in-house text processing capabilities (troff), and PARC projects come from large, established companies.
Java-Batteries. Other people don't use Java batteries. Personally I prefer a Lisp that shows real error messages (not Java mumble mumble) and shows Lisp objects and Lisp functions in a debugger. I also prefer to have a nice Cocoa binding over a Swing binding.
Re:The Axis Of Eval: Why I ignore Clojure
by shawndumas on Monday September 20, 2010 @11:04AM
(#1709064)
Yes, Java-Batteries -- and all the cognitive dissonance that implies.
I contend that while batteries are, in the short term, a big help to the b-group it would be better for the programmers to look into whether or not they have what it takes to move into the a-group. One will never fail to learn a ton walking the hallowed halls of the a-group's code trying to figure out how that formerly black box does it's magic.
Where I currently work, for better or worse, the micro-development manager has forbidden the use of JavaScript libraries. The net effect has been that some developers have left/been let go and the ones of us that have stayed have had to learn to roll our own.
pg said it best: "Powerful libraries are a cheap way to make a new language the language du jour. (Think Rails.) They're not the critical ingredient if you're trying to make something to last; they may even hurt."
[1]: no CLOS, no Tail Call Optimization, etc...