I'll pop the cork when my customers get off IE6. Until then I need to sink development resources into maintaining and testing on IE6, no matter how painful it is. Unfortunately my customers' IT departments are slow moving and not motivated in moving quickly off XP and IE6. Most of them are understaffed and underfunded and dealing with PC's that are sometimes more than 10 years old. I suppose they have more pressing problems, given that...
I think the fallacy in this argument is not that quality doesn't win out, but that quality isn't always important. The problem is that the determination process is flawed. I might make the decision that I need lesser quality (whatever that means) for an internal time-keeping application than I do for something customer-facing, such as my sales portal. The article is of course arguing that I shouldn't be making that decision based on initial cost but on longer-term factors, but on the management side of things as long as I've got a fixed budget rooted in the short-term I can't make that decision equally. Like many financial equations, X dollars today vs. X dollars tomorrow is in play.
There are two types of fools: 1. The fools who trust in the optimization skills of the compiler/JIT compiler 2. The fools who trust in their own optimization skills
[...]
Yeah, but there's rules for them:
1. Don't optimize. 2. Don't optimize YET.
Rule 1 is for type 1 - and is generally the best case. Then you can come along and after rule 2 has expired, make the improvement where it matters. Type 2 fools skip both rules and make a mess.
Jack was a charismatic person with an infectious personality. He always was genuine, and had a passion for teaching astronomy. I was traveling and visiting various planetariums up and down the East Coast, with a final stop in Miami to visit the Space Transit. Jack made me feel very welcome and gave me a ton of his time explaining what made his planetarium special. Eventually I came to know that it wasn't the equipment (although that draws the public in initially), but the people that make these programs successful. Jack Horkheimer brought the wonder of the universe down to earth for many people, and I'm glad to have known him, even if only for a short while.
... that THAT didn't go on for too long and they got 'em in a timely manner - I mean if that had kept up, millions of machines could have been compromised! I say, good thing they had LOTS of people investigating so we could catch these crooks before the damage was done.
(Yes, for the impaired, that's sarcasm!) Two years to track this down?! Give me a break...
Re:Why where rom updates needed? apple did t softw
on
The Amiga Turns 25
·
· Score: 1
Not completely true - the old 68000 series of Macs had lots of different ROM revisions. Some worked with different versions of MacOS, but others didn't. The problem wasn't the ROMs however - it was memory. Remember back in '84-'87 128K-512K was fairly standard, so if you needed to use up a big chunk of that with OS code then you reduce the memory for user applications and graphics. Later versions of the AmigaOS could do tricks and map out various ROM routines into RAM, and even map out the entire ROM to faster RAM using the MMU, giving the machine a good speed boost in the process.
Yeah, I've got that. Not a bad computing history overview, if slightly self congratulatory at times. Also let down a little by the printing quality. But overall I would recommend it.
Slightly OT, but was wondering if there was a good BYTE archive online? I've found various sources for other magazines (gazette, transactor, etc.), but nothing for byte. I've got 5-6 complete years of byte that could be a good starter if someone were doing it.
Anyone know what kind of copyright hassles some of these archives are getting? Are people getting permission, or are they relying on these publications being out-of-print and out-of-mind? I doubt there's much commercial potential left, for example.
Except as a tool of mischief, this type of laser isn't that useful. Think it through: . Laser display - not so good, as you'd have to mount it behind some scanners, etc. and the beam probably isn't that great in quality. . Laser pointer - not so good either, unless you want to point out things pretty far away. Perhaps as an astronomy pointer, but green works just as fine here at much lower powers. . Cat toy - no, unless you like blind cats . Cutting tool - not nearly enough power to be useful here.
What's left? Nothing I can think of besides the "Hey George, see how bright this sucker is!" I certainly wouldn't want a 1W laser that I couldn't absolutely control where the beam was, and hand-held would be right out. I like my eyes.
(Yes, I own several lasers in the 500mW-1W range and operate them safely, with interlocks and keys, etc. They're not toys, but you can do fun things with them if you know how to do them safely.)
I agree that throwing old hardware all over the room is excessive, but some of us "collect" these old machines. I collect them for a mixture of history and as a way to remind myself "Don't do THAT again!" I even write about them and their history: http://codeslave9000.blogspot.com/ for anyone interested in following along at home. Parts is parts, but keeping old machines in running order is much more challenging and rewarding.
Agreed - The OP is missing the point completely. I don't want to work with you if you don't know how to write a linked list or a hash table. CS isn't that different from other career paths - you need to master the basics before they let you on the big machinery. Pascal isn't a terribly useful language today (at least in it's "pure" form - I haven't used derivatives like Delphi), but its enough to get through the basics. I learned in BASIC and assembler (PDP-11), but who cares today?
If we're talking introductory courses like Data Structures, then it's pretty hard not to look like everyone else. I don't code most of the basic data structures anymore, but I expect that anyone I hire would have been through the basics at least, so I see the value in teaching these things. But I can imagine that if I were to write basic code to manipulate a hash table or binary search it would look a lot like everyone's else code.
We've managed to avoid the question so far due to the nature of the data we've put into AWS. We won't be able to avoid it forever, and I suspect that some kind of decision support DB will be needed not too far into the future. Where that will live, I don't have an answer yet.
Would it not have been less complex to use PosgreSQL for everything, or was there enough difference to be worth the complexity?
Turns out, yes and no. We're distributed already, so it would have entailed setting up another DB anyway, and all the management infrastructure around that. AWS also seemed like a good fit for things that were essentially document-oriented and it seemed that it would be efficient for this kind of data model.
I can answer why WE decided to in this case: Cost and flexibility. For our application, there is a traditional PostgreSQL DB for things that ACID does well. For places we didn't think we'd need that level of transaction we decided that it wasn't cost effective to manage another DB instance, and instead move it to SimpleDB. Scalability wasn't the major driver at the moment, as we're already a distributed system.
FTA: "In the meantime, DBAs should not be worried, because any company that has the resources to hire a DBA is likely has decision makers who understand business reality."
Bad English aside, I just don't agree. Money != Reality. I have worked both sides of this coin - Startups with plenty of money but don't see the value in proper maintainance of the data store (one almost was put out of business by a disk failure), and very smart startups that are running lean but do understand the risks.
That said, on the deeper level, why does business reality == SQL? Sure I can scale Oracle to support massive DB's (and have), but I could probably get more value from using Amazon's SimpleDB for things that don't require massive scaling. Use the right tool for the job - Hammers are for nails, etc. Do the design work up front, decide how its gonna work, and the right tool should present itself.
We're using both - about five days from our "go-live", and things look good. We just use what makes sense for each part of our application. For us, this means PostreSQL for the parts that must be transactional ACID, and Amazon's S3 and SimpleDB for parts that don't. In practice, for the 1.0 release, this means things like notes, user accounting, and documents are in S3 and SDB. The rest is plain ole SQL.
Not that there wasn't a learning curve with our developers - we're a bunch of old-time enterprise type developers, so "letting go" and moving out of the traditional SQL world took a little thought and proving time. We'll use the first few months to learn more about doing architecture this way.
We've had the language wars - lets avoid the SQL/NOSQL wars please. I'm tired.
1. Open the browser and navigate to the page you are interested in. 2. Press the "Print" button. 3. Take your new printout, and tape it across your TV. Larger TV's might require bigger printouts. 4. ???
I can see how this might be interesting in that it's related to a "writing class", but it's an on-line writing class! It is good to see that they are stressing some of the basics that may be somewhat lacking in some on-line (esp. non-journalistic) writing.
We had assignments to write articles for Wikipedia for several years as part of an electronic music class - each student submitted several articles (totals in the hundreds over the years the class ran) on music or music technology to Wikipedia. See http://wayneandwax.blogspot.com/2006/06/electro-class-of-06.html for more details.
Interesting - what WOULD happen if you stood in front of the Large Hadron Collider beam? Does it cut/burn like a laser, or something else? Just wondrin'...
Larry said he wrote the software to do the combining of the primitives for the trench, but what was the hardware? I've used E&S consoles similar to those, but those were VAX driven, which wasn't an option in 1976. The terminal looked similar to a VT05, but that was just an impression while watching.
For the most annoying types (scams mostly) this won't matter any. There's already a "Do not call" mechanism that's ignored. The legitimate ones will obey, the rest will just continue on. Yes, it gives some teeth for when you actually catch them, but for the millions of us who have been getting the "Your credit rating will be affected!!!" calls lately, I doubt it will make any difference to our evening meals.
Slashdot Mirror
I'll pop the cork when my customers get off IE6. Until then I need to sink development resources into maintaining and testing on IE6, no matter how painful it is.
Unfortunately my customers' IT departments are slow moving and not motivated in moving quickly off XP and IE6. Most of them are understaffed and underfunded and dealing with PC's that are sometimes more than 10 years old. I suppose they have more pressing problems, given that...
C
I think the fallacy in this argument is not that quality doesn't win out, but that quality isn't always important.
The problem is that the determination process is flawed.
I might make the decision that I need lesser quality (whatever that means) for an internal time-keeping application than I do for something customer-facing, such as my sales portal. The article is of course arguing that I shouldn't be making that decision based on initial cost but on longer-term factors, but on the management side of things as long as I've got a fixed budget rooted in the short-term I can't make that decision equally. Like many financial equations, X dollars today vs. X dollars tomorrow is in play.
C
There are two types of fools:
1. The fools who trust in the optimization skills of the compiler/JIT compiler
2. The fools who trust in their own optimization skills
[...]
Yeah, but there's rules for them:
1. Don't optimize.
2. Don't optimize YET.
Rule 1 is for type 1 - and is generally the best case. Then you can come along and after rule 2 has expired, make the improvement where it matters. Type 2 fools skip both rules and make a mess.
Jack was a charismatic person with an infectious personality. He always was genuine, and had a passion for teaching astronomy. I was traveling and visiting various planetariums up and down the East Coast, with a final stop in Miami to visit the Space Transit. Jack made me feel very welcome and gave me a ton of his time explaining what made his planetarium special. Eventually I came to know that it wasn't the equipment (although that draws the public in initially), but the people that make these programs successful. Jack Horkheimer brought the wonder of the universe down to earth for many people, and I'm glad to have known him, even if only for a short while.
... that THAT didn't go on for too long and they got 'em in a timely manner - I mean if that had kept up, millions of machines could have been compromised! I say, good thing they had LOTS of people investigating so we could catch these crooks before the damage was done.
(Yes, for the impaired, that's sarcasm!)
Two years to track this down?! Give me a break...
Not completely true - the old 68000 series of Macs had lots of different ROM revisions. Some worked with different versions of MacOS, but others didn't. The problem wasn't the ROMs however - it was memory. Remember back in '84-'87 128K-512K was fairly standard, so if you needed to use up a big chunk of that with OS code then you reduce the memory for user applications and graphics. Later versions of the AmigaOS could do tricks and map out various ROM routines into RAM, and even map out the entire ROM to faster RAM using the MMU, giving the machine a good speed boost in the process.
With mirrors! Seriously, I saw a "tank" 3D system back in the late 80's/early 90's hooked up to an E&S display system.
Yeah, I've got that. Not a bad computing history overview, if slightly self congratulatory at times. Also let down a little by the printing quality. But overall I would recommend it.
Slightly OT, but was wondering if there was a good BYTE archive online? I've found various sources for other magazines (gazette, transactor, etc.), but nothing for byte. I've got 5-6 complete years of byte that could be a good starter if someone were doing it.
Anyone know what kind of copyright hassles some of these archives are getting? Are people getting permission, or are they relying on these publications being out-of-print and out-of-mind? I doubt there's much commercial potential left, for example.
Except as a tool of mischief, this type of laser isn't that useful. Think it through:
. Laser display - not so good, as you'd have to mount it behind some scanners, etc. and the beam probably isn't that great in quality.
. Laser pointer - not so good either, unless you want to point out things pretty far away. Perhaps as an astronomy pointer, but green works just as fine here at much lower powers.
. Cat toy - no, unless you like blind cats
. Cutting tool - not nearly enough power to be useful here.
What's left? Nothing I can think of besides the "Hey George, see how bright this sucker is!" I certainly wouldn't want a 1W laser that I couldn't absolutely control where the beam was, and hand-held would be right out. I like my eyes.
(Yes, I own several lasers in the 500mW-1W range and operate them safely, with interlocks and keys, etc. They're not toys, but you can do fun things with them if you know how to do them safely.)
If the Chrome OS could act as a VM host, and just host the "legacy" OS as a virtual machine. Use VNC like technology sure, but put it all in one box.
I agree that throwing old hardware all over the room is excessive, but some of us "collect" these old machines. I collect them for a mixture of history and as a way to remind myself "Don't do THAT again!" I even write about them and their history: http://codeslave9000.blogspot.com/ for anyone interested in following along at home. Parts is parts, but keeping old machines in running order is much more challenging and rewarding.
Agreed - The OP is missing the point completely. I don't want to work with you if you don't know how to write a linked list or a hash table. CS isn't that different from other career paths - you need to master the basics before they let you on the big machinery. Pascal isn't a terribly useful language today (at least in it's "pure" form - I haven't used derivatives like Delphi), but its enough to get through the basics. I learned in BASIC and assembler (PDP-11), but who cares today?
If we're talking introductory courses like Data Structures, then it's pretty hard not to look like everyone else. I don't code most of the basic data structures anymore, but I expect that anyone I hire would have been through the basics at least, so I see the value in teaching these things. But I can imagine that if I were to write basic code to manipulate a hash table or binary search it would look a lot like everyone's else code.
We've managed to avoid the question so far due to the nature of the data we've put into AWS. We won't be able to avoid it forever, and I suspect that some kind of decision support DB will be needed not too far into the future. Where that will live, I don't have an answer yet.
Would it not have been less complex to use PosgreSQL for everything, or was there enough difference to be worth the complexity?
Turns out, yes and no. We're distributed already, so it would have entailed setting up another DB anyway, and all the management infrastructure around that. AWS also seemed like a good fit for things that were essentially document-oriented and it seemed that it would be efficient for this kind of data model.
I can answer why WE decided to in this case: Cost and flexibility. For our application, there is a traditional PostgreSQL DB for things that ACID does well. For places we didn't think we'd need that level of transaction we decided that it wasn't cost effective to manage another DB instance, and instead move it to SimpleDB. Scalability wasn't the major driver at the moment, as we're already a distributed system.
FTA:
"In the meantime, DBAs should not be worried, because any company that has the resources to hire a DBA is likely has decision makers who understand business reality."
Bad English aside, I just don't agree. Money != Reality. I have worked both sides of this coin - Startups with plenty of money but don't see the value in proper maintainance of the data store (one almost was put out of business by a disk failure), and very smart startups that are running lean but do understand the risks.
That said, on the deeper level, why does business reality == SQL? Sure I can scale Oracle to support massive DB's (and have), but I could probably get more value from using Amazon's SimpleDB for things that don't require massive scaling. Use the right tool for the job - Hammers are for nails, etc. Do the design work up front, decide how its gonna work, and the right tool should present itself.
We're using both - about five days from our "go-live", and things look good. We just use what makes sense for each part of our application.
For us, this means PostreSQL for the parts that must be transactional ACID, and Amazon's S3 and SimpleDB for parts that don't. In practice, for the 1.0 release, this means things like notes, user accounting, and documents are in S3 and SDB. The rest is plain ole SQL.
Not that there wasn't a learning curve with our developers - we're a bunch of old-time enterprise type developers, so "letting go" and moving out of the traditional SQL world took a little thought and proving time. We'll use the first few months to learn more about doing architecture this way.
We've had the language wars - lets avoid the SQL/NOSQL wars please. I'm tired.
1. Open the browser and navigate to the page you are interested in.
2. Press the "Print" button.
3. Take your new printout, and tape it across your TV. Larger TV's might require bigger printouts.
4. ???
Web on your TV!
I can see how this might be interesting in that it's related to a "writing class", but it's an on-line writing class! It is good to see that they are stressing some of the basics that may be somewhat lacking in some on-line (esp. non-journalistic) writing.
We had assignments to write articles for Wikipedia for several years as part of an electronic music class - each student submitted several articles (totals in the hundreds over the years the class ran) on music or music technology to Wikipedia. See http://wayneandwax.blogspot.com/2006/06/electro-class-of-06.html for more details.
Interesting - what WOULD happen if you stood in front of the Large Hadron Collider beam? Does it cut/burn like a laser, or something else? Just wondrin'...
Larry said he wrote the software to do the combining of the primitives for the trench, but what was the hardware? I've used E&S consoles similar to those, but those were VAX driven, which wasn't an option in 1976. The terminal looked similar to a VT05, but that was just an impression while watching.
For the most annoying types (scams mostly) this won't matter any. There's already a "Do not call" mechanism that's ignored. The legitimate ones will obey, the rest will just continue on.
Yes, it gives some teeth for when you actually catch them, but for the millions of us who have been getting the "Your credit rating will be affected!!!" calls lately, I doubt it will make any difference to our evening meals.
Yeah, that would bring new meaning to "Strongly Typed" that I don't think was intended...
"Damn John, that brain fart was really strongly typed!!"