• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: August 9th, 2023

help-circle

  • I had an ex tell me once that I wore too much brown and dull greens.

    Since then I’ve been aware of my color choices and have a lot of “loud” colors in my wardrobe. I will even intentionally wear clashing colors and have made it a style choice.

    I still have browns and dull greens, but I have fun with them now.

    All that said, I’ll wear something until it starts wearing out then that’ll be relegated to chore/diy project clothes.








  • Firefox had some major memory leaks when Chrome first launched (2008). It became noticeable with the more tabs you had and the longer the browser was opened. This was also during the days for consumer systems with 16GB max RAM & 32GB on higher end enthusiast systems.

    We also have to remeber that this was 10 years before Google removed their “Don’t be Evil” motto, and there was still a great deal of trust that had been earned by tech professionals.

    So when Chrome came in, had a minimalist UI (for the time) and was light weight and memory light without any obvious memory leaks, it was a performance boost for a toooon of users.

    Chrome has since become a memory hog and is now being developed and pushed by a company that has become heavily enshittified & evil. Firefox has become lightweight, memory efficient, and is an FOSS product that’s not evil and enshittified making it the right choice in 2024, but is going to be an uphill battle that hopefully more tech professionals move to as Manifest V3 becomes a reality.


  • I switched off of Firefox because of those memory leaks. I remeber when it hit the tech news circles when the community contributer that was frustrated with them went in and fixed two of the biggest culprits.

    Then I just didn’t bother til somewhat recently. For the most part, it’s great and does what ilI want/need. Biggest complaint is that some UX overhauls are needed for Mobile FX, especially around tab management.


  • Feedback:

    Format your README better. And don’t be a condescending jerk and say “wikipedia is your friend”. If you can’t explain what you’re doing here we’re going to question your solution. You don’t have to write a white paper, but enough to show you actually understand the concept enough to explain it in brief then you provide links to detailed refefences.

    Comment your code. Meaningful names are great, but you should be explaining complex concepts and algorithms within your code. This provides clear intent to people using and maintaining your code if implemented directly.


  • TBH, I never dug into rational wiki. However the timeline is fairly accurate from what I watched what happened to my friends both in the game industry and my former friends that were gamers (hint, i worked in games when this shit was unfolding).

    Unfortunately, no other “timeline” source exists, with Wikipedia starting its paragraphs of history with Zoe Quinn creating Depression Quest, and many many other articles starting there as well. Some people like to attribute a slightly earlier event of a handful of journalists critiquing gamers over their reactions to the Mass Effect 3 ending, but that doesn’t really fit with how quickly things snowballed after “The Zoe Post”.



  • Gamergate started with “The Zoe Post”, not the removal of jailbait.

    “The Zoe Post” is a hit piece from an Ex-boyfriend of game developer Zoe Quinn that alleged that she slept with a notable game reviewer to get positive reviews for her game. Said reviewer never actually reviewed her game.

    Please don’t re-write the history of these events. Especially since jailbait had been removed for around a year when “The Zoe Post” dropped.






  • And the jobs are rarely worth the stress of picking apart the terribly designed, chock full BizDev rushed ads-on features due to foolish promises, and a manager that’s stressed out due to how few experts they’re are that’s going to try and micro-manage you because his skip-level is breathing down his neck about when something is going to be fixed.

    No thanks, not again.