A couple of weeks ago, I left the biggest Perl group on Facebook. There were several reasons behind this decision, but the final straw was when the...
For further actions, you may consider blocking this person and/or reporting abuse
After I learned async/await in javascript, I realized what a game changing feature it was for nonblocking application development and immediately set about trying to bring it to mojolicious. I had a Coro based solution on cpan within a couple months (most of that trying to make the backend pluggable which turns out to have been unnecessary) and then that success pushed me and others to advocate for LeoNerd to make his native implementation (Future::AsyncAwait) reusable enough that Mojo could attach to it.
I never would have had that drive to provide a feature if I hadn't seen how powerful it was elsewhere! Show your love for your favorite language by using others and bringing the best bits back home.
Me, I am a proud member of the Python community and I program in a number of languages including, but not limited to Python, Perl, awk, TCL, C, BASIC, Verilog, VHDL, ...
After working on the Rosettacode.org site for over a decade, I note that many languages have different sweet-spots in many areas. People might pick a language as that which scratches their bigest itch the best, and is half decent in other areas.
I find Perl to solve problems but still very good. In my company, a very large part of the software is still Perl code. To rewrite all that now would not make sense. Maybe a completely new project I would not start with it. I think golang would be an adequate alternative to implement the software we have in Perl. These are mainly system processes, workflows, or transformations of different documents. So far Perl is doing very well in this area.
I find it a bit sad that Perl is often made so bad. Actually, if you make an effort (e.g. coding standards) Perl is a very nice and extremely flexible programming language.
And I've also used almost every known programming language in my career.
I just retired from a 40+ year programming career. As you might imagine I've had to learn and master a large number of programming languages (at last count, 16). The last third of my employment was programming primarily in Perl, so right now it is the language that by far I am the most fluent. It is a powerful and versatile language and I really enjoy programming in Perl. But if you were to ask me what is my favorite programming language, I'd say it is probably the one I'll learn next. This has almost always been the case.
So true. I have always said that you shouldn't use a single language to teach anything, even if it's that language. Programmers solve problems, using a variety of languages, and also the technical experience to use the best language in any part of the development: tooling, web, data access... So lots of 👍 to you.
I said as much in my response to Nigel Hamilton's Perl and Raku growing as a profession - borrowing hacks from barristers. I've also been hired in similar situations as Dave: I told them I didn't know their tools, and the said that wouldn't be a problem. In a couple months I'm as proficient (usually more) than the the rest of the team. That's not because I'm smart: I just read more of the manuals :)
I agree with the point of the article, that a programmer should have as many tools in their toolbox as possible, but I also don't see a problem with a discussion group being devoted to just people programming in perl.
Not every group has to be about enriching the toolbox, some of them can be about discussing and improving your use of a specific kind of screwdriver. People coming into that group to talk about how great hammers are should be shut down as it is off-topic. As soon as a group's admins stop enforcing on-topicness, that group is doomed.
Oh, you're absolutely right. Which I why I didn't say that there shouldn't be a group for programmers who use Perl. In fact I'm a part of many groups that fit that description (including one on Facebook).
My objection was to the name of the group. Language is powerful. And calling the group "Perl programmers" can possibly encourage some of the problems I talk about above. I'd prefer it if the group was called something like "Perl programming".
Ah, see I thought the talk of the group's title was a metaphor, and one I think works very well. But if it is an actual objection, then I have to disagree that tiny differences in suffixes are as powerful as you're suggesting. Perl Programmers vs Perl Programming is a distinction without any practical difference.
As someone who used to code mostly Perl, but now sadly doesn't I'd be interested in a group called "Perl Programming" but not "Perl Programmers" because that's not what I am anymore and it sounds like it would be of interest to those who mostly/completely code Perl
"An experienced programmer should quickly be productive in pretty much any programming language."
Oh if only that were the case. I have many years of experience with Perl and C, yet find little of that transfers to C#, which I have been struggling with for the past three months.
I completely agree, in fact anyone who has been programming enough time probably had no choice but to learn several languages. In my experience that only makes you stronger and more aware of other ways to solve problems.
I mean, ideally you can just name a bunch of alternative languages and pick one that the interviewer is somewhat familiar with.
A smart interviewer might even take the chance to ask you which one you'd consider the best choice and why (which is a nice question because it shows lots of things about how knowledgeable you are and your thought process)
I don't think the article says that at all.
"Jack of all trades, master of one" is my goal as a programmer. I want to know as much as possible about many different tools and languages, while mastering at least one of them (Lua, in my case).
i really need to help
I agree the point that resolving customer problem is very important for programmer.
hiii please help me on my career
what is happened on facebook perl group? I don't know the detail.