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.
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?”
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.
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].
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?
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!
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.
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.