SCO says it owns UNIX, but 'nix w/o tcp is like 'nix without internet. And thats not much. No vi -- no emacs either, for that matter. So what's 'nix w/o internet, vi, or emacs???
I'm trying to figure what they could even claim was there.. I can only think kernel code... Not libc.. etc... No way Linus stole anything...
Seems to me the only possible weak point for SCO to attack, is the code that was re-impped just to avoid BSD license headers. I don't know when that was done, but older kernel's (2.0.'s) had it everywhere... Sound's like they're are going to say it was copied then munged, instead of re-impped...
What was the problem with with BSD headers anyway? I bet SCO couldn't have even tried to sue if they (and the BSD code) was still there. It would be: No SCO thats the stuff you munged....
Let me dig into you metaphor...:-] Shovels can have many types of blades. There's the flat type, There's the flat-scoop ( don't know the name ) and then there's one that looks like a spade. Working outside, you might save you're beath and say "Hand me that shovel --- no, not that one, the spade shovel" Then again, if you need to dig a hole, think you want that "spade shovel" again, and say you want a "spade", you'll get the wrong thing. What I'm saying is that in industry you might want to say something like: This would be easy to solve if we had unix. Just like this would be easy to dig if "we had shovel"... It would be harder, and more tedious to tell those "not well-versed" in computer science what features of.*nix you'd use, that would make the job a snap. Kind of like describing a shovel instead of just saying "shovel ". I remember one situtation, where the problem would have a snap to solve if we using 'nix , but I knew the that politics of the company there would be no linux. I made a mistake and said "unix" thinking to steer to a BSD, that thread was hijacked and forked into 2 threads: 1. UNIX is a registered trademark. 2. I should say Linux. But, I didn't mean Linux ( though I love linux) because it would lose. So, it took 2 weeks instead. But, I understand your point.
At least, it is for any account where there powers that be give me root. Otherwise, it depends how much I care. I always hated voice-mail so I left my password 12345. A hacker tried to take over my voicemail.... I still left it 12345. Voicemail was just consistently garbage: either the message was gibberish, or the specifics would be completed changed by the next day.... Why would I feel at all threatened if someone were to delete that for me????
People who are telling you how simple their passwords are,/might/ be really expressing, how little they care.
I cared about my unix accounts --- that's why I'm working there. So, I used decent passwords. I'd look at the acccess someone has before I raised a stink about simple passwords... If they're password is just for officemail and browsing, no access to dbs or fileservers,shares, etc then why care? Most office workers don't get remote login.... When I have root, I use passwords that are pretty much "unpronoucable linenoise", and that I could type it fast while looking at the guy hovering 'round my keyboard "chatting", right in the eye.
Emacs also has simulatenous editing of buffers (and games) with etalk, enhanced talk server and client. Its been a while( '96), but if I remember correctly one could control what buffers you shared over etalk. You really have to trust some-one to to M-x make-frame-on-display... M-x shell anyone?
Dump is supposed to be better than say: dd if=/dev/hda1 bs=1k | gzip -9 > rootfs.dd.gz , because you can do it while the system is mounted rw. What it takes to implement that is like making an incrementel fsck, debugfs, tar, gzip all it one; it becomes, more and more difficult as the filesystem becomes more and more complex. And I'd venture, it's more than simply proportionally more difficult. UNIX filesystem was once simple: Superblock, Inode blocks, Datablocks in that order on the disk, now its not. For myself, I either use tar, cpio, sometimes lharc, or I umount or remount readonly and use dd, which provided I have the diskspace I can use mount -loop to browse. Something like -loopbz on a bz2 file, or some new blockcompessor maybe based on the blocksize of the filesystem would be good.
Actually, was the dump of a rw filesystem ever 100% guaranteed usable? I remember using dump on sunos...about 10 years ago, and ocassionally it simply could not read a few directories or files, and that was taken as simply part as choosing to use dump that way....
It's obvious, because sound cards and speakers have become as ubiqitous as the other resources an Xserver serves up: display, keyboard, and mouse. First thing to do would be add more flavours of 'beep' or alert, like anyother gui, mac or windows has. Since they would be stored locally, it wouldn't cause any bandwith issue, call that --with-sound=min. Maybe a level higher would allow apps to have their own 'user sounds' with the xserver caching the files, to the ultimate fullblown streaming audio. Maybe add some selectability, so some apps can run with no sound, some with min-sound, some with fullsound, etc, etc.
No, it's the 'I'm cool because I know about bugs' stage. Which is the stage directly after the 'computers are magic' stage. Then its quickly into the 'bugs suck' stage, the 'loss of data sucks' stage. Leading to the M$ sucks stage, which might lead to the apple is art stage, or the unix is hard but doesn't suck stage.... and so on.
Thing is Microsoft is aiming lower then apple right now, as for as new customer's tech level, so I imagine they always have large amounts of people moving up from the 'computers are magic' stage.
Retailers have broken the law, and simply pocketed the sales taxes that they collect. Why trust on-line companies? Seems its even easier to scam states over the internet. Enron anyone?
I don't know who is saying you don't have to pay the state sales tax. My state demands that I do, in fact. After computing the out of state sales tax on my state-income taxes last year, it came to $1 over the refund I was due. Seemed perfectedly fair to me, the state had withheld extra-money over the tax year, hence the refund, and I did not pay the sales tax due the state until tax-time so it all more or less evened out.
Did you do you're embedded programming in C? Or Forth? I'm thinking C because you seem to put as an 'either or. ' I think the difference is how much you, have to do, yourself, to get to something the resembles a 'virtual machine.' More, "Who provides the virtual machine?" than "Is it a virtual machine?"
One thing to remember is that the only thing some programmers learn from school is how to misuse elements of CS to rationalize away the fact that they suck. IGNORE sophistical arguments, instead of buying into the BS and getting the wrong idea about whatever they're using as an excuse. It sounds like you've heard 'blackbox coding' where I've heard 'implementation details'. Like: Me: What if?--- Them: I'm not worring about 'implementation details' [with a tone that suggest that they are above it all]
But for you, perhaps, it was like: You: What happens when? Them: We don' have to worry about that because we're coding to a virtual machine. You: Yeah I know, but --- Them: Haven't you taken object orientied programming and design? You: Yeah Them: Ah then you see... [start long winded lection about OO that isn't germane ].
There are two types of people: People who don't know everything, and people who don't admit that they don't know everything. If we had been dealing with the former. It would have gone like: Us: What about? Them: Well, if that happens we're fscked. That's something we'd/have to/ deal with if we were doing embedded systems programming like in medical equipment, but for now for the purposes of CS201 we implement the 'ostrich algorithm'.
If you code you've met them. They do it because they can, and because they suck. I'm sure of the last part, because if I ever have to work with one, he gets stuck on the simplest stuff. They have years experiences (supposedly) but the code you actually see them write is first-year stuff. And the bugs are first year stuff. They hoard code, lots of code, basically like it's pron. They are the code thieves. And it's all too common. They''ll steal from anything, linux or you, cut and paste and claim its theirs. And the worst part is that they suck, can't fix anything by themselves, the simplest bugs over, and over again. Recently, I've begun to think there is some code thief black market, where someone sells a system backup tape for a university to some sorry software contractor corp. And they get all kinds of code, and all kinds of bugs, ands its wierd that this huge corp. multimillion dollar corp, was insisting the problem was on our end -when in fact, its a bug on their end that anyone could have made as a first-year in CS unix programmer: that I remember making (and fixing), and its so wierd that this was a stumper for them. Which made me conjure up visions of someone stealing a server backup tape from campus, and meeting on some foggy bridge to make the 'drop'. A snapshot of all that student code, with all those student bugs, but not the student brains to fix them. (*shakes head with wry grin*)
It is not public domain software!!!!! If the license is NOT valid, then you would have no right to distribute or use under copyright law! Only the license grants you additional rights, rights that copyright law would normally strip. Copyright law does not prohibit modifying code, just distributing it.
The whole point of GPL is to keep copyright, and keep the good parts of PD software.
Forth had a history of PD software, and a few cases of corporations claiming copyright on the PD software then suing the orginal authors who had placed the code in public domain on purpose. RMS was a lisper not a forther, but I imagine he was aware of the problems, hence GPL. (At least I'm not aware him of hacking forth, but I don't know I'm not an oldtimer, just a student of computer folklore;-)
To win, Kevin would not only have to show that it is false, he'd have to show that it harmed him tangibly, that's the hard part. Writing that he could start a nuclear war from a payphone, implied lax security -- too bad NORAD isn't a private company that/could/ claim real, tangible loss and sue. Imagine if it were:
WHAT? They wrote he could hack us and start a nuclear war from a payphone?!?
They've destroyed our customer confidence, our stock just crashed. Call the lawyers,
they'll be hell to pay.
But sadly not.
Also, if it was libel why would he sue him for defamation? and not libel? Actually, he should sue him for defamation and forget the libel.
The tone of _Cyberpunks_ was like that of a GQ article -- Mitnick was portrayed as obssed but not evil. What came after was so bileous, that I could not stomach reading more than a few lines. And at first I did not recognize it as the same writer -- I thought it was someone else.
How can a credible, sincere writer's attitude change/so/ dramatically? If one assumes credible, and sincere, there has to be story behind a radical change in attitude. I've never heard an explaination that satisfies the degree of change in tone.
You may have seen better places, I've seen small dinky places that also serve as webcafe so there's nongamers there, and its never bigger than the arcade nearby. Might be Ok if you brought some friends with you. That , or is right center on the mall floor with shoppers walking by. From other articles, I've read, in korea these things are replacing the coin-op arcades, and aren't niche things. Like if I can go to any mall anywhere, and expect to get into a decent multiplayer game with no lag and minimal nonsense -- sounds like Nirvanna.
Man , thats like the network game playing of the early 90's... Your friends have class? or work? or something else stupid? Hit the Xpilot metaserver and see if you get into a pickup game somewhere, and feed the need. Maybe you can find someone only a few hops away and that's always sweet. What you're schooling them and now they're smurfing you? Can you get in a few more kills on them through the lag , before its un-playable? You can? Man, they must really suck!! Quick, with you're last once of bandwidth type afk and pause the next few rounds. Then quit the program, hit the metaserver, and find a better server with a less lame crowd. Oh yeah...
If the Korean places run their own starcraft servers and limit access to players in the room, or maybe the baang down the street etc, on their own net, no-internet, it could be cool. Something I'd pay for. It would take the lag factor out, and the culture could police itself. If you're on an completely isolated tcp/network with no route whatever to the 'net', and its nothing but gaming, then it would be pretty obvious that the guy snickering to himself that somehow got a text-terminal up, is probably the source of the sudden burst of the lag you and everyone else is suddenly feeling.
In the 80's the arcade was the place to play, today they suck, its either a fight game or some gimmick that will get old quick, I'd love to see something new come in an wipe out what arcades have become, and replace it with cutting edge gaming... with atmosphere.
I'm not as ruthless as you, because it sucks when the 'dead' was right, and the guy who/fixed/ it was wrong -- perhaps because of some other bug was introduced, in another system and the new code was coded to the buggy behavior. Or perhaps, the spec changes back and forth --- a lot.... CVS is good, but searching CVS for the 'right' version can be a pain, ESP, if I only want the 1 change -- a file might have many changes , and ESP if I'm not the one who screwed it. Instead I #if 0 things, leave it until it is 'stone dead', then clean up,/and / refactor if it looks like a win.
Also, computer systems software, the O.S. , kernel, editors, tools etc all really done differently, than company in house software. In the former you either control the spec, or can expect rational change, in the latter, the software reflects business rules which the code/must/ reflect, but some of the changes may be temporary. As in: 'our contract with X is up and for the next two monthes we need to work with Y's system' So gut that stuff, and one might make a lot more work for oneself later -- if it ever goes back to the old way -- can't just roll back CVS you'd lose all the fixes and enhancements to that file done in the mean time. Lots of fun, especially if was done by someone else, and I just took over the maintance: find old code, work out relevent part,put back in, take out 'new old' and don't bring back any old bugs, or lose any new fixes.... Throw in a network outage and really make my day.
If the CODE is the spec you might want to keep some of that old code, and if you've never heard the phrase 'just do it like it was done before', consider yourself blessed -- light a candle in the church of emacs even;-) Esp, if that code was GOOD code -- yeah throw out the stuff that never worked and quick, but if was good maybe not so quick, unless of course you work in some paradise, where everything is documented -- by someone else (of course).
But in general, I agree, just being 'ruthless' about it can cause problems in some places. I imagine its not the redundancies themselves, but that they are the tell tale markers, 'the droppings' if you will, of lazy and/or untalented programmers. Of these esp. bad are those who actively argue against efforts to refactor and clean up, even in sections they don't maintain. But also irrating, are those who are smart, but 'summarily remove dead code' when they are new hires, or contractors hired for only a quarter, and would have no sense when dead code is truly and forever dead, or when it might be easily be resurrected next year, and because it is done 'summarily', they have no idea what they gutted or when, and theres no CVS tag, of course, and they smirk as they pass the buck back to me, and go to their next job, leaving me with twice the work as I would have had before...
Re:Shouldn't my compiler be reading this book?
on
Hacker's Delight
·
· Score: 1
Of course, it may be doing other tricks we don't know about. I once tracked a bug to the compiler optimizing away a whole branch. Neat, but it wasn't an if ( 1==0) branch, it should have been reachable. Very confusing even in a debugger, just seemed to jump over lines of C code... only when I compared the assembler output files, between optimized and nonoptimized did I notice what happened. Of course, having some assembler knowledge did help. It was a major unix vendor and their compiler.
Its a result of you and the many like you. Don't mean to be harsh, just accurate. Steve Balmer described Microsoft's philosophy for dealing with IBM in the '80's, how IBM was the bear and you had to ride the bear, or you'd be under the bear. Now, Microsoft is the bear, and it's smarter than the average bear -- in the sense, that is very clever, only time will tell if it's wise. By pirating Microsoft products, you were effectively promoting Microsoft products as standard. I don't believe its really been about O.S. It was about WORD, the.doc format and those people who sneer when you don't want to take doc files from them , and sneer when you don't give to them those.doc files. And what influence those people (may) have. So, you bought into it, rather than fight it, and now they're going to to lock it up with you still inside. Potentially, they could shoot themselves in the foot, but as they know they have a history of their products achieving dominance by the old #1 fumbling, they are aware that it could happen to them.
Consider these two questions: If a man is starving and he steals bread -- is it wrong? vs if a man is starving and he walks past free bread, walks past the all you an all you can eat buffet, because he needs to keep money for beer money, and breaks into someone's house and steals the premium, gourmet grub -- is it wrong? We live in a capitalistic society: what gets money thrives, what doesn't dies. When someone with money, could have bought the latest windows game but bought linux , says more than an on-line registery, on any post to *.advocacy. That's when the 'business-types' started to notice, and the nontechs started to notice. Then, later , when debian and mandrake made installing linux mac-easy installing linux started to be confused with using linux, by some anyway.
If we move from a progressive tax system to a flat tax what would the % have to be? I wanted to figure it out... but, it seems, me have puny googlefoo. I'm either getting page after page of 1040 advice or no hits.
I'm trying to find the sum total of/all/ the personal income tax revenue the government took in from everyone for taxyear 2002. Given/that/ sum and the total income of/all/ individuals, who filed returns. I could compute what the flat tax rate would have to have been to generate the same sum. Then, we could all work out would we would have paid last year under a flat tax vs what we actually paid.
There's also such a thing as a 'compilation copyright'. Typical in anthologies (books of plays, shorts stories etc) also magazines. The individual pieces , articles, etc could be free of copyright (expired, PD, etc) but copying the whole anthology would break copyright -- the law recoginizes the act of putting the pieces together as worth protecting... And I'd say an Linux Distribution as a compilation of kernel and packages, etc would be covered by compilation copyright.
Partial is trickier, if the pieces are PD I think OK, but INAL
Let me counter one cliche with another: Don't lock the barn door after the horse has been stolen.
These would have been good things to do/before/ 9-11, perhaps when the embassy was bombed or when the Cole was attacked, but given how much time they spend researching attacks before they implement them --we need to worry about plans they've already made. As I remember, in the summer of 2001, the Right was talking about war with China while also recommending downsizing carrier fleets... and ignoring the enemy that had already attacked us twice.
And, you are wrong when you say 'Nobody ever thought' . People did think: the flight instructors thought it was odd... the fbi field agents wanted to investigate, but were ordered by higher-ups not to. One man in the fbi was watching Al Qaeda for years. His opinions that they could be a serious threat didn't jibe with the 'make no waves' culture, later made mistake and was forced out. http://www.pbs.org/wgbh/pages/frontline/show s/knew/view/ for details.
It isn't just the the PC crowd the implements the ostrich algorithm regularly, others do it too , but with more bloat.
Non-white would be good, but no pastels, or fruits. White was chosen to standout, people would notice them, and also notice that other people had macs (and not pc's). But, while I find the new imacs great looking in good conditions, it's not so hot in bad computer store light. Maybe, when this story is closer to true we can look forward to it -- I've been thinking of a brushed copper.
I checked out your site, I think you should keep it for interviews if somewants to see what you can do -- all c.s programs are not created equal, but otherwise... You have source code for projects with course numbers; you have GPL mentioned at top of the page, but aren't following the GPL as you placed no copyright notices, or mention of GPL on the source files themselves. You're best argument would be to GPL it , the right way, then claim that any student who would use the work in an assignment would violate civil copyright laws etc-- THAT the license protects againts abuse, as the student would have to cite your source. If you don't win with it, you can at least save face.
But, as it stands right now, I'd say prepare to lose. If it was ancillary stuff, like config files, a new emacs mode, or even component pieces like a class, a widget, or library that you used to solve a project, but is not in itself the project, then I'd feel otherwise. )
If it was your own explorations on the side, I'd feel differently, strongly in fact. For FUN introduce typos: swap project1 and project2, and course numbers, wait until someone does steal your stuff and turn in the wrong project.
I believe the money flows in the wrong direction to be a work for a hire -- You pay them. Although, this argument may not be sufficiently complex to impress the litigious.
Co-authorship is a potentially stronger tack. How much direction or advice does it take to be considered a joint-work? Is it "But,I told you to use verilog,'" or is it "But, you followed the design I put on the board?"
Slashdot Mirror
SCO says it owns UNIX, but 'nix w/o tcp is like 'nix without internet. And thats not much. No vi -- no emacs either, for that matter.
So what's 'nix w/o internet, vi, or emacs???
I'm trying to figure what they could even claim was there.. I can only think kernel code... Not libc.. etc... No way Linus stole anything...
Seems to me the only possible weak point for SCO to attack, is the code that was re-impped just to avoid BSD license headers. I don't know when that was done, but older kernel's (2.0.'s) had it everywhere... Sound's like they're are going to say
it was copied then munged, instead of re-impped...
What was the problem with with BSD headers anyway? I bet SCO couldn't have even tried to sue if they (and the BSD code) was still there. It would be: No SCO thats the stuff you munged....
Let me dig into you metaphor... :-] .*nix you'd use, that would make the job a snap.
Shovels can have many types of blades. There's the flat type, There's the flat-scoop ( don't know the name ) and then there's one that looks like a spade.
Working outside, you might save you're beath and say "Hand me that shovel --- no, not that one, the spade shovel"
Then again, if you need to dig a hole, think you want that "spade shovel" again,
and say you want a "spade", you'll get the wrong thing.
What I'm saying is that in industry you might want to say something like:
This would be easy to solve if we had unix. Just like this would be easy to dig
if "we had shovel"...
It would be harder, and more tedious to tell those "not well-versed" in computer science what features of
Kind of like describing a shovel instead of just saying "shovel ".
I remember one situtation, where the problem would have a snap to solve if we using 'nix , but I knew the that politics of the company there would be no linux.
I made a mistake and said "unix" thinking to steer to a BSD, that thread was hijacked and forked into 2 threads: 1. UNIX is a registered trademark. 2. I should say Linux. But, I didn't mean Linux ( though I love linux) because it would lose.
So, it took 2 weeks instead.
But, I understand your point.
At least, it is for any account where there powers that be give me root.
/might/ be really expressing, how little they care.
Otherwise, it depends how much I care. I always hated voice-mail so I left my password 12345. A hacker tried to take over my voicemail.... I still left it 12345.
Voicemail was just consistently garbage: either the message was gibberish, or the specifics would be completed changed by the next day.... Why would I feel at all threatened if someone were to delete that for me????
People who are telling you how simple their passwords are,
I cared about my unix accounts --- that's why I'm working there. So, I used decent passwords. I'd look at the acccess someone has before I raised a stink about simple passwords... If they're password is just for officemail and browsing, no access to dbs or fileservers,shares, etc then why care? Most office workers don't get remote login....
When I have root, I use passwords that are pretty much "unpronoucable linenoise", and that I could type it fast while looking at the guy hovering 'round my keyboard "chatting", right in the eye.
You'd they'd at least have someone come turn it off, before it starts smoking ;-]
Emacs also has simulatenous editing of buffers (and games) with etalk, enhanced talk server and client. Its been a while( '96), but if I remember correctly one could control what buffers you shared over etalk. You really have to trust some-one to to M-x make-frame-on-display... M-x shell anyone?
He'd need to fake the sector errors... ....
Anyway I keep a 360k drive just in case I ever get around to getting into my c64 again.
Dump is supposed to be better than say: dd if=/dev/hda1 bs=1k | gzip -9 > rootfs.dd.gz , because you can do it while the system is mounted rw. What it takes to implement that is like making an incrementel fsck, debugfs, tar, gzip all it one; it becomes, more and more difficult as the filesystem becomes more and more complex. And I'd venture, it's more than simply proportionally more difficult.
UNIX filesystem was once simple: Superblock, Inode blocks, Datablocks in that order on the disk, now its not.
For myself, I either use tar, cpio, sometimes lharc, or I umount or remount readonly and use dd, which provided I have the diskspace I can use mount -loop to browse. Something like -loopbz on a bz2 file, or some new blockcompessor maybe based on the blocksize of the filesystem would be good.
Actually, was the dump of a rw filesystem ever 100% guaranteed usable?
I remember using dump on sunos...about 10 years ago, and ocassionally
it simply could not read a few directories or files, and that was taken as simply part as choosing to use dump that way....
It's obvious, because sound cards and speakers have become as ubiqitous as the other
resources an Xserver serves up: display, keyboard, and mouse.
First thing to do would be add more flavours of 'beep' or alert, like anyother gui, mac or windows has. Since they would be stored locally, it wouldn't cause any bandwith issue,
call that --with-sound=min. Maybe a level higher would allow apps to have their own 'user sounds' with the xserver caching the files, to the ultimate fullblown streaming audio.
Maybe add some selectability, so some apps can run with no sound, some with min-sound,
some with fullsound, etc, etc.
No, it's the 'I'm cool because I know about bugs' stage. Which is the stage directly after the 'computers are magic' stage.
Then its quickly into the 'bugs suck' stage, the 'loss of data sucks' stage.
Leading to the M$ sucks stage, which might lead to the apple is art stage, or the unix is hard but doesn't suck stage.... and so on.
Thing is Microsoft is aiming lower then apple right now, as for as new customer's tech level, so I imagine they always have large amounts of people moving up from the 'computers are magic' stage.
Retailers have broken the law, and simply pocketed the sales taxes that they collect.
Why trust on-line companies? Seems its even easier to scam states over the internet.
Enron anyone?
I don't know who is saying you don't have to pay the state sales tax. My state demands that I
do, in fact. After computing the out of state sales tax on my state-income taxes last year, it came to $1 over the refund I was due. Seemed perfectedly fair to me, the state had withheld extra-money over the tax year, hence the refund, and I did not pay the sales tax due the state until tax-time so it all more or less evened out.
Did you do you're embedded programming in C? Or Forth? I'm thinking C because you seem to put as an 'either or. ' I think the difference is how much you, have to do, yourself, to get to something the resembles a 'virtual machine.' More, "Who provides the virtual machine?" than "Is it a virtual machine?"
/have to/ deal with
One thing to remember is that the only thing some programmers learn from school
is how to misuse elements of CS to rationalize away the fact that they suck.
IGNORE sophistical arguments, instead of buying into the BS and getting the wrong idea
about whatever they're using as an excuse.
It sounds like you've heard 'blackbox coding' where I've heard 'implementation details'.
Like:
Me: What if?---
Them: I'm not worring about 'implementation details' [with a tone that suggest that they are above it all]
But for you, perhaps, it was like:
You: What happens when?
Them: We don' have to worry about that because we're coding to a virtual machine.
You: Yeah I know, but ---
Them: Haven't you taken object orientied programming and design?
You: Yeah
Them: Ah then you see... [start long winded lection about OO that isn't germane ].
There are two types of people: People who don't know everything, and people who don't admit that they don't know everything. If we had been dealing with the former. It would have gone like:
Us: What about?
Them: Well, if that happens we're fscked. That's something we'd
if we were doing embedded systems programming like in medical equipment, but for now for the purposes of CS201 we implement the 'ostrich algorithm'.
If you code you've met them. They do it because they can, and because they suck.
I'm sure of the last part, because if I ever have to work with one, he gets stuck on
the simplest stuff. They have years experiences (supposedly) but the code you actually see them write is first-year stuff. And the bugs are first year stuff. They hoard code, lots of code, basically like it's pron.
They are the code thieves. And it's all too common.
They''ll steal from anything, linux or you, cut and paste and claim its theirs. And the worst part is that they suck, can't fix anything by themselves, the simplest bugs over, and over again.
Recently, I've begun to think there is some code thief black market, where someone sells
a system backup tape for a university to some sorry software contractor corp.
And they get all kinds of code, and all kinds of bugs, ands its wierd that this huge corp. multimillion dollar corp, was insisting the problem was on our end -when in fact, its a bug on their end that anyone could have made as a first-year in CS unix programmer: that I remember making (and fixing), and its so wierd that this was a stumper for them.
Which made me conjure up visions of someone stealing a server backup tape from campus, and meeting on some foggy bridge to make the 'drop'. A snapshot of all that student code, with all those student bugs, but not the student brains to fix them.
(*shakes head with wry grin*)
It is not public domain software!!!!!
;-)
If the license is NOT valid, then you would have no right to distribute or use under copyright law!
Only the license grants you additional rights, rights that copyright law would normally strip.
Copyright law does not prohibit modifying code, just distributing it.
The whole point of GPL is to keep copyright, and keep the good parts of PD software.
Forth had a history of PD software, and a few cases of corporations claiming copyright on the PD software then suing the orginal authors who had placed the code in public domain on purpose.
RMS was a lisper not a forther, but I imagine he was aware of the problems, hence GPL.
(At least I'm not aware him of hacking forth, but I don't know I'm not an oldtimer, just a student of computer folklore
To win, Kevin would not only have to show that it is false, he'd have to show that it harmed him /could/ claim real, tangible loss and sue.
/so/ dramatically? If one assumes
tangibly, that's the hard part. Writing that he could start a nuclear war from a payphone, implied lax security -- too bad NORAD isn't a private company that
Imagine if it were:
WHAT? They wrote he could hack us and start a nuclear war from a payphone?!?
They've destroyed our customer confidence, our stock just crashed. Call the lawyers,
they'll be hell to pay.
But sadly not.
Also, if it was libel why would he sue him for defamation? and not libel?
Actually, he should sue him for defamation and forget the libel.
The tone of _Cyberpunks_ was like that of a GQ article -- Mitnick was portrayed as obssed but not evil. What came after was so bileous, that I could not stomach reading more than a few lines. And at first I did not recognize it as the same writer -- I thought it was someone else.
How can a credible, sincere writer's attitude change
credible, and sincere, there has to be story behind a radical change in attitude. I've never heard
an explaination that satisfies the degree of change in tone.
Do vitreolics sell better?
You may have seen better places, I've seen small dinky places that also serve as webcafe so there's nongamers there, and its never bigger than the arcade nearby. Might be Ok if you brought some friends with you. That , or is right center on the mall floor with shoppers walking
by. From other articles, I've read, in korea these things are replacing the coin-op arcades, and aren't niche things. Like if I can go to any mall anywhere, and expect to get into a decent
multiplayer game with no lag and minimal nonsense -- sounds like Nirvanna.
Man , thats like the network game playing of the early 90's... Your friends have class? or work? or something else stupid? Hit the Xpilot metaserver and see if you get into a pickup game somewhere, and feed the need. Maybe you can find someone only a few hops away and that's always sweet. What you're schooling them and now they're smurfing you? Can you get in a few more kills on them through the lag , before its un-playable? You can? Man, they must really suck!! Quick, with you're last once of bandwidth type afk and pause the next few rounds. Then quit the program, hit the metaserver, and find a better server with a less lame crowd.
Oh yeah...
If the Korean places run their own starcraft servers and limit access to players in the room, or maybe the baang down the street etc, on their own net, no-internet, it could be cool. Something I'd pay for. It would take the lag factor out, and the culture could police itself. If you're on an completely isolated tcp/network with no route whatever to the 'net', and its nothing but gaming,
then it would be pretty obvious that the guy snickering to himself that somehow got a text-terminal up, is probably the source of the sudden burst of the lag you and everyone else is suddenly feeling.
In the 80's the arcade was the place to play, today they suck, its either a fight game or some gimmick that will get old quick, I'd love to see something new come in an wipe out what arcades have become, and replace it with cutting edge gaming... with atmosphere.
I'm not as ruthless as you, because it sucks when the 'dead' was right, and the guy /fixed/ it was wrong -- perhaps because of some other bug was introduced, in another /and / refactor if it looks like a win.
/must/ reflect, but some of the changes may be temporary. As in: 'our contract with X is up and for the next two monthes we need to work with Y's system' So gut that stuff, and one might make a lot
;-) Esp, if that code was GOOD code -- yeah throw out the stuff that never worked and quick, but if was good maybe not so quick, unless of course you work in some paradise, where everything is documented -- by someone else (of course).
who
system and the new code was coded to the buggy behavior. Or perhaps, the spec changes back and forth --- a lot....
CVS is good, but searching CVS for the 'right' version can be a pain, ESP, if I only want the 1 change -- a file might have many changes , and ESP if I'm not the one who screwed it.
Instead I #if 0 things, leave it until it is 'stone dead', then clean up,
Also, computer systems software, the O.S. , kernel, editors, tools etc all really done differently,
than company in house software. In the former you either control the spec, or can
expect rational change, in the latter, the software reflects business rules which the code
more work for oneself later -- if it ever goes back to the old way -- can't just roll back CVS you'd lose all the fixes and enhancements to that file done in the mean time. Lots of fun, especially if was done by someone else, and I just took over the maintance: find old code, work out relevent part,put back in, take out 'new old' and don't bring back any old bugs, or lose any new fixes.... Throw in a network outage and really make my day.
If the CODE is the spec you might want to keep some of that old code, and if you've never heard
the phrase 'just do it like it was done before', consider yourself blessed -- light a candle in the church of emacs even
But in general, I agree, just being 'ruthless' about it can cause problems in some places.
I imagine its not the redundancies themselves, but that they are the tell tale markers, 'the droppings' if you will, of lazy and/or untalented programmers. Of these esp. bad are those who actively argue against efforts to refactor and clean up, even in sections they don't maintain.
But also irrating, are those who are smart, but 'summarily remove dead code' when they are new hires, or contractors hired for only a quarter, and would have no sense when dead code is truly and forever dead, or when it might be easily be resurrected next year, and because it is done 'summarily', they have no idea what they gutted or when, and theres no CVS tag, of course, and they smirk as they pass the buck back to me, and go to their next job, leaving me with twice the work as I would have had before...
Of course, it may be doing other tricks we don't know about.
I once tracked a bug to the compiler optimizing away a whole branch. Neat, but it wasn't an if ( 1==0) branch, it should have been reachable. Very confusing even in a debugger, just seemed to jump over lines of C code... only when I compared the assembler output files, between optimized and nonoptimized did I notice what happened. Of course, having some assembler knowledge did help.
It was a major unix vendor and their compiler.
Its a result of you and the many like you. Don't mean to be harsh, just accurate. .doc format and those people who sneer when you don't want to take doc files from them , and sneer when you don't give to them those .doc files. And what influence those people (may) have. So, you bought into it, rather than fight it, and now they're going to to lock it up with you still inside.
Steve Balmer described Microsoft's philosophy for dealing with IBM in the '80's, how IBM was the bear and you had to ride the bear, or you'd be under the bear.
Now, Microsoft is the bear, and it's smarter than the average bear -- in the sense, that is very clever, only time will tell if it's wise.
By pirating Microsoft products, you were effectively promoting Microsoft products as standard. I don't believe its really been about O.S. It was about WORD, the
Potentially, they could shoot themselves in the foot, but as they know they have a history of their products achieving dominance by the old #1 fumbling, they are aware that it could happen to them.
Consider these two questions: If a man is starving and he steals bread -- is it wrong? vs if a man is starving and he walks past free bread, walks past the all you an all you can eat buffet, because he needs to keep money for beer money, and breaks into someone's house and steals the premium, gourmet grub -- is it wrong?
We live in a capitalistic society: what gets money thrives, what doesn't dies. When someone with money, could have bought the latest windows game but bought linux , says more than an on-line registery, on any post to *.advocacy. That's when the 'business-types' started to notice, and the nontechs started to notice. Then, later , when debian and mandrake made installing linux mac-easy installing linux started to be confused with using linux, by some anyway.
If we move from a progressive tax system to a flat tax what would the % have to be?
/all/ the personal income tax revenue the government took in from everyone for taxyear 2002. Given /that/ sum and the total income of /all/ individuals, who filed returns. I could compute what the flat tax rate would have to have been to generate the same sum. Then, we could all work out would we would have paid last year under a flat tax vs what we actually paid.
I wanted to figure it out... but, it seems, me have puny googlefoo.
I'm either getting page after page of 1040 advice or no hits.
I'm trying to find the sum total of
There's also such a thing as a 'compilation copyright'.
Typical in anthologies (books of plays, shorts stories etc)
also magazines. The individual pieces , articles, etc could
be free of copyright (expired, PD, etc) but copying the whole
anthology would break copyright -- the law recoginizes the act of putting the pieces together as worth protecting...
And I'd say an Linux Distribution as a compilation of kernel and packages, etc would be covered by compilation copyright.
Partial is trickier, if the pieces are PD I think OK, but INAL
Let me counter one cliche with another:
/before/ 9-11, perhaps when the embassy was bombed or when the Cole was attacked, but given how much time they spend researching attacks before they implement them --we need to worry about plans they've already made.
w s/knew /view/ for details.
Don't lock the barn door after the horse has been stolen.
These would have been good things to do
As I remember, in the summer of 2001, the Right was talking about war with China while also recommending downsizing carrier fleets... and ignoring the enemy that had already attacked us twice.
And, you are wrong when you say 'Nobody ever thought' . People did think: the flight instructors thought it was odd... the fbi field agents wanted to investigate, but were ordered by higher-ups not to. One man in the fbi was watching Al Qaeda for years. His opinions that they could be a serious threat didn't jibe with the 'make no waves' culture, later made mistake and was forced out.
http://www.pbs.org/wgbh/pages/frontline/sho
It isn't just the the PC crowd the implements the ostrich algorithm regularly, others do it too , but with more bloat.
Non-white would be good, but no pastels, or fruits. White was chosen to standout, people would notice them, and also notice that other people had macs (and not pc's). But, while I find the new imacs great looking in good conditions, it's not so hot in bad computer store light. Maybe, when this story is closer to true we can look forward to it -- I've been thinking of a brushed copper.
I checked out your site, I think you should keep it for interviews if somewants to see what you can do -- all c.s programs are not created equal, but otherwise...
You have source code for projects with course numbers; you have GPL mentioned at top of the page, but aren't following the GPL as you placed no copyright notices, or mention of GPL on the source files themselves.
You're best argument would be to GPL it , the right way, then claim that any student who would use the work in an assignment would violate civil copyright laws etc-- THAT the license protects againts abuse, as the student would have to cite your source. If you don't win with it, you can at least save face.
But, as it stands right now, I'd say prepare to lose. If it was ancillary stuff, like config files,
a new emacs mode, or even component pieces like a class, a widget, or library that you used to solve a project, but is not in itself the project, then I'd feel otherwise. )
If it was your own explorations on the side, I'd feel differently, strongly in fact.
For FUN introduce typos: swap project1 and project2, and course numbers, wait until someone does steal your stuff and turn in the wrong project.
I believe the money flows in the wrong direction to be a work for a hire -- You pay them. Although, this argument may not be sufficiently complex to impress the litigious.
,I told you to use verilog,'" or
Co-authorship is a potentially stronger tack. How much direction or advice does it take to be considered a joint-work?
Is it "But
is it "But, you followed the design I put on the board?"