Jump to content

basilisk-dev

Member
 View Profile  See their activity

  • Posts

    53

  • Joined

  • Last visited

  • Days Won

    6

  • Donations

    0.00 USD 

  • Country

    United States

basilisk-dev last won the day on March 15

basilisk-dev had the most liked content!

About basilisk-dev

Profile Information

  • OS
    none specified

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

basilisk-dev's Achievements

152

Reputation

  1. basilisk-dev
    I am wondering if in this PR: https://repo.palemoon.org/MoonchildProductions/UXP/commit/e10d75b7c266c30769ecac71fd8b890c6db7c47b Maybe I should have used return cpuCount instead of return threadCount. It is hard to diagnose this on my end because I am not able to replicate it on Linux or Windows 10 in upstream Basilisk either.
  2. basilisk-dev
    Yes. https://repo.palemoon.org/MoonchildProductions/UXP/pulls/3040
  3. basilisk-dev
    Yeah, they were intended to. However some of them actually hurt performance. I believe that he is just vibe coding with an AI tool for most of his changes and is not actually a developer. I can't verify that but that is my theory.
  4. basilisk-dev
    The Python 3 changes support Python 3.6 and above. I'm not sure what version of mozilla-build you use, upstream we are using mozilla-build 3.4 which ships with Python 2.7 and Python 3.6. I don't know if it will install on Windows XP, but I know for sure it will install on Windows 7. Most of his "performance improvements" code outside of restoring e10s actually make the browser slower according to benchmarks. He did import some newer WebExtensions support so you might want to merge that.
  5. basilisk-dev
    As long as the application runs in the Windows 2000 extended kernel you do not need to directly support Windows 2000. For example, Roytam's browsers work on Windows 2000 with the extended kernel even though he does not target Windows 2000.
  6. basilisk-dev
    Software can be open source software while not meeting the definition of free software. For example Unreal Engine and the unrar CLI tool on Linux match this description. I want to make it very clear I did not support the Pale Moon team's actions at that time and I had absolutely nothing to do with that.
  7. basilisk-dev
    Basilisk supports all of these. We started supporting PowerPC Mac OS X in the last release. We have released GTK2 binaries since I took over the project.
  8. basilisk-dev
    I don't think that anyone involved with Pale Moon or upstream UXP development hates Feodor2. That was mostly Tobin, who is no longer involved with Pale Moon or UXP. I have no opinion on Feodor2. If Feodor2 decided to continue development of Centaury I would not care.
  9. basilisk-dev
    Upstream issue submitted: https://repo.palemoon.org/MoonchildProductions/UXP/issues/3001 It was caused by the second link you posted.
  10. basilisk-dev
    I have seen PowerFox and talked to Jazzzny about it a little. Hadn't seen Machfox until you mentioned it, that is pretty neat. I do worry that I am taking away reasons to use PowerFox by releasing 10.5 PPC binaries of my own, but we have the PowerPC support in the tree so I might as well use it. I had a hard time sleeping last night and thought about it. We don't necessarily have to modify the CSS parser. We just need to de-nest the CSS before the parcer receives it. I have a proof of concept that fixes a bunch of sites using nested CSS, although it isn't 100% compatible with all nested CSS sites yet.
  11. basilisk-dev
    Yes this will get implemented in UXP at some point but I don't know how to implement it yet. It's not like I can snap my fingers and UXP magically has support for it. It takes time to research, implement, test, and verify there are no regressions or crashes as a result of that implementation. That implementation affects the CSS parser so it will literally affect how UXP reads the CSS for every single site on the web. Even if we had an implementation it would take A LOT of testing before we'd feel comfortable merging it in.
  12. basilisk-dev
    I think you misunderstood something here. Web compatibility is my number one priority right now. I already said that earlier in the thread. Basilisk does not, and will never, require AVX for release builds.
  13. basilisk-dev
    That would be a very large amount of work. I understand why users want it but at the moment it isn't anywhere near the list of top priorities. Personally, I view the lack of DRM in the browser as a feature and not a bug, but I could see why other users might not feel this way. Is it something I want to implement? Yes. Am I going to do that? Not any time soon.. If I did do it, the implementation would be Manifest V2 only because Manifest V2 is a stable target and a lot of Firefox WebExtensions still use Manifest V2. For example, the Firefox version of UBlock Origin uses Manifest V2.
  14. basilisk-dev
    I haven't taken a look at how to implement this in our codebase yet, but Mozilla's implementation is written in Rust unfortunately so we will have to do a new implementation from scratch. Happy to work together with you to get an implementation figured out, you need this for your XP builds just as much as we do upstream. I have no idea if Moonchild Productions is just Moonchild or if there are other UXP/Pale Moon contributors involved in Moonchild Productions as well. I've never asked. In my case, Basilisk Development Team is just me because nobody else seems to be interested in contributing to Basilisk outside of the occasional PRs from other UXP developers to ensure breakages don't occur after UXP updates.
  15. basilisk-dev
    Eventually I will look into it if no one else on the UXP dev team steps up to try to look into it. I did read last week on the Pale Moon forum that someone was writing a XUL extension that un-nests nested CSS, but I can't find the post right now. Right now my priorities are: * Full ES2023 compliance (eventually 2024/2025 but now ES2023 is priority) * Make Tailwind v4 playground render correctly (this will fix a lot of sites not just sites using Tailwind) * Performance improvements * Make WebRTC actually work with modern services * Fix any other sites that I find that are broken If I am being completely honest with you, I have been a bit frustrated because I have felt that the other UXP developers have prioritized things other than site compatibility, and that those other things they are prioritizing are the wrong things to prioritize. I frequently see forum posts where users are told that the CSS or JS feature a site uses is bad and that the user should email the site asking them not to use those features because they are bad. Users don't and shouldn't have to do that. People don't care about what CSS or JS a site uses, all they care about is that the site they want to use is broken. They'll just go use another browser instead. Due to that I've been learning C++, learning how our JS and CSS engines work, and I'm doing what I can to change that in order to keep UXP/Basilisk/Pale Moon/roytam's forks relevant.
×
×
  • Create New...