| 1 |
1. People developing software |
| 2 |
|
| 3 |
It is especially true for C/C++. We should focus on bringing |
| 4 |
bleeding-edge GCC, Clang and core libraries like Boost and Qt. Next |
| 5 |
thing is that we should keep track of new languages, IDE-s, text |
| 6 |
editors, and other developer tools coming up and not only adding |
| 7 |
silentely ebuilds, but also informing upstream developers that we get |
| 8 |
their software into our distro - it's quite common practice to inform in |
| 9 |
which distros app is available. |
| 10 |
|
| 11 |
To me Gentoo is the only choice if it comes to development. |
| 12 |
Unfortunately I must use Ubuntu at work and it really sucks at that. |
| 13 |
|
| 14 |
2. One install for ever |
| 15 |
|
| 16 |
This is really cool about Gentoo that you need to install it only once - |
| 17 |
no reinstalls, no risky release upgrades. If you keep Gentoo up to date |
| 18 |
you get a stable system until your machine dies (by overheating? ;-)). |
| 19 |
|
| 20 |
3. Web apps |
| 21 |
|
| 22 |
I feel that's the topic which other distros avoid, because of too rapid |
| 23 |
development of web apps. We could improve on that topic and provide |
| 24 |
bleeding edge ebuilds. We could also ask an upstream to give a note that |
| 25 |
on Gentoo it's just a matter of emerge thewebapp and a user doesn't have |
| 26 |
to follow complicated set-up guide. |
| 27 |
|
| 28 |
I find this especially problematic on Ubuntu which cannot keep up with |
| 29 |
Ruby releases. |
| 30 |
|
| 31 |
4. Security - Gentoo hardened |
| 32 |
|
| 33 |
Gentoo gives choice about security models. Do other distros provide any |
| 34 |
choice on that? |
| 35 |
|
| 36 |
5. Choice of init system |
| 37 |
|
| 38 |
In the light of recent flame wars we can take an advantage of giving a |
| 39 |
choice on that topic. (-: |
| 40 |
|
| 41 |
|
| 42 |
Cheers, |
| 43 |
|
| 44 |
-- |
| 45 |
Amadeusz Żołnowski |
Archives