The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
«When I consider my brief span of life, swallowed up in an eternity before and after, the little space I fill, and even can see, engulfed in the infinite immensity of spaces of which I am ignorant, and which know me not, I am frightened, and am astonished at being here rather than there; for there is no reason why here rather than there, now rather than then.» Blaise Pascal
All day, WookieTab has been slow and unresponsive - trying to even open a context menu in Chrome has been impossible as they show up invisible...
First, I suspect the click on k/b. Nope.
Then, I reload video drivers. It works! Sorted.
Nope, half an hour later and it's back to slug mode...
Just about to reload windows (and VS, and SSMS, and Paintshop Pro, and Libre Ofice, and ...)
Then a quick thought ... what's running? Nothing - I checked earlier ... but ... Task Manager is also running like a stunned slug on mogadons. Hmmmm... what if there is something running, but TM only gets to do anything when it stops?
Startup list has four items:
Corel Update Helper
Windows Defender notification icon
So...one I don't recognise, and three I don't trust
Disable the top three (after checking and finding CleanUpUI is an EaseUS thing and not a virus).
One restart later and all is fine.
Do I care which it is? Nope. Stuff 'em all!
Hate it when that happens...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
This sounds similar to the behavior I experienced recently with Win10, Chrome, etc.
Mine was tied to I/O and I know your wookietab is obviously SSD (or at least some type of non-HDD storage) but still sounds so similar. Win10 Again (sigh) The Lounge[^]
I moved to an SSD and haven't seen any issues since. But I also uninstalled chrome completely (now using Firefox) and I've been too lazy to try Chrome again.
I have actually to implement a wizard for a very very simple "programming language" which supports something about 1% (rather less) of c language. While reading all this stuff about Parsers and CompilerCompiler (also here on CP) I came to the idea to share all my expirience by writing an article about this.
My Immagination about the article:
- A short description what a Parser is doing (my doubts, that this can be described in short)
- Short explanation how one describes a "language" by EBNF (my doubts, that this can be described in short)
- Explain parsing EBNF to generate "the language" Parser
- "The Target Of The Article": How to use the above parsed EBNF to create a wizard
Because the whole path is something recursive (parsing ebnf to create a parser) I have my doubts wheter all this stuff could/should be explained in only one article. On the other hand, should I prescribe the knowledge about parsing?