4 ms·
Hmm, Nice to have all the up-and-coming languages lined-up in an internal comparison. I like Lua, Haskell and Io. I think that future languages will have to ha
by joe_the_user 18y ago
Hmm,
Nice to have all the up-and-coming languages lined-up in an internal comparison. I like Lua, Haskell and Io. I think that future languages will have to have a cleaner rather than an uglier look and syntax. For that reason, I have a visceral reaction to scala and factor. Even the one-line examples I've seen of these language have look like gibberish. I'm sure they are great in many ways but don't want them to succeed since they will make my brain hurt more. Also, I think that they won't succeed for similar reasons.
- stcredzero 18y agoDon't forget Eiffel and its progeny. Design By Contract and heavy use of assertions feels to me like it's closely related to Test First development. You also get fast runtime code out of it (as in C++ fast) in a very Pure-OO environment. (By many accounts, even more so than Java and C++.)
- jballanc 18y agoI played with Eiffel for a time, but found that Design By Contract was a bit overly restrictive for amateur programming. Now that I'm doing more professional stuff, I think it's worth looking at again. There's also a lot of Eiffel influence in Ruby, so moving over from Ruby is not so hard.
- stcredzero 18y agoWhat I've found is that you actually want restrictive when you're doing maintenance. You want to know as much as possible about the code you're changing. You want to know exactly what's in that instance variable. When you're doing prototyping, you want to delay that decision as long as you can, so you are making the most informed decision possible. And nothing informs your decisions like the act of developing and getting feedback from users. Optional static typing gives you the best of both worlds. But I don't know how you'd get the equivalent with Design By Contract/Unit Testing. Both of those feel a little unnatural to me. I'd rather just tinker, and not have to set up extra stuff before or after I code.