Concerning Re: Poor performance in windows. Sw
Jeff Smith wrote on 17 Feb 2007, 12:06, at least in part:
> On Saturday 17 February 2007 11:00, Jan Hendrik wrote:
> The predicament is that each time you almost come to a complete
> solution, it just barely falls short because of some feature you can't
> contol. Right? Happens to me, to.
>
> My solution has been to script, or tweak something in the tool's
> source code myself. I've been free personally from MS Win myself for
> over two years now, so I've been able to observe people who are still
> "trapped" in the environment. My greatest observation has been that
> they too easily leave the blame on "the way something is". And when I
> try to help them fix the problem, I have a heck of a time trying to
> make microsoft stuff do what I want. For example, since DOS was
> effectively meant to be a toy in the beginning, I have a really hard
> time doing serious scripting with batch files.
I started with Python (even wxPython) a couple of years ago and
about the last two years or so I did some things in PHP, Perl, and
Python, some even twice, especially in the beginning, hitting the
"safe" setting in PHP applied by the ISP. Already that was quite a
learning curve for me, only did Word macros (some quite extensive
though) before, besides some futile attempts in Visual Objects.
What I do is trying to always keeping something on the todo list,
so that by doing some scripting every few weeks I at least keep
feeling half-way comfortable with this. It's not programming, it's
finding ways to accomplish things by searching manuals and the
web. Would not dare going into a big program like SVN, changing
a line and compile things. Started with computers in 1994, but
they always were just a means to do my work on (which has
nothing to do with computers a/o programming), never something I
hacked or played on in spare time. That's my limitation, and I can't
afford taking couple of months off to overcome this and e.g. work
out a complete migration (or hiking it done). You are right in
saying that this can be quite expensive, but that's how the world
goes - the poor man usually pays twice or thrice by having to pay
in small chunks.
> It seems to be the fear of learning curve that keeps people from
> finding out what they are missing with open source.
About 1999/2000 a friend of mine set up SUSE 6.2 for me.
Swallowed up half of what then was a rather huge 2GB HDD and
was awfully slow, a real PITA. Of course no decent word
processing, no photo editing that was worth its name. I should say
just something for computer pros in network administration and
freaks hacking and gaming away their spare time. And of course it
would have been much easier for us to go for Linux in those days if
it only had come up to office needs back then - very little data
ballast in those days.
Still I keep updated with Linux development, not least with stuff
working in both worlds to ease things. Spent a week with
OpenOffice, already said that and how it mangles 1-1.5K files,
nothing big, just Word sections not honored by OO, but enough to
keep a man busy repairing the layout of 1/500 files manually.
Accounting software is another issue I mentioned. Every time I
have to buy an update just for legal reasons, not because any of
the changes would affect us, I search for alternatives in Linux, but
there isn't anything out there, or it has an industry range price tag.
Before buying the NikonCapture software for RAW photo editing (at
1.5 the price it costs in the US) I did extensive tests with
independant tools and plug-ins, including Gimp. The output of
none came close to NC or it took a lot more effort at far less
comfort & flexibility. From what I read about HTML editors there
still is nothing in Linux that matches Homesite, even though nvu
and others get closer. Probably they would be close enough for us
already. And I know a few guys living in both worlds sticking with
Windows as their principle OS just because of email client
Pegasus Mail ...
There you have the basic things we need and for which a migration
has to be as quick and smooth as can be. Maybe someday new
hardware will force us more than we would like. Have experienced
this twice before with a new machine not working with an older
WinOS, only currently I still fiddle with a laptop not working
properly with W2K, and Vista will definitely not make it into our
office. But just as well that day the solutions may be ready out
there to buy (or even for free) which currently would take a lot of
effort on our side.
> I think you could install Python on your subversion server (it works
> on MS too), learn to use it with subversion hooks, and really find
> advantage for automatically updating the website. There would be no
> need for fancy FTP sync stuff relying on dates. Unfortunately I don't
> have experience applying this yet, just see that it is a good use of
> the post-commit hook.
I had some thoughts about such a post-commit script. Should not
be too difficult in Python or Perl, probably even as batch as I
currently use for incremental dumps. One (minor) limitation though
is that for some rename/move operations SVN needs two or more
commits which would render the production webserver in in-
between states. Should not happen too often, but bad if for any
reason the follow-up commits do not work out. Probably also
worthwhile in this regard to run SVN on the Linkstation. Would be
nice to make better use of this piece of hardware. I have a receipe
for setting up, but also a report that is runs awfully slow.
Have a nice Sunday!
JH
PS:
We should better take follow-ups offlist.
---------------------------------------
Freedom quote:
Let us build cathedrals of peace,
where the people are free.
-- Ronald Reagan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Feb 18 14:23:17 2007