I mostly use Markdown, but I have also been considering learning Org-mode. Other than Markdown, Org-mode, and good old plaintext—which is not a markup language per se—there are also AsciiDoc and LaTeX, to mention two. I was curious if it is worth learning a new markup language, and what other people use. Was it easy for them to learn a new markup language? Are they using it for writing research papers, blogging, emails, and taking down notes?

No better way to find out other than by making a poll and asking the fediverse community!

Polls

Meta

• Duration: 7 days
• Date: 2023-04-02 to 2023-04-09
• Total votes: 83
• Total voters: 53
• The poll

Results

What are people saying?

For Fell’s thesis, LaTeX is the markup language of choice, but in all other cases, good old plaintext is more than enough because it is compatible with everything.

I agree. Plaintext is plaintext. It is the easiest and fastest way to take down notes. You do not have to worry about converting a particular file from one markup language to another.

However, for Nick Anderson, Org-mode is life. Nick uses Org-mode for everything: knowledge management, writing email, blogging, presentations, tracking time, Jira ticketing, and more. Nick’s entire workflow and daily routine, you can guarantee Org-mode is there.

I checked the articles Nick shared, and after going through Nick’s experience and process, I can imagine how it made Nick’s daily workflow faster and easier. This is a good thing, as I have mentioned I have been considering learning Org-mode and integrating it into my daily routine.

For Evan Keeton, the answers are LaTeX and Markdown markup languages. Evan shared that for anything mathematics related, LaTeX is the one to use. This is true, LaTeX is the choice in publishing scientific documents ¹. If you plan to publish a research paper, it is a good idea to master LaTeX.

However, for things like note-taking, Evan said that Markdown fits perfectly. For Evan, Markdown is easy to read even without a proper renderer. I can attest to that. As a long-time Markdown user, my mind processes a Markdown document as if my brain is a Markdown renderer. It flows naturally, I do not have to consciously think about the markups in the document.

Potung Thul shares the same view as Fell, plaintext is the most compatible format of all the choices in the poll. Vim is also Potung’s go to cross-platform software for editing texts.

Closing

From the above poll, while not conclusive, it gave a general overview on which format, or markup language, fediverse citizens use. The top two are: Markdown and Org-mode, followed by plaintext. While LaTeX is the de facto choice for scientific publications and in other fields ¹.

I have heard good things about AsciiDoc, though it only received a few votes in this poll, it is a markup language that one should consider. It may be easier for you compared to the other popular choices.

Should you try one of these markup languages? Yes, you definitely should. Markdown is common in software development, for example, it is the markup language used by web repository services like Codeberg ². It is also the default in many static-site generators like Hugo ³. There are also forum software which allow Markdown editing other than the old BBcode format.

And as was mentioned, LaTeX is the de facto standard in STEM (Science, Technology, Engineering, and Mathematics) publishing. Authors can submit their papers as a LaTeX document, and the publishers converts it to their own preferred format without losing any text information, like bold, italics, images, and footnotes. Compare that to submitting PDF, ODF, and DOCX documents, more likely than not the publisher will have to check if the conversion was accurate. Or, the authors of the paper have to spend more time on these things when they can better spend it doing research and experiments.

Of course, plaintext is as good as any. If presentation is not important, like bold and italics, plaintext can fill our everyday needs in documentation and note-taking. Even before the age of computers, that is what we were already doing… writing down in plaintext.

Links and more information

For more information about the various markup languages mentioned, check these useful links:

• LaTeX
• Org-mode
• Markdown: CommonMark
• AsciiDoctor
• AsciiDoc
• Wikipedia: List of document markup languages

The recent announcement by Microsoft giving up on their EdgeHTML browser engine as well as their Microsoft Edge browser frontend marks the end of the Browser Wars 2.0. Their revelation that their next flagship browser will be Chromium-based and thus powered by the Blink browser engine, signals the beginning of Browser Wars III a war to control the Internet through browser engines.

To understand Browser Wars III we need to realise that there are two fronts in this new war: the Browser Frontend and the Browser Engine. Allow me to differentiate these two fronts.

Browser Wars III Front: Browser Frontend

A browser frontend is simply the browser that users see. In this case, we have Chromium and Mozilla’s Firefox [Quantum]. Before there was a Chromium browser (the frontend and the engine), the most forked browser was Firefox. Some of the most popular Firefox-based projects are Pale Moon (also forked the Gecko engine into Goanna), Waterfox, Comodo IceDragon, Tor Browser, and the original Flock browser.

When Chromium arrived in the scene, it slowly gained converts. Flock migrated from being a Firefox-based browser to a Chromium-based browser bringing with them their loyal users (much later though, Flock development has ended). Opera Software, the company behind the Opera Browser, ended development of their browser frontend and its Presto browser engine. From there, they created a new Chromium-based Opera! Exactly what Microsoft has announced they will be doing too.

If that was not enough, fans of the Opera Browser also created their own browser called Otter Browser and Vivaldi (which happens to be far better than the new Chromium-based Opera Browser).

Other Chromium-based browsers are: Yandex Browser; Comodo Dragon; Brave; Epic Browser; and Torch, to mention a few. No one is choosing Firefox any longer!

This brings us to the …

Browser Wars III Front: Browser Engine

The browser engine part of the Browser Wars III is the most important and largely ignored in the past two Browser Wars. Today, articles are interchanging Chromium and Blink. However, Chromium is a browser frontend while Blink is a browser engine.

Not interchangeable

The frontend and engine are not interchangeable. A developer can …

• … use an existing browser frontend but use a different browser engine
• … use an existing browser frontend but add additional browser engines on top of the default
• … use a browser engine but without the browser frontend (usually seen in software with a built-in browsing feature)
• … use a browser engine but develop a browser frontend from scratch

Gecko, the browser engine behind Firefox, had seen a lot of products with the use-cases mentioned above. Blink’s use mainly concentrated on Chromium; after all, why build a browser frontend from scratch when there is already Chromium? Why add a built-in browsing feature when one can use Chromium directly as if it’s part of the software or app in both the desktop and mobile platforms? (I came across software where its browsing experience was locked into Chrome itself even if your default browser was set to Firefox. Chrome is a Chromium-based browser by Google.)

Yet, it does not mean Chromium and Blink are interchangeable, especially when …

It’s the browser engine that counts

When frontend developers design software and websites, they test it against different browsers. The reality is they are testing it against the engine powering these browsers. As long as a product or website has been tested in any browsers powered by Blink, Gecko, and WebKit (Safari and all Apple products), a developer can generally interpret it as the same in any other browsers powered by the same engine (to reiterate, generally, there are other factors involved that may change the result even if the engine and its version is the same). There is no need to install Chromium, Chrome, Opera, Vivaldi, Brave, and Yandex, these are all powered by Blink through Chromium.

With everyone choosing Chromium as their underlying browser frontend (developers) or daily browser (end-users) we are heading once again to the days of “this website works best with” and “please download a Blink-powered browser like Google Chrome, Opera, Vivaldi, Yandex, and Brave to continue to this website”. In addition, developers and companies who only cares to get a website running and money flowing as fast as possible, will only do tests against Blink now that it has the largest share of the market… today.

It puts an imbalance in the Internet. The Chromium developers, who are also the developers behind Blink, now have more power over how the Internet should be displayed. Not that they will abuse it, hopefully, but there were, are, and will always be decisions within the W3C Consortium (the group that sets Web Standards) based on numbers or how a particular element or attribute should work; or if a new web feature should follow Chromium’s version or Mozilla’s interpretation.

Conclusion

Chromium is just the surface. The browser engine is the real danger here. Chromium is simply the flagship browser of Blink. Since most do not want to start a browser from scratch, they obviously decided to use Chromium and tweaked it to their desired look and added their own features. But no one is stopping anyone from building a browser frontend from scratch and use Blink as their browser engine, Chromium have less count while Blink has a higher count.

It does not matter which browser frontend is the most popular because “this site works best on” and “this website was tested fully on” is all about the browser engine. It is about Blink, Gecko, WebKit, Goanna, and KHTML.

Use Firefox Quantum, yes, but if you do not like Firefox for whatever reason, then use a browser powered by the Gecko Quantum engine. A Chromium-based browser is not the only alternative, there are Firefox-based browsers too. If you are a frontend developer, test your website projects on Gecko Quantum powered browsers too. Let us not put the Internet in danger by letting one particular browser engine have a major gap and dominance in the market.

From my personal experience, Gecko has always been way ahead when it comes to implementing the W3C recommended specifications, always. There are also bugs in Chromium that are always ignored or were repeatedly closed as “not a bug” and/or “working as intended”, for example, in its font fallback mechanism which is affecting some [Asian] scripts but is working perfectly in Gecko-powered browsers!

One final thought. There are two Asian browsers with three browser engines (Trident, Gecko, and Blink): IE-based Avant Browser by a Chinese developer and IE-based Lunascape by a Japanese developer. Yes, there are multi-engine browsers (and extensions in the case of Firefox).

This Browser Wars III clearly is about the browser engines Blink and Gecko, the browser frontends that is Chromium and Firefox are only secondary, we just see them mentioned more because the average Joe and Jane are only familiar with those “names”.