Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Technically to be more similiar to a power off it should be
"have you tried to close your browser and open it again" -
@Hedgepig of couse, but close and open are more similiar to turn off and turn on.
-
@shelladdicted I guess, though I was more making a point about the mantra pertaining to the solution of what seems like 90% of the problems we face as web developers.
-
@Hedgepig i know, that is why i used "technically" ;-)
Anyway i think the other 10% is caused by chrome and IE/Edge.
;-) -
@shelladdicted yeah we're splitting hairs really aren't we.
No doubt! I use Linux haven't event tested my app in IE/Edge, I'm in for a shitstorm -
@Hedgepig the problem is not where YOU (as dev) test your work.
But where the CLIENT use your product. -
I mentioned cachebusting above
For those that don't know, this involves "versioning" for JS/CSS files
For development, I set the version number to the Unix timestamp
E.G. style.css?v=XXX
There's also an option in Chrome developer tools called "Disable cache while developer tools is open". A fantastic feature! -
@itsdaniel0 I'm guessing meteor (and other frameworks will do this automatically. I have never had an issue with the cache
Ironically enough -
To avoid being caught by this, I installed Canary next to stable Chrome and made it so it only opens incognito and obliterates everything when it shuts down.. Just to be safe.
The Web developer's equivalent to, "have you turn it off and on again":
"Try clearing the cache"
undefined