10
BroCow
4y

Used sails js for production

Worst decision in my life made me loose 1500$

Fuxking shuld have used laravel....

Comments
  • 0
    What's the problem with it?
  • 1
    Unpredictable Bugs .... had to go through the framework source code, to fix them temporarily.

    Community sucks,
    Waterline ORM is very bad
    Ur data gets vanished
  • 1
    Why exactly did it cost you 1500$?
  • 1
    @BroCow back in the day, when I was in a team using sailsjs, waterline was removed for sequelize. Gotta fix a hook (in their repo) for M-M relations myself. We faced some problems as well
  • 1
    @lostpirate never going back to nodejs for web development again..

    Going to check out phalconphp as @artemix said

    @cr78 the client company asked for refund and damage cost
  • 0
    Thank u for the info @artemix
  • 0
    @khadez php is very good actually i could run multiple server in a single instance... without hassle
    Also dont have to transpile or restart the server every time u make a change
    And for an sqlite backend db .. php 7 is enough i think.
  • 0
    Just found this, thought to share it here

    https://twitter.com/simongarm/...
  • 0
    You shitting me? I’ve been trying to pick between sails and laravel for this new project. I prefer node over php any day but do you think sails still having major issues in 2019?
Add Comment