search

scottefein / the-happiness-manifesto

The Happiness Manifesto-What makes a happy developer?
http://blog.sefindustries.com/the-happiness-manifesto/
171 stars 20 forks source link

Update README.md #6

Closed kschmit90 closed 9 years ago

kschmit90 commented 9 years ago

If the language is only optimized for the developer, the end user may suffer. Why not work towards an ideal? The language is the developers way of communicating with the computer, so it must be evenly optimized.

scottefein commented 9 years ago

I think we've moved to a point where our languages can both be performant and optimized for the developer. A lot of modern languages already meet this requirement. Go, Scala, etc.

kschmit90 commented 9 years ago

Yes. Does that not make it germane to developer happiness?

scottefein commented 9 years ago

Languages have many use cases. A slower language might be fine depending on what I'm doing. The one thing I care about always would be that it's optimized for the developer. Ruby is a great example-Super hard to parse for the computer, but many use cases where it works great.

kschmit90 commented 9 years ago

Ah, so you would like the language to always be optimized for the developer, relative to the use case. Makes sense.

nathany commented 9 years ago

NOT seems too strong to me.

How about "My language must be optimized for me rather than the computer."? Or before/over the computer? As you say, we can have both.