3 ms·

I'm not sure why Java is taking a bullet on this. The default in other languages is often to not do any certificate validation. That seems like the worse appr

by Eridrus 12y ago

I'm not sure why Java is taking a bullet on this. The default in other languages is often to not do any certificate validation. That seems like the worse approach since no-one can tell their code is insecure. Maybe fine for a scripting tool, but I wouldn't want that on my production boxes. I'm not sure why every language needs to be useful as a scripting tool. If there are things that help the common case and also scripting (eg classpaths being a pain), there's obviously an argument for "why the fuck hasn't this been fixed yet", but in other cases there are either fundamental tradeoffs or resource constraints.

yellowapple 12y ago
> I'm not sure why every language needs to be useful as a scripting tool. "Easy things should be easy, and hard things should be possible." -- Larry Wall One of the reasons why I switched from Java to Perl. I didn't feel that easy things were easy in Java, and I don't run into enough hard problems on a daily basis to justify the verbosity and masochism involved.
- Eridrus 12y ago
  On one hand, I'm happy you found something more productive. On the other, I've spent a good chunk of time just reading other people's code, and I've come to appreciate really straight forward verbose code. So I am a bit biased against the Perl I've seen, since it is generally not written with ease of understanding as a priority.
  - yellowapple 12y ago
    That's unfortunate. I try to keep my code (no matter what language, Perl included) as readable and tidy as possible for the sake of those reading the code in the future (myself included). While creatively stringing an incomprehensible stream of punctuation marks into a usable program is fun, I'm with you in agreeing that such coding styles should be avoided in anything that's not a one-off mental exercise. That said, too much verbosity can introduce the same problem of unreadability by making important things harder to identify. There's an important balance between verbosity and terseness that should always be considered.
- peterashford 12y ago
  HTTP should be secure. A programmer should have to go out of their way if they want something designed to be secure to act in some other way.

by Eridrus 12y ago

yellowapple 12y ago

> I'm not sure why every language needs to be useful as a scripting tool. "Easy things should be easy, and hard things should be possible." -- Larry Wall One of the reasons why I switched from Java to Perl. I didn't feel that easy things were easy in Java, and I don't run into enough hard problems on a daily basis to justify the verbosity and masochism involved.

Eridrus 12y ago
On one hand, I'm happy you found something more productive. On the other, I've spent a good chunk of time just reading other people's code, and I've come to appreciate really straight forward verbose code. So I am a bit biased against the Perl I've seen, since it is generally not written with ease of understanding as a priority.
- yellowapple 12y ago
  That's unfortunate. I try to keep my code (no matter what language, Perl included) as readable and tidy as possible for the sake of those reading the code in the future (myself included). While creatively stringing an incomprehensible stream of punctuation marks into a usable program is fun, I'm with you in agreeing that such coding styles should be avoided in anything that's not a one-off mental exercise. That said, too much verbosity can introduce the same problem of unreadability by making important things harder to identify. There's an important balance between verbosity and terseness that should always be considered.
peterashford 12y ago
HTTP should be secure. A programmer should have to go out of their way if they want something designed to be secure to act in some other way.