You are obviously not a Smalltalk person are you? The numbers of useful, productive features that a Smalltalk IDE has that VS.NET doesn't is not even funny. Check out the non-commercial version of VisualWorks Smalltalk (by Cincom) and you'll see that VS.NET is suddenly not so hot.
I'd rather use Seaside for web applications or Ruby on Rails for a web-based interface to a database than use ASP.NET. Seaside is probably the most advanced thing I've seen to date, you should check out the liveWeb project that is built with it, it's gonna blow you away.
Where is Alan Kay? Inventor of Smalltalk, the reference in terms of object-oriented languages, the inventor of overlapping windows, he worked on so many projects, visionner of the laptop computer, it's not even funny: ARPA, Ethernet, the laser printer, client/server networks, etc.
I think Mr. Kay should positively be on that list. Where would all the Java, C# and C++ people be without Smalltalk?
I think the reason there's a KVim and no KEmacs is because the Emacs folks didn't understand that the goal was to embed Emacs into KDE, not KDE into Emacs.
Re:Why Ruby?
on
RAD with Ruby
·
· Score: 3, Informative
The equivalent is Gem and the reason it isn't mentionned is because this 37 list was written about two years before work on Gem began and the list has never been updated since then.
Matz was present as a keynote speaker last year, or two years ago.
Re:Help is on the way...
on
Learning PHP 5
·
· Score: 2, Informative
I agree! I recently started playing with Rails, and man it's the funnest thing to build web-based applications! It's easy, fun, simple (you have less code in your controller than some frameowkrs have just for their XML configuration files) and it works very well and very naturally!
The sad part is that, what reason are students going to give to their teachers for not having their homework done? I mean, I quickly moved from "My dog ate my homework" to "My dog ate my floppy". What now? "My dog ate my computer!"?
First of all, the opposite of dynamic typing is not strong typing, it's static typing. I'm sure you knew that, but I wanted to make sure people who are not familiar with the difference between static/dynamic and strong/weak typing get it.
Using Ruby and Smalltalk here, and thanks to unit tests, I rarely have such problems. When I worked with O'Caml, I spent quite a lot of time doing conversions back and forth to please the type system. Programming should not be about that.
Winamp could go with 8 for the next version and go with fibonacci version numbers
Re:Using the right tool for the job
on
OpenGL in PHP
·
· Score: 2, Insightful
Python is fast has a superb set of built in functionality and very flexible, and has great OO support.
Ruby is fast has a superb set of built in functionality and very flexible, and great OO support.
Smalltalk is fast has a superb set of built in functionality and very flexible, and great OO support.
Common Lisp is fast has a superb set of built in functionality and very flexible, and great OO support.
Nothing about PHP makes it more suited for this job. Also, PHP is a language that was made specifically for web pages and turned into a general purpose language because of some mad scientists. On the other hand, Python, Ruby, Common Lisp and Smalltalk are all general purpose languages, and were made that way from scratch.
Did you whine when Slashdot had a story about how LOTR won 11 awards? Did you whine when they had a story about every signed actor who's going to appear in H2G2? Did you whine when they linked a speech by Gollum at the MTV Movie Awards?
C and C++ programmers can't seem to write a single large application that does not have at least one buffer overflow security hole. We don't need that, especially now that more and more stuff is done on the internet such as banking.
the whole point of Mono is the binary compatibility at the bytecode level. Would you keep using a Microsoft JVM if it could only run MS-compiled applets and Java apps? I think not.
No, the whole point of Mono is to provide Linux developpers with better tools than the usual C and C++ provide, it's to provide something that gives more productivity to application developpers. The.NET compatibility is just something nice we have. If Microsoft makes their.NET implementation incompatible, we'll still have something that works better to make user applications than C, and that's the whole point.
Well, if more people used Smalltalk, we might see more interestingapplications. Stuff that C# and Java people find revolutionnary has been in Smalltalk for a long time now, just get ahead of your time, use Smalltalk.
I don't understand this guy. He rails in his previous blogs about how bad microsoft is, yet he goes out of his way to emulate microsoft technology. It's mind blowing.
You don't understand Mono then. Miguel, Nat et al thought that programming for GNOME in C was becoming too hard, not fast enough, etc. So they decided they needed something new. They looked at the available alternatives, but none of them seemed to fit the bill. They then looked at.NET and C# and they liked what they saw and saw how it could be useful to program for GNOME. So they decided to use that. But the goal was not to copy what Microsoft has, it was to bring a better tool to Linux and GNOME developpers, that tool just happened to be made by Microsoft. This has the advantage that they don't need to write as much documentation as other languages' teams because Microsoft does it for them.
Fast is not always good. There are applications you can upgrade, add code, etc. while it's running! The reason why we use so-called slower languages (because languages aren't slow per-se; implementations are fast or slow) is because they often allow us to do much more complex things much more easily. Try to code a regular expression in Assembly, you're still gonna be at it in 2 years. Computers evolve and we now demand more from them, and if it costs a little CPU time, well so be it.
And if you're so smart and good and not lazy, go ahead and write the Assembly version of this program. Now, make sure it can work on all platforms you can get.NET or Mono on (this means Windows, Linux, Mac, Sparcs, x86s, motorollas, alphas, etc.), otherwise it's not as useful.
If you want someone that seems to agree with you, read recent interviews of Chuck Moore. Even the guy who wrote C doesn't use it anymore; Dennis Ritchie uses Aleph.
So while we're learning, why not go with something like Smalltalk, O'Caml or Common Lisp? In Objective C, you still need to do your own memory mangement.
Slashdot Mirror
You are obviously not a Smalltalk person are you? The numbers of useful, productive features that a Smalltalk IDE has that VS.NET doesn't is not even funny. Check out the non-commercial version of VisualWorks Smalltalk (by Cincom) and you'll see that VS.NET is suddenly not so hot.
I'd rather use Seaside for web applications or Ruby on Rails for a web-based interface to a database than use ASP.NET. Seaside is probably the most advanced thing I've seen to date, you should check out the liveWeb project that is built with it, it's gonna blow you away.
I think Mr. Kay should positively be on that list. Where would all the Java, C# and C++ people be without Smalltalk?
I think the reason there's a KVim and no KEmacs is because the Emacs folks didn't understand that the goal was to embed Emacs into KDE, not KDE into Emacs.
The equivalent is Gem and the reason it isn't mentionned is because this 37 list was written about two years before work on Gem began and the list has never been updated since then.
Matz was present as a keynote speaker last year, or two years ago.
I agree! I recently started playing with Rails, and man it's the funnest thing to build web-based applications! It's easy, fun, simple (you have less code in your controller than some frameowkrs have just for their XML configuration files) and it works very well and very naturally!
The sad part is that, what reason are students going to give to their teachers for not having their homework done? I mean, I quickly moved from "My dog ate my homework" to "My dog ate my floppy". What now? "My dog ate my computer!"?
Using Ruby and Smalltalk here, and thanks to unit tests, I rarely have such problems. When I worked with O'Caml, I spent quite a lot of time doing conversions back and forth to please the type system. Programming should not be about that.
One of the requirement could be to clearly comment the code.
Slashdot nerds will complain that iPod's do not have OGG support and are thus evil and should never be purchased.
Winamp could go with 8 for the next version and go with fibonacci version numbers
Ruby is fast has a superb set of built in functionality and very flexible, and great OO support.
Smalltalk is fast has a superb set of built in functionality and very flexible, and great OO support.
Common Lisp is fast has a superb set of built in functionality and very flexible, and great OO support.
Nothing about PHP makes it more suited for this job. Also, PHP is a language that was made specifically for web pages and turned into a general purpose language because of some mad scientists. On the other hand, Python, Ruby, Common Lisp and Smalltalk are all general purpose languages, and were made that way from scratch.
Did you whine when Slashdot had a story about how LOTR won 11 awards? Did you whine when they had a story about every signed actor who's going to appear in H2G2? Did you whine when they linked a speech by Gollum at the MTV Movie Awards?
Except Chomsky is boring like hell. Michael Moore can hook the average people, that's his strength.
C and C++ programmers can't seem to write a single large application that does not have at least one buffer overflow security hole. We don't need that, especially now that more and more stuff is done on the internet such as banking.
No, the whole point of Mono is to provide Linux developpers with better tools than the usual C and C++ provide, it's to provide something that gives more productivity to application developpers. The .NET compatibility is just something nice we have. If Microsoft makes their .NET implementation incompatible, we'll still have something that works better to make user applications than C, and that's the whole point.
Well, if more people used Smalltalk, we might see more interesting applications. Stuff that C# and Java people find revolutionnary has been in Smalltalk for a long time now, just get ahead of your time, use Smalltalk.
You don't understand Mono then. Miguel, Nat et al thought that programming for GNOME in C was becoming too hard, not fast enough, etc. So they decided they needed something new. They looked at the available alternatives, but none of them seemed to fit the bill. They then looked at .NET and C# and they liked what they saw and saw how it could be useful to program for GNOME. So they decided to use that. But the goal was not to copy what Microsoft has, it was to bring a better tool to Linux and GNOME developpers, that tool just happened to be made by Microsoft. This has the advantage that they don't need to write as much documentation as other languages' teams because Microsoft does it for them.
viper-mode. 'Nuff said.
And if you're so smart and good and not lazy, go ahead and write the Assembly version of this program. Now, make sure it can work on all platforms you can get .NET or Mono on (this means Windows, Linux, Mac, Sparcs, x86s, motorollas, alphas, etc.), otherwise it's not as useful.
If you want someone that seems to agree with you, read recent interviews of Chuck Moore. Even the guy who wrote C doesn't use it anymore; Dennis Ritchie uses Aleph.
He doesn't talk about how Fortune 1000 see the Mono initiative, that would be interesting.
Actually, I read that if Whidbey is delayed and Mono stays on schedule, Mono will be the first to support C# 2.0.
Java is not standarized and C# has an open ECMA standard.
So while we're learning, why not go with something like Smalltalk, O'Caml or Common Lisp? In Objective C, you still need to do your own memory mangement.