egads. i know a few gods. none of them write assembly or opcodes. they may write their own microcode compiler for the processor they're designing to solve what ails them, though:)
seriously, these are a few things i know most grad-student CS guys have never been exposed to but which should be taught: . source code revision control systems . debugging techniques (vs. broken hardware, not software) . platform integration (e.g. where do i store preferences!?!?, etc) . multi-programming in event-loop schemes . techniques for gaining understanding of a large body of code, relatively quickly . Makefiles/code build environs . packaging . testing, with large systems/moving parts.
i do device drivers so i don't often come across people who'd rather code in java. but the rest are widely applicable, i think.
I can get things done with it which were a complete pain before STL started to work w/o too much thought.
I don't write Perl scripts any longer. But, I never really try to use things like exception handling, inheritance, multiple or otherwise (unless seriously shallow), non-trivial const correctness, operator overloading, etc. There are weeds in there you're not likely to recover from brushing against.
Long story short: now great for simple, "get it done" jobs which were sending me to scripts before. If I were writing a modern library (e.g. Qt or the like) I'd stay way away from it.
I'll second the "immersion" angle... I'm a sucker for a story line but Burning Crusade just didn't do it for me. This one has me hooked. The wrathgate quest line and almost suprise cut-scene was fabulous.
Well, I for one was about to purchase a Dell or Alienware desktop for games. Now I'll likely wait around until the Intel-based Mac desktops show up instead. Just when are they coming anyway?
if i were in a position to influence the "infrastructure" of an emerging service industry... i would ensure that said infrastructure was riddled with techniques not usable without license from me.
> If you wanted 'community support' then you should have bought hardware/software that had been made 'by the community'.
i'm not the most incredibly open source literate person on the planet... for sure:) but i don't think i've ever heard of an open source hardware project. has there been one (many)? and how successful have they been if so?
personally i'd love to see someone (ahem) dream up verilog and chip/board specs for a floating point (scalable, of course) graphics system...
Slashdot Mirror
so is it impossible to extend png to include more aggressive (but still lossless) compression?
i'm getting tired of the tower of babel.
egads. i know a few gods. none of them write assembly or opcodes. they may write their own microcode compiler for the processor they're designing to solve what ails them, though :)
seriously, these are a few things i know most grad-student CS guys have never been exposed to but which should be taught:
. source code revision control systems
. debugging techniques (vs. broken hardware, not software)
. platform integration (e.g. where do i store preferences!?!?, etc)
. multi-programming in event-loop schemes
. techniques for gaining understanding of a large body of code, relatively quickly
. Makefiles/code build environs
. packaging
. testing, with large systems/moving parts.
i do device drivers so i don't often come across people who'd rather code in java. but the rest are widely applicable, i think.
I can get things done with it which were a complete pain before STL started to work w/o too much thought.
I don't write Perl scripts any longer. But, I never really try to use things like exception handling, inheritance, multiple or otherwise (unless seriously shallow), non-trivial const correctness, operator overloading, etc. There are weeds in there you're not likely to recover from brushing against.
Long story short: now great for simple, "get it done" jobs which were sending me to scripts before. If I were writing a modern library (e.g. Qt or the like) I'd stay way away from it.
slashdotting is apparently still easy :)
Yes, teach it to them for historical purposes. So they see how awful it is and no one makes that same mistake again :P
I'll second the "immersion" angle... I'm a sucker for a story line but Burning Crusade just didn't do it for me. This one has me hooked. The wrathgate quest line and almost suprise cut-scene was fabulous.
Well, I for one was about to purchase a Dell or Alienware desktop for games. Now I'll likely wait around until the Intel-based Mac desktops show up instead. Just when are they coming anyway?
won't die, then neither will this.
I'll take the bug, you can have the goofy stylized "sgi" one.
I always wondered if scads of little, white floating balls trapped with an oil slick clean-up mechanism would do the trick.
just curious.
Why would they want to be standards compliant? That's nuts.
This has been covered elsewhere.
0 3_americablog_archive.html#109690350018230874
0 3_americablog_archive.html#109690608330802330 0 3_americablog_archive.html#109697989288905008
Drudge hung his own... the one with the cheat sheet was Bush. See: http://americablog.blogspot.com/archives/2004_10_
and subsequent postings about the same topic:
http://americablog.blogspot.com/archives/2004_10_
http://americablog.blogspot.com/archives/2004_10_
i remember thinking ducted fans were nuts...
200,000 rpm and 500c exhaust!
fun fun
without it rewrites are dangerous. Well, just about any coding is :)
who's on bacca?
hey what are you gonna do with that bacca?
man that's the shizbacca!
lather, rinse, rebacca.
if i were in a position to influence the "infrastructure" of an emerging service industry... i would ensure that said infrastructure was riddled with techniques not usable without license from me.
is this ddos attack confirmed? who's reporting it?
actually, i thought it was hardware abstraction layer...
> If you wanted 'community support' then you should have bought hardware/software that had been made 'by the community'.
:) but i don't think i've ever heard of an open source hardware project. has there been one (many)? and how successful have they been if so?
i'm not the most incredibly open source literate person on the planet... for sure
personally i'd love to see someone (ahem) dream up verilog and chip/board specs for a floating point (scalable, of course) graphics system...
i'll pretend i'm dreaming until it happens.