HNHacker News
TopNewBestAskShowJobs

dan353hehe

382 karma · joined October 2, 2015

submissionscomments
dan353hehe··on Visions of the Future
I don't think I have ever heard anyone say "juvenile foible of nostalgia" before in my life.

I have generally found that when people become art critics and try to describe why the like/don't like a certain piece, it tells more about them as a person then it does about the piece.

I think the best description of why the posters were created is:

> As you look through these images of imaginative travel destinations, remember that you can be an architect of the future.

They are simply trying to encourage people, probably younger people, to realize that things that are impossible today, don't necessarily have to remain that way. But who knows, maybe I just have a "stunted" mind.

dan353hehe··on Saying 'no' to keep crap out of products
This reminds me a bit about what was mentioned in the book "good to great". A company, or in this case a product, can do everything at a level a little above garbage, or it can focus on its core competencies and be the best at something.

The more features you add to a product, (in my mind) the worse it becomes.

dan353hehe··on Google Open Source Load Balancer in Go
seesaw is just a management layer on top of ipvs (or lvs).
dan353hehe··on Google Open Source Load Balancer in Go
The third link that you posted is for keepalived. keepalived uses LVS as the actual load balancer (which is what seesaw uses as well). So as long as you can setup seesaw to run a few scripts to inform DisitalOcean which droplet currently has the ip, then it should work fine. There is an example for keepalived in the link that you posted.
dan353hehe··on Postgres high-availability cluster with auto-failover and cluster recovery
True it is, however to use manatee you have to build on ZFS, which unfortunately is not as widely adopted as it should be.
dan353hehe··on Postgres high-availability cluster with auto-failover and cluster recovery
Thats true, however in yokes case, each cluster needs a third member called a monitor who only serves to resolve network partitions. a secondary cannot self promote to primary without the monitor agreeing.

two node systems can never work as a primary/secondary failover solution in the presence of a network partition.

disclosure: I helped write yoke.

dan353hehe··on The New InfluxDB Storage Engine: A Time Structured Merge Tree
sustained writes of several hundred thousand, with a 25x decrease in database size?!

I knew it was the future today when I woke up.

← PreviousPage 4 of 4