Commentary

Serdar Yegulalp
 

To Sink Or Swim In Linux's Waters?

I've been running Ubuntu Linux on my notebook, a Sony VAIO TX model, for some time now.  I'm impressed with how stable it's been and how a whole raft of features like action-key support (for things like dimming the display) are available directly out of the box, without having to install additional stuff that I needed to download from Sony's site.  But because getting used to Linux itself can be jarring for Windows folks, I decided not to just dive in and hope I'm able to swim.  Instead, I'm using a gradual approach: I take it to bed with me.

I've been running Ubuntu Linux on my notebook, a Sony VAIO TX model, for some time now.  I'm impressed with how stable it's been and how a whole raft of features like action-key support (for things like dimming the display) are available directly out of the box, without having to install additional stuff that I needed to download from Sony's site.  But because getting used to Linux itself can be jarring for Windows folks, I decided not to just dive in and hope I'm able to swim.  Instead, I'm using a gradual approach: I take it to bed with me.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

OK, wipe that smirk off your face.  I'll explain.

I typically spend about an hour before bedtime getting caught up with favorite blogs, Web sites and whatnot by sitting up in bed with my notebook.  When I first bought the notebook, I did this with Windows, but now I do this with Linux.  Doesn't sound like much, but just working with Linux in that much of a "nonjudgmental" way has been a huge help in allowing me to get used to it.

"Nonjudgmental" in this case means that I'm not doing anything mission-critical yet on that machine, but the more stuff I do casually with it, the easier it becomes for me to do more important things later on.  If I start with easy stuff like reading (and writing) blogs, then I'm generally working with applications and functions that have easy equivalents in Linux -- Firefox, for instance.  Even something as familiar as Firefox can be a bit thorny, though: installing the Gnash (open-source Flash player) plugin required a little more work than I expected.

Some people cling instinctively to the way certain things work, even if they don't realize it.  Friends of mine have tried to make the switch to Linux, only to be stopped because of one or two deal-breaking details that they didn't see going in.  I think the "cold turkey switch" approach may be at least partly responsible for this -- that the better approach for such folks might be to run Linux in tandem whenever possible, and to do less demanding things with it using apps people are already familiar with in other incarnations.  (Firefox and OpenOffice.org are two of the biggest and most obvious examples.)

Unfortunately, this isn't always that easy to pull off, either.  Many people don't have both a desktop and a notebook machine, are gun-shy of setting up a dual-boot, don't have the resources for a virtual machine, and so on.  And booting from a live CD or DVD has its own issues -- mainly speed.

Still, any habitual use, however you can get it, is better than none.  And, ultimately, it's easier to swim in Linux's waters when you've had a chance to wade rather than simply dunk your head and hold your breath.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links