91–100 of 143 posts
Earlier quoted context omitted.
+1 It is so hard to know that @ means array and % means a hash (key/value pair) haha.
It's not that hard to know the types of the variables you created without punctuation in the identifiers, either.
Agreed. However, working for a company with more than one developer...
Good article, especially the praise towards CPAN. It seems to get lost in the hustle and bustle of the cutting-edge discussions, undeservedly so.
I wonder if this will make hiring easier or harder in the valley?
Earlier quoted context omitted.
As has been alluded to in another comment: Which other languages that compare to perl have you actually looked at? Python has rich meta-programming. Ruby has (almost) single-handedly super-hyped and re-invented the idea of domain specific languages (DSLs). Lisp is of course all about this (as is Forth). Javascript builds on the ideas from Smalltalk and (especially) Self to allow you to crazy stuff with how objects wo…
"As has been alluded to in another comment: Which other languages that compare to perl have you actually looked at?" I am very familiar with all of the languages that you mention. They are all great languages in their own right. My comment however was about Perl's ability to easily evolve the core language via contributions from its community, as opposed to other languages that require a lenghty process performed by…
The problem is that Perl's TIMTOWDI culture and the inconsistent evolution of the core language make learning "enough" Perl harder than learning e.g. "enough" Python.
Earlier quoted context omitted.
Perl lets you add new language keywords which take effect during the parse phase.
So, basically, Perl has macros? REAL macros? Like, say, in Lisps? Could I, for example, make fully inlined merge sort, as demonstrated a couple days ago here by a post from Racket blog? Now I'm curious.
One could, in theory, build something like Lisp macros using it, but I don't think that anyone has.
There is some decent justification in there, but I think the generic question, in a lot of questions is: Why did I choose to build X with Y? The generic answer is usually: Because it is what I know. The extended answer may include particular features of the language or environment or it may include the support provided by a particular cloud infrastructure. As an example, the stuff I am personally working on now, I mo…
There are always tradeoffs, but sometimes you can find "the best tool for the job". And that may or may not be the tool that you know. You gotta be flexible and open to learn other tools that may suit the situation better. In the post I don't bash any other languages at all. In fact, I encourage people to learn other languages too. At the end of the day, it'll help you evolve your thinking process and extend your ski…
What I liked about the post - it didn't focus on hype, like that around NodeJS (it's badass rock star tech); additionally it brought up a language no so en vogue.
Keep up the good work.
There is some decent justification in there, but I think the generic question, in a lot of questions is: Why did I choose to build X with Y? The generic answer is usually: Because it is what I know. The extended answer may include particular features of the language or environment or it may include the support provided by a particular cloud infrastructure. As an example, the stuff I am personally working on now, I mo…
There are always tradeoffs, but sometimes you can find "the best tool for the job". And that may or may not be the tool that you know. You gotta be flexible and open to learn other tools that may suit the situation better. In the post I don't bash any other languages at all. In fact, I encourage people to learn other languages too. At the end of the day, it'll help you evolve your thinking process and extend your ski…
Earlier quoted context omitted.
"As has been alluded to in another comment: Which other languages that compare to perl have you actually looked at?" I am very familiar with all of the languages that you mention. They are all great languages in their own right. My comment however was about Perl's ability to easily evolve the core language via contributions from its community, as opposed to other languages that require a lenghty process performed by…
"People have had to deal with Perl code that they do not understand. It may have been poorly written, or it may have been perfectly written Perl code. If you do not take the time to learn Perl, you would not know the difference." The problem is that Perl's TIMTOWDI culture and the inconsistent evolution of the core language make learning "enough" Perl harder than learning e.g. "enough" Python.
Earlier quoted context omitted.
Perl lets you add new language keywords which take effect during the parse phase.
So, basically, Perl has macros? REAL macros? Like, say, in Lisps? Could I, for example, make fully inlined merge sort, as demonstrated a couple days ago here by a post from Racket blog? Now I'm curious.
I wonder if this will make hiring easier or harder in the valley?
Hiring people willing to work in Perl isn't that tough. Hiring experienced Perl developers with experience solving specific issues is tougher. Hiring a experienced Perl hacker that's fully embraced something front-end development using Extreme Programming is going to be virtually impossible in your local area. I'm a recruiter w/ first hand experience trying recruit for many languages, and I find Perl-based posotions…