Hacker News new | past | comments | ask | show | jobs | submit | jcburke's comments login

Ya, I think it's more that people assume that if you choose not to drink, you look down on people who do drink, and especially in one-on-one settings that makes them feel uncomfortable drinking around you


Ah yes, the concept of "anticipated reproach", where seeing someone do something that you deep down know you should do triggers a defense mechanism that makes you dislike them.

It's pretty easy to spot in people, and I go out of my way to avoid people that are that morally and intellectually stunted, so that may contribute to me seeing less of this reaction.


Reading the comments in this thread, can you blame people?


I think that might be why it bothers people who some people do drink when you order water: they see it as you somehow saying that you're better than them by declaring your health lifestyle


No one can make them feel inferior without their consent. They are just projecting their own insecurities.


Wait, so they wrote their own bytecode, functional language (complete with compiler and libraries), functional operating system, TCP replacement, and distributed storage protocol? And will presumably write all their own apps, or some kind of interface layer that will allow non-Hoon code to run on their system efficiently? That has to be one of the most ridiculously ambitious projects I've ever seen. Good luck to them I guess, but I've always been a believer in not reinventing too many wheels at once


Perhaps it makes a bit more sense if it's explained that the original goal was to keep the whole codebase (outside of the C support layer, which adds no semantics) at 10Kloc. Unfortunately this is now rapidly slipping toward 20.

Of course, Kloc is a deceptive measure of algorithmic simplicity in a functional language, if compared to procedural. Also there is about another 15Kloc of C in the interpreter and another 10K that wraps an event layer on libuv.

Bear in mind that Urbit can also be seen as an ACID database on the log-and-snapshot principle - events are transactions. You can of course export application state to some other storage system, but you don't have to. (If you change the source code, your app reloads - you do have to write a function that maps your old state to your new state, though.) So there is a lot of strange futzing around with mmap at the bottom.


This seems pretty cool. I would be interested to see an open source version of this concept


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: