1 |
Apparently, though unproven, at 14:36 on Sunday 02 January 2011, Lubos Kolouch |
2 |
did opine thusly: |
3 |
|
4 |
> Indexer, Sun, 02 Jan 2011 10:47:46 +1030: |
5 |
> > -----BEGIN PGP SIGNED MESSAGE----- |
6 |
> > Hash: SHA1 |
7 |
> > |
8 |
> > On 02/01/2011, at 09:04, Grant wrote: |
9 |
> >> I'm sorry this is OT but I really value the opinion of many people |
10 |
> >> subscribed to this list. |
11 |
> >> |
12 |
> >> I'm starting a new project that is quite straightforward and will |
13 |
> >> interface with an old project. The only point of contact between the |
14 |
> >> two projects might be both of them having access to the same database |
15 |
> >> table. The old project is written in a language that is related to |
16 |
> >> perl so I can imagine there would be some benefit to using perl for the |
17 |
> >> new project. Am I foolish to start a new project in perl at this stage |
18 |
> >> in its lifecycle? I won't be doing the coding myself and I wonder if I |
19 |
> >> would be better off with PHP since more coders seem to be familiar with |
20 |
> >> PHP than perl. |
21 |
> > |
22 |
> > TBH use neither, most people are jumping away from PHP and Perl. |
23 |
> |
24 |
> I am not sure who is "most people" but I do almost all my coding in Perl |
25 |
> and love it. Perl has great features and is very cleverly designed |
26 |
> language! |
27 |
> |
28 |
> Lubos |
29 |
|
30 |
"Most people" is usually something like "someone who's blog I read and my two |
31 |
friends". In other words, not even close to a mass migration away. |
32 |
|
33 |
Perl has one of the healthiest code ecosystems ever. It's not going away |
34 |
anytime soon. |
35 |
|
36 |
|
37 |
-- |
38 |
alan dot mckinnon at gmail dot com |