The way I look at it, I will not switch frameworks just because the web community says so. I will switch only when the current framework is causing issues (loss in productivity, stability issues, performance issues etc) and most importantly how does it better solve the problem your application was trying to solve in the first place. IMO, code, programming styles, frameworks (js or server side)and IT in general needs to align with the problem its trying to solve. Just changing because the community thinks its cool is for the birds.
Ask HN: How to write a web app that will outlast the latest JS trends?
21–23 of 23 posts
Re: Ask HN: How to write a web app that will outlast the latest JS trends?
#22Earlier quoted context omitted.
Yeah everything was in house. I can't remember how I came about my build solution, but it works amazingly well. If I do a quick find on my JS code base, I see that I have 343 JS files, which is spread over 44 directories. It's a bit involved to explain how it works, and I probably should do a blog post to explain it in detail. I'm pretty sure the solution that I have is what other big JS code bases uses, but I could…
A blog post would be great -- I really like lightweight dev processes. Do you use map files for debugging unminified JS?
"Do you use map files for debugging unminified JS?"
No its even simplifier than that, and it has to do with how the browsers JavaScript engine reads the JS files. Well at least modern browsers. When I generate my html file with the include JS lines, I make sure to put the minified version first, then the unminified files to debug.
If the unminifed version contains the same function, the browser will use that instead of the minified one. So when an error comes up, the browser will point to the unminified JS file in the stacktrace.
Re: Ask HN: How to write a web app that will outlast the latest JS trends?
#23Earlier quoted context omitted.
A blog post would be great -- I really like lightweight dev processes. Do you use map files for debugging unminified JS?
"Do you use map files for debugging unminified JS?" No its even simplifier than that, and it has to do with how the browsers JavaScript engine reads the JS files. Well at least modern browsers. When I generate my html file with the include JS lines, I make sure to put the minified version first, then the unminified files to debug. If the unminifed version contains the same function, the browser will use that instead…
Oh that's really interesting -- thanks for explaining it!