libk  Artifact [b97c3b0969]

Artifact b97c3b0969bc42e3c5a7428a4684472ab3e01e706f94aa53a08c61da135dd680:

Wiki page [libk] by lexi on 2019-08-22 04:34:04.
D 2019-08-22T04:34:04.682
L libk
P 4fbe65deff791455fef3dcf913b3e2706ed11b9a665c57a56afcebe22b1ea3a2
U lexi
W 2538
<table><tr>
<td width="210pt" valign="top">
<font size="36pt">libk</font>
  *  [/doc/tip/libk.md|libk manifesto]
  *  [/download|download source]
  *  [rules|rules and guidelines]
  *  [roster|project personnel]
  *  [ports|porting progress]
  *  [roadmap|the road ahead]
  *  [join|getting involved]
</td>
<td>

libk is an (admittedly ambitious) project to create a reasonably cross-platform replacement for libc that uses and encourages modern coding techniques and idiomatic, efficient use of C. the existing standard library, libc, is an [http://man7.org/linux/man-pages/man3/errno.3.html|old and ailing thing], marked by idioms that otherwise would easily earn any CS student an F, replete with [http://man7.org/linux/man-pages/man3/srand.3.html|potholes and traps] for the unwary and novice alike, and was designed at a point in history where computers were still very new and anyone who knew what they were doing had [https://timeline.com/women-pioneered-computer-programming-then-men-took-their-industry-over-c2959b822523|long since been pushed out of the field].

in short, libc is simultaneously a nonviable, inflexible, dangerous basis for nontrivial new projects, and obligatory for all but the most low-level work in C, forcing coders to spend a great many hours writing blast shields around its entry points. it is our aim to wash away this stain on the CS field, and hopefully make C a great deal more pleasant to write by giving coders a standard library that doesn't fight them every step of the way.

for an in-depth look at the project's aims, structure, and basic strategy, take a look at the <strong>libk manifesto</strong>.

libk is still a very new project, and we're very much looking for new contributors, whether in the role of developer, reviewer, tester, technical writer, or sponsor - in particular, those who would take on the monumental task of porting libk to windows and maintaining a windows build chain; we currently have nothing in the way of a windows team. however, even if you're new to low-level programming, you can still play an important part and meaningfully influence the shape libk ultimately takes, and if you can learn, we can teach.

<em>please note that we place a very high importance on maintaining a mutually supportive, compassionate, and productive environment where our contributors can feel valued </em>regardless<em> of their background, identity, or level of skill; behavior that threatens this environment will not be tolerated.</em>
</td>
</tr></table>

Z 18c2e8cb16ddc950640c5adc88e32108