The Arch Way (Italiano)

From ArchWiki
Revision as of 16:02, 4 May 2007 by Axelgenus (Talk | contribs)

Jump to: navigation, search

Template:I18n links start Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n links end

I principi e la filosofia di Arch

Questa pagina cerca di descrivere i principi e la filosofia di Arch Linux. Tempo fa non c'erano documenti scritti riguardo il "metodo Arch"; molto probabilmente non succederà più. In breve, il "metodo Arch" sta per "libertà di scelta, semplicità, apprendimento e controllo da parte dell'utente".

Principi

Io, Judd Vinet, ho cominciato a costruire Arch per due ragioni:

  1. Non trovavo nessun'altra distribuzione che condividesse i miei ideali. Alcune andavano molto vicino a ciò che volevo ma trovavo noiosi cavilli e inutili complessità che spaventavano più che aiutare;
  2. Per divertimento - dare qualcosa all'intera comunità del software libero, dalla quale ho preso così tanto.

Per sua natura, Arch è:

  • Leggera e semplice. Non significa comunque che sia per chiunque...
  • NON è stata creata come una distribuzione per i novellini; è stata pensata per gli utenti più esperti. L'obiettivo è di sviluppare Arch come una base perfetta, per quanto umanamente possibile. Una base non include strumenti elaborati e meccanismi di auto-configurazione ma, piuttosto, contiene strumenti per la configurazione manuale e poche funzioni, in modo che gli utenti possano ulteriormente sviluppare e/o imparare da soli.
  • Un regalo, ripeto, "...dare qualcosa all'intera comunità del software libero, dalla quale ho preso così tanto." Quando ricevi un regalo da qualcuno, solitamente ci si aspetta qualcosa in cambio. In questo modo, gli utenti sono i benvenuti nel contribuire con le loro idee, strumenti e suggerimenti.
  • Aware there are two sides which contribute to Arch Linux: Developers and Users. Don't expect the two sides to merge, but to have a mutual relationship whereby anyone can pick up what they want to add to their machine; our GOALs are to:
  • NOT let configure tools / GUIs control the system, but that they be controlled by the user. There is nothing wrong with GUIs as long as they follow this principle.
  • NOT be controlled by or dependent on what tools offer. When developing or selecting a utility tool, it should be written in a hackable/readable programming language (KISS) to enable users to modify it if they so choose.
  • The core development of Arch Linux will NOT be providing any "newbie-friendly" GUIs/utilities at any time in the near future.
  • We humble developers will continue to provide Arch as a solid base for everyone and anyone. If you guys want to make it pretty, give 'er a rip. Free speech, free beer, and all that.

Philosophy

The System of values by which Arch develops:

  • KISS (Keep It Simple, ...) is the basis of Arch development.
  • In Arch, 'simple' doesn't always mean what it does in other distros. It's our philosophy that the learning is more important than getting something easily done.
  • Relying on GUIs to build and use your system is just going to hurt a user in the end. At some point in time a user will need to know all that some GUIs hide.
  • If you try to hide the complexity of the system, you'll end up with a more complex system. Instead, try to make the system simpler and more logical from the inside.
  • Sooner or later, you'll have to find the information on the web and usenet (if man is not enough). Learning how and where to find it on the net should be the first thing a newbie has to learn.
  • Where some users say "...such and such distro isn't like so and so distro," Arch allows the user to make all the contributions they want as long as it doesn't go against the ideals of the design or philosophy.
  • Arch Linux is different from the others: at Arch, the user isn't the only concern. Minimizing development of new tools and docs while maximizing understanding of Linux' inner workings, while keeping a watchful eye always on the "KISS" aim and philosophy of Arch Linux in general...is what makes the "Arch Way" truly different.
  • The great thing about contributions is that you don't need anyone's permission to make them. (See?) No one can physically stop you from writing something that you (personally) find useful, even if the "powers that be" don't see it as a blessing. Write it and put it up in the User Contributions forum. If other people like it, you'll receive feedback. If virtually everyone out there hates it but you, you'll receive feedback, for sure - but who cares? It took you 20 minutes to write, and you learned something along the way. It's a winning situation no matter what.
  • It is what you make it.

Comments

What users have said about Arch:

  • "After spending a lot of time with other distributions (debian, gentoo, mandrake, redhat, fedora, slackware) and even FreeBSD. I think that I finally found the distribution I was looking for."
  • Same thing with (k)ubuntu, Mandriva, and several others. Well, openSUSE is nice and easy (that's the one I would advice for my sister); but Arch is the One which really *rocks*.
  • "I have tried several distro's and even took (tired?) RHCE (took it BACK?), but there was always something I disliked about each."
  • "My dream distro was always the simplicity of Slackware with real dependency support like Debian's, and guess what - that's Arch."
  • "I also found Arch my final distro."
  • "After trying out almost all the available distributions, I have to agree that Arch is the best."
  • "Hi all. I just registered here so I could report all the problems I'm having, and ask for help. Funny thing is, I HAVE NO PROBLEMS!!! I really can't believe this, but everything is just working! I installed Arch today, had a little trouble with xorg and sound setup, but found all the answers I needed in the documentation and the forums!"
  • "I tried Mandrake, Yoper, FC3/4, Mepis and Ubuntu. I was looking for the perfect distro. I am glad that I found Arch."

PROS and CONS

PROS

  • i686-optimized
  • pacman: 'System Upgrade' is ONE command: "pacman -Suy"
  • pacman: Dependency-control, no X/GUI needed
  • ABS: the package-building function need only be done once - building another version of a package is extremely easy
  • ABS: you can build all the packages on your machine with one command
  • fully up-to-date packages at your request, and fully customizable
  • the people behind the scenes are gentle, motivated and able
  • less than 20 minutes to create a fully functional system
  • the perfect environment to learn Linux in
  • not really popular, because not known (still relevant?)

CONS

  • pacman: needs a fast internet connection to stay always up-to-date easily (less of a problem as time marches forward)
  • some conflicts from using the newest libs ("bleeding edge")
  • lack of newbie-friendly features
  • very little hardware detection (relevant?)
  • info files are almost always way more detailed than man-pages (gcc.info e.g.)
  • not really popular, because not known