innocenat

I migrated from Windows to Ubuntu 16.04 in December 2016. It was a very great idea at a time, and I enjoyed using Ubuntu immensely. The main joy being that I came to loathe Windows and its update system, and Linux allow me great freedom to install and play with a lot of libraries and softwares easily. (For the fact that almost everything on Linux can be compile using autotools or CMake, but on Windows some may requires MSVC, Cygwin, mingw32, etc, etc). Not to mention that I don’t need to compile by myself a lot of libraries as I could just apt install ****-dev.

Of course, being my first time on Linux machine, I would broke something very quickly.

When you start using fountain pen, one thing that many people notice immediately is that many papers out there doesn’t help up very well. I may have taken a bit longer since my main paper (which was my university branded) did hold up well, but when I tried it on oh-so-famous Moleskine, I immediately noticed that something was wrong (note: feathering)

Another thing is that at that time I was using Lamy Safari EF with Lamy Black.

When I came to Japan, I only brought the pens with me, so I need to restart my collection. And that’s is what happening right now. However, this post will be only about notebooks.

Fountain Pen, one of the most classic writing tools. But nowadays, they might look like a luxurious tool. A tool that is used by hipsters and the well-offs. If you think that, you are now alone. I used to think like that to, until one day. Let me tell you a story.

I have always been using Windows as my main OS since I begin using computer. I have had Windows 95/2000/Me/XP/2003/Vista/8.¹⁄₁₀ on my main computers. If we talk strictly about my personal laptop, than it was XP (2.5yrs), Vista (2.5yrs), 7 (2yrs), 8.1 (2yrs), 10 (6mo). I have use most recent major version of Windows. I never use anything prior to first major upgrade though, so I may have less problem with Windows than people who upgrade immediately. The Windows I used are all OEM tied into the laptop I bought.

But last December, I finally bailed to Ubuntu. It has been three months, and I couldn’t be happier.

I competed in ACM-ICPC for last three years. I was also an ACM-ICPC World Finalist in 2016. That year was a peak in my ACM-ICPC career as I competed in six(!) contests: three local contests, two regionals, and the world finals.

This year I retired from competing in the ACM-ICPC. My main reason is that the ACM-ICPC takes too much time. (After concentrating during the five hour contest, I would not be productive for weeks). I want to focus more on my research topics. However, I still stay as volunteer for this year contets that my university hosts.

Note: Somehow it is hard to keep a regular schedule on blogging. Mostly because I have nothing worthwhile to write

Single Page App (SPAs) is the rage nowadays. Everyone seems to do SPAs left and right, whether it fits their application or not. As with anything concerning web development, there are billions of tools, helpers and frameworks to choose from. Most popular one are Angularjs (¹⁄₂), Emberjs, React and Vuejs.

There are older one like backbone, etc. but we won’t be discussing them todays.

Apparently moving blogs is more fun than writing in it, at least for me.

There has always been three choices for blogging:

• Use WordPress.com platform: Pro: Easy Cons: Not on my domain, ads.
• Self-hosted WordPress: Pro Trusted platform, on my domain Cons: Maintenance
• Static site generator: Pro Simple Cons: Require learning new things

The very first programming framework I have ever used was CakePHP. That was around the time when MVC framework was hyped (around 8 years ago, if I remember correctly). But to say my experience with it is not so good. In fact, I remember I fought with it way more than I really used it.

The reason, if I am asked now, was that I hadn’t really developed really large web application before, and a lot of those helpers/indirections didn’t make sense to me at all. It just overwhelmed me. Really. There are lots of thing to learn: MVC, ORM, conventions etc etc etc. And that time I was very naive.

Last October I wrote TypingMania, a type-along game on web based on TypingMania Odyssey of SightSeeker studio. It’s not quite polished (the menu screen could use some serious work), but I am happy with it (well, I wrote it because I want to use it).

That was my first Javascript project in a very long time (~6 years), and of course the web changed a lot in the recent years. If you reviewed the code you will see many old style code, callback spaghetti and many synchronising boolean that look like some bad shot at thread safety, of which Javascript doesn’t have one.

Even though UI is always the most time-consuming part in any game – or application, really – the most fragile part of this piece of code is audio processing. It should be able to show loading indicator to tell how much has it buffered, it must have perfect time synchronising to the type-along part, and it must run in browser.

Web Audio API is one of the cutting edge technology Javascript has offered. (It isn’t even supported in IE11! But both Chrome and Firefox now support it without prefix). It allows direct low-level manipulation of audio data (to sample level).

While .wav file format is supported by all browsers (Support here is defined by ability to be decoded via AudioContext.decodeAudioData, which is normally the same as those supported in <audio> tag), many other format is not, such as MP3/AAC/Ogg due to various patent problems. Because audio codecs, as opposed to video codec, require very low power to decode, it has been done in pure Javascript before (jsMAD, etc). I actually aim to write some audio decoder in pure Javascript too, so the .wav file playing is the first stepping stone. (audiocogs/etc is Not Invented Here™)

tl;dr here’s the code: https://gist.github.com/innocenat/5c5a48365930b691c863 Read on for detail.

Well, this is not actually planned, but it is simple enough that I can hacked things together in a couple of day (and yes, the code is very short, but very hackish)

Let meet InnoWiki: http://innowiki.innocen.at/ [GitHub]

Although I have been programming for a while (~10 years since I first learn programming), I have not yet made any (significant) contributions to existing works. I have done many projects, but all of them are either myself only or me and another designer. This changed last October, when I start contributing to AviSynth+, a modern fork of original AviSynth project, seriously. For a note, AviSynth is a script-based, non-linear video editing program/library.

In my most recent Introduction to Computer Programming (aka CS101), the instructor decided to shows us very simple image processing: blurring and secret image hiding. There are quite a number of things he did not mention because they are too complicated, but I think someone might be interested so I decided to write it here.

I am not talking about how to load image or save image, you can easily find documentation online for your favourite language. Our professors talk about two algorithm in class: blurring and secret image hiding. I am going to cover only these two here.

I actually have wondered how JIT (Just-In-Time compiling) works for quite a long time, because it is basic knowledge that code segment in memory is write-protected, and you cannot move CPU instruction pointer to stack frame or heap for to security reason. But to do JIT you need to generate new machine code in memory and instantly execute it. How?

I stumbled upon this article titled “The Joy of Simple JITs”, which get me started. Apparently, you can do mmap (POSIX) or VirtualAlloc (Win32) to allocate virtual file in memory. And you can write to this section. And you can execute it. Looking great?