Forgot your password?
typodupeerror

Comment: Re:Bad place to ask (Score 1) 307

by Josh Triplett (#42409713) Attached to: Ask Slashdot: Typing Advice For a Guinness World Record Attempt?

1) Finger memory.
2) :w and :q exist as separate commands with numerous other combinations (:wa, :wqa, :wn) so :wq fits more naturally into that family.
3) If you want to use a shortcut for :wq, ZZ requires even fewer keystrokes (shift z z versus shift : x enter).

Between the three of those, :x never really seems preferable.

Windows

+ - ReactOS is hiring, looks to reach beta before Windows XP support ends->

Submitted by Anonymous Coward
An anonymous reader writes "From the ReactOS announcement: "For the first time ever, the ReactOS Foundation seeks to go beyond the usual small fundraising campaigns aimed at paying infrastructure expenses. We wish to raise money to formally hire as many core developers as possible, to work on the project they believe in, the project they've been working on, to transform a hobby into a job so they can dedicate all of their time to the ReactOS project.""
Link to Original Source

Comment: And yet people use webmail (Score 3, Insightful) 217

by Josh Triplett (#37672566) Attached to: US Government Seizes Email of WikiLeaks Volunteer
Why would *anyone* involved in something as sensitive as WikiLeaks trust a webmail provider of any kind, or any third-party email storage? Run your own mail server, download your mails immediately, and store all emails locally on an encrypted drive. That won't protect new emails in transit (that's what GPG is for), but it'll protect existing emails. I can understand people using webmail when they don't really care. But in this case, it seems ridiculous.

Comment: Re:Firefox will be dead by mid-2012. (Score 3, Insightful) 247

by Josh Triplett (#37077506) Attached to: Firefox 6 Ships Next Week, 8 Blocks Sneaky Add-Ons
Of the competitors, only Chrome is open. And while it seems like a fine browser, and I keep it around to check web-page rendering in WebKit, I can't stand it for normal usage for a pile of reasons:
  • The upstream packaging tries to install a new sources.list entry and cron-update itself. *Bad* software, don't mess with my package management, no biscuit. Fortunately Chromium doesn't do anything that crazy.
  • Chrome desperately wants to pretend that all monitors have 96 DPI, so I have to lie to it and say I want much bigger fonts than I do, just to get something readable. This also means that sites can't use CSS lengths like "8.5in" and get something actually 8.5 inches wide on my screen.
  • Chrome ignores all of my system font configuration that says how to render fonts, producing blurry fonts so bad they literally make my eyes water. (It does Mac-style blurry anti-aliasing, whereas the rest of my system does anti-aliasing that produces crisp lines.)
  • Chrome downloads and shows ads on the "new tab" page by default.
  • Chrome zooms images and text together, with no option to just make text bigger and leave images un-blurry.

Comment: Re:Resolved? (Score 1) 134

by Josh Triplett (#36817244) Attached to: Frustrated Judge Pushes For Solution In Google Books Case

A third party *has* mediated, and made it clear that if the two parties don't come up with a solution then the issue will go to trial, and nobody wants that.

Personally, I don't find it at all clear why Google owes a single penny for scanning books and making them searchable, *without* allowing non-public-domain books to be seen in their entirety. They might wish to make some kind of deal to allow more access to non-public-domain books, but that has nothing to do with fair use of existing books, and if snippets and search don't count as fair use then I don't know what does.

Comment: Re:I don't see the problem (Score 1) 184

by Josh Triplett (#35387192) Attached to: Red Hat Stops Shipping Kernel Changes as Patches

Still not the same thing; that just gives you the overall diff between RH kernel versions or between the RH kernel and upstream. Other Linux distributions provide full split-out patches and/or git trees of every individual patch they've applied to their kernel, to which many individual changes occur between package revisions.

Comment: Re:I don't see the problem (Score 1) 184

by Josh Triplett (#35381586) Attached to: Red Hat Stops Shipping Kernel Changes as Patches

It doesn't matter at all for CentOS. It matters for other Linux distributions that want to collaborate with Red Hat and with upstream. Digging a fix out of the Red Hat kernel becomes a lot harder with only a monolithic patch. And without fine-grained patches, any kind of conflict between the megapatch and other kernel patches becomes incredibly difficult to troubleshoot.

Badges? We don't need no stinking badges.

Working...