• 5 Posts
  • 166 Comments
Joined 1 year ago
cake
Cake day: September 7th, 2023

help-circle
  • Sorry to hear about the network manager issues! I could be wrong on this, but I think Gnome is not the best supported DE in void - possibly because of how heavily tied it is to systemd. I wish I could help, but I still configure my wifi using wpa_supplicant.conf. Maybe dbus wasn’t setup properly?

    Regarding audio, the pipewire documentation for Void is pretty good. It’s pretty thematic of the whole Void linux experience: you have to read the handbook and follow its steps closely, but it’s very well written and easy to understand. It can definitely be time-consuming as well though.

    Void is definitely all the things you mentioned. I installed it on a few machines, the first in early 2020 and it has never given me an issue. Extremely stable and boring. I’m impressed that it has so many packages in its repository, but that’s a testament to how well xbps is written. But there are a few things missing since it’s fair from the mainstream, including packagekit. I had never heard of it before you mentioned it - I found a fork on github to support it, but it doesn’t look very well maintained.




  • The difference is how you interact with the browser engine. Blink is very easy to embed into a new browser project. I’ve seen it done - if you’re familiar with the tools, you can build a whole new browser built around the Blink engine in a few hours. You can write pretty much whatever you want around it and it doesn’t really change how you interact with the engine, which also makes updates very simple to do.

    With Firefox, it’s practically impossible to build a new browser around Gecko. The “forks” that you see are mostly just reskins that change a few settings here and there. They still follow upstream Firefox very closely and cannot diverge too much from it because it would be a huge maintenance burden.

    Pale Moon and Waterfox are closer to forks of Firefox than Librewolf for example, but they’ve had to maintain the engine themselves and keep up with standards and from what I’ve read, they’re struggling pretty hard to do so. Not a problem that Blink-based browsers have to deal with because it’s pretty easy and straightforward to update and embed the engine without having to rewrite your whole browser.

    Unfortunately, since Google controls the engine, this means that they can control the extensions that are allowed to plug into it. If you don’t have the hooks to properly support an extension (ie. ublock), then you can’t really implement it… unless you want to take on the burden of maintaining that forked engine again.

    That said, Webkit is still open source and developed actively (to the best of my knowledge - I could be completely wrong here). Why don’t forks build around Webkit instead of Blink? Not really sure to be honest.


  • I chuckled a bit while reading this, because what you wrote is exactly where Blink came from. It was a fork of webkit, which in turn was derived from KHTML. Then again, the fact KHTML was discontinued does support your point to an extent too, I guess.

    But the point is, Chrome is doing exactly this - providing the engine free as in beer and letting people embed it however they like. And yet, what you’re predicting, ie. not using the original but just using forks instead, doesn’t seem to be happening with Chrome - they still enjoy a massive fraction of the market share. There’s no reason to believe that this couldn’t happen at Mozilla as well. People usually want the original product, and it’s only a small fraction of people that are really interested in using the derivatives.


  • Ironically, the anti monopoly lawsuit against Google will end this.

    People are quick to assume this, and there’s a very good chance that they’re right, but I don’t think we should take it as a given. It’s always possible that there could be some sort of court decision that allows Google to keep funding Mozilla after the “breakup” is complete.

    In any case, we don’t yet know what the outcome of the antitrust case will be, so I think it might be best to avoid making statements of certainty like this until we see how things really shake out.

    We should definitely take the possibility of this happening very seriously though.


  • You’re right about the fact that building an engine is hard, but Socraticly speaking, then why are there so many blink-based browsers and so few gecko-based ones? The answer is because blink is easy to embed in a new project and gecko isn’t.

    If Mozilla really wants to take back the web (and I honestly don’t think they actually do), then what they should really be doing is making gecko as easy to embed in a new browser as blink is. They don’t do this, and I suspect that they have ulterior motives for doing so, but if they did, I think we would be much closer to breaking chrome’s grasp on the web.

    Because let’s face it: Mozilla makes a pretty damn good browser engine. But they don’t really make a compelling browser based off it. Ever noticed how Mozilla has been declining ever since they deprecated XPCOM extensions? It’s because when they provided XPCOM, it enabled users to actually build cool and interesting new features. And now that they’ve taken it away, all innovation in browser development has stagnated (save for the madlads making Vivaldi).

    They need to empower others to build the browser that they can’t. That’s what would really resurrect the glory days of Firefox in my opinion.



  • This has always been the whole point behind the Trojan Horse that is systemd. Now that Poettering/Red Hat control the entire userspace across virtually all distros, he/they can use it as a vehicle to force all of them to adopt whatever bullshit he thinks of next.

    This is what the Linux ecosystem gave away when they tossed their simple init system to adopt the admittedly convenient solution that is systemd. But in reality, the best solution was always to drop init, and instead replace it with an alternative that was still simple to replace if the need should arise. But now that everyone is stuck on systemd, they’re all at the mercy of Poettering’s Next Stupid Idea.

    Convenience comes at a price. systemd is the Google Chrome of Linux userspace. Get out while you can.





  • Indeed, Reddit was a great example of this. All of the stupid things they tried to pull off in the past few years (selling user data, turning off the API, insulting their users, VPN blocking, to name a few) would have not worked when they were a growing website. Now that they have so many low quality users, they can do that successfully because they know that said users are too dumb to realize how they’re being abused. Even larger websites like Twitter and Facebook operate this way.

    The takeaway here is: don’t focus on having many users, focus on having good users. All relationships are a two-way street, and if you’re on the side of the street with too many people, you don’t have any personal leverage on your own. It’s in your best interests to get out of that relationship.



  • But part of the appeal of Linux is the fact that you can repurpose existing computers running other OSes to run Linux instead. This is a great way to lower the barrier to entry for Linux, because it’s easy to test it on a Live USB or a dual boot. It’s much harder to do this on phones because they have locked bootloaders.

    Another problem is that phones are not productivity devices - they’re consumption devices. Maybe this is just my personal bias, but I don’t think people will be as passionate about liberating their phones because they’re inherently less useful than computers. Convenient, yes, but useful? Not as much.

    That said, I would love to be proven wrong. I would definitely consider a Linux phone if they become more popular/useful, but I can’t really justify spending hundreds of euros/dollars on something for which I don’t see any particular use.





  • I agree, I don’t think they have any limit. Look at how invasive platforms like Facebook are, and yet they’re still massively popular. Mobile operating systems are several times worse than Windows is for privacy and data harvesting, and people clearly don’t care at all. They’ll even happily consent to ever more levels of it - there’s no evidence to suggest that they’ll ever stop.

    One of the biggest “mistakes” Microsoft made was not realizing how lucrative data collection could be. Back in the quaint old days of early PC computing, spyware was actually considered a bad thing. When Google came along, that philosophy was flipped on its head. Over the past 15 years, Microsoft has seeing what these spyware vendors are doing and salivating because they know that they are still the kings of computing - they still have total control the PC market and there’s a good chance that it’s not really going anywhere because most people hate change - even though Linux is starting to make inroads in quite a few places.

    It would not be surprising if, in a few years, a Windows OS looks like a Google search page, or a cable television channel.




  • I haven’t done too much work with WASM myself, but when I did, the only languages I saw recommended were Rust, C++, or TinyGo. From what I’ve heard, Rust and C++ are smoother than TinyGo. Garbage collected languages usually aren’t great choices for compiling to wasm because wasm doesn’t have any native garbage collection support. That limits your selection down a lot.

    But another option you may want to consider is Nim. As I understand, it compiles to C, so any C->Wasm compiler should theoretically work for you as well. I did a quick search and wasn’t able to find any great resources on how to do this, but you might get a bit more lucky. Good luck!