4 ms·
Submitter here: Yes, and some of the claims are simply factually incorrect: the original work on refactoring OO programs was done in the context of Smalltalk,
by mpweiher 13y ago
Submitter here: Yes, and some of the claims are simply factually incorrect: the original work on refactoring OO programs was done in the context of Smalltalk, the code navigation we now have in IDEs was taken from Smalltalk (in fact, Eclipse started out as Visual Age Smalltalk) etc.
So I find the post "debatable"...
- Ovid 13y agoGiven that the second paragraph makes factually incorrect claims about what you can detect at compile time in dynamic languages, I think "debatable" is rather kind :) Of course, sweeping generalizations about static versus dynamic languages tend to fall flat.
- DanWaterworth 13y agoCould you elaborate. Which claims are incorrect?
- emiljbs 13y agoOne example would be this: > If you misspell a variable [...], you discover this at run time. Ouch. CL-USER> (defun square (n) (* nn n)) ;; Ouch! nn isn't defined! ; in: DEFUN SQUARE ; (* NN N) ; ; caught WARNING: ; undefined variable: NN ; ; compilation unit finished ; Undefined variable: ; NN ; caught 1 WARNING condition SQUARE
- DanWaterworth 13y agoIt is true of other dynamic languages and there isn't any way to fix that.
- Ovid 13y agoSorry, many dynamic languages prevent against this. For example: $ perl -Mstrict -E 'say $foo' Global symbol "$foo" requires explicit package name at -e line 1. Also, his comment about properties on objects is very debatable, too. Ignoring that the term "property" is overloaded and not defined, since I use roles (see: http://www.slideshare.net/Ovid/inheritance-versus-roles-1799996 http://www.slideshare.net/Ovid/inheritance-versus-roles-1799...), I find out at compile time if my classes are missing an attribute or method (actually it's composition time, but that's splitting a hair that most will never notice). In short, I don't get frantic 2AM phone calls about a batch process trying to call a non-existent method.
- icebraining 13y ago$ cat err.py def a(): print b $ pylint -E err.py ************* Module err E: 2,8:a: Undefined variable 'b'
- tetha 13y agoPractically speaking, this is helpful, indeed. Technically speaking, the more reflection a language provides, the less correct this becomes. Python code can dynamically inject local variables into stack frames, attributes into objects and so on in more or less silly and probably non-portable ways. So in the end, you end up with pragmatic correctness for mostly sane code. If that's enough for you and your project, go with it.
- mpweiher 13y ago> I think "debatable" is rather kind :) Well, I think he has an interesting data-point, and makes some interesting points despite maybe making a somewhat incorrect generalization. But even that generalization points to something I find interesting, which is that Python and JavaScript (maybe Ruby as well) possibly form a separate group with the characteristics he describes. I also found the observation that Mock object testing doesn't seem to respond well to changes in the underlying code interesting. It's that mix that makes it "debatable" ;-)
- nfm 13y agoThere are some interesting, semi-recent (last few years) attempts to fix the pitfalls of using mocks for testing - renaming methods, wrong arity, typos, etc. rspec-fire for example validates that the object you're mocking responds to the method name you've used, and takes the same number of arguments. It also does it conditionally based on whether the class in question has been loaded, so your unit tests can run in isolation, but when you run your full test suite it will catch any mocking errors. Pretty handy!
- willvarfar 13y ago(blog author) Well I thought refactoring went all the way back to Forth. I'm sure that with some language xyz it worked out very well for some project abc and that obviously disproves my whole point and you can move on... I found writing large projects in Python - a language I was very familiar with, expert even - to become very difficult to extend aka maintain after a long time. My post should be seen in the bigger picture of the post I was following up about "Scaling My Server", and others I have written.
- mhd 13y agoIsn't "some language xyz worked out very well..." and "I found writing large projects in Python..." basically the same (anecdotal) argument?
- willvarfar 13y agoYes, but its a subjective post. If someone wants to say or blog "I use xyz and I can successfully maintain and extend large projects and it hasn't collapsed under a cognitive burden and too-specific unit testing" that'd be a cool counter data point.
- mhd 13y agoAdvocacy is cool now? Statistically you could come up with almost any methodology, sane or not, and find one project using it, unless you're going for outright cruel jokes like Befunge, INTERCAL or ITIL...
- protomyth 13y ago> Well I thought refactoring went all the way back to Forth. The original refactoring browser was in Smalltalk. Forth programmers don't go about that type of thing the same way as other language since the goal is really to write good "words" that express your program. It is more building a better language than traditional refactoring.
- PaulHoule 13y agoI think you're thinking of the very good book "Thinking FORTH", which presented an incremental style of development coupled with a Lispy DSL architecture.
- opinali 13y agoI have used the old refactoring browser in VisualWorks. It was cool for its time. I's pathetic compared to modern refactoring tools for static-typed languages.
- MostAwesomeDude 13y agoI politely submit that you have not heard of E.