Conversation
jarkko

Jarkko Sakkinen

Edited 9 days ago
Flatpak 2 driven by these cloud natives will be a catastrophe.

I'm not app developer but even I know what requirements there are from a platform to momentize on it.

#flatpak #gnome
2
0
0
Flaky@furry.engineer

Flaky

Reply to @jarkko

@jarkko Something happen with GNOME?

2
0
0
jarkko

Jarkko Sakkinen

Reply to @Flaky@furry.engineer
@Flaky Breaking backwards compatibility to previous version.
1
0
1
jarkko

Jarkko Sakkinen

Reply to @jarkko
@Flaky You can do that but with apps you need to be extremely conservative, not should at a conference that "NOBODY USES X11 ANYMORE" like the leader of this project did. It's not for apps then.
1
0
1
kayttaja@plush.city

lilja neodog_blush_hide

Reply to @jarkko

@jarkko @Flaky i dont think the guy who said that is a flatpak developer

1
0
0
jarkko

Jarkko Sakkinen

Reply to @kayttaja@plush.city
@kayttaja @Flaky OK, that's good :-) Why he made then such a bold statement? Just interested. I only speak where I do.
2
0
1
kayttaja@plush.city

lilja neodog_blush_hide

Reply to @jarkko

@jarkko @Flaky idk trolling or some shit

1
0
0
jarkko

Jarkko Sakkinen

Reply to @kayttaja@plush.city
@kayttaja @Flaky Yeah. One might be misled (like me). Thanks for correcting this!
1
0
1
jarkko

Jarkko Sakkinen

Reply to @jarkko
@kayttaja @Flaky Intrusive take but I would base myself pure app platform on top of a subset of Win32 API. It's universally cross-compatible almost and Linux is now the best version of Windows.

And it's already done, as it could be derived form SteamOS
1
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
Edited 9 days ago
@Flaky @kayttaja It would be even cross-compatible with BSD distributions i.e., maxed out spread.
0
0
0
2something@transfem.social

2something@transfem.social

Reply to @jarkko

@jarkko @Flaky @kayttaja

The “cloud native” guy who said flatpak would hard-depend on systemd is not a flatpak developer.
https://github.com/flatpak/flatpak/commits?author=castrojo

He was likely trolling, and others (including me) fell for the troll and amplified it.

1
0
0
jarkko

Jarkko Sakkinen

Reply to @2something@transfem.social
@2something @Flaky @kayttaja I'm happy to be corrected and truly sorry that I fell for it :-)

I've also spent countless hours to enable Flatpak to my Buildroot build so kind of was sensitive topic. I'll continue using it and see what happens.

The way I approach GNOME is:

1. Minimal Buildroot packaging.
2. Pre-seed majority of GNOME stock from Flatpak.

It does this use case pretty well.
1
1
1
jarkko

Jarkko Sakkinen

Reply to @jarkko
@2something @Flaky @kayttaja That has led to me googling stuff about the topic and not with that critical eye apparently. my mistake sorry!
0
1
1
tragivictoria@catgirl.cloud

Victoria 🏳️‍⚧️

Reply to @Flaky@furry.engineer

@Flaky @jarkko how come GNOME is even related here? Flatpak isn't a GNOME project

1
0
0
Flaky@furry.engineer

Flaky

Reply to @tragivictoria@catgirl.cloud

@tragivictoria @jarkko I saw the GNOME hashtag and got confused lol

0
0
0
staticnoisexyz@infosec.exchange

Adam Chovanec

Reply to @jarkko

@jarkko where did flatpak devs say that they're adopting cloud-native stuff?

1
0
0
jarkko

Jarkko Sakkinen

Reply to @staticnoisexyz@infosec.exchange
@staticnoisexyz It was here in Mastodon: https://hachyderm.io/@jorge/116607961190448307

I'm not familiar with app ecosystem in general or what cncf does actually.
1
0
0
staticnoisexyz@infosec.exchange

Adam Chovanec

Reply to @jarkko

@jarkko ok so Jorge isn't a Flatpak developer and doesn't speak for the project (neither am I). Secondly, Flatpak is considering moving away from ostree to OCI images as a means of transport of applications. S. Wick talked about it in the previous LAS talk: https://lwn.net/Articles/1020571/ And that decision sounds very solid to me. Pretty much nothing changes for the application developer, it's just Flatpak making use of existing tools and technologies instead of making their own.

1
0
1
jarkko

Jarkko Sakkinen

Reply to @staticnoisexyz@infosec.exchange
@staticnoisexyz OK, thanks for the explanation :-)
1
0
0
barthalion@treehouse.systems

Bart Piotrowski

Reply to @jarkko

@jarkko @staticnoisexyz You may want to read https://barthalion.blog/flathub-internals-cdn/ and https://barthalion.blog/flathub-internals-cdn-and-deltas/ to understand why the current way of serving files fails short. Switching to OCI will make serving large blobs effectively much easier vs the current duct taping.

1
0
1
jarkko

Jarkko Sakkinen

Reply to @barthalion@treehouse.systems
@barthalion @staticnoisexyz thanks, good to hear. seems that it's a good basis for what i'm doing after all :-)

have not seen anything this unprofessional for some time and that's why i fell for it, duh. lessons learned. i'll check the facts properly next time.
0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: