Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Re: I know I'm not alone in this

by armstd (Friar)
on Oct 02, 2011 at 13:43 UTC ( #929148=note: print w/replies, xml ) Need Help??

in reply to I know I'm not alone in this

I've read all this before. snakes and ladders So I'm not sure what the point of this is.

I know I'm not alone in this position. I've heard it said that most perl programmers hand roll their own solutions.

Unfortunately, I do see this often. Too much ego or just ignorance in the Perl developer community. Forget Perl, too many lazy developers in general would rather creatively solve problems already solved than solve problems not yet solved, because that's really hard.

I know it's easy to just assume that EVERYONE who does so is going to come up with something which is of significantly lesser quality than the established systems. But then that is a generalisation, and sometimes it's going to be wrong... completely and totally dead wrong.

I think that's not accurate. Many times that reinvented wheel does work better. Does it matter? Not really. The old wheel was round, it turned. It was good enough. But we didn't really need to improve gas mileage, we really needed to stop using fossil fuels. Because then we would really be making progress.

So maybe the assumption is not necessarily that the new wheel will be of lesser quality, but certainly there's some amount of assumption that the reinventor of that wheel isn't really community-minded or interested in working toward the greater good.

Now when reinventor starts asking for help because the new wheel isn't working out so great, they are now attempting to drain resources from the greater good. Now we're not just ignoring the greater good and not contributing to it, we're taking people's time away from it too. So yeah, there will be some resistance there. Some of the more kind hearted will see an opportunity to recruit reinventor toward the light and working toward the greater good. Others more jaded from past experience...well. Responses will clearly be mixed.

Now when reinventor starts bashing and insulting the community for not helping fix his wheel the way he demands they do... W-T-F man.

But I digress. Again. It's all been said before.


Replies are listed 'Best First'.
Re^2: I know I'm not alone in this
by Logicus on Oct 02, 2011 at 14:36 UTC
    Unfortunately, I do see this often

    Exactly! Ask yourself, how many new PHP programmers have or will ever write a session manager? Answer: probably none of them! Why? Cause PHP has that built in from the start, they are free from that sort of low-level drudgery by design.

    If it wasn't for all the things that are lost in the transition to PHP, then it would make sense to simply use that instead. But no, PHP sucks for lots of reasons I'm sure we are all aware of and there is no point going into here.

    When it comes to Perl, we have a huge huge array of choices, most of which are not apparent to the new user, so you get what happened to me 4 years ago, and without knowing I was reinventing wheels, I reinvented them anyway, at great length of effort putting together bits of information without having a complete picture. Infact Tizag was my first port of call for answers to problems with Perl for a long time, and there is no mention there at all of Perl Monks, CPAN etc so I didn't even know they existed until I was already a long way down a certain track of development.

    Unbeknownst to me was that said track was miles away from what was being developed elsewhere. I had no idea whether what I was doing was standard or non-standard, all I knew was that I had this idea for a system that worked in a way that allowed me to build projects and reuse nearly all of my code each time. I didn't know about Time::Hires or mod_perl or any of that stuff, and it didn't seem to matter because the code was not noticeably slow. Infact it takes a forking parallel stress script firing 16 simultaneous requests at my tiny little 256mb dev server to significantly slow it down, a result I would of been quite happy with not so long ago (before I found Plack/PSGI)

    The point is that it is all too easy get on a big high horse about code style while neglecting to take a real hard look at what the code actually does.

    From my perspective, having used said code for a number of years, I can freely admit my implementation of it is terribly ameture, but I will not admit that the system I built is worthless or without merit because that is simply not the case. I've seen enough spaghetti messes built on PHP to know that my code is not that bad, but when it comes to seeing a "quality" implementation done in Perl, there seems to be a lot of hot air about wheels and a few keyword names for popular frameworks, but very little actual information about how to go about building things using them, the nature of the paradigm, how it actually works... I can name you many frameworks and so on, but I've never seen a whole system using one of these things, and when I ask someone for a barebones example of a system, I get told that the code is all intertwinned with their work... a notion I find absolutely shocking coming from where I started and from using a system like aXML which is very loosely coupled to a point where I could throw a skeleton system together in minutes for someone else to develop into a working application from.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://929148]
NodeReaper cleans and fillets

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (3)
As of 2018-01-24 04:37 GMT
Find Nodes?
    Voting Booth?
    How did you see in the new year?

    Results (255 votes). Check out past polls.