[nSLUG] perl and web sites
odoepner at gmail.com
Fri Feb 28 23:10:32 AST 2014
Robin, i agree that for some tasks like text processing, file processing
perl can be much more convenient than java.
java 7 reduced the try-catch pain (added "try-with-resources" feature) and
brought a vastly improved file io api ("NIO.2"). but for experienced perl
coders it will probably still feel very clunky.
i usually have to work on bigger "enterprise" systems, often with a web
frontend and large teams of developer where a type-safe managed language
like Java and its heavy-duty JEE stuff is a more natural fit.
I use Java OOP in a very functional way and try to keep state encapsulated
and ideally immutable. I use interfaces a lot, and class inheritance only
if I have to. I tend to avoid method overriding, protected fields, super
calls and all that sticky class heirarchy glue like the plague. "Favor
composition over inheritance" as Erich Gamma used to say .. :o)
But be it many small objects or many small functions, I think it's better
to have many well-focused loosely coupled small components than long
procedural code blocks.
On Fri, Feb 28, 2014 at 10:58 PM, Oliver Doepner <odoepner at gmail.com> wrote:
> ben, the jetbrains link you sent is for the "ultimate edition" of
> intellij. the free / open source "community edition" has no rails support.
> On Fri, Feb 28, 2014 at 1:16 PM, Robin Murray <nibor.yarrum at gmail.com>wrote:
>> I don't have much experience with any framework (I come from a long
>> mainframe background and web sites weren't their main stock-in-trade), but
>> I've always felt a bit of aversion to them, it appears for the same reasons
>> you are stating - they are great for getting a web site off the ground
>> fast, but as you grow they may start to drag on your progress. I'm not sure
>> if that's valid generally but it's interesting to see your opinions from
>> actual experience.
>> Robin Murray
>> Hatchet Lake,
>> Nova Scotia
>> On Fri, Feb 28, 2014 at 11:59 AM, Ben Armstrong <
>> synrg at sanctuary.nslug.ns.ca> wrote:
>>> On 27/02/14 11:29 AM, Robin Murray wrote:
>>> > Also, I was wondering how many perl vs ruby programmers are on this
>>> > or people generally know. Is rails really more popular than perl now?
>>> > is hard to find good perl programmers in Halifax, but are ruby
>>> > programmers correspondingly falling out of the woodwork there?
>>> I'm a rubyist writing a lot of ruby code, some of it rails at work. I
>>> also have prior experience in perl, though much of that has fallen into
>>> disuse since we started writing new things in ruby.
>>> I can't say anything about relative popularity in Halifax, neither
>>> having sought a job in it, nor having looked to hire anyone in the
>>> period since I started using it. I can only say I've found my experience
>>> using ruby overall positive, and I believe the quality of our code
>>> written in it has gone up since we moved away from our hodgepodge of
>>> code written in perl. But that may have at least as much to do with
>>> other factors (learning more modern coding methodologies; at least
>>> paying lip service to "agile" practices ;) during the same period of
>>> time as the language choice.
>>> As for specifically my experience with rails, it has fairly drawn some
>>> criticism for attracting fanboys who equate ruby with rails, and are
>>> heavily dependent on using that framework to get anything done. I would
>>> avoid hiring anyone like that.
>>> I'm not convinced that rails is all that and a slice of bread. I am
>>> intrigued by lighter frameworks like sinatra, and wonder if it were
>>> possible to turn back the clock if we would have chosen something like
>>> that instead. I'm finding particularly over time, we do things less and
>>> less the "rails way" (for reasons I can't really get into here). Sure, a
>>> framework can make deploying new code rather speedy, but over time, it
>>> can start to accumulate baggage that limits your future choices.
>>> nSLUG mailing list
>>> nSLUG at nslug.ns.ca
>> nSLUG mailing list
>> nSLUG at nslug.ns.ca
> Oliver Doepner
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nSLUG