I think you missed two key points: Pick something with realistic goals for whatever sized team you have (or self) and set goals Design your work first
If you don't do those, you'll probably never learn to finish code. Setting goals with a team usually needs to be done based on time and skill levels of members. If it's just you, set goals for yourself and stick with them as best as possible. Don't worry too much about missing a date as long as you made progress towards your goal (but make sure to set a new goal).
Also don't be afraid to axe a project if you have to. I had a flight sim with some beautiful code in it (the blitter was fantastic... too bad blitters died with that era of hardware) and over a year of work and I killed the project even though completion was probably only a few months away. Why? because it had a problem at the core of the engine that was unfix-able and needed to be recoded from scratch to boost it to optimal framerates (specifically, I used virtuals at a low level not knowing that they have an expensive look-up table). I also had bought my first Voodoo card by that point and knew that was the future, not painter's algorithm and blitters. As sad as I was killing what I hoped would be a shareware quality flight sim, I learned so many lessons that it was worth the time spent.
I can't tell you how many kids I've talked to that want to make a commercial quality MMORPG or a 3D shooter in a few months...
that's a bit confusing anyhow - it's called a complex number. The component of a complex number that is "useless" is called the imaginary component.
Electronics would be in the stone ages without them (you need them for inductance calculations, which is very important in circuit and chip design), but they're not real, so who cares?
lesson 1: spoken like someone that's never been to a city like Minneapolis... the traffic "engineers" there had the brilliant idea that sometimes the left lane is for exits. The attempt at passing a law to make the left lane a passing lane fell apart because of this. For that matter, they also designed the beltway system to always fork a lane towards the cities at regular intervals, so it's a constant merge if you want to stay on the beltways (sometimes left, sometimes right).
as for lesson 2, since when did the US get an autobahn? last I heard, they shut the only one down (Montana). If it's an emergency, zip around on the shoulder (except in Boston, where I've noticed it's always an emergency, so you have to use the sidewalk;)
hey - I can rant on this too -
it really bugs me when some impetuous fool rides my bumper and flips his headlights on and off incessantly while trying to go 170 miles an hour in a 65 during rush hour and thinks that there is a chance in hell that I can find 3 inches (much less 10 feet) of space to merge into the right lane.
and BY THE WAY, if I am in the left lane and am next to another car going the speed limit on my right and you race up behind me and "tailgate" (since you say there's no such thing) trying to get me to merge right (which I can't due to the other car), I legally need to SLOW DOWN to stay within the government provided legal limits, and 99% of the time when I slow down, you merge to pass me on the right, even if I have my signal on to get in the that lane.
If it bugs you so much that some of us don't want to break the law, why don't you write a bill, take it down to city hall and get your faithful congress-people to sign it making the US freeways into autobahns? Quite honestly, I'd be perfectly happy going 170MPH and getting to work in 1/3 the time, but I find speeding tickets a waste of money and time. So stop nagging me on how to drive and enjoy the extra paper you get in your pocket for your failure to obey the traffic laws your representatives in government created to protect you and save on oil.
For the most part, if the code was written to work cross-platform to begin with, the work is trivial. Unfortunately, code usually isn't written that way - most game developers use DirectX (such as NWN2, unlike its predecessor), Physics APIs (e.g. Havok, though there is a mac version now), Tree APIs (speedtree), and others that are usually Windows only. Not only that, they usually charge premium licensing fees if they do offer a Windows alternative (ahem - Havok). Should they decide to port, they also need to beat cross-platform solutions like Cedega to market on Linux or they've pretty much lost that market.
I didn't mean TCP is a great protocol for voice (it isn't, though it might be for sample and send [uncompressed] data). My problem is with the choice of ATM, which was picked because it matched hardware the telecos were using at the time, not for being a great protocol for voice traffic. It actually is a bad protocol for the switches used by telecos today. The telecos also standardized ATM on their trunk lines for the Internet, even though it's a terrible protocol for data (using 100 motorcycles when a bus would work just as well). ATM also has a packet verification stage (guarantees QoS or "Quality of Service"), which increases the total load. I believe the average was around 17% load both ways, where load meant something like header + send verification + average packet loss at 85% capacity.
VoIP does not have a QoS guarantee - VoIP uses UDP (Universal Datagram Protocol), not TCP which does not guarantee packet arrival. UDP uses 20 byte packets over IPv4 (TCP is 36 I think). Since UDP does not reply back to the sending machine, it may actually work faster on average, but may also have jitter, especially over long, noisy, or very busy connections.
One way to counter the empty packet thing that you mentioned is a technique used in cell phones applied to IP - TDMoIP, which bundles a bunch of packets going to the same destination together.
yeah, yeah, rectifying mumbo-jumbo - nobody wants to hear about that. What you want to do is take one of those really big capacitors in an old TV, unsolder the leads and solder them in backwards. Then hook up the power.
See, it's simple - Slashdot readers want to see shrapnel - and lots of it, not how to safely do stuff with electricity. Keep your education stuff in the schools.
In Bill's first act as President, he promises to release US Government 2.0, which is already reported to be about 200 years late. Rumor has it that 3.0 codenamed "Galloway" is also in the works.
Ok, probably one person at best is gonna get that one unless I spill the beans... Galloway is a hornless breed and also hornless dominant, as crossing them with longhorns produces only hornless cattle. Yes, that was far too nerdy of a joke, even for here;)
The geoport express modem was a first generation soft-modem - it wasn't really meant to be an internet phone (as per the patent - it mentions something about phone layout), so the patent may be valid in that respect. Many manufacturers made soft modems, though they're rare today.
In high school I had a friend that made manager at McDonalds in 6 months and was running the place at 8 months, so saying you're a former McDonalds manager doesn't mean much. I imagine the turnover had to be huge for him to advance so quickly, though. I don't remember ever having much of a problem with turnover or people showing up on time when I was working at a restaurant, but maybe you just get a lot more of the dregs of society in fast food. OTOH, he was getting paid almost 3 times what I was before heading off to college and had management experience, something I didn't get until many years later.
Seems to me a Big Mac, fries, and a diet coke was 2 points over my weight on the weight watcher's chart - that's for food in a day, not a single meal. Thankfully I haven't had a craving for one of those since 1996 when I barfed one up on choppy seas (getting SCUBA certified).
I rarely eat KFC, but I recall they had a problem with being high in trans-fats, which are known to cause health problems. I'm sure it isn't as bad as health problems related to chain smoking, so you should be fine (yes, that was a feeble attempt at sarcasm).
Let me guess... you drink 6-12 355mL bottles of Miller Lite, right;)
what's so special (besides the speed)?
on
100 Gbps Via Ethernet
·
· Score: 2, Informative
The idea of packet order guarantee and ethernet are pretty much mutually exclusive, and upon further review (reading the fa), it reassembles out-of-order packets pretty much just like TCP. About the only new thing is the out-of-order disassembly and assembly and the overall speed. It still has the same flaws as Ethernet, which is that it really is only about 80-85% efficient - after that you would be better off with a Token Ring or other managed protocol (token rings are excellent for saturated networks but poor for low saturated networks).
Sigh - and the poster seems to think ATM is a good protocol, but ATM is a terrible protocol, especially for data, but even for voice it's mediocre. It was designed for voice conversations over high noise lines with significant data loss (copper) and predominantly used over low noise high speed lines with almost no loss (fiber). Its advantage is standard packet length (53 bytes) and speed. Worst disadvantage - almost 10% overhead (5 bytes of every 53, or ~9.4%). ATM also has no guarantee of sort order or collision avoidance (since it's asynchronous) so in practices it can be really bad. Incidentally, my networking class voted this the worst protocol back in 1996, but expected it to succeed mainly because of telecoms pushing it.
Actually, neither of you is wrong for Trojans, but your definition of Virus is incorrect, since viruses can propagate over network drives and diskettes (which is not activated by the user), a common problem at businesses and schools and also the original way viruses got spread.
A Trojan is an application masquerading as another application. It can contain any payload but usually refers to a malicious payload (much like its namesake, the Trojan Horse). A Trojan is therefore not a virus and also does not self-replicate and is activated by a user.
A Virus refers to self-replicating code. Many viruses also contain a payload, but this is not really the virus itself. Some of the more malicious viruses will e-mail Trojans of themselves, while others may be entirely benign.
A worm essentially refers to a program that self-replicates over a network, but worms with a payload of viruses and/or Trojans are usually just called worms.
and the other category (though rare) - the timebomb A timebomb (or bomb) is a program that is tacked onto another program, usually manually. It has no self-propagation. When it "detonates" after a prescribed number of launches or time period, it does something malicious, including wiping drives, installing viruses, or running zombies.
Microsoft and others have stated that a parts of Paragraph 3 and 4 of the LGPL are ambiguous and depending on interpretation, could force them to be construed a derivative work. After reading that section, I decided that I can't link LGPL into my mac apps as well. My best guess as to the meaning of sections of those paragraphs: The LGPL essentially forbids you from statically linking a library into your work The LGPL allows dynamically linking (though this may be interpretable, as there are wording conflicts with the previous paragraph)
Mac applications, however, make an ambiguity between the 'application' and the library if the library is built as an embeddable framework. Essentially an embeddable framework is a dynamic library that gets bundled into a specially formed directory tree that is seen by the GUI as an application. It is built and functions exactly the same as a dynamic library, aside from that it isn't placed in a globally accessible place like/usr/lib and that it has a special install path (@executable_path/../Frameworks). Since the finished application bundle is seen as an application and not a directory tree, this could be interpreted as part of the application as per the LGPL and therefore is a violation of the LGPL.
A project I'm working on decided not to use any LGPL code in our project and instead only provide hooks to such code (for instance, someone added OpenAL hooks) because we don't want to be superseded by the LGPL. Actually, I don't believe we can even switch licenses if we wanted to at this time unless we freeze and fork the current Zlib licensed version due to several co-authors using commercial pieces (that forbid becoming derivative code).
I just read in US News and World Reports (early November 2006 issue, if I'm up-to-date - I was a bit behind due to a vacation) that the numbers acknowledging to be Atheist are more like 1% in the US and 10% don't believe in a single all powerful deity (so spiritualists and agnostics).
Too bad it doesn't have religious crazies - I'd like to know the percentage of people that believe all other religions should be destroyed with whatever means necessary.
Most game programmers have none of the above. I've known 3 and the best educated of them has between 2 and 3 years of college, which got him through C++ and then he got hired by Volition (and has moved around since). The other two started working straight out of high school for MECC (the Oregon Trail people) and Wizard Works (or wizworks? - low budget games), both of which were absorbed into larger companies. I lost touch with all three of them in college, but I do still chat on IRC with some other game industry people (and lots of wannabes) due to some open source game engine work I do.
Incidentally, I wanted to get into games once upon a time (I'm currently employed by a CAD company) and I had Graphics and AI, but not operating systems. I did have hardware courses because I took CE for 2 years before switching to CSCI, but no fundamental OS courses. Quite honestly, I don't see the point of AI - A* is probably the most important part of game programming and it was less than one day in my coursework. Most of the other stuff is not really suited to game programming, though some of that class was redundant to my hardware classes (doing AND, OR, XOR, etc in software). Heck, we wasted more time on learning the differences between Lisp and Scheme (the "starter" language taught at the college I transferred into) than A*. The only thing I've used Lisp for since is customizing emacs. I've used A* a LOT.
You missed Networking, though I'd have to stress finding a network coding class as opposed to a survey of networking (my first networking class was more of a survey class - it was interesting, but had almost no programming).
Yeah, but it's still an underlying 64 bit architecture that's running in a 32 bit mode. Fixes for bugs to that would be provided by AMD.
Since you tried a single core, though, it makes me suspect the real problem is with the shared cache between the cores. I can't think of anything else that AMD would patch, at least, that would fix application problems, especially if the cores themselves are the same architecture as the single core chip you had in first.
3.8% is a tiny percentage. Compare that to individual protestant groups and it may seem like a nice slice, but compared to all religions it's a tiny percentage.
anyhow, I noticed I had a train-of-thought error in my post earlier. Gotta proof-read better after I get interrupted.
That's not necessarily a multicore problem. With most games, it's probably more likely a problem with the 64 bit architecture running 32 bit code.
The exception would be if the code is, in fact, multithreaded or if it runs a server and clients as separate processes. Most games don't, or at best use a thread to dynamically load files in the background (and most games that do that are RPGs like Diablo 2 and Gothic 1-3). Even then, assuming that threads are stable, it's highly likely that the problem would crash 32 bit machines as well (with the possible exception of race conditions).
The major problems with threads are lock/starvation (see the dining philosopher's problem and race conditions (you have A and B in separate concurrent threads but A needs to finish before B). Both of these problems are usually caused by coding errors.
The only confirmed atheist I know considers Bush a vegetable in more ways than just name, so I guess neither side likes the other much. Aside from our mutual dislike for Bush, I don't agree with her political or ethical beliefs (Green party, PETA, vegan), but she's married to one of my buddies, tho, so I can't exactly divorce her (he's agnostic).
All things considered, if you wanted to persecute one particular group, atheists are an easy target. Most people believe in some sort of God or gods, and only a tiny percentage of people believe there is no God. One thing all the religions in the world can agree upon is that the atheists are wrong (even if they're right - I have no proof one way or the other).
I haven't reinstalled Windows for years on my own system and by using good registry and spyware cleanup software, then a defrag I usually can clean up most other people's computers.
PC Enthusiasts are the ones that swap out hardware. I have a 5 year old case, but no hardware in it is more than 2 years old. I repair other people's computers, too - heck, I'm doing it now for my brother-in-law, whose heatsink fan (HSF) failed and the computer was overheating after 5-10 minutes of use. I'll charge him $10 because I had to buy some new thermal compound (which is why it's not done yet), but I had plenty of spare HSFs lying around, so he gets one of those free. That repair woulda been $100+ anywhere else and takes me all of 5 minutes and had a net part cost of $15 with new parts.
The problem is, enthusiasts will often swap out a mobo, CPU, and memory at the same time and suddenly Windows thinks that it is a pirated system since too much hardware has changed. I talked to Microsoft reps twice now because I had to re-enable my Windows XP and had used up my installs. The first time was because of a bug in Windows XP where it incorrectly identified my ATA disk as the SATA drive I was trying to install on and wiped all my data, so I was pretty miffed when I called (incidentally, I noticed that bug was fixed in the XP SP1 installer when I installed on my wife's machine with a similar setup).
Before someone heckles me about why I don't switch to Linux, I do run Linux, and MacOS, for that matter. I need them all for work, so I'm pretty much screwed and can't dump Windows. For that matter, for the most part I like Windows. It's certainly not without its flaws, but I can say the same about KDE, Gnome, and MacOS X.
I think the Linux GUI is adequate if not "good enough" in its current state, tho - I find both Gnome and KDE perfectly usable and even more so if you're already familiar with Windows. The problem I have with both is after a default install I had a bunch of applications with names like xmms, and I often get multiple redundant applications like Helix or MPlayer. What do these do? Which is best? You're making a novice user make a lot of choices about software they don't understand. Yes, I know both the 3.0 versions of Gnome and KDE made strides against this with descriptive menu names, but I still get three or 4 apps called media player and I have no idea what media they play (I pick on this because I remember from my own experience that some of these played MP3s, others didn't and I could never remember which).
The Linux way seems to be to experiment with each media player until you find the one you like best, but to be honest, I think a novice user doesn't want to make a decision - they just want to click their song and the GUI picks the one that works. I mean, if I want to dye my hair green, do I care if the dye is made by Bob's Dye Factory or Garnier? Most people, at least the first time, just want something that does the trick. Maybe later they'll find that the Bob's stuff washes out after a week and the Garnier stuff is basically permanent, but let the user figure that out for themselves and make the switch later - they may be perfectly happy with Bob's stuff forever, since that way they never have telltale roots. What there should be IMO is something like an icon called Media Player that gets mapped to a default media player. If the user wants a different media player (a more advanced user), they change the mapping for their login user or create a new icon and map the next media player to it. An admin should be able to remap the global media player, if necessary.
Yes, what I'm getting to is to create a basic installation of dumbed down linux (maybe even a distribution - NoobLinux;) - I'd go as far as say make a recommended package based on the easiest to use tools rather than the most powerful ones. I base this on my own experience - back when I first had to learn UNIX editors (mostly vi and emacs) I always found great joy moving to the SGI boxes and running jot. Jot had no power whatsoever, but it was intuitive and easy to use, and until I really got the handle on emacs and vi (which took years) it was more than powerful enough for me. Even now I'm practically a vi god (and decent in emacs), but I forget stuff little things I don't use much like the mark/cut/paste tool rather than yank or delete and paste and there is no simple way to remember them. At that point I usually just open it in xemacs rather than look up the command, since I use vi mainly for fast editing and if I have to look up a command it's not fast.
I find it hard to believe SGI and ATI weren't aware of this a long time ago and I doubt they can win a court case on it unless they are referring to work done before it became an ARB extension of OpenGL.
SGI (Jon Leech to be specific) was part of the ARB group that near-unanimously approved the ARB extensions WGL_ARB_pixel_format_float, ARB_texture_float, ARB_half_float_pixel, and ARB_color_clamp_control into OpenGL in 2004. The real problem is that SGI LICENSES OpenGL, something hardware and software manufacturers pay a licensing fee to use (Mesa is an OpenGL work-alike, NOT OpenGL). I believe the licensing fee is supposed to cover any patents involved, but I could be wrong.
What I don't understand is that I thought GPUs were made to offload a lot of graphics computations from the CPU. So why are we merging them again? Isn't a GPU supposed to be an auxillary CPU only for graphics? I'm so confused.
A very similar argument is FPUs (floating point units) 20 years ago. Separating the floating point and integer processors was more expensive if you wanted both (it was cheaper to put them on a single die) but since the majority of machines didn't need an FPU, entry-level (the majority) PCs without them were much cheaper and if FPU operations were required they could be done with much slower software methods (e.g. Newton's Method).
Essentially, I think this is signaling that we're getting to the point where it may be more cost effective to put the GPU, or at least a base-level GPU on the die. There may be alternative reasons like sharing unused high speed GPU memory as a L2 or L3 cache to speed up non-graphics operations, as well, but I'm speculating.
Where I'm from (Minnesota) if you say Hockey, you mean Hockey on ice, though it's perfectly fine to call it Ice Hockey if you want. The modifier appeared to distinguish it from Floor Hockey and Roller Hockey, both of which I played without helmets or pads as a kid, leading to lots of scrapes and bruises. I also played hockey with pads - mainly as a goalie since it was easier to avert exercise induced asthma that way, and got tons of bruises that way, too.
I don't think the schools should be sued, tho - sue bastards like my 8th grade gym teacher, a guy that graded on performance only - completely unfair to moderate-persistent asthmatics like myself. On the last lap around the track in my fall gym class I told him I didn't think I would make it because my asthma had gotten so bad and he basically said he had no problem with failing me, so being the bull-headed kid I was, I kept running. I woke up in an ambulance getting oxygen (I think they gave me an adrenaline shot, too, but I don't remember). Thankfully I was good at most other gym sorts of things, but that class was the only 'B' I got in Jr High - all because of that race.
I think you missed two key points:
Pick something with realistic goals for whatever sized team you have (or self) and set goals
Design your work first
If you don't do those, you'll probably never learn to finish code. Setting goals with a team usually needs to be done based on time and skill levels of members. If it's just you, set goals for yourself and stick with them as best as possible. Don't worry too much about missing a date as long as you made progress towards your goal (but make sure to set a new goal).
Also don't be afraid to axe a project if you have to. I had a flight sim with some beautiful code in it (the blitter was fantastic... too bad blitters died with that era of hardware) and over a year of work and I killed the project even though completion was probably only a few months away. Why? because it had a problem at the core of the engine that was unfix-able and needed to be recoded from scratch to boost it to optimal framerates (specifically, I used virtuals at a low level not knowing that they have an expensive look-up table). I also had bought my first Voodoo card by that point and knew that was the future, not painter's algorithm and blitters. As sad as I was killing what I hoped would be a shareware quality flight sim, I learned so many lessons that it was worth the time spent.
I can't tell you how many kids I've talked to that want to make a commercial quality MMORPG or a 3D shooter in a few months...
that's a bit confusing anyhow - it's called a complex number. The component of a complex number that is "useless" is called the imaginary component.
Electronics would be in the stone ages without them (you need them for inductance calculations, which is very important in circuit and chip design), but they're not real, so who cares?
this just reminded me of a friend from Philly -
Geez man, for a few minutes there you were so close I thought you were gonna rear-end that guy.
what? I was giving him 2 feet!
It's the 2 SECOND rule you idiot!!
lesson 1: spoken like someone that's never been to a city like Minneapolis... the traffic "engineers" there had the brilliant idea that sometimes the left lane is for exits. The attempt at passing a law to make the left lane a passing lane fell apart because of this. For that matter, they also designed the beltway system to always fork a lane towards the cities at regular intervals, so it's a constant merge if you want to stay on the beltways (sometimes left, sometimes right).
;)
as for lesson 2, since when did the US get an autobahn? last I heard, they shut the only one down (Montana). If it's an emergency, zip around on the shoulder (except in Boston, where I've noticed it's always an emergency, so you have to use the sidewalk
hey - I can rant on this too -
it really bugs me when some impetuous fool rides my bumper and flips his headlights on and off incessantly while trying to go 170 miles an hour in a 65 during rush hour and thinks that there is a chance in hell that I can find 3 inches (much less 10 feet) of space to merge into the right lane.
and BY THE WAY, if I am in the left lane and am next to another car going the speed limit on my right and you race up behind me and "tailgate" (since you say there's no such thing) trying to get me to merge right (which I can't due to the other car), I legally need to SLOW DOWN to stay within the government provided legal limits, and 99% of the time when I slow down, you merge to pass me on the right, even if I have my signal on to get in the that lane.
If it bugs you so much that some of us don't want to break the law, why don't you write a bill, take it down to city hall and get your faithful congress-people to sign it making the US freeways into autobahns? Quite honestly, I'd be perfectly happy going 170MPH and getting to work in 1/3 the time, but I find speeding tickets a waste of money and time. So stop nagging me on how to drive and enjoy the extra paper you get in your pocket for your failure to obey the traffic laws your representatives in government created to protect you and save on oil.
For the most part, if the code was written to work cross-platform to begin with, the work is trivial. Unfortunately, code usually isn't written that way - most game developers use DirectX (such as NWN2, unlike its predecessor), Physics APIs (e.g. Havok, though there is a mac version now), Tree APIs (speedtree), and others that are usually Windows only. Not only that, they usually charge premium licensing fees if they do offer a Windows alternative (ahem - Havok). Should they decide to port, they also need to beat cross-platform solutions like Cedega to market on Linux or they've pretty much lost that market.
I didn't mean TCP is a great protocol for voice (it isn't, though it might be for sample and send [uncompressed] data). My problem is with the choice of ATM, which was picked because it matched hardware the telecos were using at the time, not for being a great protocol for voice traffic. It actually is a bad protocol for the switches used by telecos today. The telecos also standardized ATM on their trunk lines for the Internet, even though it's a terrible protocol for data (using 100 motorcycles when a bus would work just as well). ATM also has a packet verification stage (guarantees QoS or "Quality of Service"), which increases the total load. I believe the average was around 17% load both ways, where load meant something like header + send verification + average packet loss at 85% capacity.
VoIP does not have a QoS guarantee - VoIP uses UDP (Universal Datagram Protocol), not TCP which does not guarantee packet arrival. UDP uses 20 byte packets over IPv4 (TCP is 36 I think). Since UDP does not reply back to the sending machine, it may actually work faster on average, but may also have jitter, especially over long, noisy, or very busy connections.
One way to counter the empty packet thing that you mentioned is a technique used in cell phones applied to IP - TDMoIP, which bundles a bunch of packets going to the same destination together.
yeah, yeah, rectifying mumbo-jumbo - nobody wants to hear about that. What you want to do is take one of those really big capacitors in an old TV, unsolder the leads and solder them in backwards. Then hook up the power.
See, it's simple - Slashdot readers want to see shrapnel - and lots of it, not how to safely do stuff with electricity. Keep your education stuff in the schools.
In Bill's first act as President, he promises to release US Government 2.0, which is already reported to be about 200 years late. Rumor has it that 3.0 codenamed "Galloway" is also in the works.
;)
Ok, probably one person at best is gonna get that one unless I spill the beans... Galloway is a hornless breed and also hornless dominant, as crossing them with longhorns produces only hornless cattle. Yes, that was far too nerdy of a joke, even for here
The geoport express modem was a first generation soft-modem - it wasn't really meant to be an internet phone (as per the patent - it mentions something about phone layout), so the patent may be valid in that respect. Many manufacturers made soft modems, though they're rare today.
In high school I had a friend that made manager at McDonalds in 6 months and was running the place at 8 months, so saying you're a former McDonalds manager doesn't mean much. I imagine the turnover had to be huge for him to advance so quickly, though. I don't remember ever having much of a problem with turnover or people showing up on time when I was working at a restaurant, but maybe you just get a lot more of the dregs of society in fast food. OTOH, he was getting paid almost 3 times what I was before heading off to college and had management experience, something I didn't get until many years later.
;)
Seems to me a Big Mac, fries, and a diet coke was 2 points over my weight on the weight watcher's chart - that's for food in a day, not a single meal. Thankfully I haven't had a craving for one of those since 1996 when I barfed one up on choppy seas (getting SCUBA certified).
I rarely eat KFC, but I recall they had a problem with being high in trans-fats, which are known to cause health problems. I'm sure it isn't as bad as health problems related to chain smoking, so you should be fine (yes, that was a feeble attempt at sarcasm).
Let me guess... you drink 6-12 355mL bottles of Miller Lite, right
The idea of packet order guarantee and ethernet are pretty much mutually exclusive, and upon further review (reading the fa), it reassembles out-of-order packets pretty much just like TCP. About the only new thing is the out-of-order disassembly and assembly and the overall speed. It still has the same flaws as Ethernet, which is that it really is only about 80-85% efficient - after that you would be better off with a Token Ring or other managed protocol (token rings are excellent for saturated networks but poor for low saturated networks).
Sigh - and the poster seems to think ATM is a good protocol, but ATM is a terrible protocol, especially for data, but even for voice it's mediocre. It was designed for voice conversations over high noise lines with significant data loss (copper) and predominantly used over low noise high speed lines with almost no loss (fiber). Its advantage is standard packet length (53 bytes) and speed. Worst disadvantage - almost 10% overhead (5 bytes of every 53, or ~9.4%). ATM also has no guarantee of sort order or collision avoidance (since it's asynchronous) so in practices it can be really bad. Incidentally, my networking class voted this the worst protocol back in 1996, but expected it to succeed mainly because of telecoms pushing it.
Actually, neither of you is wrong for Trojans, but your definition of Virus is incorrect, since viruses can propagate over network drives and diskettes (which is not activated by the user), a common problem at businesses and schools and also the original way viruses got spread.
A Trojan is an application masquerading as another application. It can contain any payload but usually refers to a malicious payload (much like its namesake, the Trojan Horse). A Trojan is therefore not a virus and also does not self-replicate and is activated by a user.
A Virus refers to self-replicating code. Many viruses also contain a payload, but this is not really the virus itself. Some of the more malicious viruses will e-mail Trojans of themselves, while others may be entirely benign.
A worm essentially refers to a program that self-replicates over a network, but worms with a payload of viruses and/or Trojans are usually just called worms.
and the other category (though rare) - the timebomb
A timebomb (or bomb) is a program that is tacked onto another program, usually manually. It has no self-propagation. When it "detonates" after a prescribed number of launches or time period, it does something malicious, including wiping drives, installing viruses, or running zombies.
Microsoft and others have stated that a parts of Paragraph 3 and 4 of the LGPL are ambiguous and depending on interpretation, could force them to be construed a derivative work. After reading that section, I decided that I can't link LGPL into my mac apps as well.
/usr/lib and that it has a special install path (@executable_path/../Frameworks). Since the finished application bundle is seen as an application and not a directory tree, this could be interpreted as part of the application as per the LGPL and therefore is a violation of the LGPL.
My best guess as to the meaning of sections of those paragraphs:
The LGPL essentially forbids you from statically linking a library into your work
The LGPL allows dynamically linking (though this may be interpretable, as there are wording conflicts with the previous paragraph)
Mac applications, however, make an ambiguity between the 'application' and the library if the library is built as an embeddable framework. Essentially an embeddable framework is a dynamic library that gets bundled into a specially formed directory tree that is seen by the GUI as an application. It is built and functions exactly the same as a dynamic library, aside from that it isn't placed in a globally accessible place like
A project I'm working on decided not to use any LGPL code in our project and instead only provide hooks to such code (for instance, someone added OpenAL hooks) because we don't want to be superseded by the LGPL. Actually, I don't believe we can even switch licenses if we wanted to at this time unless we freeze and fork the current Zlib licensed version due to several co-authors using commercial pieces (that forbid becoming derivative code).
I just read in US News and World Reports (early November 2006 issue, if I'm up-to-date - I was a bit behind due to a vacation) that the numbers acknowledging to be Atheist are more like 1% in the US and 10% don't believe in a single all powerful deity (so spiritualists and agnostics).
Too bad it doesn't have religious crazies - I'd like to know the percentage of people that believe all other religions should be destroyed with whatever means necessary.
Most game programmers have none of the above. I've known 3 and the best educated of them has between 2 and 3 years of college, which got him through C++ and then he got hired by Volition (and has moved around since). The other two started working straight out of high school for MECC (the Oregon Trail people) and Wizard Works (or wizworks? - low budget games), both of which were absorbed into larger companies. I lost touch with all three of them in college, but I do still chat on IRC with some other game industry people (and lots of wannabes) due to some open source game engine work I do.
Incidentally, I wanted to get into games once upon a time (I'm currently employed by a CAD company) and I had Graphics and AI, but not operating systems. I did have hardware courses because I took CE for 2 years before switching to CSCI, but no fundamental OS courses. Quite honestly, I don't see the point of AI - A* is probably the most important part of game programming and it was less than one day in my coursework. Most of the other stuff is not really suited to game programming, though some of that class was redundant to my hardware classes (doing AND, OR, XOR, etc in software). Heck, we wasted more time on learning the differences between Lisp and Scheme (the "starter" language taught at the college I transferred into) than A*. The only thing I've used Lisp for since is customizing emacs. I've used A* a LOT.
You missed Networking, though I'd have to stress finding a network coding class as opposed to a survey of networking (my first networking class was more of a survey class - it was interesting, but had almost no programming).
Yeah, but it's still an underlying 64 bit architecture that's running in a 32 bit mode. Fixes for bugs to that would be provided by AMD.
Since you tried a single core, though, it makes me suspect the real problem is with the shared cache between the cores. I can't think of anything else that AMD would patch, at least, that would fix application problems, especially if the cores themselves are the same architecture as the single core chip you had in first.
3.8% is a tiny percentage. Compare that to individual protestant groups and it may seem like a nice slice, but compared to all religions it's a tiny percentage.
anyhow, I noticed I had a train-of-thought error in my post earlier. Gotta proof-read better after I get interrupted.
That's not necessarily a multicore problem. With most games, it's probably more likely a problem with the 64 bit architecture running 32 bit code.
The exception would be if the code is, in fact, multithreaded or if it runs a server and clients as separate processes. Most games don't, or at best use a thread to dynamically load files in the background (and most games that do that are RPGs like Diablo 2 and Gothic 1-3). Even then, assuming that threads are stable, it's highly likely that the problem would crash 32 bit machines as well (with the possible exception of race conditions).
The major problems with threads are lock/starvation (see the dining philosopher's problem and race conditions (you have A and B in separate concurrent threads but A needs to finish before B). Both of these problems are usually caused by coding errors.
The only confirmed atheist I know considers Bush a vegetable in more ways than just name, so I guess neither side likes the other much. Aside from our mutual dislike for Bush, I don't agree with her political or ethical beliefs (Green party, PETA, vegan), but she's married to one of my buddies, tho, so I can't exactly divorce her (he's agnostic).
All things considered, if you wanted to persecute one particular group, atheists are an easy target. Most people believe in some sort of God or gods, and only a tiny percentage of people believe there is no God. One thing all the religions in the world can agree upon is that the atheists are wrong (even if they're right - I have no proof one way or the other).
I haven't reinstalled Windows for years on my own system and by using good registry and spyware cleanup software, then a defrag I usually can clean up most other people's computers.
PC Enthusiasts are the ones that swap out hardware. I have a 5 year old case, but no hardware in it is more than 2 years old. I repair other people's computers, too - heck, I'm doing it now for my brother-in-law, whose heatsink fan (HSF) failed and the computer was overheating after 5-10 minutes of use. I'll charge him $10 because I had to buy some new thermal compound (which is why it's not done yet), but I had plenty of spare HSFs lying around, so he gets one of those free. That repair woulda been $100+ anywhere else and takes me all of 5 minutes and had a net part cost of $15 with new parts.
The problem is, enthusiasts will often swap out a mobo, CPU, and memory at the same time and suddenly Windows thinks that it is a pirated system since too much hardware has changed. I talked to Microsoft reps twice now because I had to re-enable my Windows XP and had used up my installs. The first time was because of a bug in Windows XP where it incorrectly identified my ATA disk as the SATA drive I was trying to install on and wiped all my data, so I was pretty miffed when I called (incidentally, I noticed that bug was fixed in the XP SP1 installer when I installed on my wife's machine with a similar setup).
Before someone heckles me about why I don't switch to Linux, I do run Linux, and MacOS, for that matter. I need them all for work, so I'm pretty much screwed and can't dump Windows. For that matter, for the most part I like Windows. It's certainly not without its flaws, but I can say the same about KDE, Gnome, and MacOS X.
I think the Linux GUI is adequate if not "good enough" in its current state, tho - I find both Gnome and KDE perfectly usable and even more so if you're already familiar with Windows. The problem I have with both is after a default install I had a bunch of applications with names like xmms, and I often get multiple redundant applications like Helix or MPlayer. What do these do? Which is best? You're making a novice user make a lot of choices about software they don't understand. Yes, I know both the 3.0 versions of Gnome and KDE made strides against this with descriptive menu names, but I still get three or 4 apps called media player and I have no idea what media they play (I pick on this because I remember from my own experience that some of these played MP3s, others didn't and I could never remember which).
;) - I'd go as far as say make a recommended package based on the easiest to use tools rather than the most powerful ones. I base this on my own experience - back when I first had to learn UNIX editors (mostly vi and emacs) I always found great joy moving to the SGI boxes and running jot. Jot had no power whatsoever, but it was intuitive and easy to use, and until I really got the handle on emacs and vi (which took years) it was more than powerful enough for me. Even now I'm practically a vi god (and decent in emacs), but I forget stuff little things I don't use much like the mark/cut/paste tool rather than yank or delete and paste and there is no simple way to remember them. At that point I usually just open it in xemacs rather than look up the command, since I use vi mainly for fast editing and if I have to look up a command it's not fast.
The Linux way seems to be to experiment with each media player until you find the one you like best, but to be honest, I think a novice user doesn't want to make a decision - they just want to click their song and the GUI picks the one that works. I mean, if I want to dye my hair green, do I care if the dye is made by Bob's Dye Factory or Garnier? Most people, at least the first time, just want something that does the trick. Maybe later they'll find that the Bob's stuff washes out after a week and the Garnier stuff is basically permanent, but let the user figure that out for themselves and make the switch later - they may be perfectly happy with Bob's stuff forever, since that way they never have telltale roots. What there should be IMO is something like an icon called Media Player that gets mapped to a default media player. If the user wants a different media player (a more advanced user), they change the mapping for their login user or create a new icon and map the next media player to it. An admin should be able to remap the global media player, if necessary.
Yes, what I'm getting to is to create a basic installation of dumbed down linux (maybe even a distribution - NoobLinux
I'm sure that it's a reference to the Billgatus of Borg or maybe the old joke
I find it hard to believe SGI and ATI weren't aware of this a long time ago and I doubt they can win a court case on it unless they are referring to work done before it became an ARB extension of OpenGL.
SGI (Jon Leech to be specific) was part of the ARB group that near-unanimously approved the ARB extensions WGL_ARB_pixel_format_float, ARB_texture_float, ARB_half_float_pixel, and ARB_color_clamp_control into OpenGL in 2004. The real problem is that SGI LICENSES OpenGL, something hardware and software manufacturers pay a licensing fee to use (Mesa is an OpenGL work-alike, NOT OpenGL). I believe the licensing fee is supposed to cover any patents involved, but I could be wrong.
A very similar argument is FPUs (floating point units) 20 years ago. Separating the floating point and integer processors was more expensive if you wanted both (it was cheaper to put them on a single die) but since the majority of machines didn't need an FPU, entry-level (the majority) PCs without them were much cheaper and if FPU operations were required they could be done with much slower software methods (e.g. Newton's Method).
Essentially, I think this is signaling that we're getting to the point where it may be more cost effective to put the GPU, or at least a base-level GPU on the die. There may be alternative reasons like sharing unused high speed GPU memory as a L2 or L3 cache to speed up non-graphics operations, as well, but I'm speculating.
Where I'm from (Minnesota) if you say Hockey, you mean Hockey on ice, though it's perfectly fine to call it Ice Hockey if you want. The modifier appeared to distinguish it from Floor Hockey and Roller Hockey, both of which I played without helmets or pads as a kid, leading to lots of scrapes and bruises. I also played hockey with pads - mainly as a goalie since it was easier to avert exercise induced asthma that way, and got tons of bruises that way, too.
I don't think the schools should be sued, tho - sue bastards like my 8th grade gym teacher, a guy that graded on performance only - completely unfair to moderate-persistent asthmatics like myself. On the last lap around the track in my fall gym class I told him I didn't think I would make it because my asthma had gotten so bad and he basically said he had no problem with failing me, so being the bull-headed kid I was, I kept running. I woke up in an ambulance getting oxygen (I think they gave me an adrenaline shot, too, but I don't remember). Thankfully I was good at most other gym sorts of things, but that class was the only 'B' I got in Jr High - all because of that race.