Is it just me, or is Nit's answer to dependency management: "just throw it in the standard library"?

These are what I found taking a quick look through the standard library (http://nitlanguage.org/doc/stdlib/):

- OpenGL Wrapper A (http://nitlanguage.org/doc/stdlib/group_egl.html)

- OpenGL Wrapper B (http://nitlanguage.org/doc/stdlib/group_glesv2.html)

- emscripten framework (http://nitlanguage.org/doc/stdlib/group_emscripten.html)

- Github API wrapper (http://nitlanguage.org/doc/stdlib/group_github.html)

- Web Framework A (http://nitlanguage.org/doc/stdlib/group_nitcorn.html)

- Web Framework B (http://nitlanguage.org/doc/stdlib/group_popcorn.html)

- Game Framework A (http://nitlanguage.org/doc/stdlib/group_mnit.html)

- Game Framework B (http://nitlanguage.org/doc/stdlib/group_gamnit.html)

- Game Framework C (http://nitlanguage.org/doc/stdlib/group_bucketed_game.html)

- Game Framework D (http://nitlanguage.org/doc/stdlib/group_scene2d.html)

- A twitter like web app (http://nitlanguage.org/doc/stdlib/group_tnitter.html)

- Web app for planning meetups (http://nitlanguage.org/doc/stdlib/group_opportunity.html)

- An unofficial app for bargoers?? (http://nitlanguage.org/doc/stdlib/group_benitlux.html)