You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like the first part of your book (and that of each chapter) where you describe and analyze different approaches to the architecture. I agree with most of it and I'm very glad someone on the Internet expressed these thoughts at last.
I also like the part where you describe how to refactor an existing project towards better architecture. This is something new around modern web app books, too.
But the second part where you provide examples and implementations does not fit with the first one.
The code mainly uses approaches you label as bad (globals, no explicit dependencies, no packages).
The server-side is opinionated towards Node.js and npm (surprisingly, not all web apps are built upon Node.js).
The browser-side is biased towards Ember-like patterns where "Ember" is replaced with "Framework", though Ember uses globals all around.
Many of your thoughts on architecture describe better approaches than the modern frameworks provide, so having them as examples of your thoughts is confusing.
Please elaborate more on the architecture part and drop the examples which do not fit into. I would be glad to discuss confusing parts here. Thanks in advance.
The text was updated successfully, but these errors were encountered:
hi @sompylasar, thanks for filing these issues. I'm actually working on a second edition which will address some of these issues - let me know if you'd be interested in an early copy in exchange for some feedback...
I like the first part of your book (and that of each chapter) where you describe and analyze different approaches to the architecture. I agree with most of it and I'm very glad someone on the Internet expressed these thoughts at last.
I also like the part where you describe how to refactor an existing project towards better architecture. This is something new around modern web app books, too.
But the second part where you provide examples and implementations does not fit with the first one.
The code mainly uses approaches you label as bad (globals, no explicit dependencies, no packages).
The server-side is opinionated towards Node.js and
npm
(surprisingly, not all web apps are built upon Node.js).The browser-side is biased towards Ember-like patterns where "Ember" is replaced with "Framework", though Ember uses globals all around.
Many of your thoughts on architecture describe better approaches than the modern frameworks provide, so having them as examples of your thoughts is confusing.
Please elaborate more on the architecture part and drop the examples which do not fit into. I would be glad to discuss confusing parts here. Thanks in advance.
The text was updated successfully, but these errors were encountered: