Maybe. Maybe we should recall Jim Carey, Dana Carvery, Mike Meyers and Lesley Neilson. We'd take John Candy back too but you killed him with all that McDonalds food!
The format for Open Office files are OPEN you dimwit. There's no "lock in" here. Read about at
http://xml.openoffice.org/ before before posting nonesence.
I don't agree. Properties can hide performance deficits in code.
Example (agnostic language)
for j = 1 to prism.Colors
-- do whatever next
In this example referencing the 'Colors' property is really calling a hidden getColors() method. What if getColors() is doing something that could be time consuming like getting the value from an XML document or from a socket connection or from counting rows from a large rowset? In these cases it would not be obvious why where the performance deficit was.
If, on the other hand you see:
for j = 1 to prism.getColors()
-- do whatever next
You are reminded that 'get' means 'go do something and then return a value'.
When one of my programmers writes something like the above example, I can spot this easily and give him a good slap on the wrist.;)
This should obviously be written as:
n = prism.getColors()
for j = 1 to n
-- do whatever next
But it's much obvious when using an explicit getter.
Naw. Fact is as long as IBM and Oracle support Java, it will be around and they'll keep supporting it because they don't want M$ encroaching on their turf (big systems).
My 2 cents.
"I have a relative who will be teaching a college class on the topic of ethical dilemmas brought about by new technology. Unfortunately, he doesn't keep up with technology news, so he's not sure what the most relevant dilemmas are. "
So why is he teaching a subject that he knows nothing about?
What college is this? Do you think I could get a job teaching the brain surgery class?
No, you're wrong.
Keep dreaming Miguel, you're wasting everyones time with this mono crap.
Why don't you do something useful for the planet and get Gnome working properly.
XUL is a fantastic concept. It allows you to completely sepertate not only UI from business logic but also UI from the *look and feel* of the UI.
Creating client specific versions of apps is a simple as applying a new CSS.
You can create apps that look like native apps and which are 'write once - run anywhere'.
Java hasn't been able to accomplish that with Swing yet.
XUL is cool!
Yes and franky, I've always detested the term "scripting". This is a term that came out of Apples marketing departement in the late 80s with HyperCard.
Programming is programming. Some things are better to develop in C/C++/Java and some in higher level languages.
The week before last my boss asked me and our Java guru for an estimate on how long it would take to write a simple KnowledgeBase for our intranet. My estimate using dBASE (of all things!) was 5 hours, his - a week.
Yes, the Java version would have been enterprise ready, etc, etc... but he wanted it now.
So I wrote it in 2 hours over the weekend and demoed it last monday (3 hours more to add some miscelaneous features he wanted).
Slashdot Mirror
This is old news. Anyone who would post a DOC file on the web is a dunce anyway. My 2 cents. :)
We need a new super hero. RabbitMan - where are you?
LookOut has no news reader. LOL!
Shouldn't Adobe take the hint and port the damn software?
Maybe. Maybe we should recall Jim Carey, Dana Carvery, Mike Meyers and Lesley Neilson. We'd take John Candy back too but you killed him with all that McDonalds food!
What are we, commies?
The format for Open Office files are OPEN you dimwit. There's no "lock in" here. Read about at http://xml.openoffice.org/ before before posting nonesence.
I don't agree. Properties can hide performance deficits in code.
;)
Example (agnostic language)
for j = 1 to prism.Colors
-- do whatever
next
In this example referencing the 'Colors' property is really calling a hidden getColors() method. What if getColors() is doing something that could be time consuming like getting the value from an XML document or from a socket connection or from counting rows from a large rowset? In these cases it would not be obvious why where the performance deficit was.
If, on the other hand you see:
for j = 1 to prism.getColors()
-- do whatever
next
You are reminded that 'get' means 'go do something and then return a value'.
When one of my programmers writes something like the above example, I can spot this easily and give him a good slap on the wrist.
This should obviously be written as:
n = prism.getColors()
for j = 1 to n
-- do whatever
next
But it's much obvious when using an explicit getter.
My 2 cents anyway.
Er, that's 3 words... ;)
Hmmm, maybe the US should go invade someone. Getting a little slow around here.
Naw. Fact is as long as IBM and Oracle support Java, it will be around and they'll keep supporting it because they don't want M$ encroaching on their turf (big systems). My 2 cents.
So why is he teaching a subject that he knows nothing about?
What college is this? Do you think I could get a job teaching the brain surgery class?
--- Mono - going nowhere slowly....
"For those of us who prefer Linux to the candydrop OS..." You mean all 7 of you? :)
XUL is a fantastic concept. It allows you to completely sepertate not only UI from business logic but also UI from the *look and feel* of the UI. Creating client specific versions of apps is a simple as applying a new CSS. You can create apps that look like native apps and which are 'write once - run anywhere'. Java hasn't been able to accomplish that with Swing yet. XUL is cool!
Yes and franky, I've always detested the term "scripting". This is a term that came out of Apples marketing departement in the late 80s with HyperCard.
Programming is programming. Some things are better to develop in C/C++/Java and some in higher level languages.
The week before last my boss asked me and our Java guru for an estimate on how long it would take to write a simple KnowledgeBase for our intranet. My estimate using dBASE (of all things!) was 5 hours, his - a week.
Yes, the Java version would have been enterprise ready, etc, etc... but he wanted it now.
So I wrote it in 2 hours over the weekend and demoed it last monday (3 hours more to add some miscelaneous features he wanted).
Smell the glove.
http://www.dbase.com