Adding new features makes the code non-backwards compatible. Removing them does the same thing.
I've seen it happen in other languages (ruby, for example) and it wasn't the end of the world. If you really, really need to keep compiling old code, you just use an older compiler.
Host an email account on your own server IMAP access, and store files by sending them to yourself. Depending on your client, you can arrange the emails in files/folders/tags.
If you are comfortable with using gmail (probably no, but hey, information is free) you can use GMailfs and mount a http://sr71.net/projects/gmailfs/ . I haven't used it myself, I don't know if it's any good.
I couldn't find a working "general mailfs" system, which kindof surprises me.
It's not that I can't figure it out. It's that I don't *care*.
And a lot of programmers shouldn't. It's a perfectly automatizable problem that can be done by the machine itself. In most cases it's just inefficient to do that manually. You might as well be writing the machine code yourself.
Granted, there are some cases in which it's necessary to manage memory by hand. But those are the exception, not the norm.
If you are spending time figuring out the memory that all your programs are allocating, chances are that you are an inefficient programmer - and you don't know what is important in programming.
a) On a *single* static website (yes, static, only html + javascript + css) b) Whose single purpose is basically *defending copyright*. c) When the unemployment rate has recently surpassed 10% d) And the site isn't even good looking.
Agile means being conscious that the client *will want* to change the project requirements. This means making sure that the client understands that, and establishing a way to make it work.
And that is why you don't look surprised when you use Agile.
"Traditional" programming, on the other hand, is like making a map of a road with the client, and then getting in a car with him, start driving, and then refusing to turn the wheel even if there's a cliff just in front of the car "because it's not in the map that we agreed upon 2 months ago".
Slashdot Mirror
Thanks. I wish that list was longer, but it's better than nothing.
Adding new features makes the code non-backwards compatible. Removing them does the same thing.
I've seen it happen in other languages (ruby, for example) and it wasn't the end of the world. If you really, really need to keep compiling old code, you just use an older compiler.
I really like that they added new stuff to the language but ...
Have they *removed* anything at all from it? That's the only way I could get interested in that language again.
that LulzSec are worms.
Host an email account on your own server IMAP access, and store files by sending them to yourself. Depending on your client, you can arrange the emails in files/folders/tags.
If you are comfortable with using gmail (probably no, but hey, information is free) you can use GMailfs and mount a http://sr71.net/projects/gmailfs/ . I haven't used it myself, I don't know if it's any good.
I couldn't find a working "general mailfs" system, which kindof surprises me.
It's not that I can't figure it out. It's that I don't *care*.
And a lot of programmers shouldn't. It's a perfectly automatizable problem that can be done by the machine itself. In most cases it's just inefficient to do that manually. You might as well be writing the machine code yourself.
Granted, there are some cases in which it's necessary to manage memory by hand. But those are the exception, not the norm.
If you are spending time figuring out the memory that all your programs are allocating, chances are that you are an inefficient programmer - and you don't know what is important in programming.
You might want to check your irony detector. It might be malfunctioning.
My country has spent 600.000 *euros*
a) On a *single* static website (yes, static, only html + javascript + css)
b) Whose single purpose is basically *defending copyright*.
c) When the unemployment rate has recently surpassed 10%
d) And the site isn't even good looking.
Judge yourselves:
http://www.culturaenpositivo.es/
That's how we roll in Spain. Malaysians are just aficionados.
The difference between a hobbyist tennist and a professional one is the amount of tennis rackets he has.
"Raenex"
Ugh.
I have another phrase for you then: "spaghetti code". I hope you like pasta.
Agile means being conscious that the client *will want* to change the project requirements. This means making sure that the client understands that, and establishing a way to make it work.
And that is why you don't look surprised when you use Agile.
"Traditional" programming, on the other hand, is like making a map of a road with the client, and then getting in a car with him, start driving, and then refusing to turn the wheel even if there's a cliff just in front of the car "because it's not in the map that we agreed upon 2 months ago".
It's a "Patent Tgoll"
And also, potassium.
All the other countries are ruled by little girls.
I agree. It's not going to move from where it is.
"Flash didn't require you to know a real programming language"
Please explain what a "real programming language" is to the rest of us, mere mortals, so that we can get a glimpse of enlightenment.
What a shame.
... not
Your point?
Being an asshole is an implicit requirement.
Monkey island I-III are awesome. ... meh
Monkey island IV is
What The France
Only play videogames that you have programmed yourself.
Tenacious D has you covered:
http://www.youtube.com/watch?v=O2MmqbAaoZA
Just make sure your heart doesn't catch a fart.
Yeah, those 10 aren't affected. :P