4 ms·
You're putting words in my mouth. I never said PHP was bad - it's reasonably good for common use cases on the web. I'm just saying that if hypothetically lisp
by kahrkunne 10y ago
You're putting words in my mouth. I never said PHP was bad - it's reasonably good for common use cases on the web.
I'm just saying that if hypothetically lisp became super popular, it would inevitably change to fit the work flow of the mainstream. Maybe not directly (i.e. through the spec changing) but definitely indirectly, through changes in common practice, libraries etcetera, as well as the general culture of relatively CS-literate, experienced hackers surrounding it.
Of course, I'm not worried about this happening - what's happening instead is that lisp features are finding their way into other languages (a process that has been going on since the 70s).
- Annatar 10y agoI'm just saying that if hypothetically lisp became super popular, it would inevitably change to fit the work flow of the mainstream. Being a functional language designed for metaprogramming, it is expected that it be extended: just by defining a new function, one defines LISP on the fly. That's the core idea of LISP! (:-))
- Nekorosu 10y agoSorry. I've reread my answer. It was kinda offensive. I don't see anything bad in Lisp becoming good for common use (on the web or wherever else) and I don't agree with your hypothesis. Lisp would just become more diverse in terms of libraries ecosystem and community. It will keep it's spirit and a core of really experienced users.