Become a fan of Slashdot on Facebook


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:Something It Isn't (Score 1) 775

by Nbrevu (#43838317) Attached to: Google Glass: What's With All the Hate?

Very different, actually, and it's a matter of degree. What google glass introduces is a constant surveillance, eerily close to the third episode of Black Mirror.

That said, I'd love it if everyone stopped permanently carrying cameras (this includes smartphones) with themselves, although I may be relatively alone about that.

Comment: Re:ActionScript + Python + Ruby (Score 1) 312

by Nbrevu (#43792737) Attached to: Dart Is Not the Language You Think It Is

I don't know about the others, but for me, it's like muscle memory after a few years of C++.

First, you have to take into account that not everything that accepts "++" is a number. It may be anything, and in particular it may be an iterator, which is very common.

Now, you have to consider that "++variable" is not the same as "variable++"; they are two distinct operations with their own behaviour. So, "++variable" increments in-place, but "variable++" returns an anonymous copy of "variable" and then increments "variable". It doesn't seem like a big deal when you're doing a standalone increment (i.e., not assigning "++variable" or "variable++" to a result, which has different behaviours because the result won't be incremented in the second case), and indeed the result is the same, but the preincrement doesn't create a copy, while the postincrement does. So, preincrement is more efficient (especially if the copy is not trivial, if it's inside a loop, or both. The second case is the most frequent). It's a micro-optimization (which means that you won't speed up your code by 200% by doing this) and many compilers will probably do the fastest thing if you use postincrement and do not assign the result, but it doesn't have any downside. And, like I said in the first sentence, it becomes muscle memory quickly. I've ended up doing it in all C-like languages, but I'm not sure if there are differences in anything that isn't C++. I certainly hope there isn't any downside.

Comment: Re:"Importing" labor? (Score 1) 293

Wrong. You destroy businesses by destroying their customer base, which you attain by ridiculous race-to-the-bottom labour laws that erase their purchasing power. We've seen it first hand, here in southern Europe.

There is a heavy demand problem, and you won't solve it by worsening workers' conditions.

Comment: Re:"Learning curve" is missing the point. (Score 1) 536

by Nbrevu (#43663283) Attached to: Microsoft Prepares Rethink On Windows 8

Not really, Unity it's more like a compromise between desktop and touch. The problem is that it's optimal for none of them: it's too touch-y for desktop, and too desktop-y for touch, so I'd prefer a more 100% desktop oriented for my desktop, and the same for touch interfaces. I understand the appealing of having a common "universal" interface, but I still prefer a specialization, using the best tool for each machine.

Still far better than the Win8 approach of trying to push a heavily touch-center UI for desktops (even if the desktop UI is still present).

Comment: Re:mature response to a corporate stumble (Score 1) 536

by Nbrevu (#43663137) Attached to: Microsoft Prepares Rethink On Windows 8

You are missing a huge point. It's not that users don't want to get rid of XP, it's that they don't want to get rid of the XP UI. Make it so newer systems look identical to Windows XP and people will happily upgrade (by the way, Classic Shell is not identical enough for a lot of people), but start changing things and users will start to get pissed off about changing their workflow, re-learning where to find whatever they need and having to get accustomed to the new look of certain components. I know a few cases of people with dual boot that still use Win7 only when strictly needed (in most cases, because of compatibility problems), going back to XP for the everyday use. Some of them are actual power users (baking their own Windows install CDs with their own preferred bundle of applications and preset configuration, for example).

Changes in UI are a big point of friction, probably even more than susceptibility to malware, performance problems or even compatilbility (with both software and hardware, although this last one is sometimes a good reason to keep your old OS). Well-known example: for a lot of people, and this one includes me, Windows 7's Start Menu was already a step in the wrong direction, and many of us still think so. Go figure.

Comment: Awful idea (Score 1) 381

I don't like smartphones and I like to erect a metaphorical concrete wall between my job and my life. So obviously I hope this idea doesn't get far, and in fact I cannot see how could any employee like it.

I'd go as far as not to let my employer know my phone number, so they can't call me: after all, if it's worktime, I'm at the office, so no phone call needed. Do you want to call me on a weekend because something happened to the server? I won't even try to charge a million, I just won't do it.

You are lost in the Swamps of Despair.