Quick Non-Review Wall of text on the OnePlus One

June 20, 2014 in tech

Let’s put the obvious out first: I’m related to the CM team, as a very small-time official maintainer of a device now deprecated (sunfire) because of a lack of support from upstream. So, to a certain extent, you all will jump on the bandwagon that is the OMG THIS DUDE IS SO PARTIAL TOWARDS CYANOGEN IT’S UNREAL and all of that bullshit. I expect it, and to a certain level I actually welcome it; it will keep me humble.

So, it is with gleeful excitement and a small bit of pride that I welcomed the announcement of the OnePlus’s first-ever official product, the One, a Cyanogen-powered Android device. To see +Steve Kondik ‘s brainchild in a commercial device, complete with out-of-the-box Google Apps instead of having to acquire said applications through funny means is no small feat; to that, I tip my hat to the +Cyanogen Inc. staff.

A glee level only equivalent to the one when I got my 2013 Google Interviews would be needed to describe the moment that I received, and subsequently insta-ordered within 5 minutes, my Sandstone Black 64gb OnePlus One order voucher. Come on, that badass of a device, at that price, with those specs? I NEED IT. I just NEED it.

And in retrospect, after 3 hours with the thing? I was mostly right, but in some aspects that are sadly core to my device usage… I might actually be just wrong enough to cast doubt.

Device

The device itself is, let’s be honest, a slab of sexy. With a back I can only describe as “Nexus One meets soft-touch sandpaper [in a good way]”, this device holds good in your hand, is decent, and is operable. Then, you’d be hard-pressed to find a lack of standard stuff. Microphones galore, speakers up the wazoo, cameras where ya need ‘em, the power button placed just where it needs to be for one-handed operation, the device itself is neither the Next Big Thing nor a contender for the Blast-from-the-Past-of-the-year Razzie (hello Canada). The screen is expectedly decent, the camera too, and in the end, it’s a well-rounded piece of awesome. The device itself is good and I won’t really mess with the fact that it. just. works.

Software

This is the part where I expect each and all of you to say YOU’VE GOT A HARD-ON FOR CYANOGEN EVERYTHING! YOU MOD RANDOM DEVICES FOR BREAKFAST AND MOD LAPTOPS AT 30K FEET IN THE AIR. And you know what? You’re right. I’ve always preferred developer-level customisation and “fun things” to “Stock Experience”, except for the Nexus level starting with 4.3; I never really felt the absolute NEED to mod devices starting with 4.4. The only reason I modded my hammerhead was to acquire root so I can debug an NDK project I’m working on more easily than fixing a REAL great mess of a build output with Gradle. Fact is, there was a time when I modded devices before actually eating Nutella in the morning, and to an extent, I’d still do it.

So you will not be surprised when I say that the software in it is awesome. Cool over-the-top customisability, very decent out-of-the-box user experience, and overall badass simple-mode-goes-geek-level when I want it. I simply will not sing the praises of this, only because I’d sound even MORE partial to them. And I’m right to do this, because I’ll sound like a freaking fanboy… at least more than right now.

The Bad

So how come this. How come there’s some bad? Is there REALLY something bad with this device? It would seem so, as after 3 hours with the device, there are two things that get to me in a bad way, and it’s in such a “bad way” that I actually would have considered NOT getting the device in the first place. Those two points are at the very least completely personal opinions and peeves related to my tastes, so the two are YMMVs. These points are only my experience, and for some people like +Arthur Brownlee IV and +Chris Sewell it would actually be a SELLING POINT; dem freaking giants.

First: the device is large. Like, freaking large. It’s actually near-phablet, and I actually loathe the Note series not because they’re Samsungs (and that’d be enough for me to hate ‘em), but because they’re phablets. I nearly pulled the trigger on a Sony Z Ultra once only because it was a Z device that could have replaced my aging Nexus 7 first-gen. So, basically, it’s big. I can operate the One with one hand, but just barely, and I have pianist fingers; it’s too freaking big!

Second: this device has a presence in hand that I just don’t get. I held a Z1 Compact in my hands, and to be fairly honest, the Z1c has a better presence, a better “ohai user, lemme help you with stuff” feeling than the OnePlus One. The 1+1 is more like “sup brah, use me” directly, sort of like an in your face USE ME image… That leads to the real core of the feel: the heft. Call me classic, but I like that my personal devices have a size and weight that are not necessarily proportional, but arranged in such a way that they validate the existence of the device. Imagine that you would have one device that had its weight distributed equally all over, and one that had its weight distributed with the “core” of its presence in your hand, like it was saying “Hello user, I am on you” instead of “surfing on your hand and in the air NO HANDS ‘MA!”. The images make no sense, but if you imagine the thing, it starts making sense.

The End, for now

In the end, those last two points have been a peeve of mine for the last devices. I preferred the N4 to the N5 in terms of heft and device feel, and it is sadly a renewed experience with the OnePlus One; but as I said, that bad experience is limited to only two factors that can actually steer others’ decision towards actually buying one. Provided nothing changes about my current impressions, I know I’ll be recommending the device to whomever wants a cheap, awesome performer that comes with a near-AOSP user experience enhanced with customisation up the wazoo and a really enjoyable screen, and to giants. For people that like a device to have a more defined and restrained, but self-explanatory, presence in hand, this may not be the best of choices.

Are we worthy of our tech?

May 10, 2013 in humanity / foolishness, tech

We are immature, uncaring children.

In a time of constant technological evolution, as far as the technology-based geekness nature goes, it is actually hard not to be. Every week, some minuscule but pretty important advancement gets plastered all over as a Big ThingTM. Every other week, some game gets announced, or some graphics hardware that’s going to revolutionize display tech or be able to process ungodly amounts of data thanks to GPGPU coding and processor technology refinements gets either leaked, announced, or released on the market. And it was not long ago that every other month was essentially seeing one, if not two, new smartphones on the market. So, essentially, over the last few years, we technology geeks were nothing less than spoiled by the market. Some would say that it’s for the better, that this helps the market grow and lowers the prices. While this last point can be argued, it is nonetheless valid.

I’m here today to argue that this extremely fast-paced evolution amplified a perverse aspect of humanity. I am talking, of course, of instant gratification, something that everyone can notice in their daily activities, on the street, in their children, in themselves, basically everywhere. New products using new technologies have been released at such a pace, and in such a way as to gratify us of their arrival, that they end up blinding us to a fairly simple reality: such tools are no more than, well, tools, and are not an end unto themselves; rather, they are means to an end, mere tools to accomplish a task. I personally fear that, as users, many of us have lost that sight, and care only for the latest gadget, and nevermind the multiple usages that the device could serve; the new things are good enough to keep us entertained.

Some will argue that this is kind of the point of marketing and product releases, and I will admit that it’s true. Essentially, the multiple competitors are doing their job and doing it rather well. It is thus on us users that the responsibility of caring beyond the toy lies, and it is this specific point that leaves me worried right now, especially since, from my point of view, we think more of the toys and less of what they can do for us humans, at any stage of our personal and physiological growth. Let me give you a simple, yet revealing, example.

My good friend +Erica Joy made me aware that +Sergey Brin, one of Google’s founders, has reason to believe he may end up with Parkinsons’ disease. While this is in and of itself pretty sad to hear, it also sheds a whole new light, a completely unseen dimension, on potential uses of some Google X projects [reminder: Google X is the Skunkworks Department of the company, so to speak]. For example, the driverless car would allow a Parkinsons-afflicted person to still be independent in his or her transportation. The Glass project could be used as an easy interface with people and many functions normally requiring hand input, for example shooting a video or taking a picture, become less of a task for said Parkinsons-afflicted being.

That point of view took me by surprise, to be honest. Not only had Erica opened my eyes to a whole other dimension that I normally care about only in passing, but it adds a whole new layer of possibilities, of potential innovation, of ideas, to nearly everything that has a CPU and a display. I personally couldn’t forgive myself for what I perceive as a crime against our own kin: forgetting that we can help people with disabilities with all of this now accessible technologies. Through something I like to call the Connected Lifestyle has emerged a whole subset of potential uses for technology, uses that may not be obvious at first sight, but that, when you just stop for a second and think, they become apparent. They become so simple that you think “hey, why doesn’t this exist yet?”

As geeks, we like the new shiny. But I am saddened to say that I had only thought of the above points in passing before, never truly seeing new developments, new technologies, for what they can accomplish instead of what they are and can easily be. Some new uses of tech are well-hidden, or sometimes they’re total flukes, but I’m wondering if some really new ways of use, some new approaches, aren’t discarded only on the grounds of “people won’t know what this is and won’t like it”. And, to be honest, I don’t blame the companies for thinking that; we like the shiny and are so vocal about wanting new shiny, new tech, new everything, bigger/faster/prettier devices, that they themselves feel they can “play it safe” to satisfy both their hunger for money and our hunger for technology.

So maybe it’s time to grow up.

Programmer by day, mobility enthusiast, code monkey and writer by night, Renaud Lepage isn’t your typical geek from Canada. You can reach him at +Renaud Lepage.

This editorial post is licensed under the CC-BY-SA 2.5 CA Creative Commons license.

Republication d’une opinion écrite sur Google+ [sauce critique]

April 25, 2013 in google+, tech

Je réfère ici au fil de discussion de l’événement “Le vol d’identité, loin d’être un cadeau!”, le premier d’une série qui, je l’espère, sera longue et intéressante. L’événement a été organisé par +Desjardins, et je trouve que c’est un excellent moyen d’aller chercher du capital-sympathie chez les utilisateurs de Google+, clients ou pas de +Desjardins, en plus d’aider à l’éducation de ces derniers quant à certains dangers reliés à l’économie personnelle.

+Dominic Desbiens parlait de dispositifs de paiment NFC. Le monde ne le sait peut-être pas, mais toutes les machines paypass/paywave prennent NFC; j’ai testé avec une MC Paypass et +Google Wallet, et ils n’ont jamais changé la machine et pourtant j’utilise VISA PayWave. C’est juste que le protectionnisme gouvernemental et les banques refusent de laisser +Google Wallet arriver au Canada. J’aimerais vraiment que +Desjardins fasse une alliance tactique avec +Google Wallet pour emmener la technologie au Québec, au contraire de CIBC/Tim Hortons/RIM qui à mon sens agissent en bébés sans vergogne et en corporatistes atteints du syndrome du Not-Invented-Here.

En réponse au paragraphe ci-haut, +Dominic Desbiens se demandait quelle solution était la meilleure. En fait, aucune n’existe encore! On en est aux balbutiments du portefeuille NFC! Le problème, c’est que personne ne veut embarquer sur la technologie NFC, ou bien par peur de la tâche à faire, ou bien par “Allergie aux Technologies Non-Internes” [tiens, j'ai traduit NIH: ATNI]. +Google Wallet est une bonne implémentation, la solution MasterCard en est une autre, CIBC/RIM en est encore une autre [protectionniste], etc.

Au final, une alliance +Desjardins/+Google Wallet augmenterait le “capital de sympathie” des geeks envers +Desjardins et forcerait la main aux autres banques et coopératives; ils n’auraient d’autres choix que d’emboîter le pas, vu que les paiments NFC se feraient sur de multiples appareils Android avec NFC/secure. Avec +Google Wallet, c’est simple, BEAUCOUP d’appareils Android récents pourraient d’ores et déjà payer. On parle ici des Nexus S, Galaxy et 4 (un Nexus de 2½ ans d’âge peut payer! Imaginez!), du +HTC Amaze [sur +Vidéotron], du +HTC One, du Galaxy S III [partout] et de plusieurs autres, fort probablement.

/chiâlageRespectueux

Événement disponible ici: https://plus.google.com/events/cg5tkufnmfohkc0pukt12tcke90

Hoot doesn’t work

February 23, 2013 in Uncategorized

Why doesn’t hootsuite give a hoot about my crossposting? DARN IT ALL

Hootsuite crosspost test, 3rd

February 23, 2013 in Uncategorized

no idea if it’s even going to werk.

Of games and applications, programming, patches, progress and scale

November 19, 2012 in tech

tl;dr at the end. I’m a douche and I like when people read.

My bro-in-law [to be] +Danick Massicotte got his deluxe WiiU unit today, as everyone who knows him would expect. New console, nice packaging and all, and the internal software is a nice evolution that integrates elements of the DSi and the original Wii software in a very nice way. But as soon as he plugged it in and started everything, before he could even play his games, he got hit with what we all came to know as an inevitable thing on the Xbox360 and the PlayStation 3.

Patches

More specifically, the WiiU was hit by a global, gigantic update post-launch, that basically brought it online. While I don’t doubt that Nintendo had their reaons to not send their console “blueprint” to the factories and foundries without the online-enabled internal software, instead putting in an offline-but-feature-complete software stack, it was nonetheless a bit peeving to be hit with that at the beginning of the console experience. And then it got me thinking: why do we even need patches? Wasn’t it more simple “in our youth”, when consoles were one-make-don’t-break, never updated, always stable? And then the programmer in me took over, and there’s a simple, good reason why we now have patches for console systems the same way we have patches for our computers, and the same logic applies to games as well [sometimes games can be hit with multiple patches throughout their shelf life].

The scale of it is too damned big
[cue Jimmy McMillan]

And it’s simple as that. Back then, with our trusty 1st-gen Famicoms and MegaDrives, SuperFamicoms, Genesis and even that Saturn thing, console system software was way less complex to build, test and be assured of its stability. The systems were required infinitely less of, and we can all agree on that, though there were a couple of exceptions: the SuperFamicom, for example, got a Satellite Uplink, but that was an addon unit and was tested independantly. Fact is, “in that time”, the software was working with things on a WAY smaller scale than now. These days, a game must precalculate the equivalent of a 25KM radius of “environment”, preload resources differently from near to far, manage physics, manage line of sight, 3D, a network uplink, recalculate lighting every split-second, and on top of that, there’s evolved state machines called AI that have to run in the background. All of this must also be near-recalculated every nanosecond in order to guarantee the best gaming experience there is. Know what it was in the good ol’ days?

Move right, jump and shoot.

Though the complexity back then was of coding games in near assembly all the time time, which would make any random person crazy, it was still, architecturally speaking, less complex, as the programmer/s had to manage way less different systems: framebuffer, input and sound. BOOM. Way less chance of a game having bugs. A game could still have a couple of bugs, but it was, in hindsight, proportionally less.

So, in essence, what I’m trying to say here is that, in the case of great and good games and in the case of console systems, updates are far from an annoyance and a pain. They’re a must.

Though, in the case of crappy games, no quantity of patching will fix the suck.