Web Store extensions unfortunately don't work in Ungoogled Chromium. There is a a way around it however. It requires a website that fetches the extension file. Source: about 1 year ago

Yeah, that's definitely a downside to creating Chrome extensions for constantly changing sites. However, you could implement checks that notify you quickly of any breaking changes. I don't have the code hosted publicly on GitHub, but you can use sites like this one to obtain it. The code for this extension is not obfuscated. Source: about 1 year ago

Go to https://crxextractor.com/ and use the link from the downloadhelper download page (https://chrome.google.com/webstore/detail/video-downloadhelper/lmjnegcaeklhafolokijcfjliaokphfk) download the crx and then go to brave://extensions/ and enable developer mode and drag and drop the crx file. Source: over 1 year ago

Chrome extensions are written in Javascript. In fact, you can look at the full source code for any Chrome extension you want - you can find where it's downloaded on your computer (~/Library/Application Support/Google/Chrome/Default/Extensions for Mac) or you can use a website like this to download it. Source: over 1 year ago

P.S. You can always grab the code from https://crxextractor.com it’s a bit messy, but thats my style of coding :). Source: over 1 year ago

It has, but it wasn't adopted by the pragmatists in that time. It's hard to tell if the early adopters adopted it either - It doesn't show up at all in the 2023 stack overflow survey (nor in the previous two years) - https://survey.stackoverflow.co/2023/#technology-most-popular-technologies - It doesn't show up in questions asked on Stackoverflow since 2008 -... - Source: Hacker News / 6 months ago

> In 2017 I had React projects in production for years. I doubt that. React wasn't stable until 2015, and wasn't mainstream until 2016. > And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are faster than React out-of-the-box. Again, Next.js != React; the former builds on the latter, it doesn't replace it nor does it claim to be the same... - Source: Hacker News / 7 months ago

> Prior to Next.js, React was hard to setup and maintain No, it wasn't. > I started using Next.js in 2017. It made React a real production framework In 2017 I had React projects in production for years. > React was hard to setup and maintain and hard to make it go fast (on first load) And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are... - Source: Hacker News / 7 months ago

Based on what? https://insights.stackoverflow.com/trends?tags=python%2Cjava. - Source: Hacker News / 9 months ago

Fair enough, my information is outdated. StackOverflow agrees. [1] [1] https://insights.stackoverflow.com/trends?tags=django%2Cruby-on-rails. - Source: Hacker News / 9 months ago