-
-
Notifications
You must be signed in to change notification settings - Fork 1
/
README
52 lines (38 loc) · 1.76 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
sc
=======
For years I have strived to make the best and smallest service manager I
could do. I had written sysmgr, a POSIX shell service manager. It wasn't
enough. I finally did it, Reddit. This is maximum simplicity, sc.
`sc` is a simplistic hyper-minimal static portable C99 POSIX shell service
manager in POSIX compliant shell script in a single minimal line of code.
It is so simple, that it can be run under all POSIX systems. It is so
static that this readme is part of this hyper-minimal service manager.
Dependencies
============
- systemd
- POSIX make
The `Makefile` is built-in for maximum minimalistic static-link-like
portability coolness!
Unit Tests
==========
The unit tests are also built-in for this hyper-minimal service manager,
just run `sc --test`.
Install
=======
In order to install sc, run (as root if needed):
./sc --install PREFIX=/usr
Rant
====
If you still did not pick up on the sarcasm, this is how you look like with
your minimalistic 'Boost/jQuery/some-other-bloat-library' programs.
SLOC doesn't mean anything if you are calling a huge piece of crap to make
up for your lack of skills.
If you are making your code unreadable for the sake of SLOC, you are also
in the wrong. You may not be calling a huge library, but you are giving
others (and yourself) a hard time reading your code. I have seen
programmers introduce horrible bugs to perfectly running software just
because of their obsession with SLOC, and byte size. You should always make
sure your code is readable and well commented instead of garbling it up to
brag about your code size. Just take a look at this mess of a code, it
really is a one-line shell script containing this README file of 52 lines,
and it is an absolute pain to read. Don't be like this, be smart.