4 ms·

So right. Just spin the damn jetty, put the postgre driver and off you go. Most of the infrastructure is done in a day or two, and if not enough you can always

by Ingon 14y ago

So right. Just spin the damn jetty, put the postgre driver and off you go. Most of the infrastructure is done in a day or two, and if not enough you can always revisit it later. And it runs fast. So fast that it feels like dynamic language. And even with the modern apps, where most of the action is on the client (and the server is interface to the DB most of the time) you even don't need to restart your server that often. I think that whoever says that Java is not good language for development either have seen only j2ee or never did looked around. (as a prime example the stupid bean convention and tools which operate on it)

kbenson 14y ago
I know my reason for not wanting to develop in Java is that since for the most part the speed difference doesn't matter for my needs, it boils down to how easily I can transcribe/translate my concepts into code. The conceptual impedance of Java is just higher for me. I think most of the code I write (the non-algorithm complex stuff) that boils down to stuff like "take the subset of the collection of orders with a total over 100, and sort by number of items." In Perl, that may be as simple as: my @large_orders = sort { $a->{items} <=> $b->{items} } grep { $_->{total} } @orders; I think allowing me to express myself easily and succinctly like this saves time, reduces errors and allows me to concentrate my time and attention on the more complex portions of the code. I also think succinctness (where idiomatic for the language, so it's not confusing) is useful in it's own right. The more of the current (or related) function and program state that's obvious on the screen when I'm coding, the less likely I am to have to break off from what I'm doing to go look up a detail I need.
- zimpenfish 14y ago
  Not a great advert for Perl, that, since it doesn't implement the quoted action correctly...
  - kbenson 14y ago
    D'oh! You're totally right, I forgot the greater than filter in the grep. my @large_orders = sort { $a->{items} <=> $b->{items} } grep { $_->{total} > 100 } @orders; Embarrassing.
  - prakashk 14y ago
    Because `> 100` is missing from the condition? Other than an example of poor copy-pasting of code, how do you conclude that it is "[n]ot a great advert for Perl"? For the record, this would be the code with missing part included: my @large_orders = sort { $a->{items} <=> $b->{items} } grep { $_->{total} > 100 } @orders;
    - zimpenfish 14y ago
      It might lead someone to conclude that Perl users were slapdash in their approach and prone to tossing off untested code. Possibly unreasonably, possibly not.

by Ingon 14y ago

kbenson 14y ago

I know my reason for not wanting to develop in Java is that since for the most part the speed difference doesn't matter for my needs, it boils down to how easily I can transcribe/translate my concepts into code. The conceptual impedance of Java is just higher for me. I think most of the code I write (the non-algorithm complex stuff) that boils down to stuff like "take the subset of the collection of orders with a total over 100, and sort by number of items." In Perl, that may be as simple as: my @large_orders = sort { $a->{items} <=> $b->{items} } grep { $_->{total} } @orders; I think allowing me to express myself easily and succinctly like this saves time, reduces errors and allows me to concentrate my time and attention on the more complex portions of the code. I also think succinctness (where idiomatic for the language, so it's not confusing) is useful in it's own right. The more of the current (or related) function and program state that's obvious on the screen when I'm coding, the less likely I am to have to break off from what I'm doing to go look up a detail I need.

zimpenfish 14y ago
Not a great advert for Perl, that, since it doesn't implement the quoted action correctly...
- kbenson 14y ago
  D'oh! You're totally right, I forgot the greater than filter in the grep. my @large_orders = sort { $a->{items} <=> $b->{items} } grep { $_->{total} > 100 } @orders; Embarrassing.
- prakashk 14y ago
  Because `> 100` is missing from the condition? Other than an example of poor copy-pasting of code, how do you conclude that it is "[n]ot a great advert for Perl"? For the record, this would be the code with missing part included: my @large_orders = sort { $a->{items} <=> $b->{items} } grep { $_->{total} > 100 } @orders;
  - zimpenfish 14y ago
    It might lead someone to conclude that Perl users were slapdash in their approach and prone to tossing off untested code. Possibly unreasonably, possibly not.