Basilisk new... available from Moonchild but

>TLS 1.3
It's not even fucking standard,
it's a DRAFT you faggot,
so why even implanting test protocols, which aren't enabled in servers...

That is not the point. The point is to get a job done, no matter how complex it is. And in Pale Moon teams case it is that complex jobs almost never get done.

Even you should understand that it is simply not acceptable to be unable to get a job done when you are developing something complex as a browser.

Oh wait, Moonchild has not done that actually, they taking an already done code base and changing a big number of lines, but most of the work is done by Mozilla!

Pwned!

>chrome clone
Nice meme. Firefox can still do many more things than Chrome. Especially with about:config.

Attached: read.png (1530x800, 104K)

Who cares about internal features. It is all about customization, baby!

And Mozilla has removed almost everything what can be customized to be like Chrome.

Also userchrome.css will be cut away in the future.

But actually it is true to call Firefox a Chrome clone. It is an inferior Chrome clone. And most Ex Firefox users or users who still use Firefox but are not happy at all with what Mozilla are doing would agree.

The point is Firefox still allows you to do more than Chrome. For some reason you choose to deny this.

>userchrome.css will be cut out in the future.
Source?

Attached: quantum.png (3840x2079, 529K)

reddit.com/r/firefox/comments/7iq1n9/the_beginning_of_the_end_for_userchromecss/

Even Mozilla guys say that it will not stay forever.

As it makes "the same problems like XUL"

Just think - what happened so far when Mozilla added telemetry collection to something?

It was going to be removed. So will userchrome.css

bugzilla.mozilla.org/show_bug.cgi?id=1416044

And if you ask yourself why... because userchrome is not Google Chrome enough.

When Google does not have something, it will be axed by Mozilla sooner or later in most cases too.

Google Chrome devs added a bug report about removing FTP internal support... Mozilla did too.

And they already limited it already recently.

So, say bye bye to the last amount of customization... and say hello to Chrome 2 with a different engine!

They use Visual Sudio to code?? I thought they were on Linux at least.

developer.palemoon.org/Developer_Guide:Build_Instructions/Pale_Moon/Windows

You guys are retarded. And did you even read the link?

Attached: Clipboard01.png (1833x353, 129K)

reddit.com/r/firefox/comments/7tu98a/wontfix_the_future_of_userchromecontent/

Some more links to see it is true?

bugzilla.mozilla.org/show_bug.cgi?id=1431962

Kris Maglione [:kmag] (long backlog; ping on IRC if you're blocked)

Comment 3 • 3 months ago

Not supported means that we will not actively support it, yes.

This isn't a new stance. These are undocumented features that happen to still work, but are no longer part of any official customization system. The functionality of userContent.css can mostly be duplicated using extension APIs. The functionality of userChrome.css will not be supported, for the same reasons that we removed support for legacy themes.

Support will probably be completely removed from Firefox in the future, yes, but there are no immediate plans to do so.

-----------------

You can read? removed, maybe not know, but in the future, as it seems "to make the same problems like legacy stuff"

----------------

Now go back to cry inside the hole from where you have been coming in the first place, punk!

And if you still believe you get the same complexity back over Webextensions from Mozilla... Boy, they are not going to deliver you the power of webapps like the one over which Vivaldi was created.

Whatever Mozilla gives you in API form will be inferior to what existed in the past.

Anyway, that is not the topic.

Thanks reddit!

So most stuff can be done using extension APIs but some things may not work. This is depending on whether they actually do completely remove it. Which still isn't definite.

Lets say the following. Mozilla will add things back, but not enough for power users, geeks or nerds who have been loving the Firefox versions up to 24.

And that ones have left the ship already almost as a whole.

Mozilla is only interested in supporting the Chrome user base and the less demanding users.

Power users, ricers, geeks and nerds do no longer play any role for them.

So, what Mozilla thinks of "enough" is an inferior amount of features as compared to the XUL past where you had freedom to do shit without almost no limits.

Firefox is currently superior. I get more functionality than chromium-based browsers with the same responsiveness.

It still has more features than Chrome

Believe in Mozilla if you want. But that cunts and SJW liberal leftist assholes give a rats ass about real diversity, no matter in supporting conservatives or features.

Liberal diversity is SJW restricted. And excludes all features all the dumb people can not understand.

And yet it is a second class Chrome clone with a different engine.

What are you? A paid Mozilla troll? A die hard dreamer, or fanatic or a general leftist SJW cunt? As said, go back to your hole punk and let the adults and the gifted ones have their talk.

What are you, a google shill? I would rather promote FOSS software than that shit.

Why does moonchild pretend that he won't need to refork off mainline firefox again in a couple years?
He's done it multiple times to palemoon and every time pretends like he will diverge into something to overcome the backporting and not need to rebase anymore.

It's made me lost any confidence.
Then he releases Basilisk which is a whole new fucking rebase because he realized how much of a shitshow backporting to ancient palemoon was.
So what's going to happen now?
He's going to drop palemoon support and force me to basilisk? What about when basilisk doesn't get a certain feature and needs to rebase again?

I'm fucking done being yanked around.