They couldn't accent it correctly. What you're getting is a smooth, meaty paste made from... cloth. Don't get me wrong, expensive cloth, it is! And I'm sure eating it will make you feel secure. Ummmm. Good, right? Can I interest you in a coffee, or a port?
that the S&M community will find a ton of interesting, uses. And also that everyone else will be distraught everytime Newsweek recycles the topic, and need to Do Something, with exceptions for watching what other people do.
However, that is no argument for locking up publicly funded data. Either the public should not be paying for it, or the data should remain public. This is no different than the current bill to lock up taxpayer funded weather data, so that Accuweather doesn't have to compete with free.
I've argued for some time now that it would be much better to simply have companies on the public teat bill citizens directly. You know, $2.67 for the tobacco farmer in KT, $21 for the odd oil company, $.46 for the idiots who build houses on flood plains, etc. Cut out the middleman, and make it apparent who is being payed here. Never fly, of course.
I do not mean to insult you here, but what I've seen in your responses so far leads me to suspect that in your mind there is a clear answer to whether The Bomb was right or wrong, and that Truman bears the brunt of the responsibility for The Bomb being dropped. I would respectfully submit to you that neither is true, and that the militaristic, atrocity-prone Imperial government holds a great deal of responsibility for the outcome.
Um. One point. Truman clearly was the one who chose to use the bomb.
If a mugger puts me in a position where I can either shoot him or be beaten up, it is still my decision to pull the trigger. This blame-the-loser mentality might be fine for muddling the ethics debate after the fact and may even be correct, but does nothing to illuminate the choices made at the time.
You can play games once you aren't an hiding behind the Coward mark. For the record, Brown, and then Berkeley (Math) and then Columbia (Law). And yeah, my little "webfaggot" (nice) shop will toast you in either finance or computational linguistics, and we aren't so bad on realtime animation, either, even if we're still figuring that out. Don't ask me; ask your boss why they're using me while you're doing charts and graphs, hoping the nice HR chick will put out.
You have enough to find me now. Shove your dick where your mouth is (oh, my, um) and wi'll see how cool you are.
C'mon big boy. Post under your real username. Whip it out, show us whatcha got.
P.S. If you don't see the value of predicate logic in haskell, you've probably never done any real work in haskell, and maybe you should pay attention next class. Smooches, --me
What the fuck is a "haskell-style rules engine" supposed to be?
If you have to ask, you don't need to know. I'd talk about predicates and lazy evaluation, but I think you're more concerned with your e-penis than the question at, um, hand.
Everything about what you've written says "clueless small business developing little piles of shit."
Great. So why are you wasting time with me when you could be writing Enterprise Software(tm) for the big boys? Run along, little man. I'm sure there's a marketing bunny who rilly rilly needs a report waiting for you.
The really amusing part is that even though you're an anonymous coward, I can state with absolute certainty that you've used our software.
Whilst the Interstate Commerce Clause has been abused mightily your private conversations are not commerce and for the Feds to requires logs of them to be kept based on it seem like a bit of stretch to me. It might be conceivable to ask that what IP addresses you connect to be logged, but even there, the IP addresses you connect to are not relevant to commerce because the ISP does not charge you based on where you are connecting to (as opposed to traditional long distance service).
See the recent Raich v. Ashcroft decision. If growing weeds in your own home, which are never bought or sold, entirely within a state, is a matter of interstate commerce, then logs of activity sold a commercial service that is almost by nature guaranteed to cross state lines are *certainly* interstate commerce as well. As are potlucks (effects eateries), choosing to bicycle rather than drive (effects energy firms), moving without a rental truck (obvious), growing vegetables in your garden (obvious parallels), generating solar power for personal use, and smoking (already well regulated, but also effects health care, insurance, your lifetime economic output; plus, god kills a kitten every time you light up, so it also effects religious ministries and the ASPCA.) (OK, strike that last part.)
One of those absurd federal-reach claims was referenced by a dissenting SCOTUS justice. Can you spot which one?
If you doubt the 'almost by nature' part of this, there was a recent case (having trouble finding it online, sorry) in which IM messages sent from one machine to another a couple of miles apart (in the same state) were ruled 'interstate', because they bounced off of AOL's servers in Virginia. Other cases have hinted that local phone calls are 'interstate', because they *could easily have been*, even when they're not.
If you pretend conventional reason plays a part of this sort of thing, you're setting yourself up.
But, hey, Scalia endorsed it, so it must support state's rights, eh?
it is not the end users fault for haveing spyware, i think most people blame MS, and the spyware companies (another palce where new laws need to be taken written)
Actually, "fault", in the sense that you're using the term (which is not they way it is used in law), is not a large factor when considering cases like what you're talking about, which is largely covered by tort law. (That this has almost nothing to do with the original topic is something I write off to this being slashdot.)
While it is a factor, torts cover responsibility. So, for instance, if my barn falls over and crushes you, it doesn't matter that I kept it in good repair - what matters is that it happened. (There are a huge number of modifiers here, in terms of case law, but that is the basic assumption.)
I'm not saying this is the way I'd write law, but this is the way it is. And it is quite easy to extrapolate to computers, here. (Reasoning by analogy is sort of a meta-law of law.)
Given the option, we're mod_perl/Mason all around. We've written our own O/R mapping layer, and have a nice haskell-style rules engine, and general toolset - for time-to-market and quality, we'll take any consulting shop on. Java bugs me, but it is fine, I guess - enough clients like it, so I deal with it. Of course, for speed sensitive things, mod_* and DB extensions, we're C all the way.
Oh, by the way: bite me. Come back and play when you've gotten your degree.
Downloaded it, played with it, probably won't ever bother again.
It is neat and all; I like the structure, and it looks fine for form-per-table sorts of toy apps, but I really don't see the advantage for anything more complicated.
What you need to do is write up a business impact analysis for the various options.
You're already thinking in the right ways - C/B of selling at a certain price.
Don't forget support commitments, opportunity cost of turning your R&D lab into a customer facing "profit" center, etc.
Also, don't be surprised if, as you go through the process, you find that a certain price-point, set of behaviours, or various possible changes would make it profitable.
Re:Rails, great for those fed up with J2EE.
on
Ajax On Rails
·
· Score: 3, Interesting
Were you trying to shoehorn rails onto an old schema?
This, I think, is the crux.
My company has a library, too, that makes certain assumptions about the DB. We're really wicked-fast when using it, when building an app from the gound up. It has hooks for overriding some assumptions, so we can shoe-horn it in to some other projects. But if the DB is hopeless, the game is over, and we have to do things like everyone else.
And nearly every company out there has a hopelessly messy DB, that can't be refactored because of X, where X is legacy apps, no money, management resistance, [...]
Hell, even Hibernate/middlegen has a problem related to this: all it takes is one clueless app developer that scorns DB constraints, and you have a Situation that can cost 10s of K to fix.
Rails is neat (I'm a pretty big perl bigot, and I like it), but it isn't designed for integration. Folks playing around with it should recognize that up front, so that they don't try to do the wrong thing with it.
One one hand, liability concerns drive this kind of crap. We have too much law. (Yes, this means you, those of you who want to bind corporate hands at every turn - SOX means bosses reading your email, in many cases. Hope you enjoy sticking it to your ass, I mean, the man.)
On the other, this just means smaller companies will get better employees who don't want to be drones. That's one of the reasons I started my own - I hate oversight, and am bad at playing employee.
On the gripping hand, ethics are important. And they're hard in large companies. To some extent, if you're a large corp, you need process in place of understood ethics, because the former is enforcable and the latter much less so. I still think the balance tips to small corps. But then, we can't turn out replacement Apple CPUs, so our role is constrained.
They don't have a claim to the code. They do, however, have the right to sue. That right can be leveraged to coerce the author into handing over rights to the code and signing all manner of "voluntary" agreements.
Example: Here's an air/alcohol mixure analogous to a person with a.8 BAC. Does it consistently trigger the mechanism? Here's an air/alcohol mixture of.5. Does it?.4?.3?.2?.1? 0?
Actually, I suspect part of the reason why cops and prosecutors don't want this discussed in open court is because breathalizers do not test for ethanol. They test for other chemicals created by metabolizing alcohol.
They also are based on the fiction of the average person, and are generally pretty dodgy devices, capable of giving wildly divergenct readings for similar amounts of alcohol consumption depending on the person, timing, how deeply the person breathes, whether they've had a cigarette recently, etc.
Check out duiblog, which is run by a DUI defense attorney. Lots of really interesting articles on the topic.
If one takes the statement, "the only thing that kept Bob from starving to death was the jar of pickles", and then and then the statement maker says that he didn't mean to imply Bob wasn't also eating cookies, do you feel like the statement was misinterpreted?
You seem to have an astoundingly myopic view of WWII. Sure, cheering for the home team is nice and all, but for someone telling others to 'grow up', you seem to have a lot to learn about the real world. Free clue: WWII was won by the allies, not the U.S. One of those allies happened to be an "aggressive totalitarian conqueror with no respect for freedom or human rights".
Napster was found guilty of contributory infringment. The Sony decision is very clear on what 'contributory infringment' means. There are what non-law people think of as loopholes here. Other people doing the same thing in different ways will be judged differently. Law is funny. But be prepared to stand up for yourself. Fuckwads with money will fuck with you.
I'll bite.
Had to look up what K3b was. I don't burn DVDs, and Paranoia works great for me for CDs. Amarok looks nifty, but I have already built my own MP3 manager, so I like mine better, even if it may have fewer features. I don't IM (hate it), so I don't need kopete or anything like it. Konq: only for testing webapp compatibility, day to day it is Mozilla. Quanta/Kate: (g)Vim, baby. A lot more powerful, available in consoles, and in any case, my fingers are hardwired to vi keystrokes from years of brain damage.
I do use gnome-multi-term. Just like the way it works enough to eat the GTK overhead. And Afterstep is exactly what I want in a WM - small, fast, lightweight, unobtrusive and highly configurable.
Slashdot Mirror
They couldn't accent it correctly. What you're getting is a smooth, meaty paste made from... cloth. Don't get me wrong, expensive cloth, it is! And I'm sure eating it will make you feel secure. Ummmm. Good, right? Can I interest you in a coffee, or a port?
-I heart ubiquitous computing
However, that is no argument for locking up publicly funded data. Either the public should not be paying for it, or the data should remain public. This is no different than the current bill to lock up taxpayer funded weather data, so that Accuweather doesn't have to compete with free.
I've argued for some time now that it would be much better to simply have companies on the public teat bill citizens directly. You know, $2.67 for the tobacco farmer in KT, $21 for the odd oil company, $.46 for the idiots who build houses on flood plains, etc. Cut out the middleman, and make it apparent who is being payed here. Never fly, of course.
Um. One point. Truman clearly was the one who chose to use the bomb.
If a mugger puts me in a position where I can either shoot him or be beaten up, it is still my decision to pull the trigger. This blame-the-loser mentality might be fine for muddling the ethics debate after the fact and may even be correct, but does nothing to illuminate the choices made at the time.
I do, in fact, know with absolute certainty that you've also used the software. Think about it. I'm sure you'll get it sooner or later.
You have enough to find me now. Shove your dick where your mouth is (oh, my, um) and wi'll see how cool you are.
C'mon big boy. Post under your real username. Whip it out, show us whatcha got.
P.S. If you don't see the value of predicate logic in haskell, you've probably never done any real work in haskell, and maybe you should pay attention next class. Smooches, --me
If you have to ask, you don't need to know. I'd talk about predicates and lazy evaluation, but I think you're more concerned with your e-penis than the question at, um, hand.
Everything about what you've written says "clueless small business developing little piles of shit."
Great. So why are you wasting time with me when you could be writing Enterprise Software(tm) for the big boys? Run along, little man. I'm sure there's a marketing bunny who rilly rilly needs a report waiting for you.
The really amusing part is that even though you're an anonymous coward, I can state with absolute certainty that you've used our software.
See the recent Raich v. Ashcroft decision. If growing weeds in your own home, which are never bought or sold, entirely within a state, is a matter of interstate commerce, then logs of activity sold a commercial service that is almost by nature guaranteed to cross state lines are *certainly* interstate commerce as well. As are potlucks (effects eateries), choosing to bicycle rather than drive (effects energy firms), moving without a rental truck (obvious), growing vegetables in your garden (obvious parallels), generating solar power for personal use, and smoking (already well regulated, but also effects health care, insurance, your lifetime economic output; plus, god kills a kitten every time you light up, so it also effects religious ministries and the ASPCA.) (OK, strike that last part.)
One of those absurd federal-reach claims was referenced by a dissenting SCOTUS justice. Can you spot which one?
If you doubt the 'almost by nature' part of this, there was a recent case (having trouble finding it online, sorry) in which IM messages sent from one machine to another a couple of miles apart (in the same state) were ruled 'interstate', because they bounced off of AOL's servers in Virginia. Other cases have hinted that local phone calls are 'interstate', because they *could easily have been*, even when they're not.
If you pretend conventional reason plays a part of this sort of thing, you're setting yourself up.
But, hey, Scalia endorsed it, so it must support state's rights, eh?
--Another libertarian fucktard.
Actually, "fault", in the sense that you're using the term (which is not they way it is used in law), is not a large factor when considering cases like what you're talking about, which is largely covered by tort law. (That this has almost nothing to do with the original topic is something I write off to this being slashdot.)
While it is a factor, torts cover responsibility. So, for instance, if my barn falls over and crushes you, it doesn't matter that I kept it in good repair - what matters is that it happened. (There are a huge number of modifiers here, in terms of case law, but that is the basic assumption.)
I'm not saying this is the way I'd write law, but this is the way it is. And it is quite easy to extrapolate to computers, here. (Reasoning by analogy is sort of a meta-law of law.)
Given the option, we're mod_perl/Mason all around. We've written our own O/R mapping layer, and have a nice haskell-style rules engine, and general toolset - for time-to-market and quality, we'll take any consulting shop on. Java bugs me, but it is fine, I guess - enough clients like it, so I deal with it. Of course, for speed sensitive things, mod_* and DB extensions, we're C all the way.
Oh, by the way: bite me. Come back and play when you've gotten your degree.
It is neat and all; I like the structure, and it looks fine for form-per-table sorts of toy apps, but I really don't see the advantage for anything more complicated.
You're already thinking in the right ways - C/B of selling at a certain price.
Don't forget support commitments, opportunity cost of turning your R&D lab into a customer facing "profit" center, etc.
Also, don't be surprised if, as you go through the process, you find that a certain price-point, set of behaviours, or various possible changes would make it profitable.
This, I think, is the crux.
My company has a library, too, that makes certain assumptions about the DB. We're really wicked-fast when using it, when building an app from the gound up. It has hooks for overriding some assumptions, so we can shoe-horn it in to some other projects. But if the DB is hopeless, the game is over, and we have to do things like everyone else.
And nearly every company out there has a hopelessly messy DB, that can't be refactored because of X, where X is legacy apps, no money, management resistance, [...]
Hell, even Hibernate/middlegen has a problem related to this: all it takes is one clueless app developer that scorns DB constraints, and you have a Situation that can cost 10s of K to fix.
Rails is neat (I'm a pretty big perl bigot, and I like it), but it isn't designed for integration. Folks playing around with it should recognize that up front, so that they don't try to do the wrong thing with it.
Huh. I thought the kinda sucked. Just a bunch of windbags full of hot air.
I know the owner of that domain, and yes, she got so much mail that she ended up turning MX off for it.
On the other, this just means smaller companies will get better employees who don't want to be drones. That's one of the reasons I started my own - I hate oversight, and am bad at playing employee.
On the gripping hand, ethics are important. And they're hard in large companies. To some extent, if you're a large corp, you need process in place of understood ethics, because the former is enforcable and the latter much less so. I still think the balance tips to small corps. But then, we can't turn out replacement Apple CPUs, so our role is constrained.
They don't have a claim to the code. They do, however, have the right to sue. That right can be leveraged to coerce the author into handing over rights to the code and signing all manner of "voluntary" agreements.
Actually, I suspect part of the reason why cops and prosecutors don't want this discussed in open court is because breathalizers do not test for ethanol. They test for other chemicals created by metabolizing alcohol.
They also are based on the fiction of the average person, and are generally pretty dodgy devices, capable of giving wildly divergenct readings for similar amounts of alcohol consumption depending on the person, timing, how deeply the person breathes, whether they've had a cigarette recently, etc.
Check out duiblog, which is run by a DUI defense attorney. Lots of really interesting articles on the topic.
If one takes the statement, "the only thing that kept Bob from starving to death was the jar of pickles", and then and then the statement maker says that he didn't mean to imply Bob wasn't also eating cookies, do you feel like the statement was misinterpreted?
"The only thing that saved Europe from being fed into Nazi death camps was American blood."
You can qualify it now, but it is hard to read it any other way.
You seem to have an astoundingly myopic view of WWII. Sure, cheering for the home team is nice and all, but for someone telling others to 'grow up', you seem to have a lot to learn about the real world. Free clue: WWII was won by the allies, not the U.S. One of those allies happened to be an "aggressive totalitarian conqueror with no respect for freedom or human rights".
Napster was found guilty of contributory infringment. The Sony decision is very clear on what 'contributory infringment' means. There are what non-law people think of as loopholes here. Other people doing the same thing in different ways will be judged differently. Law is funny. But be prepared to stand up for yourself. Fuckwads with money will fuck with you.
His retarded Debian? His retarded red hat? His retarded devil?
Speak up.
Maybe he likes them better? But I will load Firefox and konqueror and not
I like the koan aspect of that.
I do use gnome-multi-term. Just like the way it works enough to eat the GTK overhead. And Afterstep is exactly what I want in a WM - small, fast, lightweight, unobtrusive and highly configurable.