No! they cannot touch my graphics card! It is a necessary part of my system and I will not go console-less until the cranial interface is developed by Lt. Reginald Barkley.
Unfortunate for you. Not all of us college types are the stick in the ass your post suggests you boss may be. In our shop, clinging to legacy anything is just another way to look for trouble.
Let's see here, my real name is Dogbert K. Hosehead, Jr. and I have to hire somebody to be my [your favorite toy here] administrator.
I have a choice between Dilbette A. who has a degree and, Dilbert B. who has a high school education, plays a mean game of Quake and pretty much ran the schools network for 3 of his 4 high school years.
1) D.A. gets chosen because, although she has less hands on experience she DOES have lots of thought process training that will come in real handy when something wierd goes down and it's not covered in any of the tech guides.
2) D.A. gets chosen because it's well known that this person is going to be assigned to a bunch of special working groups and we know that college professors just love to make group assignments with this in mind. D.A. has experience either getting Butthead Bill to carry his weight or distributing Bill's responsibilities so the project still comes in on schedule.
3) Even if D.A.'s degree is not a complete match for the skills I require I know that the college experience has given her certain time management skills that D.B. probably doesn't have yet.
The short answer: If at all possible, go to college. Find relevant work on the side to help pay your way through school, co-op, or anything at all that will help to beef up your resume but, even a Music Education degree can get you hired as a systems operator ahead of lots of computer experience but no degree. (Actually been there and done that.)
Actually, not. There's the normal page that 99% of users will use but through effective use of SSI it doesn't have to be duplication of effort at all.
If your default design requires Javascript, include a <noscript> <meta http-equiv="refresh" content="0;http://server.domain.com/texthome.html"/> </noscript> in the HEAD.
This will send all of the folks with no scripting to the page that has none. The very first thing that should appear on the default page is a link to the text-only version. This is for the benefit of non-sighted users who are using a browser that processes the scripting. This should appear first because you don't want them to have to wait while their screen reader recites the entire page before they get to the one piece they really need to function.
Yes, by all means "know your audience." But, remember that unless you are going to authenticate your entire audience there will be other people coming to your site.
Why not? Granted, 802.11b would never be sufficient for Pink Floyd or Metallica but, if you went with 802.11a you might have something going.
On-board you would have to take the native analog signal and digitize it but hey, isn't that what MIDI is for? Build in a few extra synthesizer channels and you can make that Stratocaster sound like the Boston Pops.
On the networking side, config your network to be restricted to the actual hardware addresses of the WNICs in the equipment inventory and you should be able to lock out most or all unwanted activity.
If it's been produced anytime since 1923 - somebody holds copyright on it.
The real issue that nobody is talking about is licensing. Yes, the New York Times and/or the original author holds copyright on all of that stuff. However, under the conditions for access to the NYT website they have granted you license to access that material online. They have not granted you license to download (read this as "save") and redistribute any of their IP.
It seems the real problem for Aussie ISPs is to identify the original source for anything served through them and to go after the account owners who allegedly violate copyright law.
A truely ethical person would contact the accidental sender with the information.
However, depending on the company, and the product in question, this may be your opportunity to really score some big chash in a couple of ways.
Use the insider information to better your position on the stock market.
Send the company a letter saying something like "it will cost you $75,000.00 plus taxes for me to keep my mouth shut."
If it's Microsoft, go for option 2, set an at job that posts the information anonymously to several forums at the same time you are in the meeting to sign the ream of legal documents they will want you to sign. Purge your system logs immediately upon your return.
Code commentary is like sex. If it's good, it's VERY good.
Loud and clear and as if we are all one voice, everybody tell them how completely, utterly, and in all other ways stupid this is.
I can here it now...Stu-pid! Stu-pid! Stu-pid!... You get the point.
There ain't no way in bloody freakin' hell they can target this thing with enough accuracy to make it worth their while. One innocently slipped decimal place or one graduate student intern using the wrong unit of measure and the asteroid you intended for the Presidential Palace in Baghdad lands in the Knesset.
Code commentary is like sex. If it's good, it's VERY good.
It was produced and reviewed in an open forum. Technically, in Copyrightland that counts as publishing. There may exist records of at least meeting schedules or agenda that show the development of this product. That should be sufficient to prove that the Microsoft patent is not based on an original concept.
Code commentary is like sex. If it's good, it's VERY good.
I buy a new computer for a specific purpose in my organization... It's going to be a dedicated [yadda yadda yadda] server with no other functionality needed.
So, I unbox and assemble it, connect all the cables including the LAN ethernet line and the modem for the one outside connection in my tiny little company. On first-boot the system detects my LAN and tries that to connect to the software server. The LAN fails to connect to the designated target (Duh! It's internal access only.) so the system autodetects, installs, and configures my modem for the task.
Here's where the fun starts! This box is roughly 12,000 feet from the nearest telco CO. Even with my spiffy new 56K/V90/X.2/V.Fast... modem my maximum connection speed is consistently around 21,600 bps. Assuming a connection can be maintained for the full download it will be about 3 weeks before everything is downloaded and installed!
After I have waited about three weeks for my now geriatric system to install what somebody else thinks I need, I can go about the task of uninstalling the stuff I don't want, unsubscribe from the automatic updates that won't be needed because none of that stuff is installed anymore anyway, and install the one application I truly need.
This type of service will never be successful so long as we are still transferring data through a bottleneck.
Code commentary is like sex. If it's good, it's VERY good.
There was once a time when Novell (I'll get to the Corel relevance in a moment) owned, in addition to Netware (a perfectly respectable networking thingie in its own right):
DR (Digital Research) DOS ("A better DOS than DOS"), and
WordPerfect (including the bulk of the WP suite)
Additionally, they had reasonably good relations with Corel, famous for their Draw product.
It would have taken only a few KLoC (K Lines of Code) to integrate the lot or, make the pieces talk to each other but, Novell couldn't decide whether to shit or get off the pot. So, they flushed DR DOS down the can seeing that Windows had just made it's first big surge in the market and, sold WordPerfect to Corel for a fraction of original cost. One major opportunity to produce competition for "the collective" lost.
So now Corel has WordPerfect, a perfectly good non-collective product and ditches their up-and-coming OS, once again terminating (at least part of) another opportunity to compete with "the collective."
On days like this I am really thankful that Linux does not live or die because of one person or one company.
Code commentary is like sex. If it's good, it's VERY good.
... however, they can't sell said mod without getting the permission...
Actually, (IANAL) you can't even distribute. Distribution is publication... is (C) infringement.
Example: Johnny likes bikes. Johnny builds a website about bikes with all sorts of neat links and stuff and includes a page that quotes from the [your state here] legal code as published by Banks Baldwin Publishing. Sooner or later Johnny gets a C&D letter from BBP due to the BBP(C) on their publication. No money was ever transferred to or solicited by Johnny but, the C&D order holds because BBP stands to lose financially due to Johnny's web site.
Think it can't happen? Think again. It happened to me.
Code commentary is like sex. If it's good, it's VERY good.
When you work in a university library this question comes up a lot. Really, on a weekly basis sometimes. The entire concept of fair use is designed to facilitate the academic community (both in the university setting and for private/corporate research) for the advancement of science, knowledge, the human condition, what have you... without infringing unduly on the intellectual and other rights of the owner of a particular piece of intellectual property.
Unless stated specifically, the images, names, phrases, story lines, yadda yadda yadda of pretty much anything are considered to be intellectual properties. Any unauthorized use of those properties is itself justification for cease and decist orders and/or other legal action by or on behalf of the rightful owner. That said, unless you're using these images, names, yadda yadda... for research purposes only, your usage probably doesn't meet the criterion for "fair use."
As a starting resource for our faculty, staff, and students our library website includes the following information:
FAIR USE, 17 U.S.C 107
Fair Use is a limitation that allows reproduction in certain instances, without securing the copyright owner's permission. Fair Use acknowledges the importance of educational use of copyrighted works, by allowing reproduction for purposes such as criticism, comment, news reporting, teaching, (including multiple copies for classroom use), scholarship, and research.
Materials that meet the four factors of fair use may be used without obtaining copyright permission.
Four factors must be examined on a case-by-case basis, weighed, and balanced to determine whether copying represents fair use. The courts have maintained that no single factor is determinative. The four factors are:
Purpose and character of the use, including whether such use is of a commercial nature or is for nonprofit educational purposes
Nature of the copyrighted work
Amount and substantiality of the portion used in relation to the copyrighted work as a whole
Effect of the use upon the potential market for or value of the copyrighted work.
The fact that a work is unpublished does not itself bar a finding of fair use if such finding is made upon consideration of all of the above factors. [17 U.S.C. 107 (1994)].
Code commentary is like sex. If it's good, it's VERY good.
Actually, PDF documents generated directly to PDF and not scanned first are fairly small. This is a format for scanned documents that knocks the socks off of PDF. On average a DjVu file from a scanned document will be 1/5 the size of its PDF equivalent. I have actually achieved compression down to 1/15 the size of the similar PDF.
Code commentary is like sex. If it's good, it's VERY good.
Picture this: Start with a 15th century Flemish "Book of Hours", hand illuminated on vellum (goat skin). Scan it at 600dpi 24bit for archival purposes. Reduce your tiffs to 300dpi and you still have 1.06 GB of image data (not very downloadable). Using the DjVu compressor we achieved 205:1 compression so the final product totals 5.44MB. By separating the pages so they only download when called for the initial download is a mere 45.06KB (including all of the HTML and other images on the page) with an average download of subsequent pages only 21.34KB.
DjVu was developed by AT&T Research. It was then purchased by LizardTech last year.
Code commentary is like sex. If it's good, it's VERY good.
That's a "she-bang" with 6 lines of Perl!
No! they cannot touch my graphics card! It is a necessary part of my system and I will not go console-less until the cranial interface is developed by Lt. Reginald Barkley.
Unfortunate for you. Not all of us college types are the stick in the ass your post suggests you boss may be. In our shop, clinging to legacy anything is just another way to look for trouble.
Of course, if you really are a geek you'll read this as
'Think about "down the road (there is) a piece."'
Apologies to Scott Adams.
Let's see here, my real name is Dogbert K. Hosehead, Jr. and I have to hire somebody to be my [your favorite toy here] administrator.
I have a choice between Dilbette A. who has a degree and, Dilbert B. who has a high school education, plays a mean game of Quake and pretty much ran the schools network for 3 of his 4 high school years.
1) D.A. gets chosen because, although she has less hands on experience she DOES have lots of thought process training that will come in real handy when something wierd goes down and it's not covered in any of the tech guides.
2) D.A. gets chosen because it's well known that this person is going to be assigned to a bunch of special working groups and we know that college professors just love to make group assignments with this in mind. D.A. has experience either getting Butthead Bill to carry his weight or distributing Bill's responsibilities so the project still comes in on schedule.
3) Even if D.A.'s degree is not a complete match for the skills I require I know that the college experience has given her certain time management skills that D.B. probably doesn't have yet.
The short answer: If at all possible, go to college. Find relevant work on the side to help pay your way through school, co-op, or anything at all that will help to beef up your resume but, even a Music Education degree can get you hired as a systems operator ahead of lots of computer experience but no degree. (Actually been there and done that.)
Need I go on?
Conversely, it is also true that when bad IT and government meet everybody still loses.
thus, the real challenge here is to have both good IT and good government.
Actually, not. There's the normal page that 99% of users will use but through effective use of SSI it doesn't have to be duplication of effort at all.
" />
If your default design requires Javascript, include a
<noscript>
<meta http-equiv="refresh" content="0;http://server.domain.com/texthome.html
</noscript>
in the HEAD.
This will send all of the folks with no scripting to the page that has none.
The very first thing that should appear on the default page is a link to the text-only version. This is for the benefit of non-sighted users who are using a browser that processes the scripting. This should appear first because you don't want them to have to wait while their screen reader recites the entire page before they get to the one piece they really need to function.
Yes, by all means "know your audience." But, remember that unless you are going to authenticate your entire audience there will be other people coming to your site.
Why not? Granted, 802.11b would never be sufficient for Pink Floyd or Metallica but, if you went with 802.11a you might have something going.
On-board you would have to take the native analog signal and digitize it but hey, isn't that what MIDI is for? Build in a few extra synthesizer channels and you can make that Stratocaster sound like the Boston Pops.
On the networking side, config your network to be restricted to the actual hardware addresses of the WNICs in the equipment inventory and you should be able to lock out most or all unwanted activity.
Look at this - the documentation re: a license disagreement with Adobe is presented in PDF!
As indicated above, the reason for the closing of source is the J2EE license from Sun. All complaints should be addressed to Sun Microsystems.
The real issue that nobody is talking about is licensing. Yes, the New York Times and/or the original author holds copyright on all of that stuff. However, under the conditions for access to the NYT website they have granted you license to access that material online. They have not granted you license to download (read this as "save") and redistribute any of their IP.
It seems the real problem for Aussie ISPs is to identify the original source for anything served through them and to go after the account owners who allegedly violate copyright law.
However, depending on the company, and the product in question, this may be your opportunity to really score some big chash in a couple of ways.
- Use the insider information to better your position on the stock market.
- Send the company a letter saying something like "it will cost you $75,000.00 plus taxes for me to keep my mouth shut."
If it's Microsoft, go for option 2, set an at job that posts the information anonymously to several forums at the same time you are in the meeting to sign the ream of legal documents they will want you to sign. Purge your system logs immediately upon your return.Code commentary is like sex.
If it's good, it's VERY good.
Code commentary is like sex.
If it's good, it's VERY good.
Code commentary is like sex.
If it's good, it's VERY good.
This is why I now listen to foreign radio at work.
Feel free to chime in with yours...
Code commentary is like sex.
If it's good, it's VERY good.
I can here it now...Stu-pid! Stu-pid! Stu-pid! ... You get the point.
There ain't no way in bloody freakin' hell they can target this thing with enough accuracy to make it worth their while. One innocently slipped decimal place or one graduate student intern using the wrong unit of measure and the asteroid you intended for the Presidential Palace in Baghdad lands in the Knesset.
Code commentary is like sex.
If it's good, it's VERY good.
Code commentary is like sex.
If it's good, it's VERY good.
Code commentary is like sex.
If it's good, it's VERY good.
This type of service will never be successful so long as we are still transferring data through a bottleneck.
Code commentary is like sex.
If it's good, it's VERY good.
- DR (Digital Research) DOS ("A better DOS than DOS"), and
- WordPerfect (including the bulk of the WP suite)
Additionally, they had reasonably good relations with Corel, famous for their Draw product.It would have taken only a few KLoC (K Lines of Code) to integrate the lot or, make the pieces talk to each other but, Novell couldn't decide whether to shit or get off the pot. So, they flushed DR DOS down the can seeing that Windows had just made it's first big surge in the market and, sold WordPerfect to Corel for a fraction of original cost. One major opportunity to produce competition for "the collective" lost.
So now Corel has WordPerfect, a perfectly good non-collective product and ditches their up-and-coming OS, once again terminating (at least part of) another opportunity to compete with "the collective."
On days like this I am really thankful that Linux does not live or die because of one person or one company.
Code commentary is like sex.
If it's good, it's VERY good.
Example: Johnny likes bikes. Johnny builds a website about bikes with all sorts of neat links and stuff and includes a page that quotes from the [your state here] legal code as published by Banks Baldwin Publishing. Sooner or later Johnny gets a C&D letter from BBP due to the BBP(C) on their publication. No money was ever transferred to or solicited by Johnny but, the C&D order holds because BBP stands to lose financially due to Johnny's web site.
Think it can't happen? Think again. It happened to me.
Code commentary is like sex.
If it's good, it's VERY good.
Unless stated specifically, the images, names, phrases, story lines, yadda yadda yadda of pretty much anything are considered to be intellectual properties. Any unauthorized use of those properties is itself justification for cease and decist orders and/or other legal action by or on behalf of the rightful owner. That said, unless you're using these images, names, yadda yadda... for research purposes only, your usage probably doesn't meet the criterion for "fair use."
As a starting resource for our faculty, staff, and students our library website includes the following information:
FAIR USE, 17 U.S.C 107
Fair Use is a limitation that allows reproduction in certain instances, without securing the copyright owner's permission. Fair Use acknowledges the importance of educational use of copyrighted works, by allowing reproduction for purposes such as criticism, comment, news reporting, teaching, (including multiple copies for classroom use), scholarship, and research.
Materials that meet the four factors of fair use may be used without obtaining copyright permission.
Four factors must be examined on a case-by-case basis, weighed, and balanced to determine whether copying represents fair use. The courts have maintained that no single factor is determinative. The four factors are:
- Purpose and character of the use, including whether such use is of a commercial nature or is for nonprofit educational purposes
- Nature of the copyrighted work
- Amount and substantiality of the portion used in relation to the copyrighted work as a whole
- Effect of the use upon the potential market for or value of the copyrighted work.
The fact that a work is unpublished does not itself bar a finding of fair use if such finding is made upon consideration of all of the above factors. [17 U.S.C. 107 (1994)].Code commentary is like sex.
If it's good, it's VERY good.
Code commentary is like sex.
If it's good, it's VERY good.
Picture this: Start with a 15th century Flemish "Book of Hours", hand illuminated on vellum (goat skin). Scan it at 600dpi 24bit for archival purposes. Reduce your tiffs to 300dpi and you still have 1.06 GB of image data (not very downloadable). Using the DjVu compressor we achieved 205:1 compression so the final product totals 5.44MB. By separating the pages so they only download when called for the initial download is a mere 45.06KB (including all of the HTML and other images on the page) with an average download of subsequent pages only 21.34KB.
DjVu was developed by AT&T Research. It was then purchased by LizardTech last year.
Code commentary is like sex.
If it's good, it's VERY good.