Monthly Archives: February 2013

In over my head at LUUG but Steam for Linux!

Posted on by
Reply

This was my first VT LUUG meeting and I felt pretty overwhelmed. At the beginning we went through a series of topic including a quick snippet on RoR and I came to the conclusion that RoR is not a very secured framework. My favorite was about the release of Steam for Linux though, so from here on out this blog might just be about my thoughts on Steam for Linux. It’s about the only thing I could follow through out the entire meeting. Back to Steam for Linux though, I heard the news that Valve planned on porting Steam to Linux over the summer and I was esctatic. I was just beginning my journey
in the Linux world but I already planned on making Linux my main OS. The only reason I booted up Windows was for playing games, and trust me I tried using PlayOnLInux
as well as Wine but it was just too much work and a pain to be honest. Even if I did get it working there were a couple of games that were reported to be laggy and just not as fast.
So Steam coming to Linux was the best news to me as a new comer to the Linux world. Now that it has been released I feel like Windows is going to be hurt a bit and lose a bit of audience who only stayed on Windows for playing games. This is at least true for me, and my time on Windows will be dramatically less than before. As with the rest of the meeting I was a bit lost when the speaker went into details with IPSec, although I know the basics of VPN and such this topic was in over my head. I also found it hard to follow a lot of what the discussion was about and found it harder and harder to focus as I got more lost. I guess it’s just because I’m an amateur. I then left early since it’s Valentines day and I had arrangements. But hey, Steam for Linux!

A comment on commenting

Posted on by
4

The first language I dabbled in was Java and that was for a class in high school. Commenting in Java is pretty much the same as commenting in C, C++, C#, and Obj-C. Example:

//Single comment

/*  Block Comment */

After receiving the first assignment for the class, I glanced through it and everything seem well. Although there was no specification for comments, I had to add some anyways since ever since I started coding the idea of commenting and documenting your program was pounded into my head. So of course, by reflex I commented all my programs using the double slash even though I knew Python used a different syntax and of course I got errors. So I simply had to Google up real quick how the commenting syntax for bash and Python which luckily used the same syntax for commenting using the number sign.

Of course this isn’t a big deal or anything, but it’s just irritating sometimes when you’re working with multiple languages on a project and you’re switching between languages. Sometimes you just code and your brain can flip flop the commenting syntax, like what I’ve done so many times before and you get annoying and easily avoidable errors. The most annoying of this is developing a website. HTML’s comment tag is <!– Comment –>, which is sort of annoying when you just want to add comments real quick. Javascript and PHP uses the two slash to comment and it’s sometimes annoying when I switch around and use two slashes in some HTML snippets (even though I’m pretty sure it usually wouldn’t cause errors and just ignore the line, it still could).

Bottom line is I wish all languages just use the same syntax for commenting, even though I’m sure that there are different functionality of the characters in other languages. Here is a list showing the some of the different ways to comment in different languages:

Java, Javascript, PHP,  C, C++, C#, Obj-C: // Comment

Python and Bash: # Comment

Lua (A scripting language): — Comment

Ruby: Ruby is weird since you use the number sign for single comments but block commenting requires this:

=begin comment block =end