You may not be able to use sockets directly with WaitFor[Single|Multiple]Objects(s), but you can attach an event to a socket (using WSAEventSelect IIRC) and wait on that, along with other things (which effectively gives you BSD's select() for Windows' file handles.
As far as the discussion on concurrent programming goes, I'm surprised no one has yet mentioned boost.threads.
What is the ethical problem with using embryonic stem cells from fertalized eggs that are being thrown away from a fertility clinic?
Other than the view that not allowing fertilized eggs to naturally develop is murder (or similar views), there is no ethical problem with using embryonic stem cells for... well... any use. Make good with what you got, right? The problem with this is that the abundance of fertilized eggs is artificial. Parents want kids made from their own DNA (and perhaps don't want other people using their DNA), so leftovers aren't shared. The abundance is also artificial because there are other (more ethical -- in the sense that resource efficiency is ethical) choices than fertility treatments: adoption (of orphaned/unwanted/abandoned children & otherwise to be aborted pregnancies) & simply having no kids come readily to mind. So, to me the real problem (that you alluded to) is not using what would be otherwise discarded embryos, but rather the existence of the fertility clincs themselves.
Logic dictates that everybody buying the machine with FreeDOS will be relatively computer-savvy and thus won't need support, but humans have proven logic wrong on a number of occasions...
OTOH, it also seems logical that people will buy whatever is cheaper... so simply by overpricing the FreeDOS version Dell avoids the posibility of having to deal with potential customers who do not know the difference, and want to know where their windows are.
actually, in many jurisdictions its the law (or so says my wife who has worked in HR departments in mulitple states. This is the best I could come up with quickly in google. Of course, just as you can get away with speeding if no one is watching, so can you also get away with giving out too much information.)
If it costs the same as a CD I'll buy the CD if I want to be legit. A CD is lossless and comes with the little booklet anyhow
I aggre with your point, but a CD is not lossless. In fact, by definition all digital recording schemes are not lossless. For a CD, the analog wave form is runthrough an AtoD that encodes the music at 320kbps, sampled 44.1 Hz.
I think what you meant to say is that all online music stores (at least, all the ones I'm aware of) have encoded the music from a CD to some lossy format and sapped on some DRM scheme.
If you really want the original waveform, I suppose you'll have to settle for a live performance -- I don't even think the master DAT will do.
Not to mock your sister's, your's, or your family's pain, but have you considered seeing what she can do with a pile of cross-cut documents?
Maybe I've watched too much sci-fi, but I would reckon the goverment could find some use for her.
Re:I code C# for a living
on
Java 1.5 vs C#
·
· Score: 3, Informative
Granted I've only used a few IDEs (VS6, VS.Net2002, VS.Net2003, Tornado for vxWorks, Xcode, Kdevelop & ddd), but of all VS.Net is cleanly the easiest to get things done in overall.
I did not find Kdevelop or ddd particulary more useful than vi other than having been weaned on VS6 I am simply more comfortable with a GUI than a tty.
Xcode does every part of project management and structure more correctly than VS in my opinion. The idea that your source tree is separate from your targes and that your targets are separte from your executables just makes sense. There's a lot less special cases this way.
Tornado for vxWorks (ver 2.2.1 IIRC, its been some time since I used it) is a poor copy of VS6 -- possibly more correctly VS5 or 4, but I've never used those. The one thing that Tornado got right is the remote debugging (e.g., you build a vxWorks system, load it onto your embeded system, and you can debug through your app via ethernet, serial port, or a local pci bus). In fact, without the remote dubugging I would have considered Tornado to be utterly useless.
The things that set VS apart is its build styles and debugging features. Xcode could catch up on the both of these (esp. the build styles), but I'd say gdb has a long way to go to be on the same leve als VS's debugger. Its really nice to be able to add new code, change existing code, and arbitrarily set the execution pointer. Really the 'advanced feature' I've figured out how to replicate on gdb is changing a variable's value, but even this feels rudimentary to how in VS you can arbitrarily change the contents of memory directly.
So, in short, what I like about Visual Studio is its build styles and debugging capabilities. But I do think Xcode 1.5 is better thought out, just not as polished in these two areas.
I should add that all this does not apply to any APIs of the aforementioned products, in which I would agree with you (having used MFC, ATL, COM and WIN32), I don't see why informed person would choose these over the alternatives (wxWindows, stl, boost, Cocoa) if they had a choice.
Also, the reason it's so important is because it is less dense in the solid phase than the liquid phase, which allows it to freeze on top instead of on bottom...
Just some further claification from someone who grew up on a pond and who's father is a chemical oceanographer, water freezes top-down because it is most dense at 4C. So, as water cools from above 4C, it sinks, and as it cools from below 4C it rises.
Of course, as the above 4C water meets the below 4C water there's a heat transference. This means the WHOLE body of water has to be cooled to 4C before it will (significantly) go below 4C.
Once at 4C, then the top will begin to freeze over because of the fact that the below 4C water is less dense, and therefore rises to the top.
Please stop. The courts are NOT the place to be changing the laws. If you don't like the law, take it to the legislature, or to your local public if your state has voter initiatives.
<blockquote><i>When are the record labels going to understand that their product isn't worth what they want to charge?
It's like the NBA - a big marketing scheme where the underlying product does not have the appeal nor the value their pushers would like us to assign...</i></blockquote>
<p>Ju st further argument that all things would be better if all things were more like hockey. If I could have had my wedding on ice, I would have.</p>
...you can fix allot of bad browser bugs by giving an extra 'patch' css file to different browsers that contains your specific fix for that browsers issues.
I think if vendors treated HTML from the begining like a compiled langauge we would not need "'patch' css" files. A bug is a bug is a but IS NOT A FEATURE! For example: do C/C++ developes put up with addition of 7 numbers only really taking the inner 5? Then why does IE continue to get the box model wrong?
This is why I think XHTML is a step in the right dirrection... FrontPage et. al. may still spit out garbage, but at least it will have to be valid and well formated to be called XHTML. Of course, having said that someone is bound to show me where it currently produces non-HTML HTML.
I had to fall back on tables in some cases just to get a simple header including centered text with justified (left and right, respectively) flanking images.
It's not good enough to use CSS, you gotta make good use of CSS, and valid (X)HTML. It also helps if your target audience uses a standards compliant browser, which in my opinion is why most of the web still uses tables for layout -- its just easier than to deal with browser quirks.
With a virtual desktop you couldn't do that, and with a traditional desktop you'd constantly have to be switching, because most likely you'd have the IDE and document fullscreened.
The problem isn't traditional desktops, but the MS Windows-like multiple document interface that demands to take up the whole screen. I have no problem in OS X using Xcode, gimp, and SubEthaEdit simultaneously, with multiple windows/tool bars open for each app/document window. I suppose it also helps that there's only one menu bar, not to mention Exposé.
Logically, the correct answer is always (or nearly-always) 3. "The client who commissioned and is paying for the development".
If you're an employee, then the client is your employeer. If you're contract, then the client is... erm... the client. If you're doing it for yourself, the then client is you. If its for GPL'ed (or similar) code, then the client is the license.
I guess for those last two clients aren't paying in cash, and therein lies the problem with the question.
NOBODY expects a copyright circumvention program to work perfectly! Our chief weapon is surprise...surprise and fear...fear and surprise.... Our two weapons are fear and surprise...and ruthless efficiency.... Our *three* weapons are fear, surprise, and ruthless efficiency...and an almost fanatical devotion to the DMCA.... Our *four*...no... *Amongst* our weapons.... Amongst our weaponry...are such elements as fear, surprise.... I'll come in again.
True, in the current market, the unsuccessful yet talented artists (as well as the untalented) are dragging the ship down, until they can repay their advance. Also, the market is inundated with music that most people don't really care about, but it's what's "popular", because the labels have so heavily promoted it.
Sidenote: see any similarities in the computer industry?
In a normal state we would not have the Britney Spears type musicians, because they would not be popular. But in this current state, the labels have too much power because the half-talents have no problem jumping at a $1,000,000.00 signing bonus (which I would be more than happy to sign for, and so would any one thinking firstly of themselves).
Good music, as with any good product, comes best from a sink-or-swim market. The labels need to stop hemorrhaging money to the half-talents, and see that there's room in the market for more than one genre at a time. Unfortunately, the nature of business is to create products, and push the most profitable, not give the consumers what they want.
The winners pay. The winners pay for the losers, and the winners are not seeing rewards commensurate with their success. And they get upset. So what's the remedy? The remedy is to stop paying advances. The remedy is to go to a gross-revenues deal and tell an artist, "We'll give you twenty cents on every dollar we get, but we're not gonna give you an advance. The accounting will be simple: We're gonna pay you not on profits -- we're gonna pay you off revenues. It's very simple: The more successful you are, the more you'll earn. But if you're not successful, you will not earn a dime. We'll go ahead and risk some marketing money on you. But if you're not successful, you'll make no money. If you are, you'll make a lot more money." That's the way out. That's the way the rest of the world works.
I was listening to the Mike Reagan show around Thanksgiving time, and apparently the Pilgrims went through the same phase. Their original charter stated that each family would be given a plot of land to farm, from which all crops would be put in a community store. Everyone would get a equal share of crop.
The plan failed misserably. There was no incentive to work hard. Its the same reason the Communism lost the cold war. There's no point in working harder if the fruits of your labor are taken away by the state.
So, the Pilgrims threw away the old charter and wrote a new one. Rather than having to surrender all to the community store, families kept their crops. Those that worked hard during the growing season got to eat during the winter. Those that didn't, died. Incentive spurned the surplus we know as Thanksgiving.
As Steve Jobs has forseen, the record companies can do the same thing. I suppose the losers are the musicians who don't make it. But why should we feel bad for the leetches of society?
I live in Nampa, ID. There's a hospital/recreation center two blocks west from me, business center four blocks south, expensive developments to the east, and a university (NNU) to the north by three blocks.
I can't get DSL or cable. Neither company (CableOne or Qwest) wants to come out and hook me up. I'm convinced that they simply have the position that they have enough customers, one more (or 8 more in the case of all the people on the block that would be interested) is not going to change their minds.
My school got a pair of Phaser 840s for free under some stress-test program for the main lab. All we had to do was provide the paper, and call the service guys when it broke (which it did only once in my four years there).
Seeing that this model has been discontinued, you may want to check out the $300 savings on the Phaser 8200.
I was introduced to VxWorks when my previous employer asked me to port some drivers (ISA, PC-104 and PCI) for it. My overall impression was that it provided some nice libraries (multi-processes, semaphores, sockets, pipes, networking, as well as low-level IO) and was a piece of cake to get set up. It was Tornado, the IDE for VxWorks, that sucked. At best I was able to ignore it... at worst I actually had to use it.
I really don't know what the dev team was thinking when the released it. Its a total visual studio 6 rip off, but most of the useful features don't work, and the others are buggy or illogical at best. The debugger could never remember what radix to display data in, anytime a file was saved with the editor you lost your undo buffer, and every now and then it woud do strange things to the build rules (the makefiles were generated every time you built a module) that would generally screw everything up and leave you with an error message like 'not found' or 'error'.
So, I gave up using it and did my work in MSVC: it was far quicker to write custom build rules for VC than to fight with Tornado. When I left that job I spent an entire day writing a report on the bugs and strange things that Tornado would do.
The one thing that Tornado did do right was its remote connection. I was able to boot VxWorks off of a floppy on a test machine, and control it via Tornado's debugging terminal on my dev computer. It took some getting used to (the frame pointer wasn't always in thre right spot, and nested function calls could confuse things), but it worked well enough to finish the project on time.
Slashdot Mirror
Romanes eunt domus
You may not be able to use sockets directly with WaitFor[Single|Multiple]Objects(s), but you can attach an event to a socket (using WSAEventSelect IIRC) and wait on that, along with other things (which effectively gives you BSD's select() for Windows' file handles.
As far as the discussion on concurrent programming goes, I'm surprised no one has yet mentioned boost.threads.
Other than the view that not allowing fertilized eggs to naturally develop is murder (or similar views), there is no ethical problem with using embryonic stem cells for... well... any use. Make good with what you got, right? The problem with this is that the abundance of fertilized eggs is artificial. Parents want kids made from their own DNA (and perhaps don't want other people using their DNA), so leftovers aren't shared. The abundance is also artificial because there are other (more ethical -- in the sense that resource efficiency is ethical) choices than fertility treatments: adoption (of orphaned/unwanted/abandoned children & otherwise to be aborted pregnancies) & simply having no kids come readily to mind. So, to me the real problem (that you alluded to) is not using what would be otherwise discarded embryos, but rather the existence of the fertility clincs themselves.
yeah man, I hear you... those pesky clients are always in the way of getting work done.
OTOH, it also seems logical that people will buy whatever is cheaper... so simply by overpricing the FreeDOS version Dell avoids the posibility of having to deal with potential customers who do not know the difference, and want to know where their windows are.
actually, in many jurisdictions its the law (or so says my wife who has worked in HR departments in mulitple states. This is the best I could come up with quickly in google. Of course, just as you can get away with speeding if no one is watching, so can you also get away with giving out too much information.)
I aggre with your point, but a CD is not lossless. In fact, by definition all digital recording schemes are not lossless. For a CD, the analog wave form is runthrough an AtoD that encodes the music at 320kbps, sampled 44.1 Hz.
I think what you meant to say is that all online music stores (at least, all the ones I'm aware of) have encoded the music from a CD to some lossy format and sapped on some DRM scheme.
If you really want the original waveform, I suppose you'll have to settle for a live performance -- I don't even think the master DAT will do.
Not to mock your sister's, your's, or your family's pain, but have you considered seeing what she can do with a pile of cross-cut documents?
Maybe I've watched too much sci-fi, but I would reckon the goverment could find some use for her.
Granted I've only used a few IDEs (VS6, VS.Net2002, VS.Net2003, Tornado for vxWorks, Xcode, Kdevelop & ddd), but of all VS.Net is cleanly the easiest to get things done in overall.
I did not find Kdevelop or ddd particulary more useful than vi other than having been weaned on VS6 I am simply more comfortable with a GUI than a tty.
Xcode does every part of project management and structure more correctly than VS in my opinion. The idea that your source tree is separate from your targes and that your targets are separte from your executables just makes sense. There's a lot less special cases this way.
Tornado for vxWorks (ver 2.2.1 IIRC, its been some time since I used it) is a poor copy of VS6 -- possibly more correctly VS5 or 4, but I've never used those. The one thing that Tornado got right is the remote debugging (e.g., you build a vxWorks system, load it onto your embeded system, and you can debug through your app via ethernet, serial port, or a local pci bus). In fact, without the remote dubugging I would have considered Tornado to be utterly useless.
The things that set VS apart is its build styles and debugging features. Xcode could catch up on the both of these (esp. the build styles), but I'd say gdb has a long way to go to be on the same leve als VS's debugger. Its really nice to be able to add new code, change existing code, and arbitrarily set the execution pointer. Really the 'advanced feature' I've figured out how to replicate on gdb is changing a variable's value, but even this feels rudimentary to how in VS you can arbitrarily change the contents of memory directly.
So, in short, what I like about Visual Studio is its build styles and debugging capabilities. But I do think Xcode 1.5 is better thought out, just not as polished in these two areas.
I should add that all this does not apply to any APIs of the aforementioned products, in which I would agree with you (having used MFC, ATL, COM and WIN32), I don't see why informed person would choose these over the alternatives (wxWindows, stl, boost, Cocoa) if they had a choice.
exactly. other repliers to this post are quite uninformed. see http://www.iawca.org/mgfaq.htm for more information.
uh... that's VGER as in VoyaGER (6, IIRC)
Just some further claification from someone who grew up on a pond and who's father is a chemical oceanographer, water freezes top-down because it is most dense at 4C. So, as water cools from above 4C, it sinks, and as it cools from below 4C it rises.
Of course, as the above 4C water meets the below 4C water there's a heat transference. This means the WHOLE body of water has to be cooled to 4C before it will (significantly) go below 4C.
Once at 4C, then the top will begin to freeze over because of the fact that the below 4C water is less dense, and therefore rises to the top.
Please stop. The courts are NOT the place to be changing the laws. If you don't like the law, take it to the legislature, or to your local public if your state has voter initiatives.
<blockquote><i>When are the record labels going to understand that their product isn't worth what they want to charge?
It's like the NBA - a big marketing scheme where the underlying product does not have the appeal nor the value their pushers would like us to assign...</i></blockquote>
<p>Ju st further argument that all things would be better if all things were more like hockey. If I could have had my wedding on ice, I would have.</p>
I think if vendors treated HTML from the begining like a compiled langauge we would not need "'patch' css" files. A bug is a bug is a but IS NOT A FEATURE! For example: do C/C++ developes put up with addition of 7 numbers only really taking the inner 5? Then why does IE continue to get the box model wrong?
This is why I think XHTML is a step in the right dirrection... FrontPage et. al. may still spit out garbage, but at least it will have to be valid and well formated to be called XHTML. Of course, having said that someone is bound to show me where it currently produces non-HTML HTML.
you mean something like:
It's not good enough to use CSS, you gotta make good use of CSS, and valid (X)HTML. It also helps if your target audience uses a standards compliant browser, which in my opinion is why most of the web still uses tables for layout -- its just easier than to deal with browser quirks.
Logically, the correct answer is always (or nearly-always) 3. "The client who commissioned and is paying for the development".
If you're an employee, then the client is your employeer.
If you're contract, then the client is... erm... the client.
If you're doing it for yourself, the then client is you.
If its for GPL'ed (or similar) code, then the client is the license.
I guess for those last two clients aren't paying in cash, and therein lies the problem with the question.
NOBODY expects a copyright circumvention program to work perfectly! Our chief weapon is surprise...surprise and fear...fear and surprise.... Our two weapons are fear and surprise...and ruthless efficiency.... Our *three* weapons are fear, surprise, and ruthless efficiency...and an almost fanatical devotion to the DMCA.... Our *four*...no... *Amongst* our weapons.... Amongst our weaponry...are such elements as fear, surprise.... I'll come in again.
True, in the current market, the unsuccessful yet talented artists (as well as the untalented) are dragging the ship down, until they can repay their advance. Also, the market is inundated with music that most people don't really care about, but it's what's "popular", because the labels have so heavily promoted it.
Sidenote: see any similarities in the computer industry?
In a normal state we would not have the Britney Spears type musicians, because they would not be popular. But in this current state, the labels have too much power because the half-talents have no problem jumping at a $1,000,000.00 signing bonus (which I would be more than happy to sign for, and so would any one thinking firstly of themselves).
Good music, as with any good product, comes best from a sink-or-swim market. The labels need to stop hemorrhaging money to the half-talents, and see that there's room in the market for more than one genre at a time. Unfortunately, the nature of business is to create products, and push the most profitable, not give the consumers what they want.
From the article:
I was listening to the Mike Reagan show around Thanksgiving time, and apparently the Pilgrims went through the same phase. Their original charter stated that each family would be given a plot of land to farm, from which all crops would be put in a community store. Everyone would get a equal share of crop.
The plan failed misserably. There was no incentive to work hard. Its the same reason the Communism lost the cold war. There's no point in working harder if the fruits of your labor are taken away by the state.
So, the Pilgrims threw away the old charter and wrote a new one. Rather than having to surrender all to the community store, families kept their crops. Those that worked hard during the growing season got to eat during the winter. Those that didn't, died. Incentive spurned the surplus we know as Thanksgiving.
As Steve Jobs has forseen, the record companies can do the same thing. I suppose the losers are the musicians who don't make it. But why should we feel bad for the leetches of society?
I live in Nampa, ID. There's a hospital/recreation center two blocks west from me, business center four blocks south, expensive developments to the east, and a university (NNU) to the north by three blocks.
I can't get DSL or cable. Neither company (CableOne or Qwest) wants to come out and hook me up. I'm convinced that they simply have the position that they have enough customers, one more (or 8 more in the case of all the people on the block that would be interested) is not going to change their minds.
Sucks for me, until I move.
My school got a pair of Phaser 840s for free under some stress-test program for the main lab. All we had to do was provide the paper, and call the service guys when it broke (which it did only once in my four years there).
Seeing that this model has been discontinued, you may want to check out the $300 savings on the Phaser 8200.
A$$le... no, that's not it... App$e? erm... Appl£!!! that's better.
I was introduced to VxWorks when my previous employer asked me to port some drivers (ISA, PC-104 and PCI) for it. My overall impression was that it provided some nice libraries (multi-processes, semaphores, sockets, pipes, networking, as well as low-level IO) and was a piece of cake to get set up. It was Tornado, the IDE for VxWorks, that sucked. At best I was able to ignore it... at worst I actually had to use it.
I really don't know what the dev team was thinking when the released it. Its a total visual studio 6 rip off, but most of the useful features don't work, and the others are buggy or illogical at best. The debugger could never remember what radix to display data in, anytime a file was saved with the editor you lost your undo buffer, and every now and then it woud do strange things to the build rules (the makefiles were generated every time you built a module) that would generally screw everything up and leave you with an error message like 'not found' or 'error'.
So, I gave up using it and did my work in MSVC: it was far quicker to write custom build rules for VC than to fight with Tornado. When I left that job I spent an entire day writing a report on the bugs and strange things that Tornado would do.
The one thing that Tornado did do right was its remote connection. I was able to boot VxWorks off of a floppy on a test machine, and control it via Tornado's debugging terminal on my dev computer. It took some getting used to (the frame pointer wasn't always in thre right spot, and nested function calls could confuse things), but it worked well enough to finish the project on time.