Comments by "Mikko Rantalainen" (@MikkoRantalainen) on "" video.

  1. I read the article as a long list of interesting debug/profiling tricks which may help with more complex projects.
    4
  2. 15:20 It would make sense to have no LTO while you're developing the site and once you're happy with the results (e.g. end of the day), generate one full LTO build which may take 4–10 minutes for complex set of dependencies to run at full speed. Even if you only have small amount of users, every one of those users will have better experience if you can reduce the latency by using full LTO.
    2
  3. 36:10 For a real web site, you hopefully have development server separate from production server. In that case, you develop your code on the development server and use all the "make the compile time faster, never mind the runtime performance" optimizations you can come up with. And then you release the finished code (for a day?) to production server with full build time to enable every possible optimization. The important part is that you can compile the same source code fast for development and still get great runtime performance on production. As a bonus, when you get acceptable performance for the web site on development system, the end user performance should be at least acceptable in every case. The way I think this should be implemented is to dedicate the "release build" to the real production server config and use debug builds for development and debug builds have default config to build fast and sacrifice everything else.
    1
  4. The insane amount of dependencies is just a result towards the "no code" movement. The ultimate goal seems to be that you don't write any code, you just list a huge list of dependencies instead. I still have no idea how you're supposed to debug such a beast, though.
    1