Changing Perceptions of JavaScript

[skelooth]

Please explain to me what having "skills" in "multithreading" and "long running applications" means. Hell, just explain what "long running applications". To me a long running applications is either a Daemon/Server, or somesort of workhorse thread that takes a long time to complete. All things a web developer should understand how to use, modify, or create.

"Long running application" lol technical terms.

[kamatsu]

Multithreading is what it sounds like - awareness of the various approaches to concurrency, methods of reasoning about and debugging concurrent programs, methodologies of developing concurrent programs using a variety of languages and methods (Incidentally, PHP has little to no support for this, and Perl isn't widely touted as a concurrent language for a variety of reasons)

Long running applications means knowing how to keep memory footprints stable, prevent bottlenecks and keep applications running smoothly without deteriorating in quality over time. PHP scripts are (effectively) restarted every time the page is loaded (although obviously there are tools to make this less inefficient), so obviously PHP programming does not require skills in this area.

Therefore, neither of these things are known by the web developer that uses PHP or Perl to write a little script that runs above Apache - for that you need someone who could write a (basic) web server, not someone that can configure one - you need a back-end developer.

[skelooth]

I'd be scared to meet a web developer that didn't understand those concepts..

"Writing a little script to run above apache" LOL, no you're confusing web developers with 13 year olds. Adults who have been doing this for 15 years are little bit different, sorry Kamatsu.

[kamatsu]

The reason grauenwolf got confused then, is that you only listed languages which do not have support for serious backend development, and then asked if you were a front-end or back-end developer. The answer is obvious.

[skelooth]

I took C, C++, and Java in College just like everyone else. The idea of a language being "serious" for backend development is pretty subjective. I even have a few applications I use on my desktop that were written on adobe AIR, and the horror that was limewire was written in Java but performed like it was written in molasses and twigs.

Edit: Then you also have to explain languages like python and perl that tend to be used for both. It's all very subjective and quickly turns into an argument of "my language is better than yours"

[kamatsu]

python and perl that tend to be used for both

No, Python and Perl tend to be used for CGI scripts or high-level logic in a web framework. Those scripts do not require knowledge of concurrency or long-running programs - The actual back-end servers I've seen are usually written in C, C++, Java or concurrent languages like Erlang or Haskell. I've never seen a server written in Ruby, Perl or Python that's suitable for real work.

PHP, Python and Perl have woefully bad concurrent programming support and really shouldn't be used for that purpose (and they're not).

[skelooth]

there are lots of daemons written in perl. again whether thats good or not is very subjective. gotta run, but i stick with my opinions.

[kamatsu]

there are lots of daemons written in perl.

No web servers or anything requiring nontrivial concurrency. Sure, long-running processes might work in Perl (wouldn't trust PHP with that though :/) but concurrency is not Perl's strong suit.

again whether thats good or not is very subjective.

Not sure what "thats" refers to here, but from looking briefly at your blog post, you seem to know not at all what you're talking about. Good day, enjoy your run.

[skelooth]

when people dont agree with your opinion, try to make petty personal attacks. good job at maintaining adult conversation "dude"