I feel the change

I don't want to waste everyone's time describing the background which made me write this note. In short I'm just so impressed with the installation smoothness on the Cling, that I could not resist to write this note.

And regarding the title of this note, generally I feel that finally the world of the C++ changes to the best. Just because of many things like Cling appear and the C++ itself becomes much better than before.

I believe the hurricane is approaching.

Log: linux stuff

To mount windows (samba) share, add the line to the /etc/fstab like this:

//SERVERNAME/path /mnt/network-drive  cifs  nosuid,nodev,noexec,uid=user,gid=users,file_mode=0640,dir_mode=0750,username=BLAH,password=BLAHBLAH,iocharset=utf8  0  0

To prevent the garbling of the filenames, don't put forbidden characters (colon in my case) into the name.

Videos on C++.

G.Law on GDB:

B.Stroustrup on C++ in general:


H.Sutter on C++ mostly in general:

 

S.Meyers on C++ move semantics and other topics.

P.S.: sharpening the saw.

Electron, Node.js and their friends.

Trying to put some changes into the KeeWeb app (I even forked it), I started the WebStorm editor and then recognized that I have almost started to shave another Yak, which is in this case an electron framework, node.js and so on in the direction of JavaScript.

But the enemy is recognized and defeated! Screw it.

Recalling the beautiful article from Jeff Atwood which is called "Sharpening the Saw", I think of renaming the blog to reflect the idea that every Yak Shaving can be or can be not sharpening the saw in the context of the aforementioned article.

Yak Shaving #0: Visual regexps on steroids.

Being fed up with crazy syntax of RegExes in Emacs, I have found a replacement for it. Or I'd rather say "enhancement". It is called visual-regexp-steroids and looks so cool on screenshots, just check it out.
Exactly what Emacs should've had from the beginning. And guess what? It does not work for whatever reason. Either it is Helm interfering with it or Python is not found as expected (but it is available in the system). I don't know, therefore I'm doomed to guess wildly. Emacs, I hate you. The more I look at you the more you look like a Yak. Wait a minute, isn't it what Stallman meant choosing the Emacs symbol (the wildebeest)?

And I'm shaving, shaving...

P.S.: My emacs configuration.
P.P.S.: Another beautiful online RegEx helper with astonishing amount of interactive help. 

Yak Shaving #-1: The good news, the bad news and the Yak Shaving.

The good news are: I have definitely decided that GTK is not worth fighting with it, facing a Qt as an alternative. The difficulties to find a documentation/explanations (and alive people who would have had the knowledge and were willing to help) were so big that I decided to cancel the complete topic altogether.
The bad news is the other side of the good one: I gave up on GTK and if I want to implement any GUI stuff, Qt is an option as it just has more clear future.
But the ugly news is the fact that there is no sense to do anything based on Qt for GIMP. Or at least it sounds a bit perversely. I am not sure I want to touch it even with a 10-meter stick.

Ah yes, and one more thing. I see no place for lisp there anymore.

Hopefully Yak Shaving is over.

For those who are interested, the original idea was to introduce the non-destructive editing into GIMP. After fighting with the GTK+ (and a little bit with Lisp world, too, because I cannot imagine any good reason for developing a graphics editor on plain C in 2015), and also after confirming that there are proprietary but inexpensive alternatives to Photoshop (like Bloom) with aforementioned non-destructive abilities, I decide to give up on this topic as on not interesting. In my opinion it has no or too less potential.

Balm for my wounds

Just in time I have discovered beautiful source of the information: planet lisp. Yes, I didn't see it before.

Anyway, there after digging into old archives, I have found this: Starting to Hack on SBCL.

It is exactly what I need now. The motivational article with a number of pragmatic guidelines and examples.

Just in time, just in time...