Start From Zero

You probably asking why we use different approach to build a webapp again. Last time we talk about babel, however it is not something I like to stick with. Why TypeScript? I need to solve 2 major problems: Highly maintainable code  Good IDE support I find using Typescript could solve both at the same time while making another prototype, showroom repo :  https://github.com/zeptoTon/showroom It does help on navigating around using VSC when typescript is there. Could there be any alternative solution? Yes, we could use JSDoc and flow  (I haven't try yet) Why Mobx? I feel Mobx  did a great job comparing with Redux. Why? Redux has too much concept with it. One thing I do not agree is mixing Immutable concept into a framework. It is better to do single step at a time. We shall talk about ImmutableJS in later post. Again you should not think Mobx is great because it mix with React!!!!! React is not needed! Why React (again)? I need to p

React - 2017 - web dev Not long ago I was in a conf session which group by a brunch of passionate javascript developer. Somehow I was managed to have conversation with a few of them, some interest finding are they tend to pick the first Dev topic which is related to "React". I am not so sure why it matters to every developer in the room at that moment. My impression of React is 1. Facebook 2. Abstracting the DOM element life cycle Note that I did not put "Fast" as one of my impression. We will come back to that point. Stay with me. Could we try using React in production of HKTVmall Website ? The answer would be NO. Following would be a bit of explanation together with how to make it possible for a YES answer. What if React does not existed? ES6 would not be blending in so quick. (You could use ES5 with react, but it looks stupid to me.) With ES6, I could code faster. However you probably need a bit of time to pickup the beauty, try with Egghead in her

If you are paying huge or frustrating scaling out on your Web Application. Looking for "Cloud Solution", and your Team wish to give a try on Google App Engine. Wait... don't. not until you have learn the following things. What mistakes I made in the past 3 years with GAE ( worshiplace , BioCRF ) have given me a lot to share. Maybe there are more coming lol. 1. De-normalise datastore (ndb) "JOIN" is never gonna work in Google NoSQL Datastore - ndb. In theory, "JOIN" will cost you (in terms of money/quota) a lot. What could you do about it? de-normalise your table. Never do a second lookup will save you a lot(its depends, for BioCRF report generation save ~50% db read). Or you could choose Google Cloud SQL. It is not free, we will discuss that in the next post on "COST" 2. Take advantage on Backend Instances Hours I won't use frontend instance for serval things. e.g. report task, email task. Don't forget there are limitat