![]() NET development environment is supposed to meet every need, unfortunately, and therefore certainly not the particular needs of AutoCAD draftsmen. Thus the role of the programmer in the IT department of these companies is to describe an algorithmic procedure that would be transcribed in a transparent language understandable by the machine, then the final code would be run.Īnd I'm sorry to say, but Visual Basic, C #, F #, have no resemblance at all to a very high level language. NET should therefore be turned into writing independent libraries capable of manipulating objects that AutoCAD draftsmans know. Instead of leaving it to companies IT guys using AutoCAD who really have something else to do but to understand the inner workings of machines.Īll efforts put into the development environment. ![]() Well they just need to get back to work, and program the intermediary level between the machine and humans. But computer specialists will tell you that a computer can not directly understand an algorithmic language. Note that this already exists, it is called algorithmic. It is a decisive advantage because we will not need Champollion and the Rosetta stone and spend hundreds of hours transcribing spoken language into language understood by the machine. The huge advantage is that human beings around the machine, yes there are still a few, will also understand what it means. There is absolutely no problem for a computer to understand this sentence. A computer is quite capable of understanding a sentence logically expressed as this: I draw a polyline from the point 0,0, then I go to 5,5, and then I go to 10,10. Inventing a programming language that is a level far higher than VBA and LISP. We have to start from the begining, that is the end user. NET programmer is still looking for an hypothetical Web support among hypothetical examples of codes routines that will allow him to understand in what dialect to talk to the computer. NET environment, because while the LISP guy has already done its correction, the VBA programmer is finishing typing its line of code, and the unfortunate. And this certainly will not happen in the. ![]() And frankly, the developer is also interested in that. What AutoCAD draftsman spends his days drawing every 10 seconds 10 000 lines? I'll tell you what interests the draftsman using AutoCAD developments: it's when requesting a modification in a development from his IT department, the computers guys will have to correct one line of code rather than 25. If a program draws 10 000 lines with LISP, 10,000 lines with VBA and 10,000 lines with Visual Basic. NET developers attempting the impossible and pathetic, but brave, explanation of. I think any programmer will not deny that. To take the example of creating a single line, it is of course much faster to program in LISP or VBA, that to do so using. The people who program for AutoCAD waste time learning things that can be used in designing an operating system, but certainly not in answering CAD users needs. In the field of programming for AutoCAD, we are clearly starting to get away from the basics needs. AutoCAD end users want the job to be done more quickly than by hand, and frankly, a procedure wich takes 2 ms more than another is totally meaningless. Nothing less than that.īecause ultimately, what is the purpose of the programming in AutoCAD? Is it knowing the possibilities of the machine, worrying about how a DLL is compiled, win two milliseconds here and there? Not at all, these things are concerns for professional programmer disconnected from the real world. To be forced to move from a high level language to low level language does not seem to me we are raising the level, but instead we are likely to soon touch the floor. So we've moved from a very high level language, LISP, to a language level a bit lower, the VBA language to even lower, Visual Basic, C# or F# in the. We hear that NET is better, is faster, is more powerful than what we had until now.īut we also hear more and more little voices saying best is the enemy of good.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |