Archive for the ‘Tech Industry’ Category

The Go Programming Language

Wednesday, November 11th, 2009

The Go Programming Language.

I’m glad to see this; there has been too little innovation on the system programming language front. I do like C, though I’ve become more conscious of its faults since I learned it (*mumble*) years ago.

I’m a little disappointed that Google didn’t throw its weight behind the other major contender in this category, The D Programming Language. They have to have considered it; I wonder if their decision not to use it involved technical considerations, licensing considerations, or a little of both.

The write-up on TechCrunch is light on technical details, and the comments are hilariously clueless: paranoiacs spluttering that Google is taking over the world, people who’ve never written a line of code in their lives declaring it an instant failure, and Johnny One-Note programmers insisting that this will never take the place of PHP, or C#, or JavaScript, or whatever their One True Language is, shrieking with terror at the thought of learning something new.

For myself, I like what I’ve read so far about Go. It looks not much more complex than C (and waaaay less complex than C++), with a more modern, more streamlined feel. I like the idea of trying to head off the formatting wars by including a canonical pretty-printer in the core tool set (though I wish they had standardized on spaces instead of tabs for indentation). Requiring braces around blocks is good: it heads off a common error in C/C++ coding, and there shouldn’t be any ‘friction’ in changing a one-line block into a multi-line block. I liked structural equivalence of types when I first encountered it in Modula-3, and the Go concept of interfaces is nicely reminiscent of that. I don’t miss the whole object oriented feature list (encapsulation, polymorphism, inheritance, and dynamic binding), so long as modularity and information hiding are supported. And garbage collection is a huge win, so long as it can be done efficiently and without causing the program to stutter.

All in all, very interesting, and a worthy challenger to D as a 21st-century systems programming language.

Go vs Go!

Wednesday, November 11th, 2009

Go! is a concurrent programming language, first publicly documented by Keith Clark and Francis McCabe in 2003 [1]. It is oriented to the needs of programming secure, production quality, agent based applications. It is multi-threaded, strongly typed and higher order (in the functional programming sense).

Google’s new ‘Go’ programming language, the very day it is announced, is already embroiled in a naming controversy.

Personally, I think they should contact the makers of LabVIEW, and see if they can acquire the naming rights for the G programming language.

Posted via web from Kevination

The One Where I Say Something Nice About .NET

Friday, October 9th, 2009

I’m working my way through  Pro ASP.NET MVC Framework, by Steven Sanderson, published by Apress. So far, I like it, for values of ‘it’ of both the book and the framework.

The book — well, the reviews on Amazon were glowing, and they’re basically right: clear prose style, ideas well expressed, and enough critique of other Microsoft technologies that you can tell it’s not a Microsoft Press title.

The framework … is interesting. It mostly abandons the ASP.NET model of server-side controls, postbacks, and viewstate in favor of plain HTML and CSS. (Though there are still advantages to using their HTML helper functions rather than coding up raw HTML yourself.) For pity’s sake, they even make jQuery available for your AJAX hacking pleasure.

What has always bothered me about “classic” ASP.NET was that it seemed to be an attempt to transplant the VB/WebForms style of development — drag-and-drop controls, a low-level event loop — onto the web. It’s a layer of abstraction over the web in an attempt to hide that fact that it is the web.

And it shows in terms of performance. Outside of low-latency intranets, the underlying architecture doesn’t support the chatty postback/viewstate implementation needed to emulate a desktop GUI event loop.

ASP.NET MVC, in contrast, feels like a web-native architecture. It’s designed around the strengths and limitations of HTTP, rather than fighting against it.

On top of that, it encourages the strong separation of concerns implied by ‘MVC’; it nudges the developer towards unit testing and test-driven development; and with the source code placed under an OSI-approved license, it represents a step by Microsoft into the world of Open Source.

All in all, I think ASP.NET MVC is quite cool.

Whimsley: Online Monoculture and the End of the Niche

Sunday, July 5th, 2009

Internet sharing mechanisms such as YouTube and Google PageRank, which distil the clicks of millions of people into recommendations, may also be promoting an online monoculture. Even word of mouth recommendations such as blogging links may exert a homogenizing pressure and lead to an online culture that is less democratic and less equitable, than offline culture.

Whenever I make these claims someone says “Well I use Netflix and it’s shown me all kinds of films I didn’t know about before. It’s broadened my experience, so that’s an increase in diversity.” And someone else points to the latest viral home video on YouTube as evidence of niche success.

So this post explains why your gut feel is wrong.

via Whimsley: Online Monoculture and the End of the Niche.

Too Many Gadgets?

Thursday, February 26th, 2009

There’s no such thing, right? Well, if you have to carry them all around all day, maybe there is such a thing as too many.

It seems I am now “on call”. Which means I have to tote around the one and only IT-approved model of smartphone, the Blackberry. Which means I am now saddled with two slightly-too-big devices, being already the proud owner of T-Mobile G1 “GooglePhone”.

If this had happened half a year ago, when I was toting around the T-Mobile SDA stupidphone, I’d have counted the Blackberry as a blessing; that thing was an abomination. But now I’m feeling just a little too connected.

You Say Netbook, I Say Smartphone

Wednesday, October 29th, 2008

According to CNET, HP is diving headfirst into the Netbook market. The interesting part of the article, though, is not so much about HP, as about netbooks in general, and how they are being marketed in Europe and Asia:

It’s a dramatic increase, and the difference is all coming out of Europe, the Middle East, and Africa (EMEA), where Asus and Acer have been incredibly aggressive about their Netbooks, the Eee PC and Aspire One, respectively. Of the 10.9 million units that are estimated to ship worldwide by the end of 2008, 8.1 million will go to EMEA, says IDC.

Acer and Asus have done well in the region, as evidenced by Acer’s quick rise to the top of the portable PC market there. But they’ve been aided by local telecom companies, who are subsidizing Netbooks in exchange for a signed wireless service contract. It’s a model that in the past few months has thrived in Europe.

Dell signed up Vodafone for this kind of deal on its Netbook, the Inspiron Mini 9 in September, but HP’s mostly been on the sidelines in this regard, and representatives for the company haven’t indicated if a similar deal with wireless providers are in the works.

Wireless service contract to subsidize a Linux-based device optimized for mobile Internet access. Other than the physical size of the device, how is this different from Android (and, Linux notwithstanding, the iPhone)?

At some point in the near future, somebody is going to put Android on a netbook-class device, and the shape of the future of client computing will become clearly visible. And the day that happens is the day that Microsoft’s desktop monopoly will be truly broken.

Yahoo! (Powered by Microsoft)

Tuesday, February 5th, 2008

What do you get when you cross Microsoft and Yahoo?

Microsoft.

Over at TechCrunch, Duncan Riley makes the case that people leery of the coming Microsoft/Yahoo merger are being unreasonable, and need to start thinking of Google, not Microsoft, as the Evil Empire.

The Microsoft is evil meme is alive and well this week as many digest Microsoft’s $44.6 billion takeover offer for Yahoo. There’s Flickr users protesting, talk of Yahoo teaming up with Google to block Microsoft’s bid, and general Microsoft is bad sentiment everywhere, even from Google itself. While Microsoft acquiring Yahoo may not provide the ultimate in happy endings to many, it’s really not as bad as some would have you believe.

My own objection is not so much because Microsoft is evil (and we’ll set aside for the moment whether Microsoft is evil). Rather, it’s over the fact that Microsoft is a desktop software company. Up to now, Yahoo has been a pure Internet company, like Google. They have not had any reason to care what platform its users run; they simply don’t have a horse in that race.

But a combined ‘MicroHoo’ has a vested interest in what software is running at the other end of the pipe. Even if the people running the ‘Yahoo Division’ say all the right things, there will always be a temptation for the Microsoft brass to use the Yahoo properties as instruments with which to promote Microsoft desktop software. That should be a concern for anyone who uses non-Microsoft alternatives to Microsoft products — not just Mac and Linux users, but users of Firefox and Opera, iTunes and Winamp.

Will you have to use IE to access del.icio.us or Yahoo Finanace? Will you have to use Windows Media Player to access Yahoo’s streaming media? Will you have to use Visual Studio to develop Yahoo plug-ins? Even if the answer to all of these questions is ‘No’ now, can anyone promise it will stay that way in the future? Even if Microsoft goes into debt with this deal, and has to justify its purchase to the stockholders, can we be sure that management won’t see this as a way to monetize their new properties?

And I don’t buy the parallel being drawn by some between Google’s domination of the net and Microsoft’s domination of the desktop. Microsoft gained its position by leveraging its relationship with IBM, and muscling PC vendors into exclusive deals, precluding them from offering pre-installed alternatives to Windows. Google, by contrast, is a textbook example of a natural monopoly, exactly the kind of company we should want to see more of: they built a better mousetrap, and the world beat a path to their door.

In practical terms, the only real stumbling block to this deal may be EU intervention, and even there, Microsoft can make a compelling case that the merger will increase rather than decrease competition, so I don’t see that as likely. So the deal is likely to go ahead. I just don’t see it as cause to celebrate.

Privacy in a Social Network, and Other Oxymorons

Friday, January 4th, 2008

Much virtual ink has been spilled over the past day about Robert Scoble’s banishment from Facebook (temporary, it turns out) and the reasons for it, and whether he deserved it. One point of view, espoused by no less than Jeff Jarvis, is that the contents of Scoble’s Facebook address book should be kept in Facebook, not exported to a system of Scoble’s choosing. It violates one’s privacy, apparently.

This is a ludicrously naive position.

Facebook and others may say they will protect your data as if it were their own. They are lying. To some of us, this lie was transparent from the start; but if you still believed the lie after the Beacon fiasco, and stories of information leaks from even the most secure government agencies, then you are a fool.

Once you put information in Facebook, or any other website, and allow others to access it, it is out there, no take-backs. If you want it kept private, then keep it private; and putting it on the web and letting other people see it is not “keeping it private”.

Consider this: Scoble did what he did in broad daylight, blogging about it once he had permission to do so. And he did it with apparently noble intentions, willing to sacrifice his Facebook account for the cause of data portability. (At least, that’s how he presents it after the fact, though I have no reason to doubt him.) And he did it badly; his activity was detected because the Plaxo script was too fast; the simple expedient of slowing it down and adding a little randomness might have allowed him to evade detection.

Now, do you really think the Plaxo developers were the first ones to come up with this idea? Do you think maybe someone else might be doing exactly the same thing, but more quietly, more competently, and with less noble intentions? In view of that, do you really think it’s even theoretically possible for your Facebook data to remain protected?

Do not count on Facebook to do your information security for you; they can’t do it, even if they sincerely mean to. (And are you really sure they do mean to? No matter how much revenue it would cost them?) If you want privacy, you have to manage it yourself. If you don’t want your data out there, then don’t put it out there. Be judicious in what information you supply to the social network; and consider salting it with disinformation.

That, or stop caring so much about privacy: embrace the Transparent Society, learn to stop worrying and love the social. Seriously, that’s a perfectly legitimate stance; privacy is optional. Or find your own personal balance between hiding everything and revealing everything.

But don’t fool yourself into thinking that you can escape the fundamental tension between social networking and privacy.

One More Data Point

Wednesday, December 12th, 2007

Safari Books Online is a service by technical publisher O’Reilly and Associates, that allows subscribers to their service to access their books, and those of several other publishers, online. (Highly recommended, BTW.)

Anyway, their front page lists the most popular books on their service. For as long as I can remember, the top book was David Flanagan’s Java in a Nutshell; but today, it has been displaced by JavaScript, the Definitive Guide (also by Flanagan, as it happens).

It’s notable mainly in support of Steve Yegge’s proposition that JavaScript is the Next Big Language. It is certainly popping up everywhere, and it is, for now, the only Apple-approved method of developing for the iPhone.

UPDATE: Okay, now both of Flanagan’s books have been displaced by a C# book. Please forget I said anything.  :)

One Revolution Per Child

Thursday, November 29th, 2007

One Revolution Per Child

The OLPC project is laudable even on the basis of its stated goals; but I think there’s more going on here. As this article describes, the OLPC device is by its nature subversive. But why assume that that subversion will only take place in the underdeveloped countries that are the ostensible market?

After all, I want one. Don’t you? And if it really will just cost $100 — or even a smidge more — that makes it almost an impulse buy, at least as gadgets go. And what will happen when thousands of these are in the hands of gadget-fans here in the US, and elsewhere in the developed world?

Revolution begins at home.

Update: the Revolution marches forward. Applications as online services (e.g., Zoho, Google Apps) dovetail nicely with this trend. I remain convinced that Google Android is yet another manifestation of this, approaching the same destination by a different route.