Re: Confusing stack effects

Toys to one programmer may be invaluable tools to another. :-) You
might not need command line tools, but they make my job considerably
easier.

Command-line toys are not even considered by any user.
The simple reason why, is that they make the job more
difficult. Not easier.

I'm a user. I use command line tools to develop applications, and they
help me immensely. If you limit your view to only the end user
grandmother type who does email in her sewing room, then you're
absolutely correct. :-)

Why would I want to spend a week building a communication and
automation framework for a few GUI programs that expect human
interaction when I could spend 30 minutes doing the same thing with
command line filters? I'd rather do something serious than waste time
getting my tools to work. :-)

Mind you, this is what i do everydays. Indeed writing
whatever "filter", like i did last week, took me about
one hour... and the rest of the week for having an
easy to use (and re-use...) Dialog. But, mind you, it
would be a real shame, for me, to propose a command-
line filter.

Okay, you have one filter that supposedly does one job very well. But
let's say you want to run multiple filters on a file. Okay, run your
dialog and open the file, run the filter and save the output file. Open
the next filter dialog and run it on the output file, which produces
another output file that you'll probably overwrite the original output
file with. Open the next filter dialog and repeat the process until
you've run all of your filters.

Now we have me. I want to run multiple filters on a file. I give one
command:

C:\filter1 | filter2 | ... | filterN < input > output

But who am I to promote command line filters when Click&Go is so much
easier and more convenient. :-) Note that all of this is assuming that
you didn't write any framework to link any number of unknown filters
together to do the job, since that would add even more work to a simple
filter that is already quadrupled in complexity by using a GUI.

You've never worked on a large programming team before?

No. I am just the main Maintainer of the second biggest
Assembly written Application ever developped, envolving,
more or less, about 10 volunteers, representing a
collection of real life Applications. Sorry for chest
bombing, but i feel sometimes bored with being teased
by little boys, who have nothing to show but ass-hole
pedantic sentences.

Yes! I've achieved my goal of you calling me an ***! Now I can die
a happy man. :-D Sorry, but my claim to fame doesn't include showing
off my creations to complete strangers online. If you get off by
thinking you're superior because you wrote some open-source software,
that's your business. By the way, by "large programming team", I didn't
mean "a bunch of guys who got together on a forum one day". Everyone
and his brother has an open-source project with multiple maintainers.
;-)

So please save yourself of considering a 3 Megas
source of Assembly Coding Project, that took, up to now,
8 years of collective development, - having had more
contributors than the ones listed here... -, as a one man
toy. Otherwise, i am going to kick your ask, by asking to
you, the question that kills...

:)

Well, you seemed confused with the concept of one programmer not
touching all of the code in a project's source base, so my only
conclusion was that you've limited yourself to small projects where
either you and a few others were the only ones working on everything,
or projects that were so poorly structured any developer had no choice
but to wander all around the source base to get something done.

By the way, I'd love to hear the question that kills. :-) Is that like
the deadly joke? Or perhaps the fluffy pillows? Or better yet, the
comfy chair!

I do not program washing machines.

:)

What *do* you program, besides a single developer tool and tutorials
for using it? I'm not being sarcastic, I'm legitimately curious what
kind of programming you do. What other software have you written
besides the RosAsm bundle?

.

Loading