holon

I much prefer frameworks like Adonis (https://dev.adonisjs.com/docs/4.0/installation) - it feels a lot easier to just strip out what I don't need from an MVC framework, than to end up rebuilding 90% of the same functionality from a bare-bones Express / Koa application.

Netflix announces which content will be added/removed months ahead of time. The decision to remove content is driven primarily by the principal right holders - Netflix is largely just "leasing" the shows that it presents (hence the company's shift to producing its own content).

To present it as a decision solely made by Netflix grossly underestimates the contractual complexity and involved parties responsible for turning a screenplay into something you can stream in 4K, all of whom have ownership stakes to lesser or greater degrees.

I've used both Knockout and Vue for frontends that needed to render reasonably large amounts of disparate elements with near real-time updates, so I think I can answer this. Knockout is nice but feels closer to jQuery in that it requires a lot more discipline on the behalf of the developer to organise and maintain code. Things like ObservableArrays means dealing with another layer of abstraction; the wonderful thing with Vue is that it's just native JS objects all the way down. It also has a better structured child/parent component model with event flow, not to mention being much faster for rendering. I would also recommend Vue over Knockout.

Consensus is the main hurdle - if you have multiple nodes that can be read from, then any values that are successfully written to the system must guarantee that those same values can be read sequentially.

Issues arise when network partitions interrupt communication between nodes; even if you require all nodes to send acks when writing, how do you deal with those acks not being received?

Tried Tinder as an experiment. Hated it. I would prefer to base my approach to online dating on personality rather than a single profile picture. The entire Tinder experience is incredibly superficial and facilitates hookups rather than actually meeting interesting people.

I see web-based dating platforms as something that will always have a userbase.

Looks like an interesting project. I'm not entirely sure that you're prioritising the right information though - almost all of the text on your site is about Haskell / the technology stack you're using; but for a CMS, most people care about the admin UI / features and how they simplify the process of managing a website's content.

I think it'd be useful to show some screenshots / examples of how it works, in order to immediately engage potential users, and then lead on to the benefits of using Haskell etc.