I am intrigued. Why does the open source industry not have 'Visual' products like 'Visual' Basic, 'Visual' C++ or 'Visual' ASP.NET? Why don't we have Visual PHP? or Visual RUBY?
|
|
Well first of all, I think Microsoft would have a problem with you naming your IDE "Visual PHP" or "Visual Ruby". But I don't think the question is literally about the naming of the IDE :-) I think you'll find the reason is that "Visual" designers simply do not work well with HTML. Microsoft themselves have moved away from the "Visual" aspect of ASP.NET with the move to ASP.NET MVC. In fact, with ASP.NET MVC, there's not a lot you'll find in the IDE that you can't also get in Eclipse and other IDEs. |
|||||||
|
|
I'm an old guy who remembers. A long time ago, in the dark ages before the world wide web, most development tools were not visual. They were command line tools. You literally had one terminal window, from where you fired up your text editor (e.g. vim or emacs), and edited your software. Then you suspended or exited your editor and ran your compilers and linkers against your software and hoped that it compiled. Then you deployed your software in your test environment and tested it. Even your debuggers would have been line-by-line based. However in those days, you did not have a multi-window, multi-tab graphical layout. Just command terminals with a shell program. Then those masterful innovators at IBM and Microsoft came up with development tools which allowed you to have a window with your code open, a set of buttons to run your programs, another set of windows which showed your program step through the code in a debugger, and another window which allowed your tool to watch the transient and persistent data in your program. These tools were labelled Visual Basic, and Visual Age, etc. These tools made programming much more pleasant because you did not have to build and maintain a mental map of how your development environment looked. The tool did it for you. By the time PHP, Python, C#, and Ruby became popular visual development tools were normal and expected, and so adding "Visual" to the name of your tool set did not confer any differentiating marketing value. This is the official story. You must remember, however, that visual development tools were invented and pioneered by folks like Alan Kay, Adele Goldberg and Dave Thomas. They delivered visual development environments for a language called Smalltalk about 15 years before the rest of the industry was exposed to visual development tools. Ask any old Smalltalk hacks and they'll tell you that they had features in Smalltalk 20 years before the rest of the industry was exposed. (Smalltalk failed because it was syntactically too different from the Algol-descended and Modula-descended languages which are most popular in industry, and which most programmers can easily read, such as C, C++, C#, Java, Ada, and Fortran. It also failed because there was no easy way to separate the development tools from the database and the runtime environment, and that made it less useful for deploying in many production environments. However, the brilliant ideas of Smalltalk live on in our modern visual development tools as well as in programming languages such as Ruby and Javascript). |
|||||||
|
|
Visual Basic and Visual C++ are IDEs from Microsoft for Basic and C++ programming languages. I guess, if they picked Ruby or PHP, we would have gotten Visual Ruby or Visual PHP indeed. |
|||||
|
|
I tried to create a simple visual editor for my Apeel PHP Code Generator as I thought it would be useful to be able to visualy move fields around the page, click on a field and set / edit it's events and properties. But in the end I gave up because it was a far bigger, more complicated project than I first envisaged! It would take a lot of development man hours to complete such a project and I don't think there is the demand out there to justify it. In the PHP market place I suspect that most people are happy with a good IDE with integrated debugger and an HTML editor for "visual" editing, i.e. page layout. |
|||
|
|