Jekyll and GitHub pages are amazing things, that they make the life of a blogger very easy where we can just focus on writing mostly, and yet have full control over the website. It is so nice that GitHub came forward and allowed us to host our websites for free using GitHub Pages project, and they do also allow for custom domains.
This post is to share with you about the changes to the website, and also what I plan to do in the future regarding the tutorials that I’m writing, especially LWJGL Tutorials and WebGL4J Tutorials. I agree it’s been a long time since I wrote the tutorials, and I have been kept waiting because the libraries they use were unstable and in alpha. It was so early that I jumped in, and wrote the tutorials, even while LWJGL is in alpha, and I think it is a mistake. Now that it got released, I’m now going to refactor them with...
Normally just as every other web developer, we try to have a development mode, and a production mode. We want to keep some features only in the development mode, even though we want to commit it to our repository, or we want to include adsense code only in the production mode, that is, when deployed on the website.
Everyone wants a website with a tag viewer, who doesn’t want that? But unfortunately it was troublesome for Jekyll (or static in general) websites, because for every new tag created, one needs to create a new page with some Liquid code to display posts with that tag. For example, we used to do this in the code.
Though OpenGL is cross platform, and also has variations of it like OpenGL ES for embedded systems and mobiles, and WebGL for the HTML5 web platform, there are still differences on the shading languages they use. This means that we have to write a separate shader with changing syntax which does the same operation. Well, this post is about how we can abstract away these differences.