There's a lot to like if you're a 19 year old college girl. I mean the man is ready to join the Silver Fox club with Bill Clinton. I happen to not like either men (at all, I have no guy friends) or old people.
Stupid people still create complicated and ridiculous solutions to problems. Often it is also stupid. Consider using lead as an octane booster in gasoline (a burn regulator), when we've always used low-lead pewter for holloware and no-lead pewter for flatware because we've known lead is highly poisonous since the beginning of time. Yes that's right, for a millennium or three we've known not to use more than 4% lead in beer tankards and 0% in plates and knives to make pewter (otherwise pewter is 14% lead), and then we go and stick lead powder in something we're going to burn and belch into the air as a way to solve a complex chemical problem in which a chemical occasionally ignites too early from heat build-up during compression.
Clever, but stupid. Clever enough to use a high density metal dust to slow the reaction, too stupid to think about the implications of belching toxic heavy metals into the air. You think politicians can't think up complicated PR fuckery and still be morons?
Funny is now Romney needs to buy $1M of bitcoins. With such demand, the bitcoin market would bubble quickly. $20 per 1btc? Sure. Then the blackmailers have to unload $1M in btc and... the price drops like hell.
long is 32 bits on i386 and 64 bits on x86-64. Except maybe on Windows 64 where long might be something different, as long as it's at least as big as int. The new C99 standard defines [u]int[$sz]_t for [unsigned] integer of $sz bits.
And where do all these "earnings" go? Is there a giant bank account that grows indefinitely? Does Oracle not need liquid capital to, oh I don't know, supply a stable budget for hiring new engineers and branching out new departments?
Oracle is a big business. How many employees does it have? How much shit does it produce?
Do you make more than $26000? Maybe you should give some of that to me, you're rich.
The problem is people use 'int' and 'long' interchangeable because on x86 sizeof(int) = sizeof(long). On x86_64, sizeof(long) > sizeof(int). So they have int foo getting passed along to int func1(long foo) and set by long func1(int foo) etc. Then, strange things happen when they compile to 64 bit.
It doesn't matter what you use for what, but you must be consistent. If it's consistent, it works. If you use all int storage for a particular variable as it gets assigned to other variables, structure elements, and passed to functions, then your program is type safe and you know what you're doing. If you willy-nilly pass an int as a long or vice versa, shit breaks. If you store a pointer in an int that's even worse.
Yes, do that. Where it doesn't matter, if you go willy-nilly saying "long" or "int" what you get is 32-bit "int" and 64-bit "long" that "shouldn't matter" and then very strange shit happens. Where it matters precisely how big it is, you use uint32_t or int64_t or whatever. If it doesn't matter precisely, either say 'long' or say 'int' for shit that's going to be carrying these values--parameters to functions, local variables, variables in structs, whatever. Don't go scattering 'long' and 'int' as interchangeable or shit will break.
Where do you entitled fucking whores come from? "Oh they're big companies, they have the money" fuck, I remember a jury deliberating over an insurance company suit with some woman who was obviously off her nut. The jury agreed that she had no case and was just trolling for money, but well... she was trying to buy a house, could use the money... they decided to give it to her because the insurance company didn't need it anyway, they're rich.
From each according to his ability, to each according to his need I guess. It's the American Way(TM). Big evil rich corporations should pay for everything, and when they lose money it's just rich folk money and they have infinite money. This won't affect their opportunity to push products, to hire staff, to pay their employees, etc. The executives just won't take bonuses--because face it, those rich people don't need money and it's okay if we don't give it to them, never mind that it's actually written in their contracts and the company can be sued for that too. It's not like they'll slow hiring, reduce hiring salaries, reduce raises, etc; the millions just come from the pile of money that was going in a hole anyway.
You can complain about their behavior, you can complain about how they got their money, but god dammit stop acting like it's no big deal that corporations and/or rich folk suddenly lose "pocket change." Which one of you assholes is going to give me $50 because hell it's not like you can't afford it? I'm buying a house, help pay my down payment. For free! I'm not giving you losers shit, give me money, it's only 50 bucks.
Try the East Coast, it's terrible. Ridiculously high stress compared to the midwest--high population density, mcdonalds like every other corner (there's a map), and the East Coast is ridiculously politicized. Politics IS religion on the East Coast, people walk around all day talking about the evil otherparty. Midwest who cares? Are my crops going to fail?
Are you kidding? It's worked for me for ages, running Wine for several releases (just recently started getting 64 bit wine, which is annoying). Yes you get duplicates of major libraries, because the processor won't run in protected/long mode both, won't switch between them without magic, and you need application-level translation to use a 32-bit library from a 64-bit code base and vice versa.
You need application-level translation that's fully aware of the implications between 32 and 64 bit, which means maybe Wine could do it IF it were possible--the only way to do it on current processors is across a context switch (so into kernel or into another process via IPC and a protocol), but a generic C program written in 1995 hooked to 64-bit libc wouldn't handle it. Maybe if 64-bit libc was aware of 32-bit programs and did translation (like the kernel), but that's a hell of a lot of code support and again you don't have the processor support for it (won't call 32-bit code from 64-bit in the same process).
On the 386, you could mark code pages as 16 bit and it would execute that code as 16 bit 286 code; this doesn't happen in long mode, you can't mark pages as 32-bit. It will go across a context switch, but the kernel implementation for this is a prime example of why not to bother: separate entry point that does translation, and then the exit point has to verify that all values being returned to user space are within the storage space of the 32 bit API (i.e. a uint16 is going to be 16 bits either way, but an int that's 32 bits on 32bit and 64 bits on 64 bit better store a meaningful 32 bit value), and if not then stuff has to be moved around (i.e. anything above 4GB in RAM has to be moved down, in the worst case) or handles have to be changed/mapped/etc. The kernel has to be able to handle not breaking things for 32-bit programs. Imagine implementing this in a C library... or, just recompile to 64-bit.
you mean not confusing long int with int in C programs? Which, by the way, is WRONG, but works on i386 because sizeof(long) = sizeof(int) whereas sizeof(int) may be sizeof(uint32) while sizeof(long) is sizeof(uint64) on amd64. In C, long long >= long >= int >= short >= char. On one platform long > int, and on another long = int.
Here's a tip: say what you god damn mean; if you want a long int, declare a long int instead of just an int. If you want a short int, declare a short int instead of just an int. If you declare just an int, declare just an int everywhere where that interface is going to come into play.
Programmers do a lot of allocating something big and shoving it into something generic, and it works because the generic thing is also big. But then they change platforms and the generic thing is now big but the big thing is now HUGE, and they put something HUGE in the big thing and then copy that into the generic thing and lose half of their storage space and get weird values out and the program doesn't work. Programmers think the computer should understand what they mean, not what they say, especially when it's "always been that way before." Like being in the midwest and asking for a coke, and you get a pepsi--because coke means soda. Go out east coast and ask for a coke and they're like... we have pepsi, is that ok? People are like, what? Yes that's what I said, what the hell? Programmers have this happen on computers and don't know why it breaks.
Yes, the Germans are afraid of inflation because inflation ended with Hitler last time. They don't want Hitler again.
You know Hitler was just a regular guy that got lucky? Think about it. Let's look at Hitler. Read Mein Kampf in German; the English translations are lame.
Hitler correctly noticed that the whole of Germany was turning into social democrats ruining the economy. He also correctly noticed that the movement was driven by an extremely biased media. He ALSO correctly noticed that the Jews were running the major media. Then... he made the incorrect logical conclusion that executing all the Jews would solve the problem.
This is akin to city folk Americans noticing that mechanic shops run by blacks do a terrible job and mostly overcharge and scam their customers for poor work, and drawing the conclusion that mechanic shops that are bad are run by blacks, and thus executing all the blacks would eliminate all the badness and we'd only have white folks running things like mechanic shops and restaurants and the Government and that would solve all our problems. You know this actually happens. A lot of people don't like blacks--I get told all the time that white areas are pristine low-crime safe havens and black areas are high-crime murder traps. A lot of old people don't like asians AT ALL because of Pearl Harbor, they think all Asians are going to bomb their houses. Muslims are weird and fashionable to hate these days too.
Hitler was a normal guy who tried to change the world for the better. Like any normal guy, he was incredibly stupid and figured that one social group that happens to hold majority and poor behavior in a particular facet of society as he's familiar with must be the root cause of all problems, and that exterminating them would fix everything. In America we actually did this--as a matter of policy, handed down even from the government--with the native americans. We did it with Germans and Asians, and on a social level we do it to blacks, muslims, and arabs. There are plenty of people in the US right now who would especially just round up all arabs and muslims and execute them, people who advocate the banning and burning of mosques. Congress held a several hour long hearing to decide if they want to go that route, routing out all the Muslims from the country--this was seriously considered, we debated going to war against Islam.
The Germans don't want major inflation to give them another Hitler. Another Hitler wouldn't be unreasonable either; there's plenty worse than Hitler, like Mao. Our world is full of people who would love to be Hitler, they have an idea of who they'd like to remove from their society or from our world entirely. This is a scenario we cannot allow.
Except all your parts aren't nasty and dripping with mineral oil when you try to swap out a sound card. How the hell do you clean the mineral oil off your sound card? Let it sit a while and it'll drip away until you have a thick, sticky film of dust mixed with oil.
Why? There are a lot of engineers. There are 2000 here but we only need to hire 500; 1500 of you can go rot in hell. Enjoy your government funded debt.
What's basically happening here is the working conditions aren't that bad, but a labor union type company (with interest in showing how horrible working conditions get when you don't band together and beat your employer with a giant cock) is screaming that conditions are terrible.
By some standards, American working hours are ridiculous and terrible. The Italians wouldn't stand for it. On the other hand, $100/mo is enough to live pretty well in Romania; in China they get some money and they live on it, and people are like "well they get like $500/mo it's so horrible" but with $500/mo one man supports his entire family with a (small) home and food. Try doing that in America.
Quiet bitch, I went to school in Kentucky and they taught us that the Great Designer has a plan for everyone. If we have 8 billion people with nothing to do, then they're obviously there to help the rich get rid of their money and do good by using it to support the poor. That's what capitalism is about: from he who hath the ability to he who hath the greatest need.
Slashdot Mirror
Shrug. It's a core tenant of Socialism. I want to see how many socialist liberals go ape shit at it.
http://www.beyondtheofficedoor.com/Electric-Sit-to-Stand-Desk.php These.
Oh fine I'll change my signature.
There's a lot to like if you're a 19 year old college girl. I mean the man is ready to join the Silver Fox club with Bill Clinton. I happen to not like either men (at all, I have no guy friends) or old people.
Romney is an asshole. To be fair, the Stone doesn't like Romney at all; but there's not a lot to like. He's a Republican John Kerry.
Stupid people still create complicated and ridiculous solutions to problems. Often it is also stupid. Consider using lead as an octane booster in gasoline (a burn regulator), when we've always used low-lead pewter for holloware and no-lead pewter for flatware because we've known lead is highly poisonous since the beginning of time. Yes that's right, for a millennium or three we've known not to use more than 4% lead in beer tankards and 0% in plates and knives to make pewter (otherwise pewter is 14% lead), and then we go and stick lead powder in something we're going to burn and belch into the air as a way to solve a complex chemical problem in which a chemical occasionally ignites too early from heat build-up during compression.
Clever, but stupid. Clever enough to use a high density metal dust to slow the reaction, too stupid to think about the implications of belching toxic heavy metals into the air. You think politicians can't think up complicated PR fuckery and still be morons?
So they've already been released?
Funny is now Romney needs to buy $1M of bitcoins. With such demand, the bitcoin market would bubble quickly. $20 per 1btc? Sure. Then the blackmailers have to unload $1M in btc and ... the price drops like hell.
www.gokgs.com they rank you.
long is 32 bits on i386 and 64 bits on x86-64. Except maybe on Windows 64 where long might be something different, as long as it's at least as big as int. The new C99 standard defines [u]int[$sz]_t for [unsigned] integer of $sz bits.
And where do all these "earnings" go? Is there a giant bank account that grows indefinitely? Does Oracle not need liquid capital to, oh I don't know, supply a stable budget for hiring new engineers and branching out new departments?
Oracle is a big business. How many employees does it have? How much shit does it produce?
Do you make more than $26000? Maybe you should give some of that to me, you're rich.
The problem is people use 'int' and 'long' interchangeable because on x86 sizeof(int) = sizeof(long). On x86_64, sizeof(long) > sizeof(int). So they have int foo getting passed along to int func1(long foo) and set by long func1(int foo) etc. Then, strange things happen when they compile to 64 bit.
It doesn't matter what you use for what, but you must be consistent. If it's consistent, it works. If you use all int storage for a particular variable as it gets assigned to other variables, structure elements, and passed to functions, then your program is type safe and you know what you're doing. If you willy-nilly pass an int as a long or vice versa, shit breaks. If you store a pointer in an int that's even worse.
If it detects a big thud, the person has fallen. Also how does this prevent anything? Seriously overengineered.
Yes, do that. Where it doesn't matter, if you go willy-nilly saying "long" or "int" what you get is 32-bit "int" and 64-bit "long" that "shouldn't matter" and then very strange shit happens. Where it matters precisely how big it is, you use uint32_t or int64_t or whatever. If it doesn't matter precisely, either say 'long' or say 'int' for shit that's going to be carrying these values--parameters to functions, local variables, variables in structs, whatever. Don't go scattering 'long' and 'int' as interchangeable or shit will break.
Where do you entitled fucking whores come from? "Oh they're big companies, they have the money" fuck, I remember a jury deliberating over an insurance company suit with some woman who was obviously off her nut. The jury agreed that she had no case and was just trolling for money, but well... she was trying to buy a house, could use the money... they decided to give it to her because the insurance company didn't need it anyway, they're rich.
From each according to his ability, to each according to his need I guess. It's the American Way(TM). Big evil rich corporations should pay for everything, and when they lose money it's just rich folk money and they have infinite money. This won't affect their opportunity to push products, to hire staff, to pay their employees, etc. The executives just won't take bonuses--because face it, those rich people don't need money and it's okay if we don't give it to them, never mind that it's actually written in their contracts and the company can be sued for that too. It's not like they'll slow hiring, reduce hiring salaries, reduce raises, etc; the millions just come from the pile of money that was going in a hole anyway.
You can complain about their behavior, you can complain about how they got their money, but god dammit stop acting like it's no big deal that corporations and/or rich folk suddenly lose "pocket change." Which one of you assholes is going to give me $50 because hell it's not like you can't afford it? I'm buying a house, help pay my down payment. For free! I'm not giving you losers shit, give me money, it's only 50 bucks.
Try the East Coast, it's terrible. Ridiculously high stress compared to the midwest--high population density, mcdonalds like every other corner (there's a map), and the East Coast is ridiculously politicized. Politics IS religion on the East Coast, people walk around all day talking about the evil otherparty. Midwest who cares? Are my crops going to fail?
Are you kidding? It's worked for me for ages, running Wine for several releases (just recently started getting 64 bit wine, which is annoying). Yes you get duplicates of major libraries, because the processor won't run in protected/long mode both, won't switch between them without magic, and you need application-level translation to use a 32-bit library from a 64-bit code base and vice versa.
You need application-level translation that's fully aware of the implications between 32 and 64 bit, which means maybe Wine could do it IF it were possible--the only way to do it on current processors is across a context switch (so into kernel or into another process via IPC and a protocol), but a generic C program written in 1995 hooked to 64-bit libc wouldn't handle it. Maybe if 64-bit libc was aware of 32-bit programs and did translation (like the kernel), but that's a hell of a lot of code support and again you don't have the processor support for it (won't call 32-bit code from 64-bit in the same process).
On the 386, you could mark code pages as 16 bit and it would execute that code as 16 bit 286 code; this doesn't happen in long mode, you can't mark pages as 32-bit. It will go across a context switch, but the kernel implementation for this is a prime example of why not to bother: separate entry point that does translation, and then the exit point has to verify that all values being returned to user space are within the storage space of the 32 bit API (i.e. a uint16 is going to be 16 bits either way, but an int that's 32 bits on 32bit and 64 bits on 64 bit better store a meaningful 32 bit value), and if not then stuff has to be moved around (i.e. anything above 4GB in RAM has to be moved down, in the worst case) or handles have to be changed/mapped/etc. The kernel has to be able to handle not breaking things for 32-bit programs. Imagine implementing this in a C library... or, just recompile to 64-bit.
you mean not confusing long int with int in C programs? Which, by the way, is WRONG, but works on i386 because sizeof(long) = sizeof(int) whereas sizeof(int) may be sizeof(uint32) while sizeof(long) is sizeof(uint64) on amd64. In C, long long >= long >= int >= short >= char. On one platform long > int, and on another long = int.
Here's a tip: say what you god damn mean; if you want a long int, declare a long int instead of just an int. If you want a short int, declare a short int instead of just an int. If you declare just an int, declare just an int everywhere where that interface is going to come into play.
Programmers do a lot of allocating something big and shoving it into something generic, and it works because the generic thing is also big. But then they change platforms and the generic thing is now big but the big thing is now HUGE, and they put something HUGE in the big thing and then copy that into the generic thing and lose half of their storage space and get weird values out and the program doesn't work. Programmers think the computer should understand what they mean, not what they say, especially when it's "always been that way before." Like being in the midwest and asking for a coke, and you get a pepsi--because coke means soda. Go out east coast and ask for a coke and they're like... we have pepsi, is that ok? People are like, what? Yes that's what I said, what the hell? Programmers have this happen on computers and don't know why it breaks.
Yes because I totally did not have sexual relations with that donkey.
Yes, the Germans are afraid of inflation because inflation ended with Hitler last time. They don't want Hitler again.
You know Hitler was just a regular guy that got lucky? Think about it. Let's look at Hitler. Read Mein Kampf in German; the English translations are lame.
Hitler correctly noticed that the whole of Germany was turning into social democrats ruining the economy. He also correctly noticed that the movement was driven by an extremely biased media. He ALSO correctly noticed that the Jews were running the major media. Then ... he made the incorrect logical conclusion that executing all the Jews would solve the problem.
This is akin to city folk Americans noticing that mechanic shops run by blacks do a terrible job and mostly overcharge and scam their customers for poor work, and drawing the conclusion that mechanic shops that are bad are run by blacks, and thus executing all the blacks would eliminate all the badness and we'd only have white folks running things like mechanic shops and restaurants and the Government and that would solve all our problems. You know this actually happens. A lot of people don't like blacks--I get told all the time that white areas are pristine low-crime safe havens and black areas are high-crime murder traps. A lot of old people don't like asians AT ALL because of Pearl Harbor, they think all Asians are going to bomb their houses. Muslims are weird and fashionable to hate these days too.
Hitler was a normal guy who tried to change the world for the better. Like any normal guy, he was incredibly stupid and figured that one social group that happens to hold majority and poor behavior in a particular facet of society as he's familiar with must be the root cause of all problems, and that exterminating them would fix everything. In America we actually did this--as a matter of policy, handed down even from the government--with the native americans. We did it with Germans and Asians, and on a social level we do it to blacks, muslims, and arabs. There are plenty of people in the US right now who would especially just round up all arabs and muslims and execute them, people who advocate the banning and burning of mosques. Congress held a several hour long hearing to decide if they want to go that route, routing out all the Muslims from the country--this was seriously considered, we debated going to war against Islam.
The Germans don't want major inflation to give them another Hitler. Another Hitler wouldn't be unreasonable either; there's plenty worse than Hitler, like Mao. Our world is full of people who would love to be Hitler, they have an idea of who they'd like to remove from their society or from our world entirely. This is a scenario we cannot allow.
Except all your parts aren't nasty and dripping with mineral oil when you try to swap out a sound card. How the hell do you clean the mineral oil off your sound card? Let it sit a while and it'll drip away until you have a thick, sticky film of dust mixed with oil.
Why? There are a lot of engineers. There are 2000 here but we only need to hire 500; 1500 of you can go rot in hell. Enjoy your government funded debt.
What's basically happening here is the working conditions aren't that bad, but a labor union type company (with interest in showing how horrible working conditions get when you don't band together and beat your employer with a giant cock) is screaming that conditions are terrible.
By some standards, American working hours are ridiculous and terrible. The Italians wouldn't stand for it. On the other hand, $100/mo is enough to live pretty well in Romania; in China they get some money and they live on it, and people are like "well they get like $500/mo it's so horrible" but with $500/mo one man supports his entire family with a (small) home and food. Try doing that in America.
Germany is desperately afraid of inflation and will do anything they can to stop it.
Quiet bitch, I went to school in Kentucky and they taught us that the Great Designer has a plan for everyone. If we have 8 billion people with nothing to do, then they're obviously there to help the rich get rid of their money and do good by using it to support the poor. That's what capitalism is about: from he who hath the ability to he who hath the greatest need.