Filed under News

Governments and Their People

The intertubes are full of the news of the revolution in Egypt and while I’m glad to see millions of people embracing their freedom and responsibilities as citzens, their is one trend I find a bit worrying. I’ve seen the thought “People should not be afraid of their governments, governments should be afraid of their people” and I find that a bit disconcerting.

V for Vendetta

The line is from V for Vendetta. I think it’s an awesome movie that everyone should watch at least once. V is a very interesting character but it’s worth remembering that he is ultimately a character in a book (and movie). “Governments should be afraid of their people” is something that you would expect from someone in his position, with his past and his mission. But it is not something that should be taken as the working principle for concerned citizens.

 

Dictatorships and totalitarian regimes are bad, sure. But in a properly functioning democracy the government and the people are one and the same. Let’s not forget that the point of democracy is to have a government of the people, by the people, for the people. Government officers are stewards entrusted with protecting the interests and rights of their fellows. Their duty is to listen to their people and execute their will. They provide security, direction and cohesion, but not at the cost of liberty.

People should not be afraid of their governments, but governments should not be afraid of their people either. Fear is a primitive emotion from a time when we getting chased down and eaten by a bigger, meaner animal was a clear and present danger. Fear’s main purpose is to override everything else: including both other emotions and logic. You cannot establish a working, sustainable government on the basis of fear on any side. There must be balances and checks on the power of the government, but the atmosphere and general feelings must be of respect and cooperation, not fear and suspicion.

Democracy is based on the idea of “We, the people” not on the basis of “rulers vs. the ruled”. As citizens of the free nations of Earth, let’s keep that in mind. Freedom, Forever!

Tagged , , , ,

The Bytebaker is changing

The Bytebaker is a good few years old now and through most of that time it’s been a purely technology oriented blog. The readership has grown steadily, but I don’t take tons of readers and the ones that I do get are generally concentrated on a few posts (which are mostly Python related). Of late I’ve been giving some thought to what direction I want to take this blog in the near future.

There is a part of me that wants to keep The Bytebaker purely technology related. On one level it makes sense: it’s one website and it should have a concrete theme so that people who come here regularly know what to expect and find. But on the other hand, it’s written by one person — me, and I have more than one interest. I love music and movies and I’m trying to get back into reading regularly and I have thoughts about them that I would really like to share sometimes. But a lot of the time I either don’t share at all or it gets fragmented between here, my Tumblr blog or my static website. I’ve come to learn that maintaining multiple websites, like maintaining multiple computers, is hard and not something to be taken lightly.

With that in mind I thought it was a good idea to take a few steps and think about what I wanted to do with the Bytebaker and my other blogs and websites. In some ways I’ve been thinking about the path taken by Marco Arment and John Gruber. Their websites are technology-oriented, but also reflects their own personalities too. I think it’s a good format and something that would work well for me, because as I said, I think a lot about tech but it’s not all I think about.

However, I don’t want to just have a blog, at least not right now. I want to keep a plain static website for a number of reasons. I want a place where I can point people to if they want to know just about me, not my writing or thoughts. It’s a place to show off my projects and my writing which don’t fall nicely into a blog format. This involves papers I write for classes and things like short stories and poems that I’ve written. The blog is a great format, but it doesn’t fit everything. Since I plan on being an academic for a few more years, I also want someplace to put papers I’ve publish and things (like a resume) that would only be of interest to a small audience. I also want to keep experimenting with CSS and HTML5 without breaking my blog and a static site is the easiest way to do that.

Luckily I don’t have to decide between the two: I can have both. I already have a blog with a decent readership right here and I have a static site which is already a showcase of my projects and other writing. And the tumblelog I won’t miss much. For the time being I’m happy with just merging the Bytebaker with my tumblelog and getting a bit looser in the type of things I allow here. I’m going to rethink the categories here to reflect that. I’m changing the theme to the brighter, spacier DePo Square which is very well suited to the things I have in mind. No I’m not actually moving anything over because I don’t think there is anything really of that importance there right now. As for the website, I’m keeping it the way it is since I don’t have the time to rethink it right now. But in the end I want to be something like Professor Karl Stolley or Scott Chacon’s website: an overview of who I am with excerpts of my online activities.

I’m hoping that this change will bring with it shorter, more rapid posts offer a wider range of subjects (though probably still dealing with tech). Personally I hope it’ll remove the blocks I feel when I want to post something but don’t know where. It’s been a while since I’ve had a single unified blog and I’m rather excited to see how things turn out.

Tagged , ,

The Web is for Documents: Part II

In my last post I talked about my dilemma regarding webapps: they’re wonderful and they’re letting us do amazing things, but in the effort to become a general-purpose app platform webapps seem to be struggling against the basic document-oriented nature of the web. However, there are some applications that I think are successfully embracing the idea that web is a sequence of connected documents. I mentioned Simplenotes and Dropbox in my last post and they’re both awesome apps that you should check out. However, the document nature of the web has given rise to some new uses that aren’t applications in the conventional sense of the term.

When we hear the term “document” we generally think of something along the lines of a traditional paper document. Perhaps we can blame “word processors” for that. But in this brave new age of Web 2.0 documents aren’t just flat sheets of text. The best demonstration that I’ve seen of this new potential is the HTML5 Slideshow. It’s an HTML web page, but thanks to the the tools of JavaScript and new semantic elements it’s a great presentation too. It probably took a good amount of time and effort to put together and I don’t think you want to put this much of effort into each document. Right now, it’s a great showcase but I’m hoping that eventually there will be tools that make it easier to generate these kind of HTML5 documents with minimal effort, the same way we have great CMSs for building web pages today. There are already HTML presentation tools out there, but right now I think too many of them are trying to hard to clone desktop apps.

Moving on from presentations, another really nice example of innovative documents is the the Google book/website entitled “20 things I learned about browsers and the web”. This is almost certainly not the type of thing you think about when you hear “document” or web-page. Personally I think the pageturn effects are overdoing it a bit, but it presents a large amount of information presented in a very attractive format. I also like that the format they used is quite innovative. It’s not like anything you’d expect to see on a desktop for the simple reason that it’s not a program, it’s a document. Well, that’s not technically true: there’s a significant amount of JavaScript code being executed while you’re viewing it. But would you download and install a program whose sole purpose was to tell you 20 things about browsers and the web? We expect documents to work differently than programs (irrespective of what’s going on in the background): we don’t want to run them or interact with them to perform complex tasks, we just want information. And this book makes access to that information quick, easy and obvious.

Presenting information effectively doesn’t need to have great design and cool animations. In fact, perhaps the easiest way to present information is to get the design elements out of the way and let the content speak for itself. This isn’t a call to ignore design or to consider it as unnecessary frills. Quite the opposite: creating design that doesn’t clutter up the data is a hard job that we’re only just starting to get right. Two services that are leading the pack in this regard are Instapaper and Readability.

Instapaper has the goal of letting you save long form text you find on the web for later reading. The website itself is really simple and behaves mostly as a lightweight bookmarking service; you just save links to things you want to read when you have the time. But it really shines when paired with the iPhone or iPad apps. Instapaper strips websites of all their clutter and presents just the text on a simple background in a good font. It’s goal is simple: putting the focus back on the content and letting you read without distractions. I’ve only used the iPhone app so far, but the iPad app looks really good too. If I had an iPad it would probably be my one of favorites. Instapaper lets you read web-based content without having to be in front of a computer (or even connected).

Next up is Readability. It’s a brand new service who’s mission is similar to Instapaper: make reading easier. But Readability is focused on the web. It’s a browser plugin that will take text-rich web pages and present them in a cleaner, simpler design. There are a number of themes to choose from (I like Inverse myself). There will be Instapaper-like iOS apps soon, but that’s not the real point of Readability. It’s for people who will spend time reading in front of their computers instead of on the move (such as me). I’ve only been using it for a few days, but I’m already hooked. Whenever I see a webpage with a lot of text I want to read, but the design isn’t to my liking I hit the Readability button (or just the backtick key). I get the whole article in a nice serif font on an easy-on-the-eyes dark background as well as a list of things I’ve read recently. You can see that list here. I have some more things to say about Instapaper and Readability, but that deserves to be in a post all by itself.

I think we’re only just seeing a resurgence of the web as a document platform. These are still early days no doubt: creating HTML5 slideshows or flip-page books is not something you can do at the push of a button, but I think we’ll get there. Tools like Instapaper and Readability are helping us take back the web, so to speak. There’s still a lot of to do and I’m pretty sure we haven’t even come close to how far we can push the document-based nature of the Web. I’m certainly looking forward to seeing the new formats and services that get built in the years to come (and maybe build a few myself). While webapps won’t go away, we’ll also gain a lot from the web staying true to its document-based roots.

Tagged , , , ,

2010 in retrospect

It’s that time of year again — namely the end. I’ve never been one for new year’s resolutions but I think it’s a good idea to take some time and reflect on the year that’s past and see if there are lessons to be learned.

2010 was an interesting and exciting year. I think it’ll be remembered as the year the iPad launched and gave us a glimpse of what computing in the near future looked like. I didn’t get one, but I’ve spent some time with them and I think they’re a very interesting piece of technology. This was also the year that Android came into it’s own. Sure, it’s been around longer, but I think it didn’t really take off until this year with the newer Droids and the Samsung Galaxy. Android also made it’s way onto the tablet but it remains to be seen how far that will go. While we’re on the topic of mobile systems, I might as well mention Chrome OS. I got one of the Chrome netbooks a while ago. I haven’t had much of chance of playing around with it since I left for India, but it’s certainly an interesting idea and I look forward to spending more time with it once I get back in January.

Personally, 2010 was the year that I decided that I actually did want to go to graduate school to study programming languages. I mostly finished my applications before coming home and I’m looking forward to hearing back sometime in early March. While I don’t have plans of becoming a full-fledged academic, I’ve realized that I don’t have all the knowledge I need to be a competent computer scientist and I’m also undecided as to what would be the best way to put my growing skillset to use. Graduate school is a chance for me to learn some more and put forward a good contribution or two to the field of computer science, hopefully something that a wider audience will find genuinely useful.

This was also the year where I reaffirmed by belief in the value of reading and writing. When you’re someone who’s work is mostly in the realm of pure thought and abstract structures, writing is very important as it provides a way for you to condense and concentrate your thoughts into a communicable and understandable form. I’ve also increased my reading a lot this year. To a large extent it’s been blogs on my fields of interest — languages, applied computer technology, how society interacts with technology — but I’ve also been reading technical papers and journals. I’ve been wanting to read more books and that’s something to try for next year. I’ve also fallen in love with the Kindle DX. It’s just the right size for reading papers and the font rendering is of really high quality. In fact, I sometimes catch myself just staring at the e-ink screen instead of actually reading.

Talking of writing, I’ve had two small revelations — one that programming is essentially a form of writing and secondly, that whenever I stop writing on a regular basis, my personal efficiency plummets. Like I’ve said, writing is a great way to organize thoughts and ideas and I really appreciate having a well organized, clutter-free mind. One of the best ways I’ve found to concentrate and center myself is to sit down and write something (like I’m doing now). It doesn’t have to be great, but the very act of putting thoughts down is very beneficial to me.

Of course, this blog is one of my main outlets for writing. I’m happy to say that I’ve seen some real growth in readership this year, especially over the last few months. I’m at the point where I get about 7000 hits a month, though most of that is to just a few posts. Next year I’d like to grow that number, first to 7000 hits a week and then to that number a day. I also want to increase the number of high hit count posts. I have to sit down and give some thought to the direction and purpose of the blog (like I do every year) but it’s probably not going to change very much. If you’re a regular reader, you won’t be disappointed.

2010 has been a great learning year for me. I learned a lot about the things I’m interested in and a lot about totally new areas (art history for example). I also learned a lot about myself, how I work, what I like doing and most importantly what kind of a person I’m becoming. And through all that, learning about what I can do with my life now that I’m about to graduate.

2011, I hope, will be the year of applying all that learning. How? That’s something I’ll be thinking about in the three weeks I have until I head back to the US. I don’t know the details, but I can tell that it’s going to involve a lot of coding, writing and creating. And I’m really looking forward to it.

Looking forward to the Google Nexus S

Google recently announced the Nexus S — the successor to the Nexus One phone. More importantly, it’s an Android phone straight from Google with the latest version of the OS and none of the distractions that the carriers tend to add on. I’m not really a phone person, I don’t use an actual phone very much and my actual phone is a cheap prepaid T-mobile phone I’ve had for 2 years and have no plans of changing. So why am I interested in the Nexus S?

The thing is that enough though I don’t use a phone very much, I do use other devices a lot. I love my iPod touch (which apart from my computer is my primary communications device) and I wish my camera was smaller so that I could carry it around. However, the thing is I want to do more with fewer gadgets. I’m a bit tired of carrying a phone and an iPod Touch and I really wish I had a camera for all those little moments I want share. But I don’t want to carry another specific device around. I’m at the point where I really want just one device that does everything.

A smartphone would be really nice except for tone thing — the phone plan. Like I said I barely use the actual phone functionality. Also I’m at college which means I’m surrounded by WiFi (and will be at graduate school) which means that I don’t need 3G. Spending upwards of $60 a month when I can get about 2 months on a $30 prepaid charge makes no sense at all. An unlocked smartphone would be great, especially if I could just use it with my existing T-mobile plan. Even if I had to move to a new number, Google Voice makes that mostly irrelevant.

The Nexus S looks to be a strong device. It has all the usual features we’ve come to expect from a top-of-the-line smartphone. Along with the usual Android things, it also sports a 5MP backfacing camera which is something I’m looking forward to. Since it’s straight from Google, I can expect to get updates to Android as soon as they’re released without having to deal with a carrier as man-in-the-middle. Like the Nexus One, the Nexus S will probably be the “reference phone” for the next few releases of Android.

One part I’m a bit unsure about is actually getting the Nexus S. It won’t be sold by Google directory, but by Best Buy, which I guess is fine. By only real concern is whether it will work with my current number and SIM or if I need to get another one. Besides that, there is the question of price: according to Best Buy the unlocked version will be a hefty $529. That’s almost 6 months of the basic T-mobile data/voice plan. Of course, I do plan on holding on to the Nexus S for somewhat longer than 6 months, so in the long run paying upfront would be worth it. Still dropping $529 on a phone isn’t something I feel entirely comfortable doing.

The Nexus S is looking to be a great device and a good fit for my current device usage. However, the unlocked price is rather steep and will definitely be something to keep in mind. Luckily it’s not a decision I plan on making for another month and half at least.

Follow

Get every new post delivered to your Inbox.

Join 331 other followers