I can't say I find this to be a problem for development, but I still bash on tech interviews. Mainly because the knowledge base required to solve an interview is vastly different from the knowledge base you use in your everyday job.
As a teenager I was memorizing PHP function parameters for fun and I rarely had to jump to the docs. Even now that I have a family and my brain doesn't want to work, I rarely reach for GO or SO to do something. I mainly rely on static typing and jump to definition in the IDE.
Every once in a while I forget something stupid (eg. I forgot how to floor in JS once and I was stuck with either doing >>0 or google how to Math.floor) but I can't say I would want to store this kind of information anywhere: It's too sporadic and it's incomplete; just keep the documentation of the tools you're using nearby if you need it.
That said, I see the benefits for KB and I use them all the time.
I agree with you, doing it in the browser won't change things much.
As a teenager I was memorizing PHP function parameters for fun and I rarely had to jump to the docs. Even now that I have a family and my brain doesn't want to work, I rarely reach for GO or SO to do something. I mainly rely on static typing and jump to definition in the IDE.
Every once in a while I forget something stupid (eg. I forgot how to floor in JS once and I was stuck with either doing >>0 or google how to Math.floor) but I can't say I would want to store this kind of information anywhere: It's too sporadic and it's incomplete; just keep the documentation of the tools you're using nearby if you need it.
That said, I see the benefits for KB and I use them all the time. I agree with you, doing it in the browser won't change things much.