You can use cdn for any static file. Can be: any bundle build with webpack or other tool any js lib, module, your files, which you use (what you mentioned already) any css file (what you already do) any image (you also do that) any audio any video any HTML page for example if you build SPA you can use cdn for main page with main scripts and basic html literally any file used in your app, which is not generated dynamically by your backend But think it through. You do not want to put on cdn anything what need restricted access. Also it can be costly... For any dynamic content or data from API or DB use some cache. Cache will be "local" not spread around world like cdn, but you can build something on your own... For example use cache for http requests/response (like varnish) . You can duplicate such cache on multiple data centers in different regions. It will require some additional work to keep it consistant and up to date... CDN will speed up your page in context of network communication, but there is much more, what you can do, even in network context for example use http2, minimize files and use bundles like webpack, use "smaller" images (for example use webp instead of jpg) , optimize image (for example remove all metatags), use gzip with http...

Some time ago we used local storage on servers. It is ok as long, as you would not keep many files. It can have some security advantage, if you have good security team. Biggest issues are disk space and network capacity. In many apps we need to restrict access to files, so we do not put files on public, but process request through php/node/python/etc. and return file as response if user has access to it. For us it was easier to keep such files on the same server as app… But we had problems with disk space. When we use the same server for media and data processing, you can do less, because some of your resources are used for media transfer… For few years I avoid local storage. So you can create your own file server, but why you would do that? Only reasons which come to my mind are: security and full control over storage. But there is always some solution for example if you need to set some access restriction, in many cases you can restrict access to storage and use APIs to get files and process them within your app. Right now, when we build simple page with few images, we put image in public and use some cache… But In most cases we use amazon S3 (we use AWS a lot...). If you build social media website consider some 3rd party storage. If you need it only for image consider some service build around images like https://cloudinary.com (they have not only storage and cdn, but also lot of good stuffs like auto resizing/croping, dynamic resize/crop based on url etc.) Remember also about some cdn and cache if it is not built-in. The biggest benefits of 3rd parties are: elastic storage bigger network capacity in many cases built-in cdn more resources for data processing on your server you do not need to take care of infrastructure for file storage There can be some legal problems, so you need to consider how image access should be restricted, how they are secured, in which country physical servers are etc.

Right now two books at the same time: "Betrayer" form Horus Heresy Series written by Aaron Dembski-Bowden "Machine Learning for OpenCV" By Michael Beyeler Next: other from Horus Heresy Series... Well I even made goal for this year to read more novel than IT books ;P so...

Ok, sure maybe wrong choice of words, not "overlooked" more like "underestimated". If you compare "comments" to other subjects... Also, when I try to discuss comments with developers, discussion is short - people focus on other things like "why to use framework A or B" or even “use tab or 2 spaces"... I worked with different developers and many times, there was no comments in code, or there were too many comments (because code was bad) and that is what I'm writing about. We should use comments but for good reason... Sure "code smell" is maybe too generic, but my intention was to point that sometimes you do not need comment, instead you can write good code, so sorry for that "cute but useless" expression ;) "The value of comments in code varies in a number of ways." I absolutely agree. "The unqualified claim that code should always be self-documenting is silliness of high degree." Sure, also agree, but still code should be clean and readable. If you use language, which give you possibility to write such code, you should at least try. In tags for article I used javascript and php, examples are based on php and js. I also never claimed and never would claim that "code should always be self-documenting" because it is impossible. I even said that comment should be used as documentation for code. So, I agree with you (again ;) ) As for me, I also like comments in code, but I also like good and clean code (yep, again very generic expression). If there are too many useless comments, code become unreadable. Bad comments are like bad code ;) I said when and how I prefer to use comments, but in most cases it depends on team which I work with and languages which we use. You should always discuss "comments" as part of project guidelines, the same way as you discuss other tools e.g. test framework, language, database, linting etc. I'm repeating myself, sorry for that. I just want to thank you for comment and I agree with you (or you with me, if we take your comment as response to whole article)

First computer, which was in my room, was Macintosh Performa 520 with MacOs 7. It was not first which I've ever used, but first "own". Now I use Windows and Ubuntu.

I believe both will be used for some time. It is possible that Laravel will "die" faster. Node is runtime for JS so it has to offer lot more than Laravel, so as long as any node framework is used, that long node is used. Laravel on the other hand is PHP framework, and frameworks has short live compared to languages/run times etc. Laravel is great and is supported by many, has full ecosystem what make it perfect for me... I use both and I hope both will be supported for a long time ;)