A few hints can be found in various code style guides, but the only way to learn to write good code and comments is to
read good and bad examples of other people's code, and to practice.
I use Info-Zip, the third most portable program in the world. Info-Zip compiles on every know variety of Unix, and binaries are available for the most popular platforms.
Linux is able to install BSD ports packages if they are downloaded from Freshports and the specific application is compatible with Linux. Packages themself contain a Makefile to fetch the tarball, verify the checksum, extract, and install. Ports can also be installed from/stand/sysinstall. Very convenient.
Since Britain passed its Regulation of Investigatory Powers (RIP) Bill, security experts have examined the technology behind the e-mail snooping that is allowed in the law. Allegedly, the technology is extremely easy for savvy computer users to avoid (i.e. the sort of people that the government hopes to catch in illegal acts). If the cybercriminals can bypass the tap with ease, then whose e-mail gets scanned? Answer: ordinary people. That's why a number of experts are explaining to citizens what steps are necessary to remain invisible to the RIP's black boxes.
U.S. scientists have collaborated to describe why it is that the net is resilient to random failures but highly vulnerable to deliberate attacks. As the net has sprawled in many directions, its growth path has not led to a random or exponential network. Rather, the pattern that has taken shape resembles the ordered hierarchy of a tree whereby a few nodes are highly connected and lead to scores of less connected nodes. While this design allows the net to chug its way through random hiccups, it makes an attack on one of the key nodes particularly damaging.
FreeBSD is actually the most high-performace server operating system. This is what FreeBSD vs. Linux vs. NT has to say about Linux and FreeBSD performance:
:) FreeBSD is the system of choice for high performance network applications. FreeBSD will outperform other systems when running on equivalent hardware. The largest and busiest public server on the Internet, at ftp.cdrom.com, uses FreeBSD to serve more than 800GB/day of downloads. FreeBSD is used by
Yahoo, USWest, Xoom.com and many others as their main server OS because of its ability to handle heavy network traffic with high performance and rock stable reliability.
And Linux:
:| Linux performs well for most applications, however the performance is not optimal under heavy network load.
The network performance of Linux is 20-30% below the capacity of FreeBSD running on the same hardware as Linux. As long as you are not trying to squeeze the last ounce of performance out of your hardware, or performing mission critical transactions, Linux is a very good choice for a server OS.
Windows NT has this description (Windows 2000 is NT 5.0):
:( Windows NT is adequate for routine desktop apps, but it is unable to handle heavy network loads. A few organizations try to make it work as an Internet server. For instance, barnesandnoble.com uses Windows-NT, as can be verifyed by the error messages that their webserver produces, such as this recent example:
Error Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Can't allocate space for object 'queryHistory' in database 'web' because the 'default' segment is full. For their own "Hotmail" Internet servers, Microsoft uses FreeBSD.
This page explains well what is a geek. Some of the most interesting tidbits where:
"But just what is a geek?" you ask. Well, I'll tell you. At least, I'll tell you my definition... which may be different from "general usage" of the term, webster's definition, and even the definition used by other geeks.
A geek is someone who spends time being "social" on a computer. This could mean chatting on irc or icb, playing multi-user games, posting to alt.sex.bondage.particle.physics, or even writing shareware. Someone who just uses their computer for work, but doesn't spend their free time "on line" is not a geek. Most geeks are technically adept and have a great love of computers, but not all geeks are programming wizards. Some just know enough unix to read mail and telnet out to their favorite MUD.
...
Geek can also be used as a verb. "To geek" is to sit online and read mail, news, chat, and otherwise waste time in front of a keyboard. This "geeking" often consumes many hours, even if the intention was to "just log in and check my mail." Some would say this time would be better spent being social in person or even just being curled up in a sunbeam.
So yes, there are girl geeks, in chatrooms everywhere. In the fashion section of AOL. In a barbie discussion forum. Some might even be technically competent.
HTML is really a mess. According to the W3C, tags should be used to represent the structure of the document and style sheets should be used for how a page should look. Originally however, tags where used for everything. To provide backwards compatibility while still being valid HTML 4.0, the HTML 4.0 Transitional DTDs can be used:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
This declares the document to be HTML 4.0 Transitional. HTML 4.0 Transitional includes all elements and attributes of HTML 4.0 Strict but adds presentational attributes,
deprecated elements, and link targets. HTML 4.0 Transitional recognizes the relatively poor browser support for style sheets, allowing many HTML presentation features [such as BORDER] to be used as a transition towards HTML 4.0 Strict.
Of course, you can always use HTML 3.2 or HTML 2.0 DTD, but they lack features like tables.
IE seems to not support the CSO phone book protocol. CSO runs on top of Gopher and is not an integral part of Gopher. CSO is trivial to implement, no suprise Microsoft did not.
WinInet supports retreiving of files using Gopher, what the client does with the data is up to the client. Netscape, however, supports CSO.
Every major web browsers support Gopher, there's no reason not to use it. Gopher pages tend to be more content-rich than web pages -- Gopher simply does not allow Zero-Content sludge.
I see useless web sites all the time. Some newbie puts together a page with links to a few well-known web sites and publishes the trash on the World Wide Web, usually using a free web hosting service. Apatheticy to follow the HTML standards, unreadable fonts, annoying security JavaScript/VBScript/ActiveX/Java security holes, and eye burning colors are what make most of the web so ugly.
Admittedly, the World Wide Web is much more flexible and powerful than Gopher. Gopher is inferior to WWW. However, with power comes resposibility. ~99% of all web publishers are not resposible enough to follow the standards and make operable pages. Too many web pages suck.
Gopher does not give the publisher power to publish pages that suck. Gopher's directory listing makes this simply not possible. Of course, someone could host a Gopher site listing nothing, but what would be the point of that? I have never connected to a horrible Gopher site, and I have connected to thousands of horrible WWW sites.
Gopher serves what matters -- pure information. The original version of Gopher, now sometimes known as Gopher0, supports only a few data types, the most frequently used being text. (Gopher+ uses MIME content types, however). What other content types do you need than text? On the other hand, the World Wide Web is able to represent tables, frames, links, and many other useless features. Gopher is so simple and unbloated unlike HTML and the WWW.
The WWW sucks, because it can. Gopher will never suck.
The question is, will Gopher take off? Not a chance. Gopher will remain used by a select few, unlike the WWW. It will never have the trillions of zero content "homepages" and commericialization the WWW has. And frankly, I like it that way. Ever seen an advertisement on a Gopher server?
You can make your own barcodes online here.
I use Info-Zip, the third most portable program in the world. Info-Zip compiles on every know variety of Unix, and binaries are available for the most popular platforms.
Wotsit's Format has the JAR file format specifications. Java supports class file storage in ZIP archives also, but they're not the same thing.
Linux is able to install BSD ports packages if they are downloaded from Freshports and the specific application is compatible with Linux. Packages themself contain a Makefile to fetch the tarball, verify the checksum, extract, and install. Ports can also be installed from /stand/sysinstall. Very convenient.
This page explains well what is a geek. Some of the most interesting tidbits where:
So yes, there are girl geeks, in chatrooms everywhere. In the fashion section of AOL. In a barbie discussion forum. Some might even be technically competent.HTML is really a mess. According to the W3C, tags should be used to represent the structure of the document and style sheets should be used for how a page should look. Originally however, tags where used for everything. To provide backwards compatibility while still being valid HTML 4.0, the HTML 4.0 Transitional DTDs can be used:
Of course, you can always use HTML 3.2 or HTML 2.0 DTD, but they lack features like tables.<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
IE seems to not support the CSO phone book protocol. CSO runs on top of Gopher and is not an integral part of Gopher. CSO is trivial to implement, no suprise Microsoft did not.
WinInet supports retreiving of files using Gopher, what the client does with the data is up to the client. Netscape, however, supports CSO.
Cheers,
qbasic programmer
Every major web browsers support Gopher, there's no reason not to use it. Gopher pages tend to be more content-rich than web pages -- Gopher simply does not allow Zero-Content sludge.
I see useless web sites all the time. Some newbie puts together a page with links to a few well-known web sites and publishes the trash on the World Wide Web, usually using a free web hosting service. Apatheticy to follow the HTML standards, unreadable fonts, annoying security JavaScript/VBScript/ActiveX/Java security holes, and eye burning colors are what make most of the web so ugly.
Admittedly, the World Wide Web is much more flexible and powerful than Gopher. Gopher is inferior to WWW. However, with power comes resposibility. ~99% of all web publishers are not resposible enough to follow the standards and make operable pages. Too many web pages suck.
Gopher does not give the publisher power to publish pages that suck. Gopher's directory listing makes this simply not possible. Of course, someone could host a Gopher site listing nothing, but what would be the point of that? I have never connected to a horrible Gopher site, and I have connected to thousands of horrible WWW sites.
Gopher serves what matters -- pure information. The original version of Gopher, now sometimes known as Gopher0, supports only a few data types, the most frequently used being text. (Gopher+ uses MIME content types, however). What other content types do you need than text? On the other hand, the World Wide Web is able to represent tables, frames, links, and many other useless features. Gopher is so simple and unbloated unlike HTML and the WWW.
The WWW sucks, because it can. Gopher will never suck.
The question is, will Gopher take off? Not a chance. Gopher will remain used by a select few, unlike the WWW. It will never have the trillions of zero content "homepages" and commericialization the WWW has. And frankly, I like it that way. Ever seen an advertisement on a Gopher server?
Seriously how hard is it to get up and take a walk?
One Time Pads have been around forever.
BASIC is the best programming language out there! I don't know where i'd be without it.
A .qb TLD would be nice.
Yep, but those BIOSs where not open source.
The site is Slashdotted. Google cache is here.
-qbasicprogrammer
Who fixed it when it breaks down in space? :)
QBasic robots perhaps?
Including a QBasic OS?
..it runs QBasic?
..a QBasic BIOS.