Hacker News: yuriyguts

New comment by yuriyguts in "Never Give Them Your Face"

yuriyguts — Mon, 22 Jun 2026 17:26:44 +0000

This comment is load-bearing − the LLM-generated text was the smoking gun. (Claude)

New comment by yuriyguts in "Quick Tip: Enable Touch ID for Sudo (2020)"

yuriyguts — Wed, 15 Jun 2022 12:05:52 +0000

This is a reasonable concern. Although, whenever security-convenience tradeoff is involved, different users will inevitably have different preferences and tolerance for automation. Some will prefer to do things manually, while others will prefer something that "just works" for them.

New comment by yuriyguts in "Quick Tip: Enable Touch ID for Sudo (2020)"

yuriyguts — Wed, 15 Jun 2022 09:15:40 +0000

I love using sudo with Touch ID and have been using this trick for years. The only inconvenience is that the PAM configuration always gets reverted by OS updates.

I wrote a small tool to mitigate this by configuring PAM on system startup: https://github.com/YuriyGuts/persistent-touch-id-sudo

New comment by yuriyguts in "Programming on a Piano Keyboard"

yuriyguts — Wed, 25 Jun 2014 13:25:09 +0000

Counting the number of words is, no doubt, a sensible way to assess the academic value of something. Sure, REST may sound better than 'Architectural Styles and the Design of Network-based Software Architectures', but let's stick to http://ycombinator.com/newsguidelines.html, section "In Comments".

New comment by yuriyguts in "Programming on a Piano Keyboard"

yuriyguts — Tue, 24 Jun 2014 16:58:27 +0000

You're right, those particular mappings were mainly for demo purposes. I guess it would be quite inefficient to use the approach from the video on a regular basis. If I used it in real life, I'd probably map the keys to complex macros, unmapped IDE commands, or other features that are hard to memorize on a regular keyboard.

In addition to @JoshTriplett's idea about velocity, I guess knobs and faders might have some interesting applications too.

P.S. Btw, it's a "she", it's my colleague performing :)

Programming on a Piano Keyboard

yuriyguts — Tue, 24 Jun 2014 13:27:33 +0000

Article URL: http://elekslabs.com/2014/06/programming-on-a-keyboard-a-piano-keyboard.html

Comments URL: https://news.ycombinator.com/item?id=7937562

Points: 221

# Comments: 36

New comment by yuriyguts in "How Azure Web Sites Sucked in Production"

yuriyguts — Thu, 15 May 2014 17:44:32 +0000

.htaccess is supported not only by Apache. And I wouldn't be surprised if WAWS supported "at least a subset" of .htaccess configuration keys on Azure, since Microsoft has been trying to make a move into the LAMP world during the latest few years. I would consider it a marketable feature.

If we're discussing terms, then we must have a different understanding of what a managed hosting is. A service that allows you to select an application template, deploys the resources for you, sets up source control software, handles OS patches and host software installation for you, is _clearly not_ a managed hosting? What is then?

EDIT: I do admit that editing .htaccess was my own mistake. Not even sure where it came from actually, since the default WAWS WP template doesn't even contain it.

New comment by yuriyguts in "How Azure Web Sites Sucked in Production"

yuriyguts — Thu, 15 May 2014 17:10:11 +0000

Very good point. But the main message I was trying to deliver is not about the bang for the buck, but rather the amount of issues/decisions WAWS tries to offload to the users instead of handling them intelligently on its side. It's not hard to send an email message, or automatically configure web.config knowing the predefined quota, but the impact on customer satisfaction could be huge.

New comment by yuriyguts in "How Azure Web Sites Sucked in Production"

yuriyguts — Thu, 15 May 2014 16:56:56 +0000

Good points, but I must disagree on some details:

* We did not develop the application from scratch and therefore we cannot control its memory consumption, especially if it's a garbage-collected environment. We used WordPress as an existing application template provided by Azure. The development on our side was only about developing a custom WP theme, which is 90% frontend development. The developers barely touched the server side, and we tried to configure the environment to consume not more than X MB.

* Regarding not being built well for shared environments: WordPress powers about 60 million sites in the world, and I bet the vast majority of them runs on a shared hosting. Currently, this blog post is served from one of them :) During the typical days, our traffic is really too low for a dedicated environment, so it would really be an overkill.

New comment by yuriyguts in "How Azure Web Sites Sucked in Production"

yuriyguts — Thu, 15 May 2014 16:47:35 +0000

I tried to add php_value memory_limit 128M in .htaccess (it's mentioned in the post), but I wasn't aware that Azure pays no attention to .htaccess and I should've been modifying web.config instead.

But I'm a tech guy. As a customer, I would expect Azure to configure the server and PHP on its own and not bother me with the quotas at all :)

New comment by yuriyguts in "How Azure Web Sites Sucked in Production"

yuriyguts — Thu, 15 May 2014 16:43:01 +0000

Since we're not a professional Internet media (it's not even a commercial project), when we don't hit HN top, the traffic is very low. Currently we're serving this post from a traditional hosting worth about $7/mo, and it handles the HN burst amazingly well.

New comment by yuriyguts in "How Azure Web Sites Sucked in Production"

yuriyguts — Thu, 15 May 2014 16:38:46 +0000

While I must admit that the title of the post may seem too flashy, the main point I'm trying to make is not 'omg, the quotas are too low for this price', but rather: 'based on this experiment, Azure has given me too much trouble and hidden gotchas to consider it for small or middle-scale websites in the nearest future.'. Not notifying the user about pulling the plug on the website, or hiding a DB quota so deep in the documentation would not make a customer too happy. And while I've worked on (mostly non-Azure) cloud solutions for a couple of years and I'm prepared to read the fine print, I'm scared to imagine how a cloud newbie would feel about this.

New comment by yuriyguts in "How Azure Web Sites Sucked in Production"

yuriyguts — Thu, 15 May 2014 16:32:59 +0000

Well, currently we're running the blog on a traditional shared hosting that costs less than $10/mo (you can easily find out which one :)) and it handles the blog amazingly well, even during HN bursts. The blog itself it not our primary line of duty, more of a side project actually. So when there's no new updates, it's quiet enough for a shared hosting to handle.

New comment by yuriyguts in "How Azure Web Sites Sucked in Production"

yuriyguts — Thu, 15 May 2014 16:29:26 +0000

Please see the details in my post, I tried to limit RAM usage via usual WordPress configuration tricks, but Azure didn't seem to respond. Perhaps an even bigger question is: why Azure hasn't configured the site itself, if it imposes quotas on it.

How Azure Web Sites Sucked in Production

yuriyguts — Thu, 15 May 2014 13:31:15 +0000

Some hidden gotchas you may encounter when using Azure Web Sites, especially in Shared mode and/or with LAMP stack.

Comments URL: https://news.ycombinator.com/item?id=7749269

Points: 85

# Comments: 46