this post was submitted on 25 Jan 2024
1077 points (98.9% liked)

Technology

55703 readers
4631 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 14 points 5 months ago (5 children)

There's also Firefox Beta, Nightly and Focus.

[–] [email protected] 18 points 5 months ago (4 children)

Not at all the same. These are three outputs from the same build process and code base. Maintaining a build with WebKit and one with Mozilla’s own rendering engine is like running a different team.

It’s almost as if Apple is making this difficult.

[–] [email protected] 6 points 5 months ago* (last edited 5 months ago) (3 children)

same build process and code base.

It's not the same code base though. They're all different branches, and also differ in code (although not by much, but it still requires manual maintenance of each branch). I haven't seen the actual build process but it's likely to be completely separate CI/CD pipelines, so I wouldn't claim it to be the "same" build process either. Also, Focus uses a completely different UI with a different/cut-down set of features.

Naturally I'm not saying that maintaining these branches amounts to the same level of effort as maintaining the iOS WebKit and Gecko branches, but it's not some non-trivial effort either.

[–] Tatters 4 points 5 months ago

It doesn’t have to be separate branches - you can generate different versions of the software from the same code branch, e.g. using compiler/build time switches for those bits of the code that differ between the different target platforms. Then you would have a build pipeline per platform; even here the build pipeline can share a lot of common code, and just be parameterized for the specific platform.

load more comments (2 replies)
load more comments (2 replies)
load more comments (2 replies)