Monorail and webform, who are Swiss Army knives

From the perspective of learning costs, the initial learning cost of webform is undoubtedly quite low. For beginners, Drag and Drop controls and then write the backgroundCodeIt should be a very easy way to understand and accept; for developers who transfer from winform, this development method has long been their habit; even for people like me who transfer coding/html from classicl ASP/PHP, webform once made me feel perfect (coding/html are placed in different places, it makes people feel uncomfortable ). Learn webformNot even requiredLet's get to know what HTTP is, what HTML is, and what Javascript is ......

However, if you want to use monorail, it will be troublesome. In the initial stage, you need to know more things than webform. For example, first, you must get used to viewing the interaction between the client and the server from the traditional HTTP perspective. For example, if you are developing classical ASP/PHP, each interaction is independent. You need to know what HTML is, what form is, and what input is. To implement some special functions, you also need JavaScript, and then you need to learn the template syntax ......

It is not difficult to conclude that,Webform is easier to use than monorail. Especially for those who have never done web development, it hides many underlying web things and is displayed asApproximationQuick development of winform. At this point, we can say that webform is more like a Swiss Army knife than monorail. Isn't webform more powerful than monorail? If you want any controls, you can give them to you. You don't need to do anything else. They are all integrated, aren't you? In turn, monorail, which was originally a simple drag-and-drop control on webform, requires additional efforts to implement it.

Swiss Army knife is a good thing, powerful, easy to carry, of course, there is no learning cost, but these advantages are not what monorail has.

As I applied webform to development step by step, I realized that webform is only easy to use. To customize controls, I had to have a deep understanding of the control models and events, methods, sometimes the existing controls may not be able to meet the customization requirements, and have to rely on third-party controls, when the third-party controls cannot be found, you have to develop your own controls, when I was involved in the control development field (mainly custom controls), I learned what is calledHigh learning costs. It took me three months to develop complex controls. Even more unfortunate, the interface modification originally made by the designer has changed to something I want to do. Alas, sin and sin are a waste of life.

I think, since we have chosen web development, how can we not understand what HTTP is? What is HTML? What is JavaScript? Webform can help you block the moment, but it can help you block the whole world? You must know that, even if you change the development platform in the future, it is at least helpful to master these basic knowledge.

However, for a well-established web developer, how many things does monorail have to learn? After reading the getting statrted sample of monorail, you can get started. It will not take much time to finish reading all its documentation. But if you want to turn webform into a field of control development, you should not only understand HTTP/html/JavaScript /... for these underlying things, we have to learn more about the lifecycle of webform, control inheritance tree, and various interfaces ......

Monorail is not a Swiss Army knife, it does not help you output HTML, does not help you manage the page status, it mainly helps you to split the views and controllers, and others are auxiliary and dispensable.