"Where shall we make the waist?""Asked their highness (a film about Baron Munchhausen), but asked herself, because she answered it herself. A framework is always good, especially when it's from a notable developer: like a bootstrap from a twitter, like a foundation from zurb, or like a cherry tree on a deer's forehead, carefully planted by that baron.
All CSS frameworks are good and practical.The very fact that the well-known entity regained its importance and moved on the next path to all the same peaks, says that the question - where to make a waist - has not yet found its final solution, and there remains a peak that has not yet been conquered.
Internet is available everywhere and always, but only throughbrowser. Only with a certain electronic platform. All other options lie outside the visual interface. The browser works within the capabilities of an electronic platform: a computer, a laptop, a tablet or a phone. Other variants are possible, but the named ones are most often used.
At a time when IE "dominated", which since birth did not have absolute dominance, and the competition was initially close, there were attempts to standardize something.
As the process of production of computer equipment andmobile devices can not be controlled, and the development of browsers all the time moving in a democratic direction: everything is controlled by itself, which causes a natural difference and difficulties for developers. The Internet space does not accept either collective farms, communities or kibbutzim. In addition, all communities of fans and followers of various tools continuously migrate into each other, disappear and reappear.
Naturally, when there is a need to createresources for the Internet space, you need more or less reliable grounds, rather than shaky support on the always unsteady sand of information technology. The terms "adaptive", "rubber", "cross-browser", etc. came as a tag, as a symbol of what will allow work not to be wasted, that it will look the same and perform its function on any device in any browser.
The meaning and purpose of this product in simplifying the work of the programmer. It is believed that he was one of the first, is among the most advanced and deserves everyone's attention. Having in its composition:
This framework declares more freedomcreativity for a programmer who enjoys this remarkable development experience from Twitter. All this is beautiful, important and interesting, but all this needs to be carefully studied before the declared capabilities become available to the developer.
Indeed, the developer armedBootstrap, Foundation, Kube, Semantic UI, Uikit, UniCSS, Maxmertkit, ... can work with the formula 10/12 instead of the formula 1`000 / 100`000 (manual work) + "Pi" factor. Figuratively speaking, CSS frameworks save the time of project development from infinity or a large number of hours (manual work), up to 10-12 hours for any project.
Remembering that before you take the egg, even the chicken will have to be decently treated with it, it can be assumed: the time difference in development can not disappear anywhere, it goes away during the study of the framework, the choice of the one that should be taken, and the mass of other time wastes that are far from the development process.
Experienced developer agrees that even for a dayit is impossible to make a decent site. The human intellect works faster than any computer, but its conscious part - even very slowly and carefully weighs everything before you even take a very simple decision. The quantity and quality of the modern tools used absolutely nothing, and does not guarantee anything at all.
A modern site is far from a set of pages,demonstrating adaptive layout. Caring absolutely any site is not to show how clever its developer, and what the best CSS frameworks are in its arsenal, but in order to perform the functionality required by the customer.
The task requires a solution - this is an unshakable rule. The development of the fundamentals of adaptability and cross-browser compatibility, a dissertation on rubber imposition with analytical tabs on one or another "type" of rubber - an interesting activity, but no more. Adaptive CSS, HTML, JS frameworks are perspective, but in what context should this perspective be viewed.
There is an understanding of the required functionality. There is a certainty that the resource should work on the computer and on the smartphone. But this does not at all mean that the task of adaptive layout is more important than the task of realizing the functional.
It is impossible to demand from a horse and from a pony one andthe same: pull the same strap with the same success. It makes no sense to carry potatoes even on corn (an aircraft very popular in the era of developed socialism), when from the field to the storehouse it's easy to file. Here, even the same pony alone will manage.
The term "adaptive" in the native meaning of the worddoes not at all mean that something must be done something as it did before, in another place or under other circumstances. There is a task and its functionality, there are various platforms and devices on which this functionality should work. If the goal in the equivalence of processes, design and dialogues is a real utopia, if the goal in solving the task posed is quite another matter.
Programmers develop very quickly, and byexponent, is the specificity of the profession. The idea of a programmer is always faster than any computer, therefore to separate the interface from the code, it was decided intuitively at the dawn of the construction of an information civilization. But to separate a little, it is necessary to know correctly, where there is a necessary side.
These three points (interface, code, face) onlypart of the common information essence. There is still data and the problem of their presentation. It's only at first glance that it might seem that the data and CSS frameworks are not interconnected at all. In fact, the view is always determined not only by the code, but also by what it processes and how it does it, primarily in time.
When deciding to use CSS frameworks,choosing one or the other, assessing the time costs for development and comparing its functionality with what is required to solve the problem, it should be understood that it is not the framework itself that is important, but only the fact that the problem posed in the past has regained importance. It is important to imagine the direction in which the problem develops and its solutions.
In reality, with an understanding of the question, who canbelieve, and who does not, who should be advised, and who should not, problems never arise. But in the virtual space with this there are serious difficulties.
Every programmer (especially a teamthose) accumulate experience. This experience in one way or another is its own framework. Before you take on the faith of a stranger, even if very popular and wonderful, you need to put yourself in the position of the researcher, but not a follower.
The experience of colleagues is never a fundamental basis for work, especially in such a dynamic sphere as information, but a good incentive for the development of their own knowledge and experience.
Even if nothing is to be achieved, nothinginterferes with the study of the experience of others. With any development of events, one's own experience and experience of colleagues in the specialty is better than only one's own experience, and the plans from this will definitely be more promising and real.