Ladybird Browser Team Selects Swift as Preferred Language : opensource

[–] InternetCitizen2@lemmy.world 81 points 3 months ago (1 children)

Rust was made by Mozilla? TIL

[–] PullPantsUnsworn@lemmy.ml 48 points 3 months ago (2 children)

Yep. It was developed to improve parallelization and security of Firefox. Many core parts of Firefox have been replaced with Rust implementations.

[–] rickyrigatoni@lemm.ee 17 points 3 months ago

I see now. Rust is the color of fox, and foxes eat crabs. It all makes sense now.

[–] ayaya@lemdro.id 6 points 3 months ago* (last edited 3 months ago)

I thought it was weird such an old piece of software had so much Rust in it. I noticed all the Rust-related things while ~~Firefox~~ Librewolf compiles but never looked into it further.

[–] avidamoeba@lemmy.ca 68 points 3 months ago

That's weird.

[–] 9point6@lemmy.world 64 points 3 months ago* (last edited 3 months ago)

Independent of corporate interests

.

Picks one of the few languages created due to corporate interests

This will die on the vine

[–] moreeni@lemm.ee 43 points 3 months ago* (last edited 3 months ago) (3 children)

An interesting choice that is. Picking something like Rust would have benefitted them with a big community of open source enthusiasts that could help with contributions

[–] independantiste@sh.itjust.works 18 points 3 months ago (1 children)

they explained that they chose it because it is interoperable with their existing C++ code base

[–] Ephera@lemmy.ml 30 points 3 months ago (2 children)

But Rust is rather good at that, too, via cxx. Mozilla similarly had a C++ codebase where they wanted to integrate Rust.

Granted, this is raw theory. Maybe Swift is better in practice. But yeah, to me personally, it would need to be massively better to pretty much give up on open-source contributions.

[–] princessnorah@lemmy.blahaj.zone 9 points 3 months ago (3 children)

pretty much give up on open-source contributions.

You do realise that most major FOSS projects have an iOS app, right? The post I was looking at before this was for a new jellyfin app, small individual dev, has an iOS beta out. For a comparison, there are 9.1 million files on github in Swift, and 11.3 million in Rust.

As well, as far as contributions, Swift was designed from the getgo to be incredibly approachable for novices. While Rust is notorious for being unapproachable. Like I get the anti-Apple circlejerk is strong, but Swift is licensed under Apache 2.0, it's FOSS, so this argument is kind of ridiculous. Especially considering how much of Google's FOSS just gets a free pass.

[–] Sethayy@sh.itjust.works 2 points 3 months ago* (last edited 3 months ago) (1 children)

Most FOSS projects weren't allowed on the app store due to licencing, and although I think this has changed its also probably pushed off a lot of Foss devs.

Number of files doesn't really mean much more than number of lines though, especially between languages

[–] princessnorah@lemmy.blahaj.zone 2 points 3 months ago (1 children)

That information is well over a decade out of date. I remember when VLC had those issues. In a rare capitulation for Apple, they adjusted their terms to allow copyleft licenses.

As far as "probably" causing FOSS devs to stay away from the platform. Like I said, most FOSS projects have an iOS app. Hell, Jellyfin now has several FOSS iOS apps. Most of the iOS Lemmy apps that are available are FOSS, heck some of those are even iOS-only.

Like, I'm sorry, but this is about facts and not just your feelings. You said before that the choice of Swift over Rust would "massively" affect FOSS contributions while providing zero evidence to back that up. Sure, you're right, number of files doesn't mean much, but at least I provided a fact.

My personal opinion is that most FOSS developers are put off by "yet another chromium fork", and will flock to this project as a breath of fresh air, no matter whether it's Swift or Rust.

[–] Sethayy@sh.itjust.works 2 points 3 months ago

Not much feelings here, I was just looking into getting krita on one of my few iOS devices and found they wouldn't be able to comply with their GPL licence with apples structure, but hey were not getting personal here right so I must be wrong (personally)

[–] axat@mastodon.social 1 points 3 months ago (1 children)

@princessnorah @Ephera
Just because a code is open does not make it FOSS. There is a spirit to it.
Its the same argument that will make a country democratic just because people vote.
Apple is knows for its notorious tricks against developers and consumers, does everything that is against core FOSS values. So no it’s not FOSS.

[–] princessnorah@lemmy.blahaj.zone 3 points 3 months ago

I'm sorry, did you just retroactively change the meaning of FOSS to "thoughts and feelings" so you could throw Apple under the bus?

[–] Ephera@lemmy.ml -2 points 3 months ago

I don't know why you're so angry, just because I have a different opinion. You're also insinuating that I would be circlejerking against Apple or giving Google a free pass, which I'm not.

[–] mryessir@lemmy.sdf.org 3 points 3 months ago (1 children)

Barrier to contribute in Swift is wwwaaaaayyyy lower then Rust.

We once ported and Swift App to Kotlin by copy+pasting. It was one day of work.

Rust - imo - is overhyped. It has its niches. But to me it is not the swiss army knife. Swift has better expressiveness then Rust.

[–] Ephera@lemmy.ml 6 points 3 months ago (1 children)

It isn't, if you're already familiar with Rust. That's all I'm saying. Swift usage is largely isolated to Apple's ecosystem, which doesn't have a ton of overlap with the open-source ecosystem.

And I actually disagree that Rust is overhyped, because it can be used for creating libraries which can be called from virtually any other language, like you can with C and C++. Which means you're not locked into the Rust/Apple/whatever ecosystem, but instead could be coding the next SQLite without needing to be fluent in footgun.

From what I can tell, this would theoretically be possible in Swift, but hasn't been implemented: https://forums.swift.org/t/formalizing-cdecl/40677

But even if Rust was the most overhyped garbage, it would still be garbage that people are familiar with. ¯\_(ツ)_/¯

[–] mryessir@lemmy.sdf.org 2 points 3 months ago

Hehe. You came from a different direction. My main point is that reading, thinking and contributing in Swift is more familiar with the majority of developers. Currently.

Swift usage is largely isolated to Apple's ecosystem, which doesn't have a ton of overlap with the open-source ecosystem.

I agree that the usage is isolated and it is not represented in the FOSS community. And I am not an advocate for doing so. Though it is compatible and if it is a possible alternative it can be considered. If you compare it to other Syntax it is reading very easily and you can pick it up in 20 Minutes. They could even require to explicilty use type annotations to further aid accessibility for possible contributors or audits.

... creating libraries which can be called from virtually any other language, like you can with C and C++. Which means you're not locked into the Rust/Apple/whatever ecosystem ...

Let's agree that a lock-in should not be dependend on the implementation language. There are other implications on the build which may arise. I am neither familiar with rust nor Swift. Comparing implications for building and linking can't be compared by me on a professional level.

I further - without research - call out that Rust comes with implications on either library implementation or linkable procedures for an author in order to link to it. Neglecting thinks like nested interop between host/implementation language here.

But even if Rust was the most overhyped garbage, it would still be garbage that people are familiar with. ¯\_(ツ)_/¯

Two things: Every developer I have met in person whishes to get some project in Rust. No one has seriously started pushing or even learned it thoroughly. Second point: I didn't called it garbage! The language as it is awesome. I don't like its readability and its packaging.

When I read Rust sources it isn't fluent in my inner mind. Sure it is due to familiarity but I would also argue that the over-expressiveness kills reading speed as well. Though that should be inspected by more objective and competent people though.

[–] OfCourseNot@fedia.io 2 points 3 months ago

Take this with a pinch of salt, I'm not a programmer just a nerd that likes those kind of things. I tried them years ago first swift (I think it was in version 2) and a couple years later rust, and while both are great I found swift makes it easier to write clear code you're gonna understand and like when you come back to it. Rust was better I think with concurrency (at the time), you'll catch everything at compile time, but they talk about interoperability with c++, so this safety will be lost since most code interfacing with c++ will be unsafe.

[–] delirious_owl 0 points 3 months ago

Lol big community

[–] kionite231@lemmy.ca 31 points 3 months ago (1 children)

Thank you :/

[–] dohpaz42@lemmy.world 32 points 3 months ago

Ladybird Browser Team Selects Swift as Preferred Language Andreas Kling announces Swift as Ladybird's future language for better safety and ergonomics. Full transition awaits Swift 6.

ByBobby BorisovAugust 11, 2024 Ladybird Browser Team Selects Swift as Preferred Language Ladybird is a new name in the Linux ecosystem you might not be familiar with. So, let’s briefly explain what it’s all about.

It’s a web browser initiative, funded by $1 million, spearheaded by GitHub co-founder and former CEO Chris Wanstrath and tech visionary Andreas Kling. It seeks to challenge the status quo with a new browser written from scratch, completely independent of corporate interests. Our article on the subject has more on this. Now, back to the topic.

Over the past few months, Ladybird’s developers have been experimenting by rewriting different parts of the browser project in various languages. The outcome was clear: Swift emerged as the preferred choice among the team. According to Kling, the feedback favored Swift for its modern features and robust safety protocols.

Another significant advantage of Swift is its ongoing improvements in interoperability with C++. This development means Ladybird can adopt Swift gradually, without extensive rewrites, easing the transition and reducing potential integration issues.

Now, I’m sure you associate Swift with app development for Apple devices, where it’s been the go-to technology. But recently, that’s started to change.

What I mean is despite its strong associations with Apple, Swift has been making strides towards independence. It has been reorganized under a separate GitHub organization, distancing itself from Apple-specific projects.

This shift, coupled with better support for non-Apple platforms and diverse development environments, positions Swift as a more versatile and broadly applicable programming language.

Looking ahead, Ladybird plans to implement Swift once version 6 exits beta this fall. The upcoming release promises compatibility with the latest versions of Clang, essential for integrating Swift with Ladybird’s existing C++ code.

It’s worth noting that no browser engine has yet been developed using Swift, making this project particularly challenging. As things are still in the early planning stages, we shouldn’t expect to see any initial versions of the Ladybird browser this year.

A more realistic timeline suggests an early preview release could happen in 2025, though the developers have not yet committed to specific dates.

For more information, refer to Kling’s post on X.

Bobby Borisov Bobby Borisov

Bobby, an editor-in-chief at Linuxiac, is a Linux professional with over 20 years of experience. With a strong focus on Linux and open-source software, he has worked as a Senior Linux System Administrator, Software Developer, and DevOps Engineer for small and large multinational companies.

[–] KLISHDFSDF@lemmy.ml 25 points 3 months ago (2 children)

For anyone who knows more about this, how does it compare to Servo? https://servo.org/

[–] trevor@lemmy.blahaj.zone 13 points 3 months ago* (last edited 3 months ago)

Servo barely works right now. Ladybird somewhat works. Neither are ready for daily use.

[–] leopold@lemmy.kde.social 5 points 3 months ago* (last edited 3 months ago)

servo is a lot further along because they're not bothering with javascript and are just using spidermonkey. see WPT: https://staging.wpt.fyi/results/?product=servo&product=ladybird

[–] MigratingtoLemmy@lemmy.world 13 points 3 months ago

WTF?

[–] MultipleAnimals@sopuli.xyz 12 points 3 months ago

That page freezes my firefox and uses a lot cpu power

[–] sirico@feddit.uk 5 points 3 months ago* (last edited 3 months ago) (1 children)

Rust would have been good in the long term but it'd take a long time to get to release.

Swift mates sense for rapid deployment.

Go would have been my choice concurrency would maybe help with lots of tabs

[–] kewko@sh.itjust.works 2 points 3 months ago

Tabs are typically spun into separate processes for sandboxing reasons anyway

[–] Asudox@lemmy.world 2 points 3 months ago

I do wonder: why not rust? It would have been amazing. A fast language on par with C++ that also is memory safe. But Swift? You gotta be kidding me...

[–] delirious_owl 2 points 3 months ago

Oh, programming language. My brain was stuck trying to figure out if Swift is related to Swiss.

[–] Comexs@lemmy.zip 2 points 3 months ago (1 children)

I not entirely sure but from what I can remember Andreas Kling is seen using Mac-os in a Ladybird update video so it could be possible that it is his main operating system. Take this with a grain of salt.

[–] warmaster@lemmy.world 1 points 3 months ago

Another Chromium incoming?

[–] amzd@lemmy.world -3 points 3 months ago

Swift is a fantastic language and with c++ interop out of the box it’s the obvious choice.

[+] JustMarkov@lemmy.ml -26 points 3 months ago* (last edited 3 months ago) (4 children)

I would have preferred Rust, a language created by Mozilla instead of one with ties to Apple, but I'm not dev so I can't really judge. What are your thoughts?

I don't know anything about Swift, but people like to ignore the fact, that Rust is not entirely free, as it fails to exercise freedom 3.
tl;dr: Rust Foundation don't want you to apply modifications to their language without "explicit approval".
And you are also limited to share modified versions of their software.

(If someone can imply, that Python and Perl have similiar restriction — they are not the same, because both of their trademarks protect usage of software against fraud, but you can freely patch and modify it.)

For me personally, seeing LadyBird not choosing Rust as their main language is very promising. Rust software is everywhere now and this is concerning.

[–] Hawk@lemmy.dbzer0.com 38 points 3 months ago (1 children)

I've read through your links. They don't have much to do with the codebase itself, but with protecting the trademarks.

From what I read, you're free to change whatever you want. You just can't go around using their trademarked names for your modified version.

[+] JustMarkov@lemmy.ml -16 points 3 months ago (1 children)

If I wanna modify and redistribute their language and use Rust or Cargo in the name I should not have to ask for an explicit permission, this is the freedom 3 problem.

This is also why I gave Python and Perl examples. I can modify both Python and Perl, calling them the same way, but I can not do the same thing with Rust.

I'll leave their trademarks comparsion under the spoiler for those, who interested.

Spoiler

Rust:

Distributing a modified version of the Rust programming language, compiler, or the Cargo package manager with modifications other than those permitted above and calling it Rust or Cargo requires explicit, written permission from the Rust Foundation.

And Python:

Use of the word "Python" when redistributing the Python programming language as part of a freely distributed application -- Allowed. If the standard version of the Python programming language is modified, this should be clearly indicated. For commercial distributions, contact the PSF for permission if your use is not covered by the nominative use rules described in the section "Uses that Never Require Approval" above.

Let's also look at Perl:

People sometimes ask if TPF's use of an onion in the Perl logo means that independent projects that use or relate to Perl need TPF's permission to use an onion of their own design in connection with their project. The answer is "not necessarily" as long as no likelihood of confusion is created. One of the fundamental legal bases for trademark protection is to make sure that the public can depend on a mark as an accurate indicator of a particular source or relationship, and one way of defining trademark infringement is to say that the infringing mark creates a likelihood of confusion. Likelihood of confusion is determined based not only on making a comparison of the marks side-by-side, but also on making a comparison of the contexts in which they are actually used. Thus, it's easy to imagine independent onions that would be fine, and independent onions that might not be.

[–] jim@programming.dev 23 points 3 months ago (2 children)

Please read this and try again.

https://www.gnu.org/philosophy/free-sw.en.html#packaging

Rules about how to package a modified version are acceptable, if they don't substantively limit your freedom to release modified versions, or your freedom to make and use modified versions privately. Thus, it is acceptable for the license to require that you change the name of the modified version, remove a logo, or identify your modifications as yours. As long as these requirements are not so burdensome that they effectively hamper you from releasing your changes, they are acceptable; you're already making other changes to the program, so you won't have trouble making a few more.

[–] princessnorah@lemmy.blahaj.zone 8 points 3 months ago

Yeah, I don't exactly think it's particularly burdensome to have to rename your fork so that people don't confuse it with the software you forked from. Without this restriction, FOSS projects would have absolutely zero recourse against bad actors. A non-FOSS competitor could just waltz in, fork their code and turn it into absolute hot garbage, convincing enough people that it's the original project to make it all worth their while.

[+] JustMarkov@lemmy.ml -7 points 3 months ago (1 children)

Please read this and try again.

Try again what? This is a debatable topic. I can simply refer to this line:

As long as these requirements are not so burdensome that they effectively hamper you from releasing your changes, they are acceptable;

And point out, that rebranding a whole programming language is not a piece of cake. So this is burdensome and hence is the issue for freedom.

[–] jim@programming.dev 7 points 3 months ago (2 children)

Dude, if you're being obtuse on purpose because you have an ax to grind against Rust, try a different approach. You're not getting anywhere, clearly by the fact that no one agrees with you.

If you don't like that Rust has a restricted trademark, then call that out instead of trying to label the software and it's license as non-free. It's literally called out in my source that name restrictions ipso facto does not violate freedom 3.

But if you genuinely believe that the implementation of the Rust language and it's trademark is burdensome to create a fork, and you want people to believe you, then you gotta bring receipts. Remember, the benchmark that we both quoted is that it "effectively hampers you from releasing your changes". It being "not a piece of cake" doesn't cut it.

Hint: Google Rust forks since their existence also undermines your claim.

Good luck.

[–] refalo@programming.dev 2 points 3 months ago

As an outsider with no skin in anyone's game, I find it a bit disingenuous to say that one person's interpretation of subjective terms is somehow less "correct" than anyone else's.

[–] JustMarkov@lemmy.ml 0 points 3 months ago

Remember, the benchmark that we both quoted is that it "effectively hampers you from releasing your changes". It being "not a piece of cake" doesn't cut it.

The easiest example is that you'll have to adapt all Rust-dependant applications to the Rust fork, 'cause it is a programming language.

But still, don't get me wrong. I'm not trying to say that Rust is a bad language or something. I'm just trying to point out on the problem, that was adressed to Rust Foundation before.

Good luck to you too.

[–] turnipjs@lemmy.ml 27 points 3 months ago

That... is not a restriction on freedom 3. You could complain about your inability to use the rust name for anything you want but that is not the same thing as your ability to distribute modified versions of the software. It is also fairly standard practice for foss software to restrict the use of such trademarks. For example, Gnome does pretty much the same thin. FreeBSD as well. Libre Office also has similar restrictions, although they are defined more nebulously. It is not clear to me what usages are allowed with the Linux trademark but they certainly do restrict who can use it and for what and you must get permission before using it. See also, about trademarks in FOSS: https://www.lexology.com/library/detail.aspx?g=9d96e1bf-bced-48f7-b5b4-ee561e7a9348

The software is free. The trademarks are not. The four freedoms are about the software and not about trademarks. You could fork Rust and call it Corrosion, just like people have forked Firefox and called it Waterfox.

[–] delirious_owl 2 points 3 months ago

Its also terrible when it comes to security, specifically crates

[–] Asudox@lemmy.world 1 points 3 months ago

There's a reason why software is being made with Rust now. It has the speed of C++ (sometimes faster), has a nice syntax, is memory safe by default, has the best compiler error messages and also the book is very good. I learnt entirely by the book and it's very good at explaining things.

Open Source

Useful Links

Rules

Related Communities