Jump to page: 1 2
Thread overview
Browsers in D
Dec 19
Doigt
Dec 20
Hors
Dec 20
Sergey
Dec 19
Antonio
Dec 19
Antonio
Dec 21
aberba
Dec 20
Hors
Dec 21
aberba
Dec 22
aberba
December 19

I wrote a little blog about my browsers in D, with some discussion about how you might be able to embed them in your application too:

http://dpldocs.info/this-week-in-d/Blog.Posted_2023_12_18.html

With Firefox getting worse by the year, you might want to consider also making your own partially-usable chromium/edge skin (also known as "pukes")!

December 19

On Tuesday, 19 December 2023 at 21:15:19 UTC, Adam D Ruppe wrote:

>

With Firefox getting worse by the year, you might want to consider also making your own partially-usable chromium/edge skin (also known as "pukes")!

Firefox is getting better, not worse. That's strictly your opinion.

December 19

On Tuesday, 19 December 2023 at 21:15:19 UTC, Adam D Ruppe wrote:

>

With Firefox getting worse by the year, you might want to consider also making your own partially-usable chromium/edge skin (also known as "pukes")!

Really? It is my primary development browser. In fact, chromium has left me in the lurch more than once with its bugs (mainly with svg and resources memory management).

Imagine a company with products based on svg (complex ones with a lot of user interaction) and a new version of chrome that fails managing mouse events in some circunstances... my company begun to receive emails/phone calls from our customers telling that "our software bug" was making them lose thousands of euros every hour. (Our company was a "personalization" service used by a lot of manufacturers eCommerce in Spain).

It was not the first neither the last problem that a new version of chrome caused to our company: You can't say to a customer "tell your users to browse your ecommerce with Firefox or Safari" because Chromium dominates browsers market (it is a monopolistic control).

I remember when reported a bug about canvas/images memory leak (Our software processed hundred of images directly on web)... we find the solution to assigning 0 to width/height... but the chromium bug remained YEARS until it was solved. It gives you the magnitude of what a monopolistic control signifies.

Adam, I really heated Chrome... and I simply don't tolerate each new browser based on chromium. I consider it a giant error. "One ring to rule them all"

Firefox protection is a must.

December 19

On Tuesday, 19 December 2023 at 23:40:48 UTC, Antonio wrote:

>

Really? It is my primary development browser. ...

I apologize for the tone of my last post. I consider that what it express does not fit the rules of this forum.
If possible, I would like it to be removed by the moderator.
Thanks in advance.

December 20
On Tuesday, 19 December 2023 at 22:42:16 UTC, Doigt wrote:
> Firefox is getting better, not worse. That's strictly your opinion.

Firefox has a number of major problems:

* They invested in Rust instead of D.

* Its engine is not particularly embeddable. This means you're at the mercy of Mozilla's bad UI decisions. Something I was able to fix with the chromium engines with a simple

        url.addEventListener((DoubleClickEvent ev) {
                url.selectAll();
                ev.preventDefault();
        });

Has no solution for Firefox. This was a major strategic mistake on Mozilla's part: they could have been the base of countless tools and applications, but they ceded all this ground to their competition.

* They don't even support "app mode", to open one page in a window with its own icon and minimal ui, which could be a potential substitute for using its engine as an API; you can spin up a local web server and spawn an instance of the browser to display things. But firefox has very little support for this use case.

* The firefox engine has poor platform integration out of the box. Chrome's engine, on the other hand, works actually quite well in varied uses across platforms without requiring much custom code (they do break the X spec in places, but you can kinda tame that, you can see this in the source of the minigui_addons.webview module). Even if you could embed the firefox, it is possible it wouldn't work on your system anyway!


It is a pity that Mozilla didn't take this use more seriously, but they didn't...
December 20
On Tuesday, 19 December 2023 at 23:40:48 UTC, Antonio wrote:
> It was not the first neither the last problem that a new version of chrome caused to our company

Oh, I'm old enough to remember the Chrome auto-update that broke standard HTML links! It was such a pain supporting it in the first few years, while IE and Firefox were both working pretty well at the time.

But, like I just said in the other post, Firefox has near-zero support for being embedded in other applications. If you know of a way that we could reasonably use from D, let me know, but the only time I've seen an embedded Gecko is actually in the Wine project... and this had no other way to access it that I could find.

> I remember when reported a bug about canvas/images memory leak (Our software processed hundred of images directly on web)... we find the solution to assigning 0 to width/height... but the chromium bug remained YEARS until it was solved.

Mozilla has closed *dozens* of bugs that affect me directly as WONTFIX, including fairly simple to fix regressions. That's why I can't use it anymore.

> Adam, I really heated Chrome... and I simply don't tolerate each new browser based on chromium.

If you wanna work on my other engine to bring it up to spec, feel free lol, but the screenshots speak to the functionality gap...

December 20

On Tuesday, 19 December 2023 at 21:15:19 UTC, Adam D Ruppe wrote:

>

I wrote a little blog about my browsers in D, with some discussion about how you might be able to embed them in your application too:

http://dpldocs.info/this-week-in-d/Blog.Posted_2023_12_18.html

With Firefox getting worse by the year, you might want to consider also making your own partially-usable chromium/edge skin (also known as "pukes")!

Neither any browsers are good
In firefox sometimes pages simply crashes without any error message, you have to close tab and open it again.
In chromium sometimes caret becomes invisible, and page crashes the entire app becomes irresponsive.

Also I find it funny how people tell they use firefox for privacy, yet firefox have telemetry on by default.

December 20

On Wednesday, 20 December 2023 at 00:00:24 UTC, Adam D Ruppe wrote:

>

On Tuesday, 19 December 2023 at 22:42:16 UTC, Doigt wrote:

>

Firefox is getting better, not worse. That's strictly your opinion.

Firefox has a number of major problems:

  • They invested in Rust instead of D.
    [...]

Rust is better choice than D if you have to run code from untrusted resources (html, javascript, webassembly...) it's safer, plus faster.

December 20
On Wednesday, 20 December 2023 at 06:29:30 UTC, Hors wrote:
> Rust is better choice than D if you have to run code from untrusted resources (html, javascript, webassembly...) it's safer, plus faster.

[citation needed]
December 20
On Wednesday, 20 December 2023 at 08:17:20 UTC, Anonymouse wrote:
> On Wednesday, 20 December 2023 at 06:29:30 UTC, Hors wrote:
>> Rust is better choice than D if you have to run code from untrusted resources (html, javascript, webassembly...) it's safer, plus faster.
>
> [citation needed]

I would add *sarcasm* sign :)
« First   ‹ Prev
1 2