Over the last 18 months I have bootstrapped my startup using SailsJS. What did I learn? What do you get out of the box? How has the project evolved? Am I happy with my choice 18 months later? I have previously used Rails, ASP.MVC and Laravell. I had decided on Node for the backend - but what framework would I choose? What do I really need? What can I trust? How does SailsJS differ to the aforementioned frameworks and how much bang can my buck get?
Hi I'm Simon, physics graduate, software engineer, team lead and now technical co-founder of Kiffgo.com. After previously working at a consumer facing marketplace startup I teamed up with a motivated co-founder to create my own. As the technical co-founder I had some stack decisions to make. I arrived at Node + SailsJS. From webpack integration, unit testing to production deployment I've done it with SailsJS and am willing to share my experience. I've been to LNUG a number of times in the past and have always found it a friendly, welcoming and informative experience.
About me - I'm a technology enthusiast, working for a consultancy by day, and enjoying myself with open source by night. Here's my blog if you want to find out more about me! I'm a keen WebAssembly enthusiast, I run WebAssembly weekly and did quite a few 'scene setting' talks on WebAssembly last year.
For this talk I want to do something different, delving into the details of what WebAssembly actually is, through the process of creating a compiler that targets WebAssembly.
I'm actually giving this to at FullStack NYC in May, so would really love the opportunity to do this talk in April as a bit of a rehearsal. It will also help me avoid the usual, last-minute rush to get the talk finished!
I can fit this into a 20min slot, and I confirm that I will abide by the Code of Conduct