4 ms·

In my anecdotal experience, the type of programmers that evangelize and talk shit about programming languages tend to be on the less informed side of the knowle

In my anecdotal experience, the type of programmers that evangelize and talk shit about programming languages tend to be on the less informed side of the knowledge spectrum.

AdieuToLogic 7y ago
> In my anecdotal experience, the type of programmers that evangelize and talk shit about programming languages tend to be on the less informed side of the knowledge spectrum. Or maybe they have just expanded their "knowledge spectrum" and are experiencing an effusive moment?
- root_axis 7y ago
  Talking shit isn't effusive. It's possible to enjoy a programming language without openly denigrating others you regard as inferior.
  - AdieuToLogic 7y ago
    > Talking shit isn't effusive. It's possible to enjoy a programming language without openly denigrating others you regard as inferior. Both points you make I agree with. I simply was offering a possible explanation for those whom exhibit overly passionate opinions when they become enlightened. When people take an epiphany to the point of denigrating those around them, then they likely have issues beyond what any programming philosophy could possibly encode.
  - AdieuToLogic 7y ago
    It's apparent you have dealt with negative situations such as you describe. Here is a haiku which may be helpful: Those who can will do, Those who cannot will seek to, Hide that fact from you. HTH
vertex-four 7y ago
I occasionally program Go because it has an amazing amount of libraries - I basically use it for random microservice type things that glue systems together. (Most recently, an HTTP login endpoint that sends and receives XMPP messages to authenticate the user.) I don't like it. I program Rust the rest of the time. I'm considering learning Perl5 so that at least my type system lets me do vaguely expressive things - I'm utterly fed up of half my code looking like: foo, err := something() if err != nil { return nil, someErr{err} } I got very used to Rust's try!() macro, now ? operator, and being able to map over Results to convert between error types in a single line that feels much less noisy - I have functions in Go that are a dozen or so lines that would've been 3 in Rust, and tbh I struggle to follow what the function actually does when 3 out of 4 lines are to do with the failure case. I would consider "unacceptably crippled" to be a reasonable description of Go, even if it's the best tool I have for some jobs.
- root_axis 7y ago
  "unacceptably crippled" is a pejorative meant to insult, not a descriptive criticism.
  - deleted 7y ago
    [deleted]

In my anecdotal experience, the type of programmers that evangelize and talk shit about programming languages tend to be on the less informed side of the knowledge spectrum.

AdieuToLogic 7y ago

> In my anecdotal experience, the type of programmers that evangelize and talk shit about programming languages tend to be on the less informed side of the knowledge spectrum. Or maybe they have just expanded their "knowledge spectrum" and are experiencing an effusive moment?

root_axis 7y ago
Talking shit isn't effusive. It's possible to enjoy a programming language without openly denigrating others you regard as inferior.
- AdieuToLogic 7y ago
  > Talking shit isn't effusive. It's possible to enjoy a programming language without openly denigrating others you regard as inferior. Both points you make I agree with. I simply was offering a possible explanation for those whom exhibit overly passionate opinions when they become enlightened. When people take an epiphany to the point of denigrating those around them, then they likely have issues beyond what any programming philosophy could possibly encode.
- AdieuToLogic 7y ago
  It's apparent you have dealt with negative situations such as you describe. Here is a haiku which may be helpful: Those who can will do, Those who cannot will seek to, Hide that fact from you. HTH

vertex-four 7y ago

I occasionally program Go because it has an amazing amount of libraries - I basically use it for random microservice type things that glue systems together. (Most recently, an HTTP login endpoint that sends and receives XMPP messages to authenticate the user.) I don't like it. I program Rust the rest of the time. I'm considering learning Perl5 so that at least my type system lets me do vaguely expressive things - I'm utterly fed up of half my code looking like: foo, err := something() if err != nil { return nil, someErr{err} } I got very used to Rust's try!() macro, now ? operator, and being able to map over Results to convert between error types in a single line that feels much less noisy - I have functions in Go that are a dozen or so lines that would've been 3 in Rust, and tbh I struggle to follow what the function actually does when 3 out of 4 lines are to do with the failure case. I would consider "unacceptably crippled" to be a reasonable description of Go, even if it's the best tool I have for some jobs.

root_axis 7y ago
"unacceptably crippled" is a pejorative meant to insult, not a descriptive criticism.
- deleted 7y ago
  [deleted]