i'm a salaried programmer, so if i'm trying to meet a deadline, i work like crazy. 11-13 hour days, 7 days a week, until it's done. so around 80-90 hours a week.
however, if i'm working on a slower/less important project, or if i'm doing design instead of actual code... it's more like 6-8 hours, 5 days a week, or 30-40 hours a week.
it kinda sucks not getting paid for all that overtime, but i guess all the slacking off i do during the slow periods (e.g. reading slashdot:)) makes up for it. ---
well, even with the crappy security that's become the norm with msft products, an os using a nt kernel will always be more secure than an os using a 9x kernel.
even if nt's implementation is flawed, it at least has the design, like users, permissions, and some seperation of kernel- and user-space.
with that said, a default install of nt (dunno about win2k, never touched it) is so horrible that it brings the overall security of the system almost down to the win9x level. which is to say none at all. come on, who besides msft would ship a product with the filesystem permissions blown wide open by default?
but the moral of this story is: don't use default installs on production systems. even if they aren't windows. ---
um... as far as i know, the only advantage mysql has over postgres is speed. postgres has a number of very nice features, like stored functions and transactions.
it does seem as though mysql is catching up with the features. should be interesting to see if it can maintain the speed. ---
7 is moot, since the param list for main() isn't necessary, since the program takes no arguments. besides, it would have been much better had there been a deceptive param list.
8 is also lame. the other poster mentioned that programs calling the hello-world prog would not be reliable, but i think that's more of a design flaw rather than an implementation flaw. ---
1. left-curly-brace after `void' instead of left-parenthesis.
2. right-parenthesis starts the block of code, instead of right-curly-brace.
3. printf args start with right-bracket, instead of right-parenthesis.
4. n\ instead of \n.
5. string arg to printf closes with a single-quote, not double-quote.
6. comma after printf(), not semicolon.
now, i could be lame and count not returning a value from main(), but that's a warning, not an error. and it only shows up if you use -Wall. and let's face it, no real hacker ever uses -Wall.
just for some contrast, i got 712.57KB/s from zeus.kernel.org. and i'm guessing that's just because it's overloaded right now; i can usually pull >1MB/sec from fast systems. that's one megabyte, not one megabit.
ok, now that i'm done with the ego-stroking, time to get back to work...:)
how about an easy-for-dad divx player first? preferably one which doesn't require winelib dll hacks, since dad doesn't want to know about that sort of thing. --
well, kde 2.1 is included in debian's unstable ("sid") branch, as well as gnome, windowmaker, etc. i'm running it (with antialiased fonts, xfree86 4.0.2 w/multihead) right now...
kde 2.1 probably won't make the debian 2.3 release, but it should be in 2.4. --
"if an OS doesn't support CPRM, then it'll
just ignore the CPRM parts of a drive, and render
the copy protection useless."
so, what happens when the "foobarAA" decides to
sue linus because linux is a device which can
circumvent copy protection? --
if you want cool new stuff, you could even give the testing distribution, aka "woody" a whirl. and if you want a broken, but bleeding-edge system, go install unstable. --
"...i predict that your filesystem 'Won't ever see the light of day.'"
sounds like information to me.
and who says that humor is a waste of time? lauging is good for you.
besides which, you completely missed the point of my post; your project is vapor. you have no code (released, anyways, which is what counts), no name, nothing to show but a bunch of buzzwords thrown together in a slashdot post. you don't even have an empty sourceforge project.
now, you sound like you might have some good ideas. and as much as good ideas are necessary, good implementations are much more necessary. you'd be much better off helping integrate your ideas into an existing project. there are so many players in the next-linux-filesystem arena that even if you do manage to make a stable release, it will probably die due to one of the other projects.
my post was hardly a waste of time. it was an honest suggestion, based on my honest opionion, with a dash of humor thrown in. just because you don't agree with me doesn't mean that you have to go sling the t-word around here.
and if you actually bothered to check my user-info, you'd see that i'm not a troll at all. perhaps offensive, blunt, rude, callous and opinionated. but hardly a troll.
and grow up. if you act that way towards anyone who has an opinion contrary to your own, your little project will fork before you manage to write, much less release, a single line of code. --
y'know, i wasn't so sure about this "doom 3" thing. i was an avid player of the original doom series (imo, the best way to play it was in a dark room at 2 a.m. with a pc conneted to a big set of speakers, which are cranked all the way up) and i just wasn't sure that id could recapture that spooky atmosphere it had.
however, since i cheked out those screenshots, i have had my faith in id restored. id will be forgiven it's past transgressions (quake 2, hexen, heretic, no more commander keen games, etc) if this game is half as good as it looks.
i also seem to have something wet in my pants. excuse me. --
i went and saw the movie opening night with a friend. i told her i'd be pleasantly surprised if the movie didn't suck.
in short, i wasn't surprised. well, that's not complerely true; i wasn't surprised that it sucked, but the ways that it sucked were quite surprising.
for example, how they didn't explain how the x-rays that starling got from verger were related to lecter at all. i'd imagine that the audience would be pretty confused if they didn't read the book.
the most interesting thing was the boom and lighting gear that was in several of the shots. towards the end, when starling and lecter are in paul's kitchen, the boom with the microphone on the end was clearly visible. so were some of their lights, and a big piece of tinfoil to diffuse the light.
sounds strange, but i swear it's true. the theater gave everyone who saw it refunds.
the manager said it was their fault. and i'm sure that if something like that got in the final release of the movie, it would have been mentioned in the review, so i guess it was just me.
can someone with more of a clue than the manager explain just what went wrong with that? --
nonsense. it's his source tree, he can (and does) review anything that gets submitted to him. bitching and moaning about how "he can't do that!" is the least productive way to respond.
when faced with a rejection from linus, you have two options: suck it down and do as the man says, or fork off your own tree.
it's obvious which path the linuxppc folks took. --
from what i have heard (from linux-kernel) linus doesn't like to get huge patches. he likes to get small patches that do one thing, since that's easier to review.
the linppc folks have had a hard time accepting this. they want to send one huge patch to get the ppc architecture up-to-date.
it's not a new problem. see this bit on kernel traffic, which covers some of it. there was another thread, where linus flamed people for sending huge patches, but i can't find it atm. --
or at least let someone else post? or at least stop smoking crack?
"If you think dandruff is an unhealthy food risk, Boolean sent us what might be the greatest meal ever. How can you resist a bowl of soup that morphs into a Ant is back with Mathamatical Oragami."
Slashdot Mirror
i'm a salaried programmer, so if i'm trying to meet a deadline, i work like crazy. 11-13 hour days, 7 days a week, until it's done. so around 80-90 hours a week.
:)) makes up for it.
however, if i'm working on a slower/less important project, or if i'm doing design instead of actual code... it's more like 6-8 hours, 5 days a week, or 30-40 hours a week.
it kinda sucks not getting paid for all that overtime, but i guess all the slacking off i do during the slow periods (e.g. reading slashdot
---
interesting. except for burstnet, the register (both running linux) and e3expo (nt) all the sites in that list run solaris.
and i'd bet that burstnet & the register use some sort of linux load-balancer, skewing the results.
---
that aol/netscape/sun/time-warner was an unlikely merger.
---
well, even with the crappy security that's become the norm with msft products, an os using a nt kernel will always be more secure than an os using a 9x kernel.
even if nt's implementation is flawed, it at least has the design, like users, permissions, and some seperation of kernel- and user-space.
with that said, a default install of nt (dunno about win2k, never touched it) is so horrible that it brings the overall security of the system almost down to the win9x level. which is to say none at all. come on, who besides msft would ship a product with the filesystem permissions blown wide open by default?
but the moral of this story is: don't use default installs on production systems. even if they aren't windows.
---
yes, i know. :)
---
"...while they keep one-upping each other..."
um... as far as i know, the only advantage mysql has over postgres is speed. postgres has a number of very nice features, like stored functions and transactions.
it does seem as though mysql is catching up with the features. should be interesting to see if it can maintain the speed.
---
well, i don't think they'll care. after all, they're for the ethical treatment of animals.
now, if the People for the Ethical Treatment of Disembodied Eel Brains (PETDEB) hears about it, that's a different story.
---
lame.
7 is moot, since the param list for main() isn't necessary, since the program takes no arguments. besides, it would have been much better had there been a deceptive param list.
8 is also lame. the other poster mentioned that programs calling the hello-world prog would not be reliable, but i think that's more of a design flaw rather than an implementation flaw.
---
eight? i only see six:
1. left-curly-brace after `void' instead of left-parenthesis.
2. right-parenthesis starts the block of code, instead of right-curly-brace.
3. printf args start with right-bracket, instead of right-parenthesis.
4. n\ instead of \n.
5. string arg to printf closes with a single-quote, not double-quote.
6. comma after printf(), not semicolon.
now, i could be lame and count not returning a value from main(), but that's a warning, not an error. and it only shows up if you use -Wall. and let's face it, no real hacker ever uses -Wall.
---
bleah, i only got 132.23KB/sec. too slow.
:)
just for some contrast, i got 712.57KB/s from zeus.kernel.org. and i'm guessing that's just because it's overloaded right now; i can usually pull >1MB/sec from fast systems. that's one megabyte, not one megabit.
ok, now that i'm done with the ego-stroking, time to get back to work...
how about an easy-for-dad divx player first? preferably one which doesn't require winelib dll hacks, since dad doesn't want to know about that sort of thing.
--
well, kde 2.1 is included in debian's unstable ("sid") branch, as well as gnome, windowmaker, etc. i'm running it (with antialiased fonts, xfree86 4.0.2 w/multihead) right now... kde 2.1 probably won't make the debian 2.3 release, but it should be in 2.4.
--
"if an OS doesn't support CPRM, then it'll just ignore the CPRM parts of a drive, and render the copy protection useless." so, what happens when the "foobarAA" decides to sue linus because linux is a device which can circumvent copy protection?
--
blatant plug, since i'm a debian developer:
have you looked at debian? the last stable release, potato, supports alpha.
if you want cool new stuff, you could even give the testing distribution, aka "woody" a whirl. and if you want a broken, but bleeding-edge system, go install unstable.
--
"...there was no information in yours."
nonsense. what do you call this?
"...i predict that your filesystem 'Won't ever see the light of day.'"
sounds like information to me.
and who says that humor is a waste of time? lauging is good for you.
besides which, you completely missed the point of my post; your project is vapor. you have no code (released, anyways, which is what counts), no name, nothing to show but a bunch of buzzwords thrown together in a slashdot post. you don't even have an empty sourceforge project.
now, you sound like you might have some good ideas. and as much as good ideas are necessary, good implementations are much more necessary. you'd be much better off helping integrate your ideas into an existing project. there are so many players in the next-linux-filesystem arena that even if you do manage to make a stable release, it will probably die due to one of the other projects.
--
"Gee, thanks for wasting my time and yours.
I could name it for you -- 'TrollFS'"
now hang on a second here.
my post was hardly a waste of time. it was an honest suggestion, based on my honest opionion, with a dash of humor thrown in. just because you don't agree with me doesn't mean that you have to go sling the t-word around here.
and if you actually bothered to check my user-info, you'd see that i'm not a troll at all. perhaps offensive, blunt, rude, callous and opinionated. but hardly a troll.
and grow up. if you act that way towards anyone who has an opinion contrary to your own, your little project will fork before you manage to write, much less release, a single line of code.
--
How about "WestlodFS"? I suggest it because i predict that your filesystem "Won't ever see the light of day."
On the other hand, "VaporFS" has a beautiful succinctness.
Decisions, decisions.
--
"However, ReiserFS is broken with NFS currently..."
/net/mp3 type nfs (rw,rsize=8192,wsize=8192,soft,addr=192.168.128.25 0)
/usr/local type reiserfs (rw)
really? i sure didn't notice:
phexro!Phaktory:~$ mount -tnfs
helix:/usr/local/share/audio/mp3 on
phexro!Phaktory:~$ ssh helix mount -treiserfs
phexro@helix's password:
/dev/hdc1 on
phexro!Phaktory:~$
or are you talking about something more subtle?
--
y'know, i wasn't so sure about this "doom 3" thing. i was an avid player of the original doom series (imo, the best way to play it was in a dark room at 2 a.m. with a pc conneted to a big set of speakers, which are cranked all the way up) and i just wasn't sure that id could recapture that spooky atmosphere it had.
however, since i cheked out those screenshots, i have had my faith in id restored. id will be forgiven it's past transgressions (quake 2, hexen, heretic, no more commander keen games, etc) if this game is half as good as it looks.
i also seem to have something wet in my pants. excuse me.
--
"-600-800Mhz Pentium® Celeron or Pentium® III Processor"
well, if you bothered to actually look at the page, you would see that the fastest cpu they sell it with is a PIII 700.
they also list the hard drive as "6gb upgradable to 18gb", but have an option for a 20gb drive on the order page.
--
i went and saw the movie opening night with a friend. i told her i'd be pleasantly surprised if the movie didn't suck.
in short, i wasn't surprised. well, that's not complerely true; i wasn't surprised that it sucked, but the ways that it sucked were quite surprising.
for example, how they didn't explain how the x-rays that starling got from verger were related to lecter at all. i'd imagine that the audience would be pretty confused if they didn't read the book.
the most interesting thing was the boom and lighting gear that was in several of the shots. towards the end, when starling and lecter are in paul's kitchen, the boom with the microphone on the end was clearly visible. so were some of their lights, and a big piece of tinfoil to diffuse the light.
sounds strange, but i swear it's true. the theater gave everyone who saw it refunds.
the manager said it was their fault. and i'm sure that if something like that got in the final release of the movie, it would have been mentioned in the review, so i guess it was just me.
can someone with more of a clue than the manager explain just what went wrong with that?
--
you're married to another computer.
--
"Linus shouldn't be "reviewing" anything."
nonsense. it's his source tree, he can (and does) review anything that gets submitted to him. bitching and moaning about how "he can't do that!" is the least productive way to respond.
when faced with a rejection from linus, you have two options: suck it down and do as the man says, or fork off your own tree.
it's obvious which path the linuxppc folks took.
--
from what i have heard (from linux-kernel) linus doesn't like to get huge patches. he likes to get small patches that do one thing, since that's easier to review.
the linppc folks have had a hard time accepting this. they want to send one huge patch to get the ppc architecture up-to-date.
it's not a new problem. see this bit on kernel traffic, which covers some of it. there was another thread, where linus flamed people for sending huge patches, but i can't find it atm.
--
or at least let someone else post? or at least stop smoking crack?
"If you think dandruff is an unhealthy food risk, Boolean sent us what might be the greatest meal ever. How can you resist a bowl of soup that morphs into a Ant is back with Mathamatical Oragami."
um, yeah.
--