2 ms·
Do you think making it more open source would solve the issue? Thin is mostly based on IHP DataSync. You can the source code here https://github.com/digitallyi
by _query 4y ago
Do you think making it more open source would solve the issue?
Thin is mostly based on IHP DataSync. You can the source code here https://github.com/digitallyinduced/ihp/blob/master/IHP/DataSync/ControllerImpl.hs https://github.com/digitallyinduced/ihp/blob/master/IHP/Data... Thin itself is just a "thin" wrapper around IHP and IHP DataSync.
Additionally most of the system is just relying on postgres for doing it's work. So if you ever want to swap out Thin with another API, you could build a normal REST API, connect it to the database and switch it out.
- tomatowurst 4y ago> Do you think making it more open source would solve the issue? No is not what I'm arguing for here but you highlighted my concerns here, I see two points of failures/blackboxes that I am now betting the house on vs the "problem" mentioned (having to create API/Redux layer). As I said, this might be an issue for indie/small startups looking to create an MVP but more often than not, you would want to optimize for hireability and removing the implicit. It would be tougher to find an Haskell dev compared to "boring" full stack devs, and this is just the start of the problems.