How about:
PHP: getting Perl and CGI to work on my web server is too damn hard.
Or perhaps:
PHP: I can never remember the difference between %, @ and $.
What languages fix
51–60 of 91 posts
Re: What languages fix
#52PHP: Perl is too hard to configure and run on the web
I don't think the historical evidence supports this. PHP was invented as a templating DSL for C programmers. I'd propose:
PHP (version 0): C is not an HTML templating language; Perl and Python are too heavyweight as embedded templating languages, given that all of our logic is in C anyway.
PHP (version N): PHP works fine, except it's missing function F.
...and so on, ad infinitum.
PHP doesn't really fit the paradigm of the original essay. It's hard to even pretend that PHP was deliberately designed as a reaction to other existing languages. Rather, PHP evolved. Hence, explanations of PHP tend to be circular: "PHP exists because PHP's design, documentation, and community were tightly focused on web publishing", or "PHP exists because it's backwards-compatible with PHP".
Re: What languages fix
#53Node: It's hard to find JavaScript coders since there is no career path for them.
Re: What languages fix
#54Javascript: Scheme is too unapproachable
Re: What languages fix
#55For Java I would suggest "Lisp is too powerful for Joe Programmer, and parentheses are scary" Java as essentially Lisp's bastard child is I think undermentioned in language history.
Java is a cleaned up version of C++. The JVM is an implementation detail, albeit an important one. The language itself though is about removing the necessity to manually manage memory, but staying within the OOP paradigm (or the OOP paradigm C++ proposed).
Re: What languages fix
#56Haxe: because nothing compiles to enough targets...
Re: What languages fix
#57Coffeescript: Javascript is too ugly.
Coffeescript: I'd rather be writing Ruby
Re: What languages fix
#58Node: It's hard to find JavaScript coders since there is no career path for them.
There is no career path for anyone who only does one thing.
Re: What languages fix
#59Coffeescript: Javascript is too ugly.
Coffeescript: I'd rather be writing Ruby
Coco: I'd rather be writing Perl-flavored Ruby.
LiveScript: I'd rather be writing Perl-flavored Ruby, with a Haskell syntax. ( http://livescript.org/ )
Re: What languages fix
#60APL: Errors increase in proportion to the amount of code typed; therefore, decrease amount of code typed while keeping expressiveness and power unchanged. Alternatively: APL: Programming should be more like math.
I noticed that the APL one seemed off as well. But I would say:
APL: Other languages are verbose and irregular.