|
Bruegels Fuckbooks posted:honestly, maybe there's really a use case for doing something like that (like having to support IE8 or some other bullshit), but talking about pre-rendering javascript on the server to "improve performance" is a big sign that I'm going to have to throw out the project and start from scratch - up there with "javascript caching and data layer." Both are signs that you have old people trying to do front-end work. Uh, pregenerating the HTML for the initial page load (instead of just sending down data and having it generated client-side) is a totally worthwhile thing to do for reducing page load time. Unless by "old people" you mean "people who care about performance" or something? (Your users care about performance. This is objectively measurable.)
|
#
¿
Feb 26, 2015 14:12
|
|
|
|
| # ¿ May 10, 2024 00:55 |
|
|
Even with semantic versioning, you should be releasing to prod the exact same configuration you QAd. Even for a patch release of a library, your app could have been inadvertently relying on a bug that the patch fixes, and now you're suddenly broken in production. Semantic versioning just tells you what you can expect to upgrade as a matter of course when you start your next release cycle, vs. what you're going to have to budget time in the schedule to upgrade to.
|
|
#
¿
Aug 16, 2015 05:06
|
|