On Jul 9, 7:42 am, Peter De Berdt <[EMAIL PROTECTED]> wrote:
> Three remarks about this:
> 1) I looked into the SWFUpload code and changed some stuff to my
> liking to better integrate it with Rails (so guess what, I do
> understand what's going on). Open source means you have full access
> to the code.
Wonderful. YOU know what that code is. For me to adopt Flash I'd
have to take the time I mentioned. I've never said otherwise about
open source. As open as it can be, it's still new to many people.
Simply jumping into new technologies doesn't mean it's a strong
strategy.
> 2) I e-mailed the SWFUpload developer with some of the changes I
> made, he incorporated them together with a slew of new features a few
> weeks later. Those new features came in very handy btw, and guess
> what, I didn't spend any time implementing them and our application
> improved, if that's not good time management.
1. Having a single developer reply to emails is not what most people
would consider tech support. JQuery and Prototype now have teams of
developers, and for very good reason.
2. Good time management? Weeks later?
> 3) You're posting this on the Prototype/scriptaculous list, so I'm
> assuming you're using the libraries in your application. Seems you're
> using someone else's code, doesn't it?
You do every time you sit at a computer. But if you don't see the
difference between adopting Prototype and some guy's code posted on
his website back in 1999, then you should look again. Many
organizations, big and small, question the ability to maintain code
that's current, tested with other migrating technologies, and
supported fully. With all the JS libs out there, it's one of the
things Prototype has going for itself.
> Maybe you should write a completely new javascript parser and while
> you're at it, a new browser and rendering engine, because you don't
> know the code that's in Firefox/Safari and everyone knows there are
> quite a few bugs in every browser.
You wouldn't do well in any management position, at least for a
company that needs responsible people.
> There are two ways to deal with bugs in an open source framework or
> module: complain and wine about it, intentionally or unintentionally
> being very disrespectful towards the people who have invested a lot
> of their precious time in writing the code you're using for free or
> deal with it, find the bug that's blocking you and fix it, making the
> framework better for everyone. The other option would be to write
> your own bugfree javascript library, everyone by now must have
> realized that your code must be unbelievably good and you know all
> the quirks of all flavors of web browsers out there.
Wow. How wrong you are. I'm not whining about it, I brought it to
attention. My complaint was that there was a solution brought up that
makes little or no sense. If you still can't get that, reread the
thread. I appreciate the code I use, and continue to use it. But if
you think everybody using Prototype is going to learn Javascript to
the extent the authors know it, you are just plain wrong. That's why
it's used to begin with. Otherwise, we'd roll it ourselves.
So as a recap, I'm not only pointing out the roadblock that I've hit
(for any reason) and I'd like to get around it. But I'm not learning
how to build a rocket, take up electrical engineering, or learning 3
new computer languages. There are solutions close to what I would
like to do, and I've posted in here to see if I've missed something.
THAT is what I'm doing to solve the issue. I guess you missed that
part.
> I know one thing: this kid has actually produced a solution to a
> problem that works (our thousands of users can testify that), has
> published it for everyone to use and doesn't have an attitude like
> yourself. A large part of computer industry is based on the
> creativity and work of "children" as you like to call them btw.
Attitude? Having a business perspective is completely justified. I
guess you're a hobbyist. Well, when you get into business, you'll see
how numbers work and how they have to be represented by smart time
management, while not creating a potential disaster. And as for your
concept of tech support, just because it's worked in the past doesn't
mean it's going to work in the future. Some items in Prototype alone
have changed amongst versions. So I guess simply updating that lib
might break your apps, but you still feel completely justified.
Children are still managed professionally by managers. I suggest you
take a look at some of the professional articles that come out on
crisis management, and crisis avoidance. While adopting loose third
party random post software is quite doable, you could really be
creating a big problem for yourself if you don't understand the
underlying code. That, is not attitude, that is just common sense.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
