1 |
On Sun, 2003-05-04 at 13:12, Martin Schlemmer wrote: |
2 |
> On Sun, 2003-05-04 at 18:05, Wesley Leggette wrote: |
3 |
> > On Sat, 2003-05-03 at 05:05, Martin Schlemmer wrote: |
4 |
> > > On Sat, 2003-05-03 at 11:08, Wouter van Kleunen wrote: |
5 |
> > > |
6 |
> > > > Yes. I have thought of adding a script-service. But i removed it, because |
7 |
> > > > i do not like scripts. I agree that they are convenient for executing a |
8 |
> > > > collection of commands, but bash is a very weak programming language. |
9 |
> > > > |
10 |
> > > > I will think about adding scripts. Maybe just to lower the difference |
11 |
> > > > between my init and sysvinit. But rather not bash, bash is ugly :-( |
12 |
> > > > |
13 |
> > > > it would be nice if people wrote more scripts using functional languages. |
14 |
> > > > (haskell, miranda, etc...) |
15 |
> > > > |
16 |
> > > |
17 |
> > > Point is, where say 80% people can code in sh/bash, much less can do |
18 |
> > > that in python, haskell, whatever. Thus dropping the 'user' interface |
19 |
> > > to the init system being in bash/sh, will make it unusable for many |
20 |
> > > users. |
21 |
> > |
22 |
> > Oh come on. Like XML is really than difficult. I'm sure 80% know the |
23 |
> > syntax, and Wouter's keywords are a lot simpler than Bash's. Besides, |
24 |
> > 80% is completly off for people who know bash (and XML syntax too). |
25 |
> > Let's face it. Wouter's XML is a lot easier for newbies to learn. It has |
26 |
> > actual english in it. I don't see why everyone is so defensive about |
27 |
> > their beloved bash scripts. |
28 |
> > |
29 |
> |
30 |
> Why are you so defensive about XML ? Anyhow, you missed the point |
31 |
> totally, as I have not even talked about XML. |
32 |
|
33 |
Is your point that bash is easy to use and that changing things will |
34 |
make the system unusable? Both are valid, sure. It is important for any |
35 |
new system to work well with the old bash scripts until everything is |
36 |
available in both formats (or forever, for that matter), so an XML based |
37 |
system should work well with the older one. On the other matter, I can |
38 |
see why you're saying that bash scripts are easy. |
39 |
|
40 |
My point is that I think that bash scripts aren't as easy and human |
41 |
readable as people give them credit for. Sure, a lot of people know how |
42 |
to read bash, so to them it's easy. But I'd argue that bash has a higher |
43 |
learning curve than XML does, since XML has a lot more english in it. |
44 |
|
45 |
As for the other scripting languages you mention, I don't think that's |
46 |
relavant because nobody's suggesting converting to python or haskell. As |
47 |
far as I can tell, the suggestion is to use XML. That's why I brought it |
48 |
back up. |
49 |
|
50 |
|
51 |
> |
52 |
> > > |
53 |
> > > Having the startup scripts/modules binary though, means you cannot |
54 |
> > > do quick changes, etc as well. |
55 |
> > > |
56 |
> > > And like many others did say, python/whatever have too large |
57 |
> > > dependencies. For example, having python initscripts will make |
58 |
> > > an initrd/diet_system a PITA to get running. |
59 |
> > > |
60 |
> > > Having SVC support build into init, now that is a reason why I would |
61 |
> > > change init. |
62 |
> > > |
63 |
> > > Another question that bothers me ... if everybody is so against bash |
64 |
> > > being slow, why don't they spent time to get bash's IO more optimised? |
65 |
> > > For example, getting bash to read the whole script, and then executing |
66 |
> > > it, and not reading line by line should already add much improvement. |
67 |
> > > |
68 |
> > > |
69 |
> > > Anyhow, just a few quick thoughts, |
70 |
-- |
71 |
Wesley Leggette <wleggette@××××.net> |
72 |
|
73 |
|
74 |
-- |
75 |
gentoo-dev@g.o mailing list |