Developer experiences from the trenches

Developer experiences from the trenches

Start of a new post

How I Still Love Computing

Mon 05 January 2015 by Michael Labbe
tags rant 

I enjoyed consumer computing in the early eighties. I started programming on a Commodore 64 at a single digit age. Even with only 64KB of RAM, I was hooked. Too young to afford the raw resources necessary for creating physical things, I was able to sit at a computer and build worlds. By five I had written a racing game in BASIC. By six, I had made a game called Ninja which was my love letter to 80s ninjas, replete with cutscenes. (Yeah, I had played NES Ninja Gaiden by this point).

For me, computers have always been about making things, and not just games. Using them as a base for invention, learning and experimentation is incredibly enriching and rewarding. This, my personal approach to computing, has become increasingly dissonant with the direction of OS X and Windows. Jumping between the two as I shipped a commercial project, I became increasingly held back with a focus on closed-ecosystem communication and link sharing rather than creative and technical productivity.

When you run third party software to replace every meaningful piece of user-facing functionality that ships with the OS, it is time to take stock of how misaligned your creative endeavors are with the direction of your OS vendor. Stepping back, I realized I don’t even like where commercial operating systems are going anymore.

Linux, in 2015, is still difficult to set up correctly. EFI BIOSes, binary NVidia drivers, webcams that work in a degraded state, sound systems that are deficient in execution. If you love computing, these are all worth overcoming.

Once you have made the (oft-frustrating) investment of smoothing your way towards an actual, working Linux desktop, there may actually be a lot less friction to getting real work done. Gone are the mandatory workspace transitions animations, the need to convert vcxproj files to get libraries to compile and printer driver toast popups. Even if there isn’t a true sense of control (you can’t or won’t really influence most open source projects in reality), the people who do have that control haven’t chosen default settings that represent a bias in opposition to your interests. I enjoy Linux Mint’s defaults the most, by the way. Thanks to Dan Leslie for this recommendation.

It won’t be a small investment. Open source is the land of time consuming false starts. There are many software projects which claim to be finished but lack serious features. There are legions of bad alternatives, and it costs real time and money to investigate each one of them to figure out what is a complete, sane and functional choice.

A solid example of this is Linux C/C++ debugging. There are plenty of GUI wrappers for GDB out there but most of them are horrible and the ones that aren’t have considerable trade offs that may grate against your personal preferences. I had the fortune of attending Steam Dev Days last year, where Bruce Dawson introduced me to QTCreator. (Youtube, ppt) I have been using it for basic logical debugging on a 300kloc C++ codebase for a year and I haven’t gone crazy, yet.

Intent is an important, loaded word. We need to correctly apply the term “user hostile” to software that does something that a user ostensibly should not want. Shoehorning a full screen tablet experience into an OS built on APIs that clearly have not been dogfooded at scale by the vendor is user hostile. Putting social tracking cookies via a share button on a webpage is user hostile. Forcing your OS to have no browser competition through corporate policy and application signing is user hostile.

It is important to know the difference between user hostile software and bad software. Bad software may become better — it needs more time, more users to provide feedback, a better process, more experienced developers. User hostile software will not get better. It directs resources based on values that ensure a future of friction for creative and productive people.

I have seen talented, experienced developers publicly give up on switching to Linux, lashing out against bad software that is damping their forward motion. It is frustrating to hit a snag and it is a good idea to warn people against expensive blind alleys in open source. However, I wonder if these people, who often have similar creative origins to mine, would still have the tenacity to re-amass the experience necessary to contribute at the level they currently are. Building an alternative workspace that empowers your trade is hardly as difficult as becoming an experienced developer in the first place. Patience borne of the love of the craft must be plied to building tools we can all rely upon.

People who care about the future of computing will benefit in the long term by warning against user hostile decisions companies make and instead, make an effort to use to software that aims to serve them by working through the frustrating blind alleys and false starts. Software simply doesn’t get better without users. Usage is contribution.

On on positive note, I recently rediscovered the Raspberry Pi and Arduino communities and some of the great projects that have been attempted. A lot of the spirit of the early days of creative computing is couched in modern hardware and software hacking and the “maker” community. As an exercise, you can Google a cool project idea, append it with Raspberry Pi and usually find someone who has experimented with it. This is a tremendously fun rabbit hole.

Fun!

Start of a new post

2014: The Year the Internet Jumped the Shark

Tue 16 December 2014 by Michael Labbe
tags rant 

I have been on the Internet for 19 years, and on BBSes for four more before that. This is the first year where I have found myself reflecting on trends and deciding that the Internet is poised to lead its users towards permanent entrenchment in negative experiences and outcomes. The Internet has jumped the shark. It can un-jump, but it won’t in 2015. That’s my prediction, and here’s what you can do about it for yourself.

Let’s assume, for starters, that you are using the Internet to enrich your life in some way: you are here because you want to learn something, meet someone, or make something and share or sell it to people. Sure, there are always cat pictures and all of that cheap entertainment, but that’s not what I’m talking about. I’m assuming you are interested in getting something valuable out of your time using the Internet.

The most disturbing trend we’ve seen on the Internet in 2014 is an uptick in the severity and frequency of harassment of minorities. Gamergate and its response are both bolstered by Twitter, a web service that acts as a leaderboard for mobs: retweets, follower counts, replies and favourites are tracked. Ideas that need more than 140 characters to express are scattered. This damages discourse. You could not ask for an architecture that enhances mob mentality over rational discourse any more than what Twitter provides.

Public places will never be safe places on the Internet. While that is no justification for harassment, complete safety cannot be a technical or customer service solution. If anyone can join and re-join, it is not possible to achieve complete safety. This is history repeating itself as anyone who spent time on IRC or on bulletin boards will attest. Unfortunately, this time the business models of the companies hosting these services depend on growth which can only be achieved through openness. It would appear from the actions of social companies that they believe closed communities do not scale VC-funded businesses or publicly traded companies.

Next up, we have the problem of overdependence on “the cloud” for consumers. Because many companies are primarily offering cloud-based solutions for your data, it has normalized the idea of cloud solutions for many people.

The consumer cloud is, in many cases, a tax on complacency — in some cases, quite literally a fee and in others, a sacrifice of privacy and control over your personal data. It costs more than the price of a 2TB hard drive — which could store many collections ten times over — for the permission to stream your music from Spotify for a single year. Once you’ve paid Adobe $120 a year to store your photos, that’s it — they have you on a plan because they have your photos. All of these services can be replaced by a couple of hard drives and a Synology product. Then you have complete privacy, and you are not at the whim of a huge company whose interests are at cross purposes with yours, at best.

If you told a photographer in 1990 that many of her peers would consider paying a company a yearly fee to hold her own photos in the future, she would look at you very oddly. How dystopic.

The last problem I want to address isn’t particularly new to 2014, but it isn’t getting any better, either. We get our information from social feeds now. Google famously ended Google Reader, asking us to get our news from Google+ instead. Sadly, people don’t use Facebook and Google+ to pass around truly useful information. Nine times out of ten, you get articles that amount to fodder for small talk and dinner conversations. This seriously degrades the utility of what you read on a daily basis.

I target these three problems because they are examples of companies routing us towards a less informative, more troubled Internet. They do it because they are operating at a cross purpose to our own: to scale their customer bases. I expect these assaults on meaningful Internet time will continue and increase in 2015.

You can take the Internet back for yourself. I recommend these three things:

It’s unrealistic to assume that these companies will change their ways. But you can make your time on the Internet that much more enriching and valuable. The great news is that we still have the computing freedom to sidestep these trends.

Start of a new post

What I Learned From Sharing Native File Dialogs

Thu 27 November 2014 by Michael Labbe
tags code 

I open sourced Native File Dialog last night. It’s a lean C library that pops up a native file dialog on Linux, Mac and Windows. It seems to have scratched an itch that a lot of people have, as it’s been starred 50 times on Github overnight, and my announcement tweet has received 27 retweets and 52 favorites as of this morning.

I did learn a few things writing and releasing this. Here they are in no particular order.

Linux users are reticent to link against GTK+. Plenty of people don’t want the overhead of GTK+ just to get a few paths back from the user. This makes sense if your app benefits from staying small. In order to get GTK+ up, you have to link against quite a few libraries: Cairo, GLib and GTK+ itself, to name three.

Interestingly, there must be similar overhead in Windows, but it isn’t as visible; most of what you need is given to you through COM object initialization, not linking libraries. Linux has no official toolkit, and as a result, the cost is much more visible to developers.

Of course, you can release COM objects.

GTK+ has no uninitialization. Once you have paid the cost of initializing GTK+, it permanently allocates private memory in your process. This is a shame. At least I can release COM objects.

This has led people to suggest Zenity and pipes; actually launching the file dialog in a separate process! I have always been skeptical of this approach — what happens when the dialog opens in another workspace, or the main app crashes, or X remoting causes other idiosyncrasies?

At any rate, I would be happy to accept an nfd_zenity.c patch which allows people to trade off between these problems.

People Really Like to just add one file to their project. Native File Dialog builds with SCons, which, admittedly, is not something every developer has installed. STB has spoiled people — they really want to just drop a file in to their current build! I am going to provide instructions that help people bypass SCons.

Feedback is hard to come by when you work on a small team. If you open source something useful, devs will scrutinize it and provide feedback. It doesn’t have to be a large piece of code — actually, it’s probably better that it’s not! If NFD did ten things, the issues people raised would have been broader, and the criticisms received may not have been as beneficial to me.

Start of a new post

Installing an Air Conditioner in a Window That Barely Opens

Mon 26 May 2014 by Michael Labbe
tags handy 

Around here, air conditioning is almost never part of a deal when you buy or rent an apartment. I converted a spare bedroom into an office, which was great until the sun hit and it turned into a virtual sauna.

In getting an AC unit installed, I was faced with an interesting problem: I had windows that opened up and out at an angle, but just barely. The glass is held in place by metal framing, making it intractable to drill through.

I contacted a few self-described handymen who quoted me anywhere from 50 to 500 dollars and proposed building mounts out of wood, metal, or just plain crazy gluing the AC unit to the frame (!). No two quotes proposed the same solution. That’s when I knew the experience I could hire to solve the problem would be improvising on the job. I had an idea of my own which was cheap and easy to test, so I decided to try it out.

The approach? Industrial strength Velcro® and acrylic glass.

I recently had success mounting rear speakers on stands with Velcro. This isn’t the stuff you kept your shoes on with in second grade. Industrial strength Velcro is at least two inches wide and comes in rolls measured by the foot. The rear side has very sticky glue and can easily attach to the metal frame of your window.

Here’s the finished product, with instructions below:

Finished

The total cost was under $40, took two hours, and has worked for me for two summers. I can remove the acrylic glass by tearing away at the Velcro in seconds, making end-of-season take down a five minute chore.

Here is what you need:

Step One

Mount the plastic exhaust panel on your window. Your AC panel instructions will tell you to screw it into the wall. This is intractable — we want to avoid damaging our windows by drilling into metal. Instead, throw down a few inches of that sweet, sweet Velcro and the exhaust panel stays in place:

Mount

Step Two

Measure your window and cut the acrylic glass to fit.

Unfortunately, I didn’t have a workbench, and didn’t feel like making my way to the ‘burbs to use one, so I used a table on my deck. I scoured the glass with a scouring knife and filed the edges down. This was not easy, and I was punished for my laziness and impatience by grinding away for almost an hour.

The glass:

Plexiglass on table

The scouring:

Scour

Step Three

Now that your acrylic glass is cut to fit and filed down for smoothness, attach Velcro to the edges and mount it in the window. You want it to fit in so that it is overlapping the metal frame on the top and sides, with the bottom seating directly into the AC exhaust mount.

Here’s a closeup of Velcro mounted to the metal window edge:

Velcro

Bonus Tips

At this point, you can fire up the AC and breathe again, but you should keep these tips in mind:

« Page 4 / 8 »

rss
We built Frogtoss Labs for creative developers and gamers. We give back to the community by sharing designs, code and tools, while telling the story about ongoing independent game development at Frogtoss.