• 1 Post
  • 31 Comments
Joined 1 year ago
cake
Cake day: January 9th, 2024

help-circle

  • You mentioned a buzzing in another reply. That sounds like a grounding issue to me. Any chance you blew something under the board that is causing a short? At this point it would be wise to do a full tear down.

    I’m almost at my train stop, so one final question before disappearing for the day: when resocketing the CPU did you put it in correctly and was there damage when you removed it initially?











  • Forking is indeed the way forward when Mozilla loses its way a little more. For myself, I switched to Librewolf about 6 months ago, along with replacing Thunderbird with Betterbird after using it since the Phoenix days.

    I cannot remember what prompted the move to Librewolf, it may have been the AI stuff they were pushing at the time, or possibly the update that forced the tabs into my titlebar without having to go into about:config to fix it. Or the fact that Firefox was constantly pushing me to sign up for an account. There were quite a few gripes that added up over time lol

    Betterbird restored some removed things I liked pre-supernova as well as a native systray icon under Linux and that was enough motivation to make the switch.

    It is time for a new browser to enter the market. Either Ladybird or something built with Servo seems likely.








  • I think about a feature or bugfix that I want to work on, then shoehorn it in by any means necessary. Once my code is confirmed working, the planning phase begins and I go through the module(s) I’m working with line-by-line and match the original author’s coding style and usually by that point I pick up a trail or discover a bunch of helper functions/libraries that I can use to replace parts of my code, and continue from there.

    As others have said, configuration files is a great way to learn that. Pick a config option you want to learn about, jump to the config loader, find where the variable gets set, then do a global search for that function. From there it starts to fall into place.

    Sidenote: I also learned rust this way. It took me around 6 months to learn the rgit codebase solely from adding features that I wanted from cgit. Now I’m at the point where rebasing from upstream to my soft-fork doesn’t mess up any of my changes, and am able add or fix things with relative ease. If memory serves, a proper debugger (firedbg is excellent!) was used on several occasions to track down an extremely annoying and ambiguous error message that was due to rust’s trait system being a pain in my ass.