Pc in pericolo con i processori x86, “difettosi” per 18 anni – ictBusiness.it

Come dire: ah, bello, ottimo!

Un difetto introdotto nell’architettura x86 nel 1997 e passato inosservato fino a oggi permette di realizzare attacchi al livello del firmware, particolarmente insidiosi. Lo ha svelato un ricercatore del Battelle Memorial Institute, con un test realizzato su chip Intel.

Sorgente: Pc in pericolo con i processori x86, “difettosi” per 18 anni – ictBusiness.it

C’era già OsmAnd!

Screenshot di OsdAnd
Screenshot di OsdAnd

Leggo su Marco’s Box che Marble Maps – applicazione KDE per le mappe – sbarca su Android e porta la navigazione con le mappe di OpenStreetMap.

Bellissimo, gli auguro ogni bene ed imperituro successo ma…. su Android come software libero per la navigazione basato su OpenStreetMap c’è – da anni! – OsmAnd – Offline Mobile Maps and Navigation.

E la uso con soddisfazione – molta soddisfazione – da un paio d’anni. Sorgenti compresi.

 

Both aren’t “liberi”

1000px-Chromium_11_Logo.svgChrome – one of the most widespread browser – is proprietary software with Chromium being is “open source” base.

According to Debian #Debian Bug report logs for “786909 – chromium: unconditionally downloads binary blob” Chromium even when built from source code still try to inject binary blobs – proprietary software – on your system without notifying the owner of the system where it runs. So we cannot really trust it anymore, we shouldn’t consider Chromium as “software libero” (or libre or Free-as-in-freedom-software)

That’s not a good.

 

Fat, obese npm

npm-huge-allocationI do understand that today designs tend to put less emphasis  on conservative memory usage but that’s pretty outrageous. A simple search into node’s package manager ate one gigabyte and half of main memory having to deal with a simple question like

npm find foobar

more speficically GNU time told me that it took 48 seconds and 1799Mb of resident memory to scan thorugh a local list of the 169.312 total packages available from npmjs.com.

Apt, the almighty Debian package manager consumed a mere 99 MegaBytes to search into package names and descriptions throught more than an hundred thousands packages (107819) which are usually far beefier that javascript modules.

That’s more than eighteen times.

Javascript, your librarian is obese.