“Where are we going to make the waist?” Their highness asked (a film about Baron Munchausen), but asked herself, therefore she answered herself. The framework is always good, especially when it is from a noble developer: like bootstrap from twitter, like foundation from zurb, or like a cherry tree on a deer’s forehead, carefully planted by the baron.
All CSS frameworks are good and practical. The very fact that a well-known entity regained meaning and moved on the next path to all the same peaks, says that the question of where to make the waist has not yet found its final solution, and there remains a peak that has not yet been conquered.
Responsive layout: browsers and devices
The Internet is accessible everywhere and always, but only through a browser. Only from a specific electronic platform. All other options are outside the visual interface. The browser works within the capabilities of a particular electronic platform: computer, laptop, tablet or phone. Other options are possible, but those mentioned are most often used.
At a time when IE "dominated", which from birth did not have absolute dominance, and the competition was initially intense, there were attempts to standardize something.
As the production process of computer equipment and mobile devices cannot be controlled, so the development of browsers is constantly 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 neither collective farms, nor communities, nor kibbutzim. And besides, all communities of fans and followers of certain tools continuously migrate into each other, disappear and reappear.
Naturally, when there is a need to create resources for the Internet space, more or less reliable foundations are needed, and not shaky reliance on the always shaky sand of information technology. The terms “adaptive”, “rubber”, “cross-browser”, etc. came as a tag, as a symbol of what will allow the work not to be wasted, that it will look the same and perform its function on any device in any browser.
CSS Bootstrap Framework
The meaning and purpose of this product is to simplify the work of a 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:
- grids, columns, blocks;
- templates, fixed, rubber and others;
- graphics, fonts and their descriptions;
- media, picture and movie management;
- tables, normal layout, sorting, new functionality;
- forms, design of input fields, related events, names;
- navigation, tabs, tabs, pages, menus, panels;
- alerts, dialogs, tooltips, floating elements.
This framework declares great creative freedom for the programmer who takes advantage of this wonderful development experience from Twitter. All this is wonderful, important and interesting, but all this must be carefully studied before the declared capabilities become available to the developer.
Bootstrap, its followers and competitors
Indeed, a developer armed with Bootstrap, Foundation, Kube, Semantic UI, Uikit, UniCSS, Maxmertkit, ... may well work according to the 10/12 formula instead of the 1`000 / 100`000 formula (manual work) + Pi factor. Figuratively speaking, CSS frameworks save project development time from infinity or a large number of hours (manual work), up to 10-12 hours for any project.
Remembering that before the egg is laid, even the chicken will have to decently decoy it, it can be assumed that the difference in development time cannot go anywhere, it goes away while studying the framework, choosing which one to take, and a lot of other time-consuming, distant from the development process.
An experienced developer will agree that even a day is not possible to make a decent site. Human intelligence works faster than any computer, but its conscious part - very slowly and carefully weighs everything before making even a very simple decision. The quantity and quality of modern tools used absolutely does not mean anything and guarantees absolutely nothing.
A modern site is far from a set of pages showing adaptive layout. The concern of absolutely any site is not to show how smart its developer is and what the best CSS frameworks are in his arsenal, but to execute the functionality required by the customer.
Adaptability in fact and in fact
The problem requires a solution - this is an unshakable rule. Developing the basics of adaptability and cross-browser compatibility, a thesis on rubber typesetting with analytical tabs on one or another “type” of rubber is an interesting lesson, but nothing more. Responsive CSS, HTML, JS frameworks are promising, but depending on the context, this perspective should be considered.
There is an understanding of the required functionality. There is certainty that the resource should work on a computer and on a smartphone. But this does not at all follow that the adaptive layout task is more important than the functional implementation problem.
One cannot demand the same from a horse and a pony: pulling the same strap with the same success. It makes no sense to carry potatoes even on a maize (an aircraft, very popular in the era of developed socialism), when a field is within reach. Here even that same pony will manage alone.
The term “adaptive” in the native meaning of this word does not mean that something must be done something as he 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 dialogs is a real utopia, if the goal in solving the task is a completely different matter.
Historical moment and perspective
Programmers are developing very quickly, and exponentially - this 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 it’s not enough to separate, you need to know correctly where the necessary edge is.
These three points (interface, code, facet) are only part of the general information entity. There is also data and the problem of their presentation. It only at first glance it may seem that the data and CSS frameworks are not at all interconnected. In fact, a representation is always determined not only by the code, but also by what it processes and how it does it, first of all, in time.
When deciding to use CSS frameworks, choosing one or the other, evaluating the development time and comparing its functionality with what is required to solve the problem, it should be understood that it is not the framework itself that matters, but only the fact that the problem posed in the past is again gained importance. It is important to understand in which direction the development of the problem and its solution are going.
About Tips, Advisers, and Evaluation Plans
In reality, with an understanding of the issue, who can be trusted and who cannot, who should be given advice and who should not, problems never arise. But in the virtual space there are serious difficulties with this.
Each programmer (especially the collective thereof) has experience. This experience, to one extent or another, is its own framework. Before you accept someone else's faith, even a very popular and wonderful one, you need to put yourself in the position of a researcher, but not a follower.
The experience of colleagues is never the fundamental basis for work, especially in such a dynamic field as informational, but a good incentive for the development of their own knowledge and experience.
Even if one is not destined to achieve something, nothing prevents learning the experience of others. With any development of events, the personal experience and the experience of colleagues in the specialty is better than only their own experience, and the plans for this will definitely be more promising and real.