jrsnyder
Joined 14 years ago
Karma
138
Submissions
33
Member since
Dec 11
I'm writing Clojure at Amperity
View on Hacker NewsRecent submissions
Comment · 7 years ago
I started following this same system, and after realizing how much sense it made, and how similar this system is to typical digital data storage system design, I concluded I should always design physical storage systems using the same mindset as data storage.
Comment · 8 years ago
After looking at both, I chose Atom.
The VS Code developers observed that things can pretty tangled with open-ended plugins and HTML rendering, so they cordon off plugins to separate processes, and only offer limited UI control to plugins. This helps keep things stable and fast, but I think the ability to have plugins easily create new UI in an open-ended way is the coolest feature that Electron enables in an editor.
Atom offers a lot more UI control to plugins, and in my experience, is still acceptably fast and stable.
Comment · 8 years ago
Comment · 8 years ago
As others have said, it’s a question of what you want to get from learning.
Haskell primarily tries to answer the question, “What are static type systems capable of, and what new relationships can we achieve between code representation and code execution?”
Clojure primarily tries to answer the question, “How can we write programs more efficiently in the (relatively) short term?”
Comment · 8 years ago
Comment · 8 years ago
Scraping the /popular page on del.icio.us:
https://github.com/reddit-archive/reddit1.0/blob/master/scra...
del.icio.us/popular used to be very similar to Hacker News as a source of fresh web-scene-relevant article flow.
Between /popular, and per-tag RSS feeds, in some ways del.icio.us used to be a better Reddit than current Reddit. Tags and tag feeds were a very flexible way to monitor interest topics. What is now a network of reposts between subreddits, used to just be the addition of tags.
Saving a bookmark to your own set of bookmarks also served as an "upvote". This created a nice incentive alignment; if something was interesting, you would want to keep track of it, and add it to your collection, with the tags relevant to you!
Because del.icio.us was not explicitly designed as a "hype machine" like reddit, it turned over a lot of really original content that would have been hard to discover otherwise. It helped that the peak of del.icio.us was during the rise of blogs and self-published websites.
Comment · 9 years ago
I went through a similar process recently, and ended up getting the Spindle: https://spindlemattress.com/. It's also an "assembly your own" latex setup, although instead of shopping for layers individually, they sell 3-layer sets. I'm pretty happy with it.
I liked that the layers stay separate - you can break the mattress down to make moving easier, and you can replace layers individually, if you ever feel the need (with a 30% discount if you buy from Spindle again inside 25 years).
Comment · 10 years ago
Microsoft (operating system, SQL database, programming languages / environments) and Oracle (databases, partial credit for programming language (Java)) could be considered hard-tech software companies with outcomes (so far) that are many multiples of those you mentioned.
Comment · 10 years ago
How would you say Noms compares to Datomic[1]? Both projects are working on the same idea of representing a database as tree of commits over time.
From my quick inspection, it looks like Noms shows some focus towards working in multiple branches, whereas Datomic, at least in its marketing materials, just talks about preserving a single timeline.
Comment · 10 years ago
Okay, I did not know about this law. Thank you.
Comment · 10 years ago
Okay, yeah, dctoedt points to the law[1] where this is described. I did not know about this law.
Interesting, though, that the courts' appraisals are trusted over the market in this case. It's sort of like an anti-crowd-dynamics protection, but only for people who vote no. Your decision over whether to vote no is influenced by your knowledge of likelihood for the total vote to succeed, as henrikschroder mentions[2].
[1]: https://news.ycombinator.com/item?id=11816921 [2]: https://news.ycombinator.com/item?id=11816784
Comment · 10 years ago
As maxerickson said, this possibility should be covered in the shareholder agreement. For that reason, any shareholder is already responsible for factoring in the risk of a buyout-by-vote when they buy shares. They were already responsible for making their own decisions as to "fairness" of that agreement. No information was hidden before the buyout, according to the article, so no "evening out" should be necessary, as far as I can tell.
Comment · 10 years ago
But all shareholders should have factored in the risk of this situation arising when they purchased the shares, should they not have? The risk of a future buyout-by-vote was always present. This scenario, I assume, was covered in the shareholder agreement?