[header]Oppai & Ketsu
[size=small]10 January 2017[/size]
[/header]
[block]We've decided to shelve progress on our first version of 2lewd; we were running into some pitfalls and have come up with a better way of going about things.
2lewd is now split into two components:
[size=medium]Oppai[/size]
Oppai will be 2lewd's glorious frontend. Powered by Node.js and Vue.js, it'll be pulling content from Ketsu and rendering it in the browser.
[size=medium]Ketsu[/size]
Ketsu will be 2lewd's well rounded backend. Using Crystal and PostgreSQL, Ketsu will provide a public RESTful API for 2lewd; giving Oppai (and any other third party) endpoints to retreive data from.
It's a fairly different direction to what we were playing with before, but in our opinion, it's definitely a better direction.
There are advantages and disadvantages to doing it this way, here are a few of them.
[size=medium]Advantages[/size]
Should be insanely fast
Will be easier to provide realtime updates to threads, alerts, and other data
Will be slick af to use
It'll be a hell of a lot easier to develop in the long run
Third party tools could be easily developed; looking at you Equinox, with your CLI Lewd.
RX and I can work on Oppai & Ketsu independently, meaning more gets done, quicker. Any lewd fanfics about this will result in a ban.
[size=medium]Disadvantages[/size]
Overall, we're pretty happy with the direction we're heading in, and hope to have this done eventually. We're sorry that this has taken so long, but it's fairly difficult to find time to work on developing when RX studies and I work full time.[/block]
