Yeah they do. Having run a development team, I can venture a guess why: it's a burden maintaining team skills the lager the number of skills your project requires. And in a lot of projects, you have to include Javascript *somewhere*.
It's not so bad as it would sound though. Javascript was inspired by Scheme, and while it may not look much like Lisp it actually supports functional programming pretty well, and functional programming simplifies a lot of server-side problems.
Yeah they do. Having run a development team, I can venture a guess why: it's a burden maintaining team skills the lager the number of skills your project requires. And in a lot of projects, you have to include Javascript *somewhere*.
If the language matters, you're doing it wrong. When you know what you're doing, you're wiring in existing libraries. Every business problem has been solved somewhere. Anyone who tells you how much they love a language is bad at their job...especially if they're comparing one typed language to another. I suppose broad categories, like is it typed? do you have to manage memory? (like C), but beyond those broad considerations, a good programmers spends all day wiring in libraries...rarely writing "pure" c
Nonsense. No carpenter, for example, wants a zillion specialized screwdrivers for every damn thing. I say put #2 Philips heads on as much stuff as possible. Who wants 20T heads on some things, those weird square security bits on other things, flat heads on other things, etc.? It's preposterous.
Tools should be compatible. They don't want one set of blades for Skil, another for DeWalt, and yet another for Kobalt.
Why the fuck aren't batteries standardized anyway? Why the hell should they need to lug arou
server side JavaScript (Score:4, Insightful)
Re: (Score:5, Insightful)
Yeah they do. Having run a development team, I can venture a guess why: it's a burden maintaining team skills the lager the number of skills your project requires. And in a lot of projects, you have to include Javascript *somewhere*.
It's not so bad as it would sound though. Javascript was inspired by Scheme, and while it may not look much like Lisp it actually supports functional programming pretty well, and functional programming simplifies a lot of server-side problems.
UI code is much different than backend (Score:2)
Yeah they do. Having run a development team, I can venture a guess why: it's a burden maintaining team skills the lager the number of skills your project requires. And in a lot of projects, you have to include Javascript *somewhere*.
If the language matters, you're doing it wrong. When you know what you're doing, you're wiring in existing libraries. Every business problem has been solved somewhere. Anyone who tells you how much they love a language is bad at their job...especially if they're comparing one typed language to another. I suppose broad categories, like is it typed? do you have to manage memory? (like C), but beyond those broad considerations, a good programmers spends all day wiring in libraries...rarely writing "pure" c
Re: (Score:-1)
No other trade wants FEWER tools.
Nonsense. No carpenter, for example, wants a zillion specialized screwdrivers for every damn thing. I say put #2 Philips heads on as much stuff as possible. Who wants 20T heads on some things, those weird square security bits on other things, flat heads on other things, etc.? It's preposterous.
Tools should be compatible. They don't want one set of blades for Skil, another for DeWalt, and yet another for Kobalt.
Why the fuck aren't batteries standardized anyway? Why the hell should they need to lug arou
Re:UI code is much different than backend (Score:2)
JavaScript is a surprisingly elegant language.
No, it isn't.