At the Neon Cactus at Purdue, on Thursdays, a 36 oz Old Style is 10 cents. You have to buy the cup once, for $1.50, but you can bring it back every week. On Mondays, another bar called Where Else has bottles (Miller Lite, Bud Lite, or Coors Lite) for 25 cents. You walk in, plunk down 6 bucks, and the bartender hands you a case of bottles in ice. This is one of many reasons I am proud to be American.
And I, as a matter of fact, happen to like American beer.
Furthermore, I have been on few long vacations that I truly enjoyed. People in the U.S. also take advantage of 3 day weekends. With flying as cheap as it is, you fly somewhere Thursday night, and return late Sunday night. Great way to spend a weekend partying and getting some sun on the beach.
I think people that have been out in the real world for a while don't realize how many languages are taught in school's today. I'm in Purdue's computer engineering program, and so far, I have had to learn c, c++, fotran, java, asm, python, bash, and ksh. I'm sure there are some others I have forgotten (like the little bit of perl I know). We also learn ABEL and VHDL, several version control systems and Makefiles. My roommate is taking an AI course right now which is all in scheme. People talk about the old days like their is lost knowledge, we still learn all that. I could write ATARI games in asm if I wanted to, but why do that when tools are available that let me do so much more? For learning, we don't have to learn assembly first anymore, you can start with any language. I think it is good to take a two pronged approach. Learn C first, and at the same time, start learning digital logic. C compilers are forgiving, and warn about obvious errors compared to assembly just doing exactly what you tell it do. When one is comfortable with both, I think learning assembly is much easier. Without this prior knowledge, you are just doing what you are told to do, you do not really understand it, and when you make mistakes, you have a harder time understanding why. After learning asm, it is easier to think like the machine, and easier to write efficient code in other languages.
There is one key differance however, the size of your living quarters. I live in an apartment where rent is $700 a month, and it is tiny ~700 square feet. A $100,000 house in Lafayette IN is on the order of 1200-1500 square feet, By your mortgage rates, my monthly payment for a house twice as large as my apartment would be $592.50. So my house would be twice as large as my apartment, and that $100 less I paid per month would offset the differance in property taxes. Now, when it comes time for me to leave Lafayette IN, I have something to show for my money, as opposed to rent which is thrown away. The key here is to compare similar living spaces, of course a large house is more expensive than a small apartment. You may ask, why am I renting? If I was going to be here more than 4 years, I wouldn't. When I moved here I was 18 and did not have the credit to purchase a home. There are also real estate fees for buying and selling.
Alright, let me be the first to say: WTF? Sorry big guy, I dont know if your trolling, dont speak english, or just have no idea what your asking, and cant be bothered to fix your broken keyboard.
With that said, a kernel that provides more performance will allow a slow machine to do more work in a said time period. It should be noted than none of these tests said anything about XFree86 performance, and that is the number one thing that will make a slow machine "feel" faster.
I work with a bunch of embedded applications developers, and I know of only one other guy who builds his own machine. First off, they view their time as valuable. Every minute they can spend with their families is worth it, and building a machine can be time consuming. Pricing out parts, and getting up to date knowledge can take a lot of research. Second, as people get older, it seems they just don't want to mess with it. This is synonymous to old cars. Young people will tend to buy cars and restore them, while many older people will prefer to buy the car already restored. It costs more money, but they don't have to mess with it. Finally, with computers, when you buy legal software, I don't think you save any money when building your own, and most people want the warranties and one source of support that come with someone like Dell.
>> Yes i have, and with a laptop it's easy! >> The only real complaint i have is when i get back to the board room, my laptop smells like shit. >> However, I would have to say that is an invovenience for others, and not myself. So no big deal.
I started on Red Hat 4.2, in 1997. Since then, I've tried Gentoo, Linux From Scratch, Debian, and a bunch of others. I keep coming back to Red Hat, it seems much more polished to me. I've learned how to deal with RPM dependancy hell, and Im not a huge fan of any of the other packaging systems. LFS was cool, and I learned a ton doing that. I started that on 2.2, which was in early 2000. It just took so much effort to build everything from source. I was able to get Mozilla built, without too much pain, but things like OpenOffice had quite wierd build systems (at the time) I have seen that the OpenOffice build has improved. Anyway, I'm rambling, and arguing on the intenet is like the special olympics, even if you win you are still retarted.
Solaris 8, you young kids and your fancy tools, the development environment I spend my day in is 2.6, and my company has no plans of changing. Its more of a stability issue than anything. With new versions come new compatibility problems, and the question of supporting old program under a new OS. Upgrading a large commercial Unix system with 3rd party compilers and tools can be quite expensive. The biggest expense isn't the software so much, as the time lost due to tools not being available. The current machine Im working on has been running the same OS for 6 years now, and frankly I'd be scared if our admins tried to upgrade it to even 8, not to mention 9.
Yeah, but the drivers they release suck. I bought a Radeon 9000 from them, after the website said supported in Linux. The driver has the option for dual screen, however, there is no way in hell I can get it to work. I have found hundreds of Usenet posts where other people can't get it to work. I haven't found a single post of it working. I emailed ATI on two seperate occasions. The first time I received no response. The second time I asked for a known working XF86Config, and I got a canned response saying they would get back to me. They never did. Right know, I have a $130 piece of silicon that doesn't work. The drivers they do provide only work under XFree86 4.1.0 and 4.2.0. To me, ATI has no Linux support.
I bought OpenServer 5.0.5 this past weekend. Complete media kit with 5 user license, $5. I thought I was getting ripped off, but I wanted the piece of history. Now I can put the CD on the wall and laugh at it. BTW, it doesnt run in bochs.
I used cdex as a front end, and set it to high, which I just checked and is actually 2.
Re:Thank iTunes for the skips etc.
on
AAC Put To The Test
·
· Score: 4, Informative
I disagree on the 160 vs 256 kbps statement. I listen to mostly rock and punk, so I took a Thursday song, which is kindof in the middle of the two genres, and encoded it at 32, 48, 56, 64, 96, 112, 128, 160, 192, 256 and 320 kbps. I wanted to encode my whole CD selection (350 cds) at a bitrate that I couldn't hear the differance, and a bitrate that I could stream at decently. For streaming, 56 was the magic number. Any less and it sounded like crap, any more, and my DSL line couldn't host 2 streams at once. For music, 192 was good, but I could still hear the mp3 compression. I find that bass tends to get distorted in mp3s, and once I went to 256 this seemed to go away. I did all these tests with an audigy2 under windows XP, using Lame with q=9. Playback was through the Infinity HTS-20 Speaker System.
I have come to realize that all I use my home PC for is music, AIM and web surfing. All of these are pretty platform independent, and it looks like the Mac is best for Music now. Plus, I love how you can use the UNIX tools, but you can get along without them. At times, I like the power of the shell, and the configurability of UNIX, but othertimes I just want the thing to be quiet and work. I wish the price would come down, though. Its a lot to pay for a computer, and its not like a PC where you can buy cheap and constantly upgrade over time, its all the money at once.
There are no packages. You download the official Tarball or gzip and extract, compile with your options, and install. It is probably the absolutely most vanilla linux their is. I have to second that it is very educational. I have built LFS twice, once about 2 years ago, and once about 4 months ago. The first time a system boots where you understand every little daemon and startup script and program and it's usefullness is very rewarding. LFS is basically an instruction book on how to build all the differant programs and libraries in the right order. At first, the GNU tool chain is built statically from a differant distro, then a jailed root is used to rebuild everything dynamically with the static toolchain, so the system is self-hosted. The book explains everything very well, and only minimal knowledge is needed. I can't emphasize enough how educational it is on Linux and Unix in general.
Good point, I'll keep this in mind next time I'm working on a PDP/11 (heh, thats older than me) (36 bit word size). I think it was Peter Van Der Linden, of Sun fame, who said "Code isn't portable, it is only ported"
When porting code, you can almost always use a larger type, so if I was porting from an 11 bit architecture, to a more "normal" (If powers of 2 is really normal), I would make sure to use 16 bit ints, (as an initial stab, to truly do it right, you have to read each individual line of code, and understand the logic). A lot of risk is taken when moving from a 36 bit word size to 32, because the number that your integers roll-over at is now 16 times small.
Your example of a bit-field that goes under rotation just sounds dangerous to put in any code. I try to avoid things like that, because 5 years ago, who would have thought that all kinds of code would be ported from 32 and 64 bit Solaris and HP-UX to 32 bit Linux?
Depends on the level of optimization. Many compilers will allign variables on the native processors word size, at a high enough level of optimization. I think Visual C++ actually has this as a size vs. speed tradeoff. This is one of several reasons that the sizeof a struct is not neccessarily the sum of the size of it's components.
An int is normally defined as the most natural size for the target architecture. Hence, on intel, int and long int are both 32 bits. I do not like to use this nomenclature, and instead, I put in my header files something like
typedef unsigned long int n32; typedef signed long int s32; typedef unsigned short int n16; typedef signed short int s16; typedef char s8;
and whatnot, so that I know exactly what I'm getting. This also helps when it comes time to port to new architectures, cause all your changes are just a header file, as long as you don't need the benefit of a longer word size.
About the only time I use something other than 32 bit ints is when I'm reading or writing from 8 or 16 bit hardware registers, when writing lowlevel drivers, because there is normally no speed differance.
At the Neon Cactus at Purdue, on Thursdays, a 36 oz Old Style is 10 cents. You have to buy the cup once, for $1.50, but you can bring it back every week. On Mondays, another bar called Where Else has bottles (Miller Lite, Bud Lite, or Coors Lite) for 25 cents. You walk in, plunk down 6 bucks, and the bartender hands you a case of bottles in ice. This is one of many reasons I am proud to be American.
And I, as a matter of fact, happen to like American beer.
I believe the following will sum up why people feel this way.
Amazon
Furthermore, I have been on few long vacations that I truly enjoyed. People in the U.S. also take advantage of 3 day weekends. With flying as cheap as it is, you fly somewhere Thursday night, and return late Sunday night. Great way to spend a weekend partying and getting some sun on the beach.
I think people that have been out in the real world for a while don't realize how many languages are taught in school's today. I'm in Purdue's computer engineering program, and so far, I have had to learn c, c++, fotran, java, asm, python, bash, and ksh. I'm sure there are some others I have forgotten (like the little bit of perl I know). We also learn ABEL and VHDL, several version control systems and Makefiles. My roommate is taking an AI course right now which is all in scheme. People talk about the old days like their is lost knowledge, we still learn all that. I could write ATARI games in asm if I wanted to, but why do that when tools are available that let me do so much more? For learning, we don't have to learn assembly first anymore, you can start with any language. I think it is good to take a two pronged approach. Learn C first, and at the same time, start learning digital logic. C compilers are forgiving, and warn about obvious errors compared to assembly just doing exactly what you tell it do. When one is comfortable with both, I think learning assembly is much easier. Without this prior knowledge, you are just doing what you are told to do, you do not really understand it, and when you make mistakes, you have a harder time understanding why. After learning asm, it is easier to think like the machine, and easier to write efficient code in other languages.
There is one key differance however, the size of your living quarters. I live in an apartment where rent is $700 a month, and it is tiny ~700 square feet. A $100,000 house in Lafayette IN is on the order of 1200-1500 square feet, By your mortgage rates, my monthly payment for a house twice as large as my apartment would be $592.50. So my house would be twice as large as my apartment, and that $100 less I paid per month would offset the differance in property taxes. Now, when it comes time for me to leave Lafayette IN, I have something to show for my money, as opposed to rent which is thrown away. The key here is to compare similar living spaces, of course a large house is more expensive than a small apartment. You may ask, why am I renting? If I was going to be here more than 4 years, I wouldn't. When I moved here I was 18 and did not have the credit to purchase a home. There are also real estate fees for buying and selling.
Alright, let me be the first to say: WTF? Sorry big guy, I dont know if your trolling, dont speak english, or just have no idea what your asking, and cant be bothered to fix your broken keyboard.
With that said, a kernel that provides more performance will allow a slow machine to do more work in a said time period. It should be noted than none of these tests said anything about XFree86 performance, and that is the number one thing that will make a slow machine "feel" faster.
Newton held this post as well, at Cambridge, and that is why it was so cool that Hawking does as well.
(Many other accomplished Mathematicians held this post as well.)
I think the quetion posed here shold be more along the lines of "Have the qualifications to be a professor changed in the last 300 years?"
Purdue's ECE362 (Junior level micro-processor / assembly programming) is based on the HC12, using the P&E micro assembler and debugger.
I work with a bunch of embedded applications developers, and I know of only one other guy who builds his own machine. First off, they view their time as valuable. Every minute they can spend with their families is worth it, and building a machine can be time consuming. Pricing out parts, and getting up to date knowledge can take a lot of research. Second, as people get older, it seems they just don't want to mess with it. This is synonymous to old cars. Young people will tend to buy cars and restore them, while many older people will prefer to buy the car already restored. It costs more money, but they don't have to mess with it. Finally, with computers, when you buy legal software, I don't think you save any money when building your own, and most people want the warranties and one source of support that come with someone like Dell.
I noticed a big differance between 4.5 and 5.03 in terms of stability. BeOS 4.5 was quite stable, but I've had my share of problems in 5.03.
Compaq did the original cleanroom recreation of an IBM compatible BIOS, allowing clone sales. What they have done since does not stand out so much.
>> Yes i have, and with a laptop it's easy!
>> The only real complaint i have is when i get back to the board room, my laptop smells like shit.
>> However, I would have to say that is an invovenience for others, and not myself. So no big deal.
You sure its the laptop smelling?
I started on Red Hat 4.2, in 1997. Since then, I've tried Gentoo, Linux From Scratch, Debian, and a bunch of others. I keep coming back to Red Hat, it seems much more polished to me. I've learned how to deal with RPM dependancy hell, and Im not a huge fan of any of the other packaging systems. LFS was cool, and I learned a ton doing that. I started that on 2.2, which was in early 2000. It just took so much effort to build everything from source. I was able to get Mozilla built, without too much pain, but things like OpenOffice had quite wierd build systems (at the time) I have seen that the OpenOffice build has improved. Anyway, I'm rambling, and arguing on the intenet is like the special olympics, even if you win you are still retarted.
I have my Technicians ( KB9RGV ) , I use Red Hat.
Solaris 8, you young kids and your fancy tools, the development environment I spend my day in is 2.6, and my company has no plans of changing. Its more of a stability issue than anything. With new versions come new compatibility problems, and the question of supporting old program under a new OS. Upgrading a large commercial Unix system with 3rd party compilers and tools can be quite expensive. The biggest expense isn't the software so much, as the time lost due to tools not being available. The current machine Im working on has been running the same OS for 6 years now, and frankly I'd be scared if our admins tried to upgrade it to even 8, not to mention 9.
"I one time paid 4 dollars for a Coke in Bergen"
Ive done that at just about all movie theaters and sports arenas I've been to in the U.S.
Yeah, but the drivers they release suck. I bought a Radeon 9000 from them, after the website said supported in Linux. The driver has the option for dual screen, however, there is no way in hell I can get it to work. I have found hundreds of Usenet posts where other people can't get it to work. I haven't found a single post of it working. I emailed ATI on two seperate occasions. The first time I received no response. The second time I asked for a known working XF86Config, and I got a canned response saying they would get back to me. They never did. Right know, I have a $130 piece of silicon that doesn't work. The drivers they do provide only work under XFree86 4.1.0 and 4.2.0. To me, ATI has no Linux support.
I bought OpenServer 5.0.5 this past weekend. Complete media kit with 5 user license, $5. I thought I was getting ripped off, but I wanted the piece of history. Now I can put the CD on the wall and laugh at it. BTW, it doesnt run in bochs.
I used cdex as a front end, and set it to high, which I just checked and is actually 2.
I disagree on the 160 vs 256 kbps statement. I listen to mostly rock and punk, so I took a Thursday song, which is kindof in the middle of the two genres, and encoded it at 32, 48, 56, 64, 96, 112, 128, 160, 192, 256 and 320 kbps. I wanted to encode my whole CD selection (350 cds) at a bitrate that I couldn't hear the differance, and a bitrate that I could stream at decently. For streaming, 56 was the magic number. Any less and it sounded like crap, any more, and my DSL line couldn't host 2 streams at once. For music, 192 was good, but I could still hear the mp3 compression. I find that bass tends to get distorted in mp3s, and once I went to 256 this seemed to go away. I did all these tests with an audigy2 under windows XP, using Lame with q=9. Playback was through the Infinity HTS-20 Speaker System.
They are a band. Pretty good, I've seen them twice. Check out some music:
t is t.jhtml
http://www.betterthanezra.com/
http://www.mtv.com/bands/az/better_than_ezra/ar
I have to second that, it made me crack a smile.
I have come to realize that all I use my home PC for is music, AIM and web surfing. All of these are pretty platform independent, and it looks like the Mac is best for Music now. Plus, I love how you can use the UNIX tools, but you can get along without them. At times, I like the power of the shell, and the configurability of UNIX, but othertimes I just want the thing to be quiet and work. I wish the price would come down, though. Its a lot to pay for a computer, and its not like a PC where you can buy cheap and constantly upgrade over time, its all the money at once.
There are no packages. You download the official Tarball or gzip and extract, compile with your options, and install. It is probably the absolutely most vanilla linux their is. I have to second that it is very educational. I have built LFS twice, once about 2 years ago, and once about 4 months ago. The first time a system boots where you understand every little daemon and startup script and program and it's usefullness is very rewarding. LFS is basically an instruction book on how to build all the differant programs and libraries in the right order. At first, the GNU tool chain is built statically from a differant distro, then a jailed root is used to rebuild everything dynamically with the static toolchain, so the system is self-hosted. The book explains everything very well, and only minimal knowledge is needed. I can't emphasize enough how educational it is on Linux and Unix in general.
Good point, I'll keep this in mind next time I'm working on a PDP/11 (heh, thats older than me) (36 bit word size). I think it was Peter Van Der Linden, of Sun fame, who said "Code isn't portable, it is only ported"
When porting code, you can almost always use a larger type, so if I was porting from an 11 bit architecture, to a more "normal" (If powers of 2 is really normal), I would make sure to use 16 bit ints, (as an initial stab, to truly do it right, you have to read each individual line of code, and understand the logic). A lot of risk is taken when moving from a 36 bit word size to 32, because the number that your integers roll-over at is now 16 times small.
Your example of a bit-field that goes under rotation just sounds dangerous to put in any code. I try to avoid things like that, because 5 years ago, who would have thought that all kinds of code would be ported from 32 and 64 bit Solaris and HP-UX to 32 bit Linux?
Depends on the level of optimization. Many compilers will allign variables on the native processors word size, at a high enough level of optimization. I think Visual C++ actually has this as a size vs. speed tradeoff. This is one of several reasons that the sizeof a struct is not neccessarily the sum of the size of it's components.
An int is normally defined as the most natural size for the target architecture. Hence, on intel, int and long int are both 32 bits. I do not like to use this nomenclature, and instead, I put in my header files something like
typedef unsigned long int n32;
typedef signed long int s32;
typedef unsigned short int n16;
typedef signed short int s16;
typedef char s8;
and whatnot, so that I know exactly what I'm getting. This also helps when it comes time to port to new architectures, cause all your changes are just a header file, as long as you don't need the benefit of a longer word size.
About the only time I use something other than 32 bit ints is when I'm reading or writing from 8 or 16 bit hardware registers, when writing lowlevel drivers, because there is normally no speed differance.