For years, the comment system on this site was essentially webmentions. It worked, mostly because I was able to syndicate my posts to social networks like Google+ (does anybody remember that?), Facebook, or Twitter, and then pull the comments back from there. With time, the social networks became more locked-down and I hardly go there anymore (not only for that reason).
Webmentions are quite a niche thing; not everyone wants to own a website1, and even people who do may not have webmention support on their sites2.
For a long time, I was puzzled by how popular Python was for backend development. Of course, it’s very convenient for drafting and prototyping, but the code runs slowly! Who would, in their right mind, write production code that is guaranteed to be slow (and hence to require bigger infrastructure budgets)!? Later I learned that many popular Python libraries (especially the performance-critical ones) are actually C++ and even C “under the hood”.
Go — очень хороший язык для командной разработки высоконагруженных приложений, и не только для них. Для многих это основной язык разработки. А ещё он, пожалуй, наиболее удобный в освоении из современных языков бэкенда, поэтому для ненулевого количества начинающих Go — «родной» язык, самый близкий и комфортный. Видимо, поэтому изрядное количество программистов выбирают Go для решения алгоритмических задач.
В этом посте — несколько ценных советов тому, кто решил пойти этим путём. Мне бы такой пост очень помог год назад, но он мне тогда не попался (собственно, до сих пор не попался, поэтому пишу сам).
If you don’t quite understand how thigs work, debugging can turn into an interesting endeavour.
Read carefully. Fix the code. Compiled and built an image. Pushed the image to the cloud. Installed it onto the test cluster. Not working. Log in to the pod, read logs…
Having read, dive into the code. Read carefully. Fix the code. Compile, build, push, install onto the cluster. Not working. Log in to the pod, read the logs…
Lisp is very much like a broad nib: you wouldn’t use this for everyday writing, and most of the techniques you’ll necessarily acquire would be useless with any other pen. Yet the very experience of having written a line or two with this kind of pen changes your perception of fonts and strokes, forces you to hold your pen differently, and ultimately changes — for good, I presume — both your handwriting and your approach.
I’ve been syndicating my posts from this site to Twitter, and the replies and likes back from Twitter for almost 8 years. Now it looks like I will stop doing it soon.
Kudos to Ryan for providing the great service to all of us for all these years. It’s sad to see it go, yet I agree that Twitter is less and less relevant these days. The web is about building bridges, not walls, and if Twitter wants to follow Facebook’s steps and cut itself off, so be it.
One spring evening, back in St.-Petersburg, I started a blog. Twenty years ago today.
I already had a personal website, or rather, I had already had one: by that time I had removed all but the guestbook from it. What I started this time was a personal blog, finally. Everybody already had one, blogging was at its prime, with LiveJournal and other platforms flourishing; now most of those blogs are long forgotten, and some of the platforms no longer exist. My blog has been updated more or less regularly ever since. Today, I’ve been blogging for more than half of my life.
🖉migdal-or
recently noticed that GlobalSign keeps working in Russia, and has even issued a TLS certificate to the Gosuslugi state portal, for instance.
I gave it a look. To my amusement, the Russian part of the GlobalSign’s website — https://www.globalsign.com/ru-ru — can’t even be opened from the Netherlands: 403 Forbidden. I wonder what they are trying to hide, and from whom…
