LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  March 2010

CODE4LIB March 2010

Subject:

Re: PHP bashing (was: newbie)

From:

Joe Hourcle <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 26 Mar 2010 11:48:48 -0400

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (72 lines)

On Fri, 26 Mar 2010, Doran, Michael D wrote:

>> As a first language, you want something that let's you Get Stuff Done
>> with a minimum of fuss...
>
> If you are getting started and if you are not planning on being a 
> full-time programmer, then you want to be looking at the high-level 
> languages as Mike suggests: "the strong candidates include Perl, Python, 
> arguably PHP and my own favourite, Ruby..."

Even *if* you are looking to be a full-time programmer, I'd recommend most 
people do stuff in higher-level languages.

That earlier development effort that I mentioned, the majority of their 
work is being done in C -- the system needs to go live in ~30 days, and 
they're *still* finding memory leaks (signs of poor garbage collection), 
string and integer overflows (one of the joys of strict typing), etc.

Yes, I've done a fair bit of C, and even a little assembler -- and it's 
fine, if you really, really, need the speed boost.  (and some people would 
argue that this might be a case where they *do* need it, but it'd have 
been more cost-effective to throw hardware at it, rather than a 10 person 
team for 2-3 years, even with their 100-node cluster; or better yet, wait 
to see what happens under real load, and optimize then, rather than 
building a system with no requirements, and no testing of simulated data 
flows until 2 months before launch)

I've had my share of problems in Perl, where it'd attempt to assume what I 
mean has led to problems.  (specifically, SOAP::Lite's attempt at guessing 
that a string full of numbers was an integer, not a string, and that a URL 
should be marked as such, and not a string ... once in a while, I'll hit 
one of the edge cases with braces where you have to force it as a block or 
a hash)

... but those are few and far between compared to the segfaults that I've 
gotten in trying to port their code over to a non-linux system.  (spent 
months on it, as each new version would either not fix the problem, or 
break new things ... it doesn't help they decided to write their own 
configuration and build tools because someone must've read 'recursive make 
considered harmful') ... we finally gave up and just bought new hardware 
for our caching sites, as we had a feeling that we'd have to keep going 
through these headaches every new update through the life of the mission.

... sorry, went off on a tangent again.

Anyway, the point is -- even us full-time programmers would rather be 
making new and interesting things, rather than trying to work around 
problems with our tools.  If I'm painting a room, the roller gets the job 
done fast, and I can deal with a brush for the corners and edges -- 
there's no reason to do the whole thing with a brush, and it'd just look 
like crap if I tried doing the whole thing with a roller.

Take the same approach in programming -- if you can do 90% of the work 
really fast and really well in one language, and have to do the other 10% 
in another language, it doesn't mean you need to do the *whole*thing* the 
slow way.

I believe that all of the 'higher level' languages support some form of 
linking to C code, should you need it.  (although, you don't always need 
it ... after dealing with scientists insisting that I use their libraries, 
and trying to get it compiled as an object so I could call it as a 
postgres function, I finally just gave up and hard-coded the table in 
PGPLSQL ... I'll just have to update it every few years as leap-seconds 
are added to UTC)

...crap, tangent again.

okay, back to the hell of debugging crappy code with off-by-one errors and 
race conditions due to lack of locking, and no error checking to see if 
processes completed.

-Joe

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager