| 1 |
On Tue, 2003-04-15 at 21:29, Justin Whitney wrote: |
| 2 |
> Reasons for doing this would include: |
| 3 |
> |
| 4 |
> *writing (advanced) shellscripts requires learning awk/sed, and various |
| 5 |
> other minor tools (mostly because their features aren't supported by the |
| 6 |
> language). Use of a language with these features builtin lowers the |
| 7 |
> learning requirement, or at least puts it all under one roof. |
| 8 |
> *improved performance and bytecode-compilability |
| 9 |
> *Speedups due to fewer exec calls (for awk/sed/etc) |
| 10 |
> |
| 11 |
|
| 12 |
My main problem with this is an apparent flaw in logic; one has to learn |
| 13 |
python in addition to sh now, although sh scripts will be a normal part |
| 14 |
of UNIX administration for a long time to come. As part of learning sh, |
| 15 |
one masters the associated tools (awk/sed as mentioned examples). |
| 16 |
|
| 17 |
Adding python syntax to the mix increases the learning curve for not |
| 18 |
much benefit to an existing system (I'm not so sure there would be a |
| 19 |
speedup either). |
| 20 |
|
| 21 |
Might be interesting to see as a practical demonstration, though. |
| 22 |
|
| 23 |
Brad |
| 24 |
-- |
| 25 |
// -- http://www.BRAD-X.com/ -- // |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-dev@g.o mailing list |
Archives