Slashdot Mirror


Pale Moon Devs Ponder Dropping Current Codebase And Starting From Scratch (softpedia.com)

An anonymous reader writes: The developers of the Palo Moon browser are thinking of scratching their current codebase due to the fact that it doesn't support many of today's current Web standards, and because future Firefox plans will introduce incompatibilities within its codebase. The team plans to build a new browser from scratch, which they'll use to replace Pale Moon when it reaches a stable version. As with the old Pale Moon, the browser will keep Firefox's pre-Australis interface and still support many features removed in Firefox, like Tab Groups and full themes.

76 of 167 comments (clear)

  1. interesting and I wish them luck by Anonymous Coward · · Score: 1

    Cuz that's a damn crazy undertaking

    1. Re:interesting and I wish them luck by Aighearach · · Score: 2

      This will reduce the amount of work needed, not increase it.

      Firefox has a lot of constant code thrash, with a bunch more already scheduled in the future. This is a great move, because they'll be selecting a single interface and feature set and then they can target that directly, without code thrash. Also then the code structure has enough stability to really improve over time, something that doesn't happen if new code is replacing all the old code, instead of just adding to it or fixing bugs.

    2. Re:interesting and I wish them luck by Great+Big+Bird · · Score: 1

      Is this the by product of having so many updates so quickly?

    3. Re:interesting and I wish them luck by Aighearach · · Score: 2, Interesting

      Yes. If you don't update... you don't have code trash. :)

      IMO the goal should be to stop needing to make changes, except for bugs or to interface with new protocols and formats.

      Why should a user application have more code updates than a C compiler, or an OS kernel? It seems like they should just "get there" at some point.

      Emacs isn't getting constant code changes; neither are most other programming environments. They're already stable. Gimp doesn't experience code thrash. If I had a user shell that was 10 years old, I wouldn't even notice. Most of my media viewer applications are over a decade old, with new codecs and formats added. I could run a window manager from the 90s, and it would still work.

      Of course in the context of the story, they're just re-forking to avoid backporting code thrash. So, they get to skip a bunch of versions. They'll have to do it again in the future, because firefox isn't going to stop thrashing.

      I'd prefer a finished interface, and a new rendering engine version every 5-10 years.

    4. Re:interesting and I wish them luck by serviscope_minor · · Score: 1

      Why should a user application have more code updates than a C compiler, or an OS kernel? It seems like they should just "get there" at some point.

      Get where?

      There is no "where" for a web browser except perhaps for good support for ad-hoc and official web standards. But since they are continuously undergoing standards thrash there's no chance for any browser to get there.

      I'd prefer a finished interface,

      I've come around to like the new firefox interface. I use the classic theme restorer, since the curved edge tabs look ugly as sin on my setup. I don't expecially care for the menu pictures rather than words but whatever. I do appreciate the space saved on not having a menu bar I never used. I disliked it to start with, but especially when I'm on my 1024x600 screen, it makes a pleasant differece.

      and a new rendering engine version every 5-10 years.

      You'd prefer a rendering engine that doesn't support a significant number of new websites?

      --
      SJW n. One who posts facts.
    5. Re:interesting and I wish them luck by Anonymous Coward · · Score: 1

      That is an interesting thing that I noticed in the Foxit forum recently.
      When they decided to permanently remove the option to switch away from the ribbon mode a lot of the users got irritated. (Let's face it, people switched to Foxit to get away from Acrobat, not to get another bloated copy of it.)
      What became fairly evident is that those users like to keep old version of software around.
      There was comments along the line of "I installed the 5.x version because that is that last version that does what I want.".

      At some time in the development cycle a piece of software should reach a point where it is called finished. Where it doesn't need updates without becoming obsolete.
      A software shouldn't hog its developers indefinitely. They need to move on to new projects too, without the old software being left broken.

    6. Re:interesting and I wish them luck by johanw · · Score: 1

      At least you don't have to re-fix them when a new version comes out. :-)

    7. Re:interesting and I wish them luck by Aighearach · · Score: 1

      If you can't find where "there" is, I'm not even convinced you care about using the tool, or how it functions.

      Why would I value your comments?

      As for your strange claim about rendering support... actually fuck it, in light of your above lack of interest, and the lack of correct quoting, not gonna bother. You're wrong, done.

    8. Re:interesting and I wish them luck by cfalcon · · Score: 1

      It's not old fashioned though. The thing you are complaining about- loading tons of executable code on the destination machine- is absolutely horseshit. It's terrible at every level, and the majority of it is used to track, advertise, and shut down known good interfaces. And the result is poorly written content whose entire point was to get their code to run on your machine. It's absolutely awful- that's not an old fashioned opinion, it's a fact.

    9. Re:interesting and I wish them luck by mikael · · Score: 1

      Web browsers are built on hundreds of standards. They need image file loaders (bmp, tga, tiff, gif), audio codecs (mp3, mp4, wav, ogg vorbis), video codecs (mpg, mp4, wmv), fonts (freetype, truetype TTF), the official support for HTML ... HTML5, and all the other languages CSS. There are the internet protocols specified by the RFC's (ftp, http, telnet). Then there is internet security through encryption with SSL. Each of these libraries depends on other API libraries, even OpenGL and OpenCL for WebGL, X-Windows and Gnome/KDE for Linux.

      All of those libraries are fixing bugs, refactoring code, creating interface layers, internal engines, adding caching, improving compression, reducing file IO. Every time someone removes or renames a function, or changes the way objects are created and manipulated, that causes a code thrash ripple that works it's way through the entire library dependency chain. Even adding a new rendering method to speed things up (using OpenGL texture for fonts), or Framebuffer Objects for offscreen rendering will cause a domino effect as every other layer takes advantage of that feature. Users with high-end systems seen their browser running faster. Users with old system, see their browser running slower and sucking up more memory.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    10. Re:interesting and I wish them luck by mikael · · Score: 1

      >UI changes: people hate them, especially radical irrational ones (idiotlogicallly driven?).

      No, just familiarity. Users aren't interested in playing puzzle games when they are working. They just want to get their work done as quickly as possible.
      People get annoyed when the supermarket rearranges the placement of items in the aisles. "Drinking straws? Why aren't they beside the soft drinks? Oh they're up beside the party items like napkins and cake decorations." "Where are the tinned peas? What? They've been moved beside the tinned products section? They used to be beside the vegetable section".

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
  2. Uh . . . No by Anonymous Coward · · Score: 1

    ""This re-forking would be done on the last stable version of Mozilla code that hasn't had a sledgehammer put to it yet"

    And that would be . . . Firefox 24 ESR, the version that Palemoon is based on.

  3. things you should never do part 1 by Anonymous Coward · · Score: 2, Interesting

    sounds familiar
    http://www.joelonsoftware.com/articles/fog0000000069.html

    who needs another browser anyway?

    1. Re:things you should never do part 1 by Hognoxious · · Score: 1

      I would reword your last item and put it at the top.

      0) It's a pile of shit.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    2. Re:things you should never do part 1 by Dutch+Gun · · Score: 5, Insightful

      sounds familiar
      http://www.joelonsoftware.com/...

      who needs another browser anyway?

      Just to be clear... this is not Pale Moon writing their own web browser. This is Pale Moon reforking from a newer Firefox branch and reimplementing the features that distinguishes them from Firefox. So, the article and summary says "from scratch", which is misleading because it's not "from scratch" as most people understand the term (writing a new browser yourself from the ground up), it's modifying the newly branched Firefox code, adding their own new features or stripping out crap from Firefox. It's the Pale Moon features only that would have to be rewritten "from scratch".

      Joel's advice doesn't account for this scenario, in which you're building new code on top of an existing forked codebase that is lagging behind modern web standards. There are only two choices: Moon Child can try to integrate massive amounts of Mozilla developer changes back into an older fork (impossible, really), or he can refork and redo his own changes. Given that undoubtedly Firefox's changes have been far more numerous and substantial, it probably makes sense to re-fork and rewrite the Pale Moon code.

      Honestly, I'm not sure how this is really sustainable, as the same thing is bound to happen again in the future. And I've never figured out how anyone can be assured that Pale Moon is at all secure, either. I have a sneaking suspicion it's "secure" in the same way Macs (and Linux, actually) used to be secure - too small a target for anyone to bother with. I mean, I love the guts of these guys trying this, but... well, I wish them the best.

      I also really hate whenever someone trots out this article of Joel's and presents it as gospel, because while it's a good rule of thumb, it's foolish to view any particular development rule as 100% inviolable. I've personally been involved in several highly successful near or partial complete rewrites of very large codebases. I'd say it's certainly a good default position to take - you'd need to convince me before tossing code and starting over. But there are times when doing so would actually be more damaging and end up compromising your new design too much in order to maintain compatibility. Often, it's far better to simply put in a compatibility shim, leave the old code behind, and build a new module next to it, switching over when backward compatibility is needed and slowly depreciating required dependencies.

      --
      Irony: Agile development has too much intertia to be abandoned now.
  4. Pale Moon going to re-fork from Firefox by Anonymous Coward · · Score: 1

    I actually read the article. I know it's bad form but I was bored. I already knew Pale Moon was the work of a single developer, so he/she couldn't seriously be thinking of starting from scratch. It turns out that he/she/they are just going to re-fork Firefox from a new version of the code base.

    1. Re:Pale Moon going to re-fork from Firefox by ChunderDownunder · · Score: 1

      Maintaining EOLed technology as complex as a browser is a big ask, when the Web itself evolves rapidly. Interesting to know the fate of the project if Mozilla divests itself entirely of Gecko, XUL and related technologies as early as 2018.

      Buy a book on Rust and send your CV into the Servo team... Or become just another Chromium fork.

  5. Re:Already have the internet. by Stormwatch · · Score: 2, Insightful

    Because it's not from Microsoft.

  6. tabgroups? I like that by tanstaaf1 · · Score: 2

    Actually I like the whole idea of diversity -- especially if it includes the ability to opt in where I want and opt out of any standardized way of tracking me. I'm going to take another look at pale moon now. I hope they follow through with what they are thinking. Anything but more Google/Microsoft/Safari consumerism.

  7. So frustrating by Billly+Gates · · Score: 2

    To see what Firefox has became from what it was 10 years ago

    1. Re:So frustrating by NormAtHome · · Score: 1

      Yeah, it really is!

    2. Re:So frustrating by antdude · · Score: 1

      Someone need to repeat Phoenix with a brand new web browser!

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    3. Re: So frustrating by Anonymous Coward · · Score: 1

      Look how many years late they are with the Electrolysis project, which sums them up: they've been doing fluff instead of serious features. I switched to Chrome three or four years ago because I got so fedup with their memory leaks and poor performance. Now that I've used a browser where I can figure which tab is draining my battery or using all my memory, I won't switch back until Electrolysis is deployed. And then there are the security benefits.

      Before the Firefox fork, the Netscapd and Seamonkey people always struggled with the concept of multiprocessing, claiming they needed a single monolithic process for better and tighter integration. It seems they're still struggling with this.

      10+ years ago I was complaining about Mozilla was causing Windows 2000 to BSOD. The Mozilla devs and others on this site put me down repeatedly rather than taking this seriously telling me to use s real OS because an app can't do this. It turns out of course that they had a BITMAP resource leak of many years that could bring down Windows if you left the browser running long enough. Then in the years before I switched to Chrome, same story and attitude but this time about unconstrained memory growth by the browser, always denying that it was their problem and had to be my choice of plugins. Never mind that other multiprocessing browsers don't have this problem.

      Mozilla seems to consist of weak developers with no architectural skill and no sense of responsibility or ability to make change when there are clear but difficult problems in their product. This is why Firefox is finally dying.

    4. Re:So frustrating by gweihir · · Score: 1

      Well, it nicely shows that FOSS projects can be ruined by bad management and stupid "leaders" just as much as any commercial software project. I do not know what exactly went wrong at Mozilla, but they must have used really large buckets to carry the stupid in.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    5. Re: So frustrating by Billly+Gates · · Score: 1

      I think the codebase was just not flexible. A LNG time ago I had lunch with one of the engineers at Netscape with the Linux users of New York. IE just was accelerating faster than they could keep up as more bugs kept hitting the rendering engine as features were added. IE 6 being better and less buggy should say alot right there??

      A little late now as WebKit is accelerating

  8. Not from scratch by PineHall · · Score: 4, Informative

    Moonchild's proposal involves creating a new browser from scratch, in a so-called "re-forking" operation, where the Pale Moon devs take a newer version of Firefox and rebuild Pale Moon on top of that.

    They are not building it from scratch. They will use a newer version of Firefox as a starting point. It is "re-forking". It is likely they will not use the latest version since they want to keep tab groups. Though it will be new code when compared to the old Palemoon.

    1. Re:Not from scratch by somenickname · · Score: 3, Interesting

      This is basically what Debian does with Iceweasel (and Icedove). They pick a version of Firefox for the stable release (38 at the moment) and then just backport security fixes for it. For people that are just looking for a browser that doesn't change out from under them every time they start it, Iceweasel from debian stable is excellent.

    2. Re:Not from scratch by ChunderDownunder · · Score: 2

      Wasn't the functionality of "tab groups" moved to an extension?

      Look, clearly I've never used the feature, but what is the main objection to using the extension and pouring resources into that codebase rather than maintaining it as part of the core browser?

      Surely maintaining less code in the core browser is a good thing, if the modular replacement does the job and is supported adequately by an extension writer.

    3. Re:Not from scratch by postmortem · · Score: 1

      That sounds awfully similar to Firefox ESR, which is also on 38

    4. Re:Not from scratch by ChunderDownunder · · Score: 2

      Not by coincidence. Iceweasel *was* just the ESR release rebranded for debian stable.

      Anyhow, I use the past tense.

      http://www.pcworld.com/article...

    5. Re:Not from scratch by Aighearach · · Score: 1

      It isn't a "hole" because they can just walk away and re-fork, something they're doing.

      If they were a company with a bunch of version-locked support contracts, then you'd have a point. But they're not.

  9. Re:Already have the internet. by NotInHere · · Score: 1

    Yes, why should you download some random OS from a spyware vendor? Not downloading but using the preinstalled one doesn't make matters better.

  10. None of this would have happened by Anonymous Coward · · Score: 1

    if Firefox didn't keep constantly breaking extensions, removing useful features, and generally pissing off users.

  11. Re:Ok? by aevan · · Score: 4, Interesting

    I ran it in parallel with Firefox, mirroring every action, back when Firefox when firefox changed its UI: 300 tabs on each, playing videos and long text pages heavy css, and without closing for a few weeks.

    The memory footprint was over a gig in PaleMoon-64s favour, and it wasn't showing any appreciable slowdown in performance. Can't speak towards Firefox nowadays, but I will note Pale Moon does seem to pick up a stutter with some videos lately if not shutdown. That could be entirely unrelated though.

  12. Add-ons by Nunya666 · · Score: 1

    I hope the "scratch" version will support all of the add-ons that the current version supports.

  13. Haven't they done this before? by cant_get_a_good_nick · · Score: 4, Interesting

    Netscape 4 sucks, so lets throw it out and start again. Back when Spolsky could write he bitched about this.

    Mozilla seamonkey sucks, so lets gut most of it and make Phoenix (now known as Firefox)

    And now this again?

    1. Re:Haven't they done this before? by Billly+Gates · · Score: 1

      Well MS is getting rid of IE in favor of Edge. Mozilla is creating a new browser after realizing how supperior webkit is for threading and process isolation and app integration compared to Gecko.

      Oddly Chrome will then have the most legacy and older code

    2. Re:Haven't they done this before? by Aighearach · · Score: 1

      And yet, the alternative would be to use the same thing forever. Was it a mistake for Netscape at that time? Arguably. Does that example apply to open source? Probably not, open source often doesn't (can't) "go out of business" the way a company like Netscape can.

      Any time there are 2 software products that solve the same type of problem, one of them could have just not been written because there was already something else. Is writing something new any different than re-writing something from scratch? Not if it is open source and you don't really care about user numbers.

      If everybody believed that, we'd still be using sendmail. I used to configure sendmail, because nobody else on teams would ever be willing to. I don't really want to go back to that.

      Joel was right about a few things over the years. But he was wrong about a few things, too.

    3. Re:Haven't they done this before? by EmeraldBot · · Score: 2

      Netscape 4 sucks, so lets throw it out and start again. Back when Spolsky could write he bitched about this.

      Mozilla seamonkey sucks, so lets gut most of it and make Phoenix (now known as Firefox)

      And now this again?

      Seamonkey's actually pretty decent. It's lighterweight than Firefox (!!!) and comes with tons more features and custimizability. The only thing you lose is the newer stuff like Pocket or the chatting service, and you have an older interface pre-Auralis (though I daresay many consider these features). The real loss is fewer extensions are compatible, but a decent selection of Firefox ones still are, and there's even a converter that can get solid results. I don't know if you'll like it, but I'd reccommend to give it a try, if you want a good open source browser.

      --
      "Set a man a fire, he'll be warm for the rest of the night. Set a man afire, he'll be warm for the rest of his life."
    4. Re:Haven't they done this before? by phantomfive · · Score: 1

      The key difference is that in each of the examples where it worked, it was a different team doing the rewrite (and in the case of Phoenix, it wasn't really a rewrite, it was a code cleanup).

      The guys at Mozilla have been making lousy decisions for a while now, if they decided to rewrite, do you really think the result would be an improvement, or do you think they would just make the same mistakes?

      --
      "First they came for the slanderers and i said nothing."
    5. Re:Haven't they done this before? by Aighearach · · Score: 1

      Well, anybody that engages in as much feature thrash as those guys, no. I think they would make worse mistakes the second time, but clean them up faster. It would come out exactly the same, because they're engaging in so much feature thrash that they are rewriting the whole thing continuously.

    6. Re:Haven't they done this before? by phantomfive · · Score: 1

      I think that's a big part of the problem with doing a big rewrite: people who wrote lousy code will write lousy code. For most people, it's better off to learn how to fix things than to try to rewrite it perfectly from scratch.

      Imagine if firefox had been constantly focused on improving quality all this time. Right now they would have one amazing browser.

      --
      "First they came for the slanderers and i said nothing."
    7. Re:Haven't they done this before? by Kjella · · Score: 2

      And yet, the alternative would be to use the same thing forever. Was it a mistake for Netscape at that time? Arguably. Does that example apply to open source? Probably not, open source often doesn't (can't) "go out of business" the way a company like Netscape can. Any time there are 2 software products that solve the same type of problem, one of them could have just not been written because there was already something else. Is writing something new any different than re-writing something from scratch? Not if it is open source and you don't really care about user numbers.

      The difference is natural and forced adoption. If you create something new, you don't have existing users and people would have to start using it because they find the pros outweigh the cons. If you see a massive voluntary migration it's pretty obvious you're doing something right. When you rewrite something you have existing users and features that used to work and when things stop working we call those regressions. Most are unintentional side effects that developers agree are bugs and should be fixed.

      Rewrites are typically when those rules go out the window. Not supported anymore. That's not a bug it's a feature. That's gone and not coming back. Might come back someday, but not a development priority. Often with a solid dose of hubris like "you shouldn't be doing that" or "once you get use to it you'll love it" or "users want simple, minimalist interfaces" to say "we heard you, but you're wrong". Or to belittle you by saying this is a "tempest in a teapot" by a "vocal minority" of luddites that oppose all change.

      I guess if you don't care about users and functionality but just more code and new code it can't fail, but then you could just hire monkeys to bang on typewriters. There are good rewrites where the code was just a buggy spaghetti mess and the rewrite was a huge success, you just don't hear much about those. But often it's just a version of NIH syndrome, I don't understand the code so the code must be stupid and if I could just write it myself I'm sure it would be much cleaner and better. Usually those end up as a total disaster, with the culprit abandoning it midway.

      --
      Live today, because you never know what tomorrow brings
    8. Re:Haven't they done this before? by Aighearach · · Score: 1

      I don't care about users, most of the software I use is written so that I can use it, and the software I use wasn't written to maximize users. Proprietary software has more users, for example, and that was never a problem. Software I use is written so that I can use it, not so that I must.

      You just hand-wave and claim that "functionality" is improved by never throwing anything away. I disagree, and I challenge that that is some sort of given. I also challenge the absurd idea that somehow people who want higher quality code at any cost think coding is done by monkeys. It shows a lack of theory of mind.

      You may not hear much about "buggy spaghetti," but don't tell me I don't. Because I do. The reason you don't hear about the great successes, is that in open source branding isn't important, and the good teams name the rewrite something new. So you simply don't know it happened. And often, after rewriting it, it becomes "stable" and doesn't need to be changed for years.

    9. Re:Haven't they done this before? by Rexdude · · Score: 1

      Mozilla seamonkey sucks, so lets gut most of it and make Phoenix (now known as Firefox)

      You've got that wrong. Seamonkey is the successor to the Mozilla suite (which was the successor to the Netscape Communicator suite), and it had browser + mail/news client + HTML editor and a bunch of other stuff. Firefox is the successor to just the browser component.

      Plus they haven't gutted anything. They chose to stick with the v 24 codebase and forked it from there because of how Firefox is slowly morphing into a pale imitation of Chrome by shedding all the customizability and user choice that made it great in the first place.

      --
      "..One hosts to look them up, one DNS to find them, and in the darkness BIND them."
  14. Re:Microsoft should open source Edge. by MightyMartian · · Score: 1

    Fuck no. It's a terrible buggy browser.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  15. Re:Rust and Servo... LOOOOOOOOL! by ChunderDownunder · · Score: 1

    I briefly played around with Rust about 18 months ago.

    The syntax (aaaaargh pointers!) took a bit of getting used to and admittedly I think the lack of implicit conversions involving mutable types, strings etc is a bit of a pain in the arse.

    But the functional aspects seem handy.

  16. Don't forget security by yuhong · · Score: 2

    There is the issue of security too. One security question is whether it have "Slaughterhouse" (see https://bugzilla.mozilla.org/s... and http://bholley.net/blog/2016/t...). This is not the only incident where Mozilla people have suggested hiding bugs until an old ESR goes end of life BTW.

    1. Re:Don't forget security by dgatwood · · Score: 2

      After reading that, I'm downright horrified. That further supports the common argument that responsible disclosure without a mandatory end date is irresponsible. If these people found those holes in Firefox, odds are pretty good that other people did, too, and that those people didn't have our best interests at heart.

      At least in my mind, it's really simple. If you agree to maintain something, you should maintain it. If you aren't going to maintain it, don't promise to maintain it. You may choose one or the other. You may not choose both at the same time. Not cool.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

  17. Re:Because there are no black russians by ChunderDownunder · · Score: 1

    vodka flavoured coffee?

  18. Re:Microsoft should open source Edge. by Masked+Coward · · Score: 3, Funny

    Users are fleeing Firefox like there's no tomorrow. The stats show that Firefox is likely around 7% of the browser market on all of the platforms it supports. The stats clearly show that Firefox's users are going to Chrome and Edge.

    All we need is confirmation from Netcraft. Firefox is dying and bleeding users, flowing like a river of blood.

    You don't need to be a Kreskin to predict firefox's future. The hand writing is on the wall: firefox faces a bleak future. In fact there won't be any future at all for firefox because firefox is dying.

  19. off-white pages please by Provocateur · · Score: 2

    Please provide the option to offer not just white background pages (the glare limits my browsing/web surfing in subdued ambient light conditions). I do not need the baggage of a "theme"; that would be excessive; just a light shade of gray would provide soothing comfort after long work hours in userspace. Opera has this out of the box fer chrissake, YOU ARE PALE MOON and white was the color the astronauts wore on the lunar surface, which had if I recall correctly from those photos some other color but definitely was not white at all.

    --
    WARNING: Smartphones have side effects--most of them undocumented.
  20. Re:Why not help Servo? by Ash-Fox · · Score: 2

    Personally I love Rust, and love their Code of Conduct even more.

    I've never needed a code of conduct on an open source project before... Honestly, sounds like they're drama prone.

    --
    Change is certain; progress is not obligatory.
  21. Re:Microsoft should open source Edge. by cbhacking · · Score: 3, Informative

    I don't know that I'd call Edge buggy, unless you're running the preview versions (which are pre-release software and expected to have bugs). It is undoubtedly getting better, feature-wise, too. However, it is still fundamentally a toy browser, an overgrown mobile phone app, and it is really quite worthless as a consequence.

    It has nothing resembling good tab session management (although they did add an interesting feature in that general area in the last preview update).
    It offers basically no support over what JS can and cannot do.
    It has basically no cookie filtering.
    It has no tracking protection or ad blocking (IE first got these almost a decade ago).
    It built-in Flash that can be globally disabled, but cannot be enabled and disabled for specific sites.
    It has no support for tab grouping or switching tabs in last-used order.
    It cannot understand RSS/ATOM feeds at all (renders them just as XML files, no feed reading ability).
    It doesn't support per-tab taskbar items.

    I'm sure there's many more features missing; I don't use it enough to find out because the list above already contains multiple deal-breakers for me. The only things it does well are its dev tools (which are not mobile-app-like at all), its rendering engine, and displaying which tab(s) are playing media. Nobody who has any choice in the matter should be using it on a desktop PC, and I say this as somebody who voluntarily uses all off Pale Moon, Opera, IE11, Chrome, real Firefox (on occasion), and Midori (on occasion, though it's pretty feature-less too).

    --
    There's no place I could be, since I've found Serenity...
  22. Re:Yeah, sure by Anonymous Coward · · Score: 1

    Actually they are well aware of all of that. Maybe you should try reading the discussion on the Pale Moon forum.

  23. SM... by antdude · · Score: 1

    SeaMonkey doesn't suck! Others and I till use the suite bundled versions. Also, its GUI hasn't changed much for decades unlike Firefox's.

    --
    Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    1. Re:SM... by cant_get_a_good_nick · · Score: 1

      "seamonkey sucks" at the time of the split. I haven't used seamonkey since early Phoenix days. It may have shaken out a lot.

      The point is not whether i think it sucks, but whether the devs decided "screw it lets just restart everything" and rewrite basic code. again. for the third time.

    2. Re:SM... by antdude · · Score: 1

      Weird. I don't get those flickers. Ah, autohide the status bar. I like the status bar for other stuff though. SM do need more help to make and fix stuff.

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
  24. Re:Already have the internet. by short · · Score: 1

    "Not downloading but using the preinstalled one" does matter in real world.

  25. For want of an 80C filter the plot was lost by Hognoxious · · Score: 1

    white was the color the astronauts wore on the lunar surface, which had if I recall correctly from those photos some other color but definitely was not white at all.

    That's because they forgot to correct for Rayleigh scattering.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  26. Re: Yeah, sure by Anonymous Coward · · Score: 1

    Why not use Mozilla SeaMonkey as the basis for their next browser? It would be at lot easier than trying to start from beginning. And since they are already familiar the code base they can get things going much quicker.

    -imprezza86

  27. Re:Ok? by thegarbz · · Score: 1

    Does anyone actually use this browser? Can you vouch for its relevance?

    It's very relevant as an alternative to Firefox which isn't Chrome or Edge for the policies behind the companies. Firefox was an awesome browser by a company which didn't sell all your information to 3rd parties. Unfortunately as of late they have a tendency to shit on their user base.

    Personally I started using Pale Moon as a primary browser only 6 months ago. I did a lot of active complaining about Firefox but just was never bothered to switch. Then one Firefox update caused it to simply crash on startup. I could file a bug report, but quite frankly with developers so toxic to user fuck-em. It was less effort to switch to Pale Moon than to fix what was broken and I ended up with a faster, leaner browser that reminds me of all the things I liked about Firefox in the first place.

    If you're a Firefox user there's zero cost to switching. It will pull across your profile from Firefox, and it has a rich extension base except for all the extensions that try and make Firefox look like it.

  28. As a Pale Moon user, by jenningsthecat · · Score: 1

    I really hope they do this and are successful.

    If they get enough traction soon enough and have a strong enough core team, maybe they can pick up a few Mozilla devs when FF crashes and burns. The existing team will need to reign in the new Mozilla devs and totally squash that fucking "we know better than the users" craptitude that sent FF swirling down the drain - hence the need for a strong, established core of Pale Moon devs to establish, protect, and enforce the 'user requirements first' culture.

    --
    'The Economy' is a giant Ponzi scheme whose most pitiable suckers are the youngest among us and the yet-unborn.
  29. Always sounds nice until you actually try it by Theovon · · Score: 1

    I’ve tried to start codebases from scratch a few times myself. The same thing happened that happened with Gecko. I was not able to find a truly elegant solution that accounted for all of the requirements up front, so although I solved one set of problems better, all the later hacks I had to do to fix all of the oversights made the new codebase almost as crufty as the old one. All I really accomplished was to waste a bunch of time developing a new codebase with a whole new set of bugs to fix.

    On the other hand, I have been successful at incrementally *refactoring* code. If I did my job right in the first place, most functionality was already modular. Then I can take some of the stuff on top of my libraries and extract it into more libraries, which I can then improve individually.

  30. Re:Ok? by Cederic · · Score: 1

    If you're a Firefox user there's zero cost to switching.

    The very real cost is needing to start up another browser to use certain websites, or specific capabilities of certain websites.

    This is happening at an increasing rate and unless better compatibility with whatever web standard those sites are using lands quickly I may have to switch to another main browser.

    It would be a shame, but a browser that can't render the web isn't terribly helpful.

  31. Remember when Netscape did this? by JustAnotherOldGuy · · Score: 1

    Remember when Netscape did this?

    The decision was one of the major reasons for the death of the Netscape browser. It was a terrible idea and led to Netscape (the leading browser at the time) disappearing from the market for all intents and purposes. The browser (and the company) sank like a stone, never to be a dominant player in that space again. Or ANY space as far as I can tell.

    Years later (during the Netscape post-mortem) everyone agreed that "redoing the codebase from scratch" had been a stupid and horrible idea. It was an undeniably fatal move by the company.

    --
    Just cruising through this digital world at 33 1/3 rpm...
  32. Re:Why not help Servo? by gweihir · · Score: 2

    A code of conduct written by SjWs (and they all are) is an absolute no-go, because these projects obviously place product quality a distant second to other considerations. That cannot work.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  33. Re:Why not help Servo? by gweihir · · Score: 1

    Older white males know better than to join a cult like the Rust community, and so apparently do non-whites/non-males ;-)

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  34. Re:Yeah, sure by cfalcon · · Score: 1

    > They seem to have no idea how massively complex project a modern web browser engine is.

    Yes they do lol. They already maintain a browser fork of firefox, I'm sure they know a lot about what they need to do.

  35. Re:Microsoft should open source Edge. by iampiti · · Score: 2

    Haven't you gotten the memo? You're supposed to use, simple, feature-limited mobile apps in your desktop and throw away the featureful, desktop-oriented-UI programs we've been using for decades...because...reasons and then doing your work...I don't know how.

  36. Re:There are so many good FLOSS browsers by Scoth · · Score: 1

    And yet it's still Webkit. Are there any major non-IE browsers left which aren't Gecko or Webkit/Blink? As in, could use them for day to day browsing including multimedia, social media, major sites, etc etc? Opera was the last major one I knew about. Servo could be interesting if it makes it.

  37. Re:Why not help Servo? by narcc · · Score: 1

    There's nothing but pointless bickering and drama in just about every open source project. It's disgusting. Having a code of conduct keeps that down to the absolute minimum.

  38. Re:Yeah, sure by mikael · · Score: 1

    From the forum:
    "Allow me to further clarify .. ONE AGAIN.. Our future and whatever path we take is going to still have specific requirements and parameters. It is gonna be a mozilla-like codebase.. It is gonna have a gecko-like rendering engine (Goanna) it will have XUL, XBL, all the technologies everyone wants and needs. What this will not be is a trident shell, a webkit shell, a blink shell, or whatever servo is gonna be.. No, does not and would not support all the bits of technology to be a product we and you could use and be proud of. If you think this is gonna happen.. Just stop because it isn't going to ever be that. So get that out of your heads."

    http://forum.palemoon.org/view...

    --
    Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
  39. Works fine by suppo · · Score: 1

    I've used Pale Moon on linux on my main home computer for about six months with zero issues. NoScript and Adblock Latitude are supported. Haven't found any web sites that do not render. Only minor complaint is that on text boxes like this one the default (but changeable) language is German vice English. Haven't really tried to fix it yet.

    --
    NON-geek Linux user since 1998
  40. Re:Microsoft should open source Edge. by david_thornley · · Score: 1

    That's a difference only if upscaling and downscaling aren't too difficult. Otherwise, you're either writing multiple UIs or picking a target platform and doing a hack job on the other ones. iampiti may not be describing the goal correctly, but he may well be describing the results of aiming at the goal correctly.

    --
    "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  41. Re:Yeah, sure by MoarSauce123 · · Score: 1

    If anyone can pull it off, then the folks from Pale Moon. This project is one of the few FOSS projects that does not alienate its users.