Hello, yet again.

I figure I’ll continue off in this post where I left off in the last, detailing more things.

Vaporwave

This is a very dead sub-sub-genre of electronic music from back in 2012 (or 2011, I’m not sure), but it surely died some time in 2013. The joke of the genre was to be some sort of musical, and sometimes visual, critique on capitalism, hyper-consumerism, and all celebrations of it in disguise of culture.

The thing of course is, given that artistic pretension abounds on the Internet, I have my reservations as to the actual purpose and message of the genre.

But it’s, although declared dead, quite alive with a somewhat cult following (including by yours truly).

But other than that, I wouldn’t read much more into it. And unless you grew up some time during the 1980’s and 1990’s, you’re likely not to get the material from where the tracks are made with and are free to, as a result, take them and enjoy at face value.

The following video, a review of a well known Vaporwave album back from 2012, will explain better the genre.

And another thing, some may say that vaporwave, is really nothing more than so called “meme music”. Perhaps, but if there’s something that the internet has proven, is that you can find audiences for all kinds of things anywhere. Even if they were meant to be a one-off joke.


Continuing on why I chose Jekyll

One of the reasons that I’m deciding to learn and work on learning Jekyll is that it has a template engine that is quite simple and easy to learn for a novice like myself that is just barely getting passed the basics of HTML and CSS and going onto the basics of JavaScript, and programming for that matter.

Although, this is more about about JavaScript as, since coming in discovery of GitHub’s text editor - Atom - I’m given more chances to learn on how to use JavaScript as Atom uses JavaScript for customizing the text editor itself. This goes against the grain typical of open source text editors that prefer to have their own, arguably proprietary in nature, scripting language than use a standard scripting language like JavaScript.

In addtion to this, Atom has a built-in Markdown editor and previewer, this eliminates the need to use tools like Sublime Text and Markdown Pad 2 (both somewhat expensive proprietary tools with the former being somewhat multi-platform and the other not being at all).

I do have reservations, on the other hand, about Atom in terms of performance if should there be the need to have multiple files opened at once. This is partially because Atom is built with Chromium as a desktop application framework and that means having to use mostly web development technologies, namely JavaScript - a language that’s even categorically “higher” than Python which is used for Sublime Text, as the language of development for Atom.

This puts me to believe that the developers and maintainers of GitHub’s Atom text editor project, are constantly working in checking under the Chromium framework’s hood and making sure to not end up being totally dependent on the, sometimes horrid, nightly builds that come out from Google’s repositories - I would know this given that some nightly builds of the Chromium browser break pretty badly.

And then of course, should I chose to, Jekyll offers a chance to consider seriously into checking out Ruby. Jekyll relies heavily, as it’s been developed with, the Ruby programming language. So if I should ever want to, I could look into learning Ruby in order to, in turn, help in improving Jekyll.

So with those things said, there are many lined up birds that I could choose to hit with one stone, and it all starts with Jekyll

As a side note: Neo*Vim is coming soon, and it’ll be something else that I’ll be looking forward to couple with Atom as part of my set of tools to use in projects. So once I manage to get my hands on a stable release, I’ll be sure to post up here if and when I can about my impressions of it.

Misc.

I have also added a page, for fun, sharing my video game backlog. It’ll show the games I’ve finished, which ones I’m playing currently, but not have any listed that I have pending as such lists, I’ve come to find personally aren’t helpful necessarily.

I’m also going to be upgrading to Windows 10 Pro. I’m looking forward to it for two reasons: I’ll have virtual workspaces and I’ll finally be able to stop using Display Fusion for generating taskbars on the additional monitors!

Because as much as I like Windows 7, it’s high time for an OS upgrade.

In addition, I’m hoping to take the time to make a fun post on what I’d like in my hardware upgrade in my desktop system.

There’s lots to write about, and I hope to hear from you.