Letture quotidiane

Mele e appunti

Come sempre, il buon Lucio Bragagnolo riesce a condensare il succo del discorso nel titolo stesso dell’articolo: Il dispiacere della lettura. In questo pezzo recente, Lucio prova a dare qualche consiglio su quali fonti aggiungere alla propria lista di letture per tenersi al passo in ambito informatico. (Colgo l’occasione per ringraziarlo della menzione indiretta). C’è un punto essenziale sul quale sono in pieno accordo con lui:

E bisogna fare una premessa: le notizie sono molto sopravvalutate. Anche per il professionista più esigente, le notizie importanti della giornata, di qualsiasi giornata, sono da zero a tre. Quelle che veramente impongono l’urgenza di sapere sono da zero a tre. Ogni anno. Si provi a stare senza la minima news Apple o informatica per una settimana, e vedere che cosa ci si è “perso”.

Il resto viene riempito da sciocchezze, invenzioni, i famosi rumor che hanno perduto da anni ogni ragione d’essere, frantumazioni del capello in sessantaquattro, inutili notizie di aggiornamento […] e marchette.

Insomma, chiacchiere. Un particolare su cui Lucio non si è soffermato ma che voglio sottolineare io è la replicazione e la ritrasmissione di queste chiacchiere. Prova della sostanziale vuotezza di molti siti — specie italiani, duole dirlo, ma anche in lingua inglese — è la straordinaria frequenza con cui ripetono a pappagallo notizie e chiacchiere prodotte da terzi. Spesso non esiste nemmeno una verifica della bontà della fonte, e notizie ‘buone’ vengono tragicamente mischiate con ‘previsioni’ tecnologiche il cui valore equivale all’oroscopo della settimana; il risultato è un calo qualitativo del sito intero.

Notavo in modo particolare questo fenomeno agli inizi della mia esperienza con i lettori di feed RSS, quando buttavo nel calderone un po’ di tutto prendendo più o meno indiscriminatamente dai bookmark del browser. Anch’io ho avuto, per una stagione, la frenesia del tenermi aggiornato, la paura di perdermi qualcosa. In realtà, con tutti quei feed, mi ritrovavo a leggere le stesse cose ripetute e riciclate da un sito all’altro. Senza una scrematura si finisce col perdere di vista gli articoli o le notizie che meritano davvero la nostra attenzione.

Un altro punto su cui sono d’accordissimo con Lucio:

Tornando a bomba, che cosa leggere per l’aggiornamento abituale di una persona giustamente curiosa, senza interessi professionali specifici ma solo con una giusta dose di interesse per il mondo (informatico) che la circonda? […]

Se non si vuole avere a che fare con l’inglese, la risposta è: niente.

(Leggersi bene la spiegazione che segue e i vari distinguo). Fra i siti in italiano passabili, Lucio cita Wired e Macworld. Anche qui sono perfettamente allineato con le sue osservazioni, e aggiungo che se non avete problemi a leggere l’inglese, la prima cosa da fare è passare agli equivalenti in lingua inglese di quei due siti: Wired.com e Macworld.com.

Per il resto: in italiano non c’è nulla nel mio lettore di feed. Controllo periodicamente qualche blog e seguo volentieri il link occasionale che viene passato da fonte fidata, ma poco altro. Se ci si vuole tenere aggiornati sul mondo Apple e non si conosce l’inglese, meglio seguire un sito come Macworld in italiano che affidarsi alla sezione informatica di quotidiani online come Corriere, Repubblica e affini.

Lo so, tutti hanno l’amico bravo che scrive per la testata tale o il sito talaltro. Può essere, ma pur con tutto il valore che può aggiungere, non è in grado di mantenere costantemente alto il livello qualitativo della testata tale o del sito talaltro. Personalmente cerco di tenere fra le letture quotidiane fonti che offrano una certa qualità sempre e costantemente. Certo, ogni tanto capita l’articolo mal fatto, ma meglio che sia l’eccezione e non la regola. 

Se l’inglese non è un problema, i consigli per le letture si sprecano. Per me, l’accoppiata Macworld.com / Ars Technica è più che sufficiente per stare al passo con il mondo Mac e tecnologico, a livello di notizie ed editoriali (mentre iLounge mi è utile soprattutto per tenermi aggiornato sugli accessori per Mac e dispositivi iOS). A questi aggiungo l’imperdibile Mac OS X Hints. Low End Mac è un ottimo sito, specie per chi, come me, possiede Mac più datati e vuole continuare a tirarne fuori il massimo. Low End Mac contiene moltissimi articoli e risorse a questo scopo, in più a volte è interessante leggere certi articoli di opinione, che invece di focalizzarsi su quanto sia fantastico l’ultimo Mac uscito, provano a mettere le cose un po’ in prospettiva.

Dopo un periodo discendente, MacFixIt è tornato nel mio lettore di feed. A esserne bandito, invece, è Gizmodo, sin dai tempi del famigerato ‘scoop’ sul prototipo di iPhone 4. Non sono persone serie, e non mi piacciono certi metodi di fare giornalismo. Se interessa un sito orientato in particolar modo alla tecnologia portatile e ai nuovi gadget tecnologici, meglio Engadget, anche se ora gli autori migliori sono migrati su This Is My Next, progetto temporaneo in vista del lancio di The Verge a inizio autunno.

Con questi siti nel lettore di feed, più i consigli nell’articolo di Lucio, si arriva a una certa completezza di informazione evitando troppe ripetizioni e sovrapposizioni (una volta, oltre a Macworld USA, seguivo anche il Macworld britannico, ma con una sovrapposizione di notizie del 90% non valeva la pena tenere i due siti nei feed). Ultimi due consigli: se vi interessano discorsi di design, interfacce e usabilità, allora dovete seguire Lukas Mathis (e magari acquistare anche il suo libro, Designed For Use, di recente pubblicazione). Se vi interessa leggere articoli d’opinione di alto livello sull’industria della tecnologia, allora non tralasciate Monday Note, di Jean-Louis Gassée e Frédéric Filloux. Sì, quel Gassée, in Apple negli anni Ottanta, poi fondatore di Be Inc., fra le (molte) altre cose. Il sito viene aggiornato con frequenza settimanale, per cui non c’è timore di accumulare troppi articoli non letti.

How to speed up an aging MacBook with a solid state drive

Handpicked

Nice three-page feature by Ars Technica: How to speed up an aging MacBook with a solid state drive, with good pieces of advice, detailed photos and benchmarks. Particularly interesting since the MacBook being upgraded was an original 2.0 GHz Core Duo (32-bit) white MacBook. 

With the Mercury Extreme Pro 3G installed, the MacBook suddenly seemed like a new machine. Boot times decreased from 33 seconds to just over 20 seconds. Logging into my user account, which includes a few small apps that launch at login as well as a cluttered desktop full of performance-robbing file icons, went from 45 seconds to just 10 seconds. Waking from sleep was nearly instant, whereas I was used to watching a spinning beach ball for as long as ten seconds while the hard drive spun up and paged-in virtual memory.

Operations that are largely CPU bound didn’t seem any different, but anything that hit the disk was suddenly much, much faster. Applications that took several seconds to launch before launched almost instantly. Office and Creative Suite apps launched so fast I could no longer read all the various “Loading…” messages on the splash screen. And Safari could load dozens of previous tabs in seconds instead of what used to seem like minutes.

Repairing RAR archives

Software

A few days ago, I was downloading a series of hefty RAR archives from the server of a former client of mine (I had left a lot of resources there and forgotten to retrieve them after our collaboration ended). The download process was really slow, and after downloading hundreds of megabytes of stuff, I was prepared for a little trip down memory lane, so I started extracting the archives using the always good UnRarX. However, I was immediately greeted with a series of CRC errors. (This article explains what CRC errors are in the context of .zip archives.)

What to do? Re-downloading may have been an option, but the slow speeds weren’t encouraging. A quick search of the Web revealed that I could try to repair the compressed archives. With what, exactly? Well, this old MacRumors Forum thread pointed me in the right direction: going to RarLab and downloading RAR 4.01 for Mac OS X (from this page).

Yes, it’s a command line tool, but nothing too difficult or scary. After downloading it, you’ll have a rarosx‑4.0.1.tar.gz archive in your destination folder. Double-click it, and it’ll create a ‘rar’ folder. Inside this folder you’ll find some text files and two UNIX executables, rar and unrar. The process is now rather simple:

1. Open the Terminal.

2. Drag the rar executable on the Terminal window.

3. You have just executed the rar command. You’ll see a prompt like this:

4. Make sure there’s a space after the cursor. Type r then another space.

5. Go to the Finder, and drag the RAR archive to be repaired on the Terminal window. The Terminal prompt should look like this now:

Richard-XV:~ rick$ /Applications/Utilities/rar/rar r /Users/rick/Downloads/example.rar _

(of course your output will be slightly different. Here, rick is my Home folder and username, the “/Applications/Utilities/rar/” before the rar command is the path where the executable is located, and the “/Users/rick/Downloads/” before the RAR archive is the path where the corrupt archive is located).

6. After the archive name, enter another space, then start typing the path to the destination folder where you want the fixed archive to be saved. To keep things simple, I just entered my Home folder, like this:

Richard-XV:~ rick$ /Applications/Utilities/rar/rar r /Users/rick/Downloads/example.rar /Users/rick/

(Note the spaces. Also note that this should be all on a single line in Terminal.)

7. Hit Return. The repair scan will begin, and then hopefully the repairing process as well. This operation can last seconds or minutes, depending on the size of the archive.

8. If all goes well, you should have a new RAR archive in the folder you specified above. It will have a fixed prefix. In this case, in /Users/rick/, the file fixed.example.rar will be generated.

9. Remember that if you’re repairing a series of split RAR archive parts that need to be joined afterwards, you’ll have to rename the repaired files deleting the fixed prefix in their names.

That’s it. I was able to successfully repair a 526 MB, a 335 MB and a 614 MB RAR archives in a matter of minutes.

The ‘bet on webOS’

Handpicked

Earlier today I was reading this brief piece on This Is My Next, titled Why HP killed its webOS devices, and while what Cathie Lesjak (CFO of HP) claims makes sense, I still fail to grasp the general logic behind HP’s strategy regarding webOS.

From the article:

To put it simply, the TouchPad and webOS devices failed to meet HP’s financial targets and unit sell-through expectations. And HP failed to “position webOS as the clear number two platform for tablets.” According to Cathie, HP’s “bet on webOS” would result in an even larger loss in Q4 if the company continued business as usual […] 

Ms Lesjak adds:

To make this investment a financial success would require significant investments over the next one to two years, creating risk without clear returns. […]

As I said other times, I’m not an analyst, and business strategy is definitely not my field. But simply as an observer, I can’t help wondering what HP was thinking all along since the Palm acquisition, and also why HP decided to acquire Palm in the first place. This ‘bet on webOS’, how did HP expect would pan out? 

They showed the TouchPad, the Veer and the Pre³ at the Think Beyond webOS event in February (and the photos taken by Engadget during their liveblogging well capture the atmosphere of a company which apparently believed in its products); the presentation was entertaining and, I’d say, rather well orchestrated (especially since it heavily borrowed from Apple’s keynotes). They teased the audience only to announce that those three fantastic devices would have been available ‘in the summer’. First mistake. 

The first of those three products to be available was the Veer, launching on AT&T on May 15, arguably the least powerful, attractive or interesting of the three. Second mistake.

Then the TouchPad, finally available on July 1, only in the USA. July and August, from what I’ve observed, are by far the slowest months of the year. Did HP really expect the TouchPad to be an exceptional success during this time of year? Third mistake. 

Many who reviewed the TouchPad pointed out some issues which — from what I’ve heard — have largely been addressed in the latest webOS 3.0.2 update. Now the TouchPad works a bit better, I hear, but it’s too late because the tepid reviews are already out there and sales have been disappointing. Instead of prematurely launching a half-baked tablet in a less than ideal timeframe, why not aim for a September launch of a more refined TouchPad? Fourth mistake.

I reckon this ‘bet on webOS’ has been developed like this: let’s make all the possible false steps to thwart our own products, and hope for the best. 

HP was in a unique position: the only Apple competitor to be in control of both the hardware and the software. It was a path worth risking for despite initial slow sales[1], instead HP just gave up. Without even launching the TouchPad outside of the USA. Without even trying. This, for me, is the most exasperating detail.

Now HP’s webOS VP Stephen DeWitt says that “We are not walking away from webOS” — I’m tempted to quip Well, perhaps it’s better if you just leave webOS alone instead of screwing it up even more, but really, I think that with this move, HP has shown how not serious it has been with webOS, how little it has believed in webOS, not to mention the blow to HP’s credibility as a company. How can you develop for (or buy products of) a company with this kind of throwaway approach?

 


 

  • 1. What do you expect to sell in August, anyway? I don’t know in the States, but here in Europe August is traditionally devoted to holidays — people go away, shops are closed, etc. — and is a really slow month, commercially speaking.

 

Ten months without Flash

Tech Life

At the beginning of November 2010, I removed Flash from all the Macs I use on a daily basis (I documented my going Flash-free here, here & here). The only exception has been the Flash plug-in inside Google Chrome, which I kept on my MacBook Pro for the occasional ‘just in case’ scenario. 

I’ve never been a fan of Flash, yet at first its removal — as opposed to using Flash-blocking tools such as ClickToFlash — seemed a bit excessive. “What if I can’t access certain content on a website because it’s in Flash?”, I thought. My fears didn’t last much, though, and not because I had left a bit of a safety net by not deleting the Flash plug-in inside Chrome. 

I don’t know whether my natural attraction to well-designed websites has always conditioned my browsing, but the fact is that I soon discovered I didn’t have one single full-Flash website in my bookmarks (well, except Typophile). And my browsing, after the Flash purge, has been even more selective. Which means, if I stumble on a Flash site, or on a site that heavily relies on Flash to deliver its contents, services, experience, without giving me any alternative (i.e. offering HTML5 contents after detecting I don’t have Flash installed), then I just browse away. Because let me tell you this: it’s 2011, and if your website still hasn’t got an HTML version to display at least its core contents, or to give me a basic idea of what it’s about, then you’re not worthy of my attention and my time.

In these ten months, I willingly opened a page with Flash contents using Google Chrome only under the following circumstances:

  1. The site, though mostly Flash-free, inexplicably featured essential parts in Flash (such as the Account Login interface);
  2. It was a Flash YouTube video I really really wanted to see (that didn’t happen very often);
  3. It was a Flash website whose link was passed on by a trusted source (read: worth seeing anyway);
  4. I wanted to access and browse Typophile.com.

Nothing else comes to mind. All in all, I very rarely felt compelled to resort to Google Chrome to enjoy something Flash-based and I never felt I was ‘missing out’ or having a somewhat crippled Web experience. The benefits of not having Flash installed (especially on older Macs) greatly outweighed the ‘drawbacks’. I put the word in quotes because, really, what drawbacks? Not being able to look at your super-cool, all-Flash, website? Or animated ads? Come on. 

(Many websites still present an irritating behaviour; they assume you’ll enjoy the Flash version more than the HTML(5) version, so they put Flash all over the place and an Enter HTML site label lost in a corner, in small typography and in such a position you’ll likely overlook the link entirely. If anything, it should be the opposite. Or better, just auto-detect the lack of Flash plug-ins in my browser and switch to HTML(5) on the fly. You’ll be amazed at the amount of sites out there that don’t perform this check.)