3 ms·
Am I in some parallel universe here ? We are talking about hundreds of KBs of memory total which is nothing and if it's a worry for mobile devices we have the
by threeseed 10y ago
Am I in some parallel universe here ?
We are talking about hundreds of KBs of memory total which is nothing and if it's a worry for mobile devices we have the disk. It's not a feature that demands instant performance.
- heartbreak 10y ago> It's not a feature that demands instant performance. Hence it's acceptable to request the document from the server when opening 'View Source'.
- gbog 10y agoNo, because when you want to view the source you mean to view the source of this very document, not the source you'd get by asking to reload the page, it is often different.
- sp332 10y agoIf you want to see the page as it's currently being rendered, looking in the developer tools seems more relevant anyway.
- evilDagmar 10y agoIf they wanted that, they'd have looked at the developer tools to begin with. Many of you folks are completely missing the point. The world wide web took off in large part because it was incredibly easy to learn HTML, because with every webpage if one wanted to know how it worked one could just look at the source code. How the page is currently being rendered, what state the DOM might be in... These things do not matter to someone trying to view the source HTML for a page. They're looking to learn about the HTML. They're not goimg to get that by viewing pre-digested DOM information.
- speeder 10y agoOr a website I was trying to fix: the source in view source, and thr stuff on dev tools, never matched each other, even with JS disabled. in the end after days I gave up and the page is in production, crazy bugs and all, because I can't figure why on both chrome and Firefox the webpage end with lots of random "strong" and "span" tags that don't exist anywhere in the original source. The tags aren't even closed properly, some are never closed, some are closed multiple times.
- jmcdiesel 10y agoThats just it... There are edge cases where a bug is intermittent... and is masked by something on the client side, especially possible with browser plugins. In fact, plugins were the cause of 2 of these for me... Where some issue on page load was causing a bug, but then JS was changing the source away from what cased the bug, but a refresh wasn't guaranteed to have the same information (this was a fast changing log-viewer, for one of them) ... So you end up not being able to capture the init state of the page... but the bug wouldnt show up without JS enabled because the error is in the JS... Not common case... but it seems like fetching from the server is MORE work for no reason when the data is already there...
- evilDagmar 10y agoNo it's not, and it's particularly inappropriate for any document being viewed as a result of a POST request.
- EpicEng 10y agoBut who does this feature help exactly? A _tiny_ number of users. Chrome is currently using over 3GB on my machine. Anything they can do to trim that without affecting performance is worth it to me.
- ComputerGuru 10y ago3GB is how much memory the _rendered/executed_ source code takes. The source code is nothing. Store it LZ4 compressed in memory and it's less than a rounding error.
- EpicEng 10y agoYes, I know that, but all of these little inefficiencies add up, and for what? A tiny portion of users who need the developer tools? Not worth it. This kind of thinking is exactly what leads to our software being as slow or slower than that of two decades ago while running on machines hundreds or thousands of times more powerful.