Welcome to turystyczny.org

The History of Writing (history of writing) Writing is commonly used by billions of people each day. However, many of us don’t know the history of writing, and some of us would rather not ponder it for fear of getting a headache. Written communication is much needed today, and many societies could not survive without writing. Writing has a history like everything that is in existence today. The exact history of this form of communication may be clouded and even over exaggerated at times, but there are two known facts, writing has been used for a very long time and writing will be used for a very long time. The true beginning of writing is unknown, but it does have a comprehensive history. The first artistic paintings and writings were said to be done in the form of naturalistic paintings of animals and people in caves. The pictures were known as attempts to appease the spirits of animals that were needed to kill in the hunt. In ancient times pictures were also done of human beings. These pictures of humans were typically done in series, with a figure appearing in different physical positions progressively, which represented positions a ceremonial dance performed by ancient people. Progressively, the early societies began to stylize their messages, which were similar to using symbols to represent restrooms, handicap-accessible places, and international road signs. These stylized symbols are known a petroglyphs and hieroglyphs. The most famous system of hieroglyphs belonged to the ancient Egyptians who had hieroglyphics that were partially representational pictures that were stylized. Petrogylphs were often used by Native Americans as messages along trade routes, ritual information, and various other things. However, they were not as sophisticated as hieroglyphs. During this ancient period, Europeans preserved esoteric knowledge in runes and in an alphabetic writing system known as ogham. The Chinese culture also has a place in the history of writing. The culture began by writing like many others by using pictures then slowly moving to stylized pictures. However, over time the pictures became less representational and more abstract. Today, Chinese, Japanese, Korean, and other Asian languages are written with the use of ideeographs. An ideeograph is used to represent an idea instead of a word. Around 1700 B.C. a new form of writing appeared in the Middle Eastern cultures. During this time, the Phoenicians created an alphabet. This development was different from all others because the symbols represented sounds, not pictures or ideas. The combinations of sounds made up the words of the language, which was crucial in the history of writing. The alphabet developed by the Phoenicians spread to Northern Africa and became the system of the Arabs, and spread northwest to Greece. The Greek developed their own letters, which were modified even more to become the Cyrillic alphabets of Russia, the Balkans and the Romans. The Romans modified the alphabet and made it the alphabet that is recognized today. The history of writing developed even further into the 20th century. Following World War II, the Japanese and Chinese began to use the alphabet to represent the sounds of their languages. For these Asian cultures, the alphabetic system was easier to write by hand and to print economically, so it made life far simpler for those cultures. The artistic form of writing used by these Asian cultures will likely never die, but there are many advantages to using an alphabetic system, and many modern people of these cultures benefit handsomely from learning to read and write using the current alphabet. The history of writing is long and sometimes vague, but it can be seen as a necessary teaching that will help modern societies understand the importance of written communication, and understand how the world would be forever changed without it.

Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience.

Web Hosting - Unix vs Windows-Based Hosting, Which Is Better? An operating system functions largely out of sight, or at least is supposed to. It doesn't matter to non-geeks how a file gets stored, or how memory is used, or how simultaneous processes share the limited resources available on a computer. These are among the basic functions of any operating system. Yet, you can find very passionate supporters - who offer very detailed lists of pros and cons - for every operating system. Why? Because, though the low-level functions of an operating system do their work out of sight, there are many other features that rise to visibility. Sometimes, they do so when they're not supposed to. Weighing the pros and cons objectively could consume a book. But to select a web host operating system, a manageable level of considerations apply. They can be weighed even by those who don't know a processor queue from a pool cue. Learning Curves For most web site owners, administering the site/server is just overhead. It's not something they take pleasure in doing and they have plenty of other things to worry about. Many wouldn't know how and have no interest in learning (rightly so, given their priorities). Consequently, ease of administration is paramount for such people. Whether a Unix-based site (usually Linux these days) is easier to administer than Windows depends on your current skill set and the type of tools and level of access the web hosting company provides. But in general Linux is more difficult to install and maintain than Windows and the learning curve is steeper. FTP and Control Panels Often, you don't have to care. For many, the operating system is fairly transparent. FTP file transfers to get a new web page up to a Windows server are very much like they are to a Linux-based site. The user/administrator simply doesn't see what's behind the curtain. Many companies provide other utilities that completely mask any awareness of the operating system underneath. When that's the case, the web site owner has no reason to care, until or unless they need or want to go 'inside the black box'. Performance Performance issues can be relevant in selecting which operating system host type to choose. But for the most part, that aspect is outside the web site owner's control. Overall performance can be good or bad on either system, depending on many factors that the publisher will rarely see. The issue is a wash, as far as tipping the scales is concerned. What is more likely to be seen by a web site owner, at some point in their (and their site's) development is the database product that can be used to store information. Databases Microsoft SQL Server is relatively simple to use, yet extremely powerful and can deliver great performance. But it doesn't run on Linux. At least, not without special software to emulate Windows, which usually kills performance. On the other hand, with a bit of time invested, MySQL isn't significantly more difficult to learn than MS SQL Server and there are many free installations. Cost may well outweigh other considerations for most on this issue. Programming Languages Last, but not least, there are differences in programming languages that can be (or at least typically are) used on Windows vs Unix. If you have programmers who are skilled in Visual Basic, ASP and other Microsoft technologies, then a Windows-based host will be your preferred choice. For Perl and PHP programmers, Linux is the more common platform of choice. No single factor can push you to one versus the other operating system. And, in the long run, it isn't the primary consideration, unless you just enjoy playing with operating systems.