jrsnyder

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.

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.

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?”

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.

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).

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.

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.

[1]: http://www.datomic.com/benefits.html

Okay, I did not know about this law. Thank you.

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

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.

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?

This is interesting. I have definitely seen a similar idea before, even down to the "six people" setup.

A quick search turned up: https://www.smeeters.com/ http://www.sixr.com.au/ https://www.joingrouper.com/

It would be interesting to know how successful those services have been.

Establishing a public forum for earnest discussion of startup ideas seems likely even more valuable than the actual funding of community-picked proposals. But also, the chance of receiving funding adds incentive for discussion and earnesty!

I'm excited!

In Europe, I noticed that the cell phone shops carry many more small (4 inches and below) Android phones than you see in the US. Unfortunately, these models seemed to have very sub-par specs.

Garmin Aviation | Olathe, KS | Full Time | ONSITE

Aviation Engineering Tools Team

We build server and client tools to support Garmin's aviation software development process.

Our tools help with:

* Requirements management

* FAA auditing

* Code reviews

* Version control

* Avionics software configuration

We work in Node.js and Electron with TypeScript and React. Our older apps are in Java/Swing.

We're looking for a JavaScript/TypeScript developer to help us expand and upgrade our tools. Experience with React is a plus.

Apply at http://careers.garmin.com/en-US#1600004. I'm at [email protected].

What is the French approach?

Wow, both of these look really cool! I'm glad to see the database + friendly UI category is getting some reinvigorated attention.

Last time I researched this category, the best options I could find were MS Access and FileMaker Pro. I'm often annoyed with overly use-case-specific apps, as they do not have good flexibility in interacting with the data they use. It seems like many use-case-specific apps would be better suited as templates in a generic database UI tool.

Chris Granger's Eve is also tackling the database UI problem, and they are investigating wider-scoped UI patterns, beyond spreadsheets.

As others have said in this thread, the bottleneck of solving epic problems is solving social problems. The bottleneck of solving social problems is coordination of individual behavior; cooperating.

As far as I can see, the bottleneck of social coordination is information transfer, especially information transfer towards facilitation of trust.

Solving epic problems usually requires making long-term investments. I think many individuals would make more long-term investments towards solutions to epic problems if they were able to establish more trust in the cooperative behavior of other individuals.

I think it comes down to counteracting the dilemmas studied in game theory. I think there is opportunity to leverage software and the internet to create new/stronger information flows that can more often raise us above the pessimistic equilibrium of game theory dilemmas.

Despite the increasing ubiquity of internet-connected hardware, messaging systems, and search engines, I think there is still a lot of opportunity for tech-trained people to improve and build information systems that provide key information to key places in support of social cooperation. Software and the internet has made information flow a lot more liquid, but there is still a lot of opportunity to improve query-ability of data sources, and improve the value of information propagation across communication networks.

Ultimately, we can seek to increase cases where an individual changes his/her behavior, due to trust in other individuals changing their behavior.

The "Top 10 Cities for Social Mobility, Ranked by Affordability" graph suggests that the affordability drop is extremely sharp, but as we can see from the "Percent of Homes Millennials Can Afford vs. Social Mobility" graph, Absolute Mobility remains fairly steady for a number of cities beyond the top 10 cities. Cutting off at the top 10 makes the affordability vs mobility tradeoff seem more severe than it is.

Could you elaborate on the supply of quality VCs? What are some examples of high quality vs low quality VCs? How would you suggest ranking different VCs? Do you have any rough count of quality VCs in the top 3 cities?

Cool! I was just thinking about building something like this myself, after reaching the point where I save almost everything I read to Diigo, just to get searchability.

It just means precalculate a small number of fixed screen sizes.

So portable devices, and maximized desktop browsers would benefit, as they have regular dimensions.

I imagine they would precalculate the constraint "solutions" in the variables used inside the solver. GSS would still be supplied, and would still need to translate the solver variable values to CSS style values.

This way, if the window resizes, or has an initial size that is not precalculated, it can still be accommodated.

The fact that someone thought this was necessary emphasizes the amount of problems Google has with user experience design.

I definitely agree with you on your spatial memory explanation.

There are so many applications out there trying to come up with new digital ways to record / access information, but almost all of them discard the spatial organization tools we have in physical workflows.

When you are trying to use information in your head (the most important stop in a workflow), you often need to build a lot of organizational structures in order to make the information maximally accessible from memory. Spatial "shuffling" is one of the quickest ways set up informal organizational structure. It makes use of our brains' good memory for spatial locations, compared to our brains' memory for abstract concepts.

In order to use spatial shuffling to organize information, you need to be able to place things freely, and have them stay there. Digital applications so infrequently offer this ability - they do not allow informal organization or spatial organization.

In an application, pieces of information are usually laid out according to a well-defined sorting algorithm. Layout-by-algorithm breaks both your ability to place a piece of information freely, and your ability to find a piece of information by location (because a new piece of information could shift the whole layout according to the sorting algorithm).

Seconded.

The whole article is behind a paywall, but the first paragraphs have the base facts.

Garmin's post here: http://garmin.blogs.com/pr/2013/11/victory-for-garmin-in-fir...