HNHacker News
TopNewBestAskShowJobs

yegortimoshenko

442 karma · joined July 6, 2015

submissionscomments
yegortimoshenko··on How to Become a ‘Superager’
I don't think wealth accumulation is an issue. However, heritage is what heavily contributes to wealth accumulation. With aging gone, and subsequently, heritage heavily delayed, wealth distribution gap will become smaller, not larger.

Life expectancy increases tend to decrease birth rate. And with Elon Musk currently working on colonizing Mars, and seasteading making some progress, there will likely be a lot of place to live in by the time we work out aging. Actually, if both fail, there is a place for 6 billion more people on Earth.

You're afraid of your own prejudices about something that isn't even here yet. And I don't understand your use of word "immortality": it is aging we are discussing here, a condition that causes people to die, often in misery and pain over long periods of time. I think it is a very humane, global, noble cause, and I honestly don't understand how you can be so cynical about it.

yegortimoshenko··on How to Become a ‘Superager’
I'm preaching to the choir, but for the sake of visibility — there is a very inspiring fable that puts aging into another context: http://www.nickbostrom.com/fable/dragon.html
yegortimoshenko··on Closure Compiler in JavaScript
It makes a completely self-hosted ClojureScript compiler possible.
yegortimoshenko··on Ask HN: Best current model routers for OpenWRT, DD-WRT, Tomato, etc.?
PC Engines APU2 (or Soekris net6501) + OpenBSD is the best router you can get.
yegortimoshenko··on Dear JavaScript
I'd argue that most breaking changes are not about fixing problems. They are about API consistency and taste, like Babel 6 mentioned above.

If problem is a bug that people might rely upon, I don't mind fixing it. If problem is fundamental design-wise, however, the right way is to create a new library.

There are a lot of designs that never break anything (or at least try hard not to): Linux, macOS, Erlang, Java, Clojure, x86 instruction set, life on earth, and they all improve over time. And they obviously didn't get everything right the first time.

yegortimoshenko··on Dear JavaScript
I don't think you understand. The critique itself, whether constructive or not, is something to learn from.

Just like breaking changes in Babel 6. There is a lesson waiting to be learnt, namely, don't make breaking changes to existing software.

As a matter of fact, I honestly don't understand why you take it so personally. Sometimes I do stupid things and people call me an idiot, and it's helpful to know that. Sometimes it gives me a perspective I haven't thought of.

Look at how Theo de Raadt and Linus Torvalds manage their projects. It is kind of the same.

yegortimoshenko··on Dear JavaScript
> When we launched Babel 6, we made an API change that we had planned for awhile. We moved from having an implicit (“works out of the box”) behavior to an explicit (“will work for everyone”) behavior.

Just like Rich Hickey said in his last talk (see https://news.ycombinator.com/item?id=13085952), breaking changes are broken. For greater good or not, it's no surprise people complain when you break their code/workflow.

> I want to talk to you about an article that was written the other day titled “Angular 2 is terrible”. For starters, that title alone is an attack on the maintainers. Surely the author wants a set of problems addressed. But why should the maintainers want to even click on that link, let alone try to address the problems?

I too think that Angular 2 is terrible. It is not an attack on the maintainers, it is just a piece of (IMO) bad technology with maintainers feeling attached to it.

It is a very crucial skill in life to be able to withstand critique and take it to your advantage. There is a lot of usually unnoticed utility hidden in critique, waiting for someone to reap its benefits.

yegortimoshenko··on ClojureScript and optimized C [video]
Clojure on JVM is about 80x slower than ClojureScript in this scenario, by the way.
yegortimoshenko··on Ask HN: What's your go-to back end for simple projects?
Clojure and Elastic Beanstalk.

You take an arbitrary Ring-compatbile HTTP server, write a handler, and glue together whatever you need to. And you most likely don't need a routing library, you can just use an array-map for that. When it is time to deploy, you create a jar that contains your whole project and upload it to AWS.

Rollback is easy, too, as you don't overwrite your previous version. Funny enough, it means you can treat versions as immutable values of your application over time. I use yyyymmdd for versioning in most projects, that works great with this approach.

There are many discussions on virtues of Clojure's dynamic development environment, so I'll skip that.

yegortimoshenko··on Taking PHP Seriously
Totally. PHP is a great technology and a bad language.
yegortimoshenko··on Ask HN: Any unfinished side projects to give away?
I made Paper, an Instapaper addon for Firefox: https://github.com/yegortimoshenko/paper

The problem is, I don't use Firefox anymore, so I'm looking for a new maintainer.

yegortimoshenko··on OpenBSD 6.0 released
Now, that OpenBSD runs on Xen (and, by extension, on Amazon EC2), is there an official AMI?
yegortimoshenko··on SRL – Simple Regex Language
AppleScript, SQL, COBOL and others have all made the same mistake.
yegortimoshenko··on The Plan 9 Effect or why you should not fix it if it isn't broken
With such conclusions you are not going any further than PDP-11 assembly language.
yegortimoshenko··on English Syntax Highlighting
It is not really interesting, see: http://www.linusakesson.net/programming/syntaxhighlighting/i...
yegortimoshenko··on Instagram's Million Dollar Bug
> At no time did we say that Wes could not write up the bug, which is less critical than several other public reports that we have rewarded and celebrated.

There is no bug more critical than one that results in complete access to Instagram infrastructure. Sure, the bug is stupid, but you are fooling yourself.

yegortimoshenko··on The Web We Have to Save
It is about Blockchain and Xapo wallets or even about centralized validation in wallets like Mycelium.

Such centralized systems had not existed in Bitcoin before it became popular.

← PreviousPage 2 of 2