One of my frustrations as a web developer is that we as an industry have gotten so bad at doing stylesheets the default behavior for modern web applications is to use shadow root disable the cascade in "cascading style sheets" because people do not know how to properly scope them in their own web pages.
We've basically reverted to the bad old days where styles were defined on each element individually rather than globally, as was the intent of CSS.
I just ended up disabling the shadow root by defining my own custom class that inherited from LitElement. Supposedly this is not recommended because it make composition more difficult but I'm not really concerned about that. If I feel up to it I'll re-enable shadow root, but only for the top-level element(s). I definitely don't need 300 nested shadow roots in my page.
One of the things about getting older they don't tell you about is that when you see someone post a picture of an item and exclaim, "This antique was made 50 years ago! Can you believe it??" you have to constantly remind your brain that they are not talking about the item being created in the 1940s.
Ok, got one important errand done today. Next up I have to get ready to head up to the northern 'burbs to pick up some soda.
Nearby, there is this old brew pub I used to hang out at in the days before I stopped drinking. The building is still there but the owner sold it last year and there hasn't really been any updates as to what has been going on with the place since the new owners took over. So I'm planning on sneaking over there to take a few pictures of the building. 😈
So yesterday I learned that the next-best alternative to Google search (DuckDuckGo) that everyone kept recommending, including myself, is in fact Microsoft Bing with a different skin.
I almost panicked because I just realized I had to book an appointment for an oil change next week, but fortunately it's usually not an issue to find a time slot right after a major holiday.
I just stopped working in a project this afternoon in frustration because of a stupid CORS error and I might need to talk to the architect in the morning to fix it because this application's architecture seems designed to turn even the simplest of tasks, AKA setting up an endpoint in the server to return some key/value store data, into a collosal headache.
I actually don't mind the rain. I'm just hoping that we don't get like a summer's worth of it before June and then nothing for the following three months, just like the last two years have been like.
Just an FYI, I did not get hacked. I replied to somebody with a long CW that originated from the Georgia Humane Society as a joke apparently. When you reply to a post with a CW your post automatically has that CW, too.
That made it look like I was posting a singles ad from my account.
I've deleted my post just in case anyone got the wrong impression.
It's been almost a decade since I've done a live coding stream. This will be fun!
Today I'll be migrating my website from React to Lit, which is a lightweight framework built around web components. I have the scaffolding set up mostly, so now it's time to get this done.
Come watch. Ask questions in chat! You don't need to create an account, just a username is needed to participate.
Ah ha! I figured out why I was having issues with the rollup tool previously. Once I got past that stubborn error, the rest of the comfort was pretty easy.
I think I'll be able to do that technical stream tomorrow. The web page redesign project is a go!
Ok, we're set for a techie stream after lunch. This is different from my normal gaming streams. I won't do a whole lot of talking and will have some copyright-free music playing in the background. Come join me in my adventures in neovim!