From my experience as a developer using MySQL on several projects, MySQL has a looong way to go. It not only lacks a ton of features, but also lacks data integrity checks, stability, and data validation (amongst other things). E.g. I've once managed to insert (by mistake, of course) two rows in a table with same PKs. The result? MySQL didn't warned me about it, inserted the data instead. Every SELECT on that table killed the server in the background, causing automatic mysqld restart.
Being open source/free software doesn't mean that we have to be less forgiving to the glitches mysql has. Look at postgresql - it's doing fine, supporting every DB feature I can imagine and is rock-solid stable. I haven't seen lame excuses like "stored procedures coming really REALLY soon" on their site recently.
I wouldn't recommend mysql for anything other than address-book type of things... and all the mysql fanboys can go screw themselves - it's not a good database, period.
Well, as you put in your question, I guess this is every programmer's dream: to get a stable, 40 hours week programming job surrounded with people that you know and care about. But I think that programming is not the kind of job that one can do untill retirement - it is a highly-demanding job that requires up-to-date knowledge and brings higher levels of stress than other jobs.
So, I think that after certain age every coder gets tired of keeping up with the technology and stress, and this is the time when they either get pushed into a managerial role, or stay coders till retirement, maintaining legacy applications in legacy languages.
In a way, programming is like soccer: you play it till you reach the age when you no longer can keep up with the younger (or leave it early because of a bad injury, for example). And then you train the younger until retirement.
It is certainly not a something than man can do for all of his life.
Seriously, who in their right mind can put its trust and record his/her essential data onto a mass produced medium with an average price of $0.10?
What do you think about using a quality hard drive as an alternative for long-term storage? Coupled with a drawer cabinet for the drive, open-sourced file system format, and a safe place for keeping it when it's offline -- this seems to me like a better long-term solution than CDs (well, at least for 10-15 years - until the disk interface changes...).
Yes, but compare today's word processors with those from 20 years ago, when C/ASM was commonly used. The release schedule was same as now, maybe even longer -- and the project complexity then was far less than todays. Simply, there was more time, and less competition.
When you have to release something yesterday, optimization is the last thing you think of as a programmer - which is a sad fact of today's software industry...
Re:I'll wait for the next beta ...
on
New Red Hat Beta
·
· Score: 1
Yeah, I hope they stick with Phoebe. And the promotion will be going with the main theme:
Smelly cat, smelly cat What are they feeding you? Smelly cat, smelly cat It's not your (seg)fault
And to keep it on topic, let's hope Phoebe will organize the zillion kinds of "Settings" sub-menus under the main BlueCurve menu into one global.
Slashdot Mirror
Intel should be wide open to purchase nVidia if they want
I somehow doubt that even Intel has the necessary dough to buy nVidia.
Here's a list of another MySQL gotchas: http://sql-info.de/mysql/gotchas.html
From my experience as a developer using MySQL on several projects, MySQL has a looong way to go. It not only lacks a ton of features, but also lacks data integrity checks, stability, and data validation (amongst other things). E.g. I've once managed to insert (by mistake, of course) two rows in a table with same PKs. The result? MySQL didn't warned me about it, inserted the data instead. Every SELECT on that table killed the server in the background, causing automatic mysqld restart.
Being open source/free software doesn't mean that we have to be less forgiving to the glitches mysql has. Look at postgresql - it's doing fine, supporting every DB feature I can imagine and is rock-solid stable. I haven't seen lame excuses like "stored procedures coming really REALLY soon" on their site recently.
I wouldn't recommend mysql for anything other than address-book type of things... and all the mysql fanboys can go screw themselves - it's not a good database, period.
Troll alert! Troll alert! Put on your mod-parent-troll shields!
Well, as you put in your question, I guess this is every programmer's dream: to get a stable, 40 hours week programming job surrounded with people that you know and care about. But I think that programming is not the kind of job that one can do untill retirement - it is a highly-demanding job that requires up-to-date knowledge and brings higher levels of stress than other jobs.
So, I think that after certain age every coder gets tired of keeping up with the technology and stress, and this is the time when they either get pushed into a managerial role, or stay coders till retirement, maintaining legacy applications in legacy languages.
In a way, programming is like soccer: you play it till you reach the age when you no longer can keep up with the younger (or leave it early because of a bad injury, for example). And then you train the younger until retirement.
It is certainly not a something than man can do for all of his life.
Yours no longer,
S C
Dear S C,
I didn't give a fuck about you anyway -- already took all your money AND made you look like an idiot - what woman can possibly want more?
Sincerely,
Ms. Windows
This kind of jokes are just plain rude -- not funny!
Whole Linux distros are dragged from the net via BitTorrent - we're talking about OS + apps here, not just a patch for the OS.
.iso images distributed via BitTorrent?
So, what makes XP SP2 different from the majority of Linux
Seriously, who in their right mind can put its trust and record his/her essential data onto a mass produced medium with an average price of $0.10?
What do you think about using a quality hard drive as an alternative for long-term storage? Coupled with a drawer cabinet for the drive, open-sourced file system format, and a safe place for keeping it when it's offline -- this seems to me like a better long-term solution than CDs (well, at least for 10-15 years - until the disk interface changes...).
Yes, but compare today's word processors with those from 20 years ago, when C/ASM was commonly used. The release schedule was same as now, maybe even longer -- and the project complexity then was far less than todays. Simply, there was more time, and less competition.
When you have to release something yesterday, optimization is the last thing you think of as a programmer - which is a sad fact of today's software industry...
Yeah, I hope they stick with Phoebe. And the promotion will be going with the main theme:
Smelly cat, smelly cat
What are they feeding you?
Smelly cat, smelly cat
It's not your (seg)fault
And to keep it on topic, let's hope Phoebe will organize the zillion kinds of "Settings" sub-menus under the main BlueCurve menu into one global.