:::FoxM:::

Weak and Powerless

Subscribe to RSS feed

Posts tagged with "Linux"

Sticky post

Jabber and other gibberish

, , , ...




This work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License
By this work, I mean the images, sound, text and stuff like that, which I own, in every page related to this site. Other works belong to their respective owners, and not me. p
Note. This site will NOT work properly with Internet Explorer. Go get a real browser, like Opera.

Comments also available on pigeongrams ( http://twitter.com/arguapacha ).

Rebooting is obsolete

, , , ...

A few days ago a competition for a linux ad was over and the finalists, and winner, of course, were finally public. A lot of work, time and immagination went through all those videos, some of them, very good. Others very strange or funny.

Here, the 5 who made it to the end.

(Comments after each video)

Read more...

Lo dije!

, , , ...

Una imágen vale más que mil palabras:

New photos added, and a big THANK YOU!

, , , ...

This is just a 'thank you' post to Michel Xhaard for his effort in writing (ALONE!!!) the drivers for around 260 webcams for the Linux Operating System!

http://mxhaard.free.fr/download.html

Read more...

Desktop for Dummies

, , , ...

GNOME users are idiots. Not my words... not words of anyone in particular, but resemble (and are based on) Linus Torvalds's words in THE flamewar of GNOME vs. KDE.

For those not knowing I left behind the GNOME environment for a much better KDE, and in the process I found that there has been a bit heated debate about GNOME's flexibility (the reason I left it). I just read the WHOLE thing! and it was quite amazing... really can't believe I did that (^o^) . Anyway, the point is that Linus advocates for a more customizable desktop environment, which he compares to a game: each time should be more challenging; and the challenge, in this context, is to be able to change the desktop so I can do what I want to do, and not what other might think I would like to do because he/she feels is better at something just by studying one of those undetermined fields of design... The GNOME designers and developers, think that the average user they are aiming at are those who start up things by reading the "... For Dummies" series, then (may be) followed by some fast Wikipedia search and then, done. KDE users, on the other hand, like to explore things around, but also have tools to mimic the behaviour of other desktops, and by those things, KDE targets a lot more users, in the sense that, if you like simplicity, you can just start using KDE with the default configurations, but if you want more complex customization, you can still use KDE to modify a lot of stuff, all at once, or one by one.

It is, however, worrying that some people inside GNOME, do think ``users are idiots'':

[quote Rodney Dawes from bugzilla 408898]
Comment #13 from Rodney Dawes (developer, points: 20)
2007-02-18 17:45 UTC
A Novice/Expert setting has been tried before in Nautilus, and it failed.
Everyone is just going to set the setting to Expert anyway, because people like
to make themselves feel like they are better at something than they actually
are.
[/quote]

It shows how people seem to love taking decisions for other people they do not even know. Things like this made me drop Windows altogether, and really, really, keep me a little bit away from MacOS (It is annoying to use the stupid mouse all the time and with no way to use the keyboard whenever I want it)

The question is, then, does your desktop enables you to change things about it? No... let's put it more general: Does your software enables you to customize it the way you want? Opera does... and that is one more reason to love it!

GNOME is getting on my nerves

, , , ...

It all started when I downloaded a new Linux distribution to install in my PC. It was all perfect at the begining. At least it was quite a lot of stuff new to learn, but... to be honest, GNOME, a very popular desktop environment in linux, quite disappointed me.

To everyone else not using linux, a Desktop Environment is the most complicated concept you can fit in your brain when you hear that in linux there are a lot of ways of representing and manage the windows in a graphical way... In other OSes, namely MacOS and Windows, there is only one graphical way to talk to the user, the former a lot better than the latter one. Linux is somewhat in the middle (kind of). As a part of the you-are-free-to-do-with-your-pc-whatever-you-want philosophy, not found in neither the Mac or Win worlds, a lot of people decided that the existing options of graphical outputs in Linux were not acceptable to their needs, and so, the window managers and desktop environments appeared. Both form the perfect complement to the so-called window server and thus, offer the most flexible and customizable OS in the market.

One of those couples (window manager + desktop environment) is GNOME, the one I am throwing flames today. Hehe. Although it shares some of the ideas of the Macintosh User (Usabilitiy) Guidelines, it is not a clone of it, neither it has the power the mac UI has. Yes, as one of the guidelines says, Usability is essential, and yes, it is simple to use and understand. So simple, that is is impossible to do many things with it. Note that I left out the word "advanced". Ordering the windows can become a problem if you don't install some extra software. Yes. I know that customizing the window behaviour is not a DM's work, but the doctor told me not to use the mouse that much! I need keyboard shorcuts to move the windows around, to open applications, to handle devices. If it is about usability, seems that the concept could have multiple definitions, if you consider the experience and capabilities of the user, and not the designer whishes.

Look at this wonderful Web Browser called Opera and make an example from it. It has what every user needs in a quite simple interface. if you want to use the mouse, you have the gestures, but if you want to use the keyboard your have a whole miriad of shorcuts so powerful that would make mac and windows users blush in shame. That's what I am asking for in my GNOME and I find that for every new capability it would need to download more software.

I used GNOME Bittorrent client for a while. And yes, for quite basic stuff is just perfect, but then I found that in one particular torrent I had to do some hash checking (mathematical comparision of data) and... guess what! There is no checking in that software! Propietary and boring OS (hehe mac and win) are out of question here; you must download / buy extra software to do... well.. anything, but why does GNOME have this kind of inconsistencies being an open source project? Could be that taking that usability goal to the extreme is counterproductive?

I do not know. GNOME is nice, visually (OpenOffice looks more than great!) but its simplicity seems to be a drawback, more than an advantage. I think I am heading back to KDE, as it is not my ideal to complicate more my computing life using simplier or smaller Window Managers that are difficult to understand.

Note to self - ATI binary drivers installation

, , , ...

I was trying today to create a temp directory in my home, but then I couldn't. In my way to investigate the issue, I noticed that I already had a temp file there. the file command taught me a lesson:
file temp
temp: ASCII English text, with very long lines


After some kind of little smile that took my lips to some delicate movement, I opened the file and found a set of instructions I had done a few weeks ago when updating the ATI video drivers. It's merely a dump of this page, but I still want it here... you never know when something like that can come handy p

ATI video drivers

SUSE Linux 10.1 ships with the newly revamped open source radeon driver. That may be fine for 2D rendering, but it doesn't do direct rendering for 3D graphics. To get hardware 3D acceleration (and for XGL support), you still need the proprietary ATI fglrx driver.

Go to the ATI Web site, click on Drivers & Software, then Linux Display Drivers and Software, then on the driver appropriate to your video card. 32-bit SUSE installations need the x86 drivers, and 64-bit SUSE needs the x86_64 versions. After you have clicked the link for your card, yet another link comes up. Click it, scroll down to the downloads table, then right-click the ATI Driver Installer download link and save it to your home directory. You do not need to download any of the other packages.

After the file transfer completes, close all open programs, then press ctrl-alt-F1 to switch to the first virtual terminal. You'll see a text-mode login prompt; log in as root. When you're at the command prompt, type in this command:

init 3


You'll see a bunch of text scroll by, and then a message saying that runlevel 3 has been reached. Press Enter to get the command prompt back, then change directories (cd /home/username)to go to the one you downloaded the driver

Be sure to substitute "username" with your user name, in the above example. Now you need to change the ATI installer permissions so that it can be run from the command line.

For long file names, you don't have to type the whole name into a terminal window. Instead, just type the first few letters and then press the Tab key, and the file name will be automatically completed for you. This is useful in situations like the one you're in now, where there is a long and complex file name to type in. So type the following command into your terminal, and use the Tab key to complete the ATI driver file name, then press Enter to execute the command:

chmod +x ./ati-driver


That will make the program executable; this must be done before you can run it. Now it's time to run the installer. Again, use tab completion instead of typing the name in. You have to add the ./ before the filename to tell the terminal program that the file you are referring to is in the current directory. If you don't specify that, the terminal will look in other places for the file. It sounds crazy, yes, but that's the way GNU/Linux is (and Unix before it). For the below example, the entire file name is typed in. Please note that this may not be the same file name that you downloaded -- it is only an example. You should use tab completion when you type this command in so that you don't accidentally mis-type the long file name. The part of the example that will not change is the switch statement after the file name (the part with the dashes). Here's the example command for the ATI driver installer for a 32-bit system:

./ati-driver-installer-8.24.8-x86.run --buildpkg SuSE/SUSE101-IA32

And for a 64-bit system:

./ati-driver-installer-8.24.8-x86_64.run --buildpkg SuSE/SUSE101-AMD64


After a few dozen lines of text, a driver package will be created. Go ahead and run it with the following command (the first example is for 32-bit systems):

rpm -ivh fglrx_6_9_0_SUSE101-8.24.8-1.i386.rpm

And for 64-bit systems:

rpm -ivh fglrx64_6_9_0_SUSE101-8.24.8-1.x86_64.rpm


Update your system environment variables with this command:

ldconfig


Next, you need to tell SUSE that you want to use this driver instead of the standard one:

aticonfig --initial --input=/etc/X11/xorg.conf


Lastly, you have to tell YaST which driver to load (that's a zero in the example, not a letter):

sax2 -r -m 0=fglrx


Now reboot your computer by typing the following command:

reboot


The next time your system starts, you'll have hardware 3D video acceleration. Please note that every time you update your kernel, you must re-install the ATI video driver.



Thanks to Jem Matzan!!

Note to self - Intel High Audio Definition

, , , ...

I have an Intel D945GNT board wich has Intel High Definition Audio subsystem. I discovered today that if I want to use the microphone, I have to enable the line and mic as output and select the front mic as source for capture. Otherwise, and with no apparent reason, the recording line won't catch a single sound. It's a shame, as I hate when something is working in strange ways.



I also discovered that Krec and Krecord do not work as I thought they would. I record something and then save it as a wav file, but the results are not quite the expected. I know I need to read the documentation p but... let's face it, that's the last thing I do. I then had to use the gnome-sound-recorder, which actually records a lot better than Audacity in Windows. I like KDE, but if some gnome software works better or easier, why not use it? At least there's KDE support for Gnome applications and I thank to the KDE developers for it.

Note to self - VMware installation

, , , ...

Being a little bit egoist here, I found that I forget quite easily some details of the things I do in Linux. The last one was related with the VMware Workstation installation.

To install VMware, follow the steps (grealty resumed into a few lines):

  1. Check that kernel-source, gcc (and/or gcc-c++) and make are installed. I think I will never forget to install those, as I use them a lot. The kernel-source packages must match the installed kernel! running YOU will find the proper packages.
  2. Download the latest vmware-any-any patch. (Probably available at cvut). This is needed because it's higly probable that compilation errors might appear when running the vmware-config.pl script. The last error I got was from a confligting defined variable in the kernel source against the vmware client code
  3. Be sure to have the vmware rpm ready and anxious to get installed
  4. Prepare the kernel to recive new modules: remember the
    make mrproper
    (for cleanup),
    make cloneconfig
    (for cloning the kernel and configuring it to the current version) and
    make modules_prepare
    (well... it's self explanatory)
  5. With a prepared and happy kernel, the rpm installation can be done by the typical
    rpm -ivh PACKAGE
    where the package here it's, of course, the vmware file.
  6. After this, I normally do a step I think it's not really necessary. I like to run
    ldconfig; SuSEconfig
    sequence, just to see how happily my PC works wink
  7. Now the update. I've seen it tarred and gzipped, so a
    tar -xz -f vmware-any-any-update.tar.gz
    will do the work. Changing to the vmware-any-any-update directory (I wonder... that any-any name), and executing
    ./runme.pl
    will do the rest, even call vmware-config.pl for me. When this is done, answering a few questions it's all it's needed for completing the procedure. The default options are fine for my SuSE 10.1 so if any compilation error occurs, be sure to check this and the vmware-any-any-update version.
  8. Configure the three network devices (bridged, NAT and host-only); that it's normally just accepting the default options.
  9. Mount the USB system to access those devices from the Virtual Machine. As root:
    mount -t usbfs /dev/bus/usb /proc/bus/usb


And that's it... at least as I remember. I'm not sure where did I get this "any-any-update" info, but I'm sure it's not that difficult to get. Wait... I found it in my history (I love opera wink)


I decided that when I see it fit (and achievable or worthly), I should translate some of what I write in english to spanish, or viceversa. This is one of those cases.

--- Versión en español ---

Para instalar VMWare, seguir los siguientes pasos de la receta (resumida en pocas líneas):

  1. Verificar que los paquetes de kernel-source, gcc (y gcc-c++) y make están instalados, pero creo que no hay problema con eso pues los uso mucho y no creo que los olvide. Los paquetes del kernel source deben encajar con la versión del kernel instalado! Correr YOU sería una buena idea en este momento para asegurarse.
  2. Bajar la última versión del vmware-any-any-update (Probablemente disponible en cvut). Esto lo necesito para evitar algunos errores de compilación en el proceso. La última vez salió un error de una variable en conflicto por estar definida tanto en el kernel como en el cliente
  3. No olvidar tener listo el rpm de vmware (hihihi)
  4. Preparar el kernel para recibir nuevos módulos: No olvidar:
    make mrproper
    (para limpiar, o eso me dijeron),
    make cloneconfig
    (para clonar el kernel, configurándolo a la versión correcta) y
    make modules_prepare
    (para preparar en sí la utilización de los módulos)
  5. Con un kernel listo y felíz, la instalación del rpm es cosa de niños:
    rpm -ivh PACKAGE
    donde PACKAGE es obviamente el archivo del VMware.
  6. Después, lo que hago no es realmente necesario... solo me gusta hacerlo por poner el pc a hacer algo:
    ldconfig; SuSEconfig
    . En teoría eso actualiza las variables del sistema, entre otras cosas.
  7. Ahora la actualización. Como viene en tar.gz, ya se sabe que está comprimido y unificado, pero tar nos ayuda fácilmente con ese trabajo.
    tar -xz -f vmware-any-any-update.tar.gz
    hace todo el trabajo. El resto se hace cambiando al directorio creado por tar para vmware y ejecutando
    ./runme.pl
    . Esto inclusive llama vmware-config.pl por mi. Cuando todo haya pasado, solo falta responder unas preguntas. Las opciones preseleccionadas que trae el script funcionan perfecto en mi SuSE 10.1, así que si algo falla (como errores de compilación, yo supongo), este es el primer sitio a revisar, junto con la versión del any-any-update.
  8. Configurar los tres dispositivos de redes (es otro módulo montado en el kernel), bridged, NAT y host-only. En general es al estilo windows: yes, yes, yes, yes p
  9. Montar el sistema USB para tener acceso a estos dispositivos en la máquina virtual: como root:
    mount -t usbfs /dev/bus/usb /proc/bus/usb



Y listo... ahí la instalación correcta del vmware... antes que se me olvide.

Sony Ericsson usb-serial cable

, , , ...

I noted recently in one of the last projects that some people were interested in using a DCU-11 usb-serial cable to plug their phones to a linux box. At that time I did not know how to make that possible, but after a little e-search I found how to mount the cable in my SuSE 10.1 (Kernel 2.6.x). For all those interested I will tell my story wink

First when the cable was connected nothing happened, so I knew I had to go a little bit deeper. dmesg showed that "something" usb was connected, but not linked to any device in the system. I left the research there because of other projects, but when I came back to install my scanner I was shocked when two devices were found, and one of those was something like "ArkMicro USB-UART Controller". I knew that was the generic usb-serial converter because ArkMicro was the name given for the company that makes those chips in the installation driver for Windows. Along with the name, there was also the hex number for the vendor and the product! so that was a relief. After a google search and a su, I tried:
# modprobe usbserial vendor=0x6547 product=0x0232

And no problem! I could check that the cable was there in /dev/ttyUSB0, but I have to check the modem connection yet.*

I could not do that because I went to pick my new P800 at the store and as I have just arrived, I'm still playing with it, but I have to say that the support for the SyncStation seems perfect, but I could not find the phone with any of the syncronization programs that came with SuSE. Well... going a little bit deeper doesn't harm anyone.


* I read somewhere that the ArkMicro driver for this cable will be supported in the kernel in the next version (2.6.17), so it won't be too long before everyone can use the cable almost with no problem.

Projects

, , , ...

I'm working now in some projects that have been keeping me very busy. The two most important are a controlling software for mobile phones using AT commands. I'm planning to use python for this project, and maybe for the other one too. The second project it's easier: simplifying calculations for most of the basic formulas in finance management (calculating interest rates, present and future values of money, etc).

The first project it's one of the most complicated I have started, so I think about start applying some of the extreme programming disciplines (but I'm not an expert at all). I'm just starting to reading the characteristics of the problem, but will be posting my progress here.

For the second project I thought about applying some those "tenets" from the Gancarsz book, The Linux and Unix Philosophy, specially the "Small is beautiful" one. It's going to be a perfect first excercise for learning python.


First Update 6.5.2006: I'm a little behind schedule p Well... ok, ok, not "a little". WAY behind schedule. I realized the first project is not very difficult, but has a lot of little details that have been keeping me busy for a lot of time. I noticed that one of my main weak points is that I lack of that capacity for designing the system and keeping the structure. I have changed twice the main design, the first time because the original design had a terrible flaw with the communications logic. The second time because my classmates told me that the teacher (who is a VB fan) likes those fancy but useless GUI, yet all the program is designed to work as a command line program. I hope I find a way to communicate the programs via stdIO, creating the GUI with Visual Basic; Tkinter has not a very nice appeareance.

The second project has been declared completely stalled. Unfortunately my time has been reduced and my sparetime is not enough for that.... I will continue after all classes are finished.

I'm also beginning to understand why building a prototype as soon as possible is very important! There is nothing good in analysis paralysis.

Windows Vs. Linux

, , , ...

Hace unos días me pasaron un artículo sobre Windows y Linux, originado en las recónditas regiones virtuales argentinas, desde las planicies de Microsoft MSDN. Como trabajo de la universidad me pusieron a escribir un ensayo al respecto, pero obviamente mi capacidad para las palabras ha disminuído exponencialmente con los años, así que lo único que resultó fue un completo y sesgado texto lleno de opiniones a medio fundamentar, sin embargo, el ejercicio me gustó y me gustaría compartirlo.




El artículo original se puede conseguir en
MSDN Latinoamerica
. Es un buen artículo, pero en general falta mucha información sobre Linux.




Aunque le falta mucho, porque lo escribí de afán, mi respuesta al artículo va como sigue




Sin duda alguna, una de las más interesantes experiencias de mi vida académica ha sido el contacto con el sistema operativo Linux. Tal vez sea por la novedad, o porque se siente como un aire fresco entre todo el mundo visto desde Windows. Incluso puede que solo sea esa necesidad innata de pensar diferente al común de la gente. Cualquiera sea la razón, la experiencia ha sido bastante gratificante durante el poco tiempo que he podido trabajar y divertirme con este sistema operativo. Mi experiencia con Windows ha sido variada y relativamente extensa (desde la versión 95 hasta la XP) y antes de eso la experiencia con D.O.S. fue aún mayor. Sin embargo, comenzar a trabajar con Linux ha exigido una apertura mental que antes no existía. El cambio debía ser tan fundamental que era la filosofía lo que cambiaba, es decir, los cambios eran de fondo, no solo de forma. Al leer el artículo me encuentro entonces, a grandes rasgos, con una persona, o un grupo de personas que tienen arraigados en sus mentes la filosofía Microsoft, aquella filosofía del ocultar, esconder complejidad, casi mentir, al decir que algo es fácil, cuando no lo es. Linux, por otro lado, intenta ser como esas corazas transparentes con las que se ven algunos dispositivos electrónicos. Es obvio que la inclinación del autor, implícita y explícita en todo el texto, deja con poco crédito al esfuerzo y el tiempo dedicado a la creación y mejora de Linux y ese es el sabor concreto de toda la lectura, sin embargo, hay ciertos puntos en los que considero hay una falta grande de información por parte del MVP. En orden de aparición en la lectura, las cosas serían más o menos así: Se dice claramente que por windows se paga una sola vez, pero una sola vez por cada equipo, debería hacerse la aclaración. Las grandes distribuciones que cobran por el soporte, lo hacen para cualquier número de máquinas, sea la versión para estaciones de trabajo como para servidores, mientras que cada licencia windows por estación de trabajo aumenta los costos netos para la empresa. Luego se habla de las características gráficas de Linux contra Windows y se critica duramente que Linux no cumple lo que promete, al decir que corre en un 386. Obviamente un procesador de tan atrasada tecnología no puede cumplir las exigencias de ningún sistema de Interfaz de usuario, ni siquiera Windows, a menos que sea Windows 3.1 (obsoleto desde hace mucho). Sin embargo, el kernel de Linux (incluso las versiones 2.4 que aún tienen actualizaciones) pueden correr sin problemas, y con un poco de memoria se pueden cargar interfaces tan útiles como KDE o GNOME. (Personalmente trabajo en un Pentium II - 266 con 32 MB en RAM y mi Linux funciona perfectamente). Habría que preguntarle al señor si alguna vez intentó cargar una memoria USB con Windows 3.1 en un 486 o un pentium. Hay otro punto aquí con las interfaces gráficas que me gustaría aclarar. Volviendo a la filosofía Microsoft de ocultar la complejidad, vale la pena comentar que las UI, desde mi punto de vista, no se hicieron para hacer fácil lo difícil. Se crearon para satisfacer a los usuarios poco exigentes, desinteresados en el mundo de las computadoras y que se tornan en un riesgo para ellos mismos y para otras computadoras. Carl Sagan decía: "We live in a society exquisitely dependent on science and technology, in which hardly anyone knows anything about science and technology. We have also arranged things so that almost no one understands science and technology. This is a prescription for disaster. We might get away with it for a while, but sooner or later this combustible mixture of ignorance and power is going to blow up in our faces." Los resultados de ello lo estamos viendo lentamente, pero con mucha claridad: la rápida expansión de virus por las redes de computadoras es el ejemplo más claro que me llega a la mente en este momento. Mucha de esa expansión se debe en gran medida a la falta de educación e interés de los usuarios hacia las computadoras, a esa combinación de "ignorancia y poder". Luego de todo esto, se empieza a considerar qué tan serio es Linux como Sistema Operativo. El autor argumenta que Windows es más fácil de configurar. En parte tiene razón, pero volvemos a la filosofía adoptada por su creador: Windows toma muchas situaciones por "pre-establecidas" y deja solo las configuraciones más superficiales al usuario. Es muy difícil (lo he intentado) configurar el sistema operativo en determinados casos en los que se desea cierto comportamiento específico. En otras palabras, Windows toma muchas decisiones por el usuario. En mi punto satírico del día, que no va a ser muy largo, leo con afán que cuando llegó Windows 2000, Microsoft había tomado "otra filosofía, otra potencia de software", y luego cita un comentario irónico sobre la desfachatez con la que antes se presentaban los productos basados en Windows NT. Mi pregunta-comentario irónico es: ¿Cuál fue la razón para Microsoft de cambiar su filosofía? Obviamente, el mercado, sería la respuesta. Unix y lentamente Linux han estado muy fuertes en el campo de servidores, que es un área bastante importante, así que Windows tenía que (al menos) alcanzar lo que había alcanzado UNIX y Linux. Eso sí, se le abona a Microsoft, que hizo un buen trabajo. Luego vienen los consabidos comentarios sobre virus y seguridad. Ha sido un caballito de batalla (de ambas partes) desde hace mucho tiempo. La defensa del autor para Windows se basa casi exlusivamente en Windows 2003 Server, para lo cual diserta durante muchos párrafos, en los cuales dedica en total 4 líneas en nombrar a Linux, diciendo que tampoco es seguro. Un comentario un poco sesgado y algo precario. Defiende también a Windows diciendo que la base de usuarios es mucho mayor. Claro que es mayor, pero lo es en Windows XP, no en Windows 2003 Server y aunque ambos están basado en la misma tecnología (NT), la versión server tiene énfasis en seguridad. XP es como las ingenierías: un mar de conocimientos de 5 cm de profundidad. Ahora, cuando el autor habla de que la base de Windows Update es mejor que cualquiera de Linux, en parte tiene razón, pero se debe a que su Knowledge Base es mucho más extensa, también debido a que la cantidad de usuarios es mayor, por lo que así mismo, la cantidad que reportan errores es también mayor. Aún así, las grandes distribuciones, o por lo menos la mía utiliza el YOU (YaST Online Update) que permite mantener el sistema actualizado con facilidad. Algo con lo que ahora está luchando Microsoft, dado su temor a los usuarios con copias ilegales del sistema XP instalado en muchos equipos del mundo. La discusión sobre la cantidad de programadores dedicados a un sistema operativo no es un argumento para decidir qué tan bueno es el producto porque: 1. Nadie tiene datos con los que se pueda comparar naturalmente la situación. 2. Con menos precisión se sabe la calidad de los programadores ni de uno ni de otro lado del espectro. Lo único que se podría decir es que tal vez sea cierto que la jerarquía que se lleva en Microsoft con los programadores, puede ser un elemento que contribuya a un mejor control del progreso del sistema operativo, pero Linux también tiene su contraparte: personas dedicadas 100% (por dinero o por placer) a Linux, organizadas en comités de desarrollo que proyectan y diseñan las partes más sensibles del sistema. Incluso, si el desarrollo se hace dentro de una compañía, como RedHat o SuSE, a estos les es más fácil adoptar proyectos actuales, posiblemente GPL o LGPL y desarrollar a partir de ahí, que ponerse a desarrollar sus propias herramientas, como hace microsoft. Yo sospecho que esto también colabora en el hecho que un producto Microsoft rara vez es lanzado el día que se había acordado al comienzo. En cuanto a la estabilidad de Linux, tengo que aceptarle al autor que cuando Linux se cae, queda totalmente bloqueado, sin embargo, debo aclarar que en el 98% de estas situaciones el problema ha sido de hardware. En un ambiente casero (real) nunca se me ha caído Linux. Lo máximo que se ha caído por software es el KDE (que por cierto, con un Ctrl + Alt + BackSpace se soluciona). En el siguiente punto se aclara que como servidor de Bases de Datos, Windows es mejor porque tiene el SQL Server y su relación Precio - Prestaciones. Pero ambos productos hay que comprarlos por aparte, y pagar licencias separadas. Ciertamente las bases como MySQL y PostgreSQL aún tienen mucho por mejorar (aparte de los comentarios irónicos sobre las formas normales), pero son una buena opción para un PyME con necesidades básicas de rendimiento y confiabilidad, es decir, para el 80% de los casos. Luego llegan a criticar la experiencia de Java en Linux y Windows. Pero Java y su JVM son cosas aparte del mundo Linux. Otro comentario que se cae por su propio peso. Sin embargo, cabe aclarar que algo de perspicacia le faltó al autor: En Linux casi no hay IDE avanzadas de desarrollo porque la base de los programadores es C y C++, por lo que mucho del trabajo se realiza con editores sencillos y no complejísimas herramientas, no solo por simplicidad y flexibilidad, sino por preferencia personal de los programadores. Para finalizar el autor coloca los tan ansiados resultados de la experiencia: Sin embargo, aclara débilmente, que la población de muestra ha tenido, al menos, 4 años (académicos) de experiencia en Windows, y ni uno solo en Linux. La desventaja es clara contra Linux, pues no se trata solo de instalar un servidor web, base de datos y otras arandelas, sino de aprender Linux en el proceso. Además de eso, la población claramente sufrió de un síntoma típico (que yo también sufrí) de la transición: intentar hacer las cosas en Linux, de la misma forma que se hacen en Windows. Estoy seguro que más de uno intentó buscar un Panel de Control.

February 2012
M T W T F S S
January 2012March 2012
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