• 1 Post
  • 85 Comments
Joined 1 year ago
cake
Cake day: September 7th, 2023

help-circle

  • 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.


  • Website redesigns. Just more whitespace all over the place, less information on the screen, and more trouble trying to get anything done.

    Github is especially bad about this. I’m so tired of only being able to fit about 50 lines of code on the screen at a time, or issues with a similar lack of information density. I can understand this paradigm for websites that you only use once every year or so, but for something that most people use regularly every day, it’s such a backwards anti-productivity trend. I hate it… hope it dies someday.


  • 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.


  • Completely agree. He just needs to look within his own borders to see why. The Left Alliance scores the largest bloc of the election; then Macron spurns them and looks to the right for a Prime Minister instead. Are we really supposed to believe him when he says he’s shocked that people are losing faith in the system?

    At this point, it’s hard to see how he can be this stupid. The man is a liar and always has been. He understands well that to build trust (no matter with whom - either the Left Alliance in his own country or the Global South, or anyone else), he has to back down and learn to compromise.

    But for him, it’s much easier to pretend that he doesn’t know what’s going on, bury his head in the sand, and continue with the status quo - the way he’s paid to do.




  • 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 think each of these needs to be handled in separate ways. For example, search could continue to be a conglomeration that includes maps, mail and possibly cloud. Android can just be split very easily into a separate company and same for Youtube, since that would basically be another Netflix or whatever.

    Ads, in my opinion, is the most important one though. That absolutely has to be shattered into thousands of tiny pieces, all of which need to be forced to compete with each other, for the benefit of all internet companies anywhere. It would be a massive boon to companies everywhere and would provide an opportunity for lots of innovation in the advertising space, ie. trying ads that are less intrusive or ones that are cheaper because they don’t rely on tracking information.

    And another thing I think people need to understand about search is that building the search engine is not the hard part - the hard part is figuring out how to pay for it. Search is really expensive - crawling websites, indexing, fighting spam abuse. That’s what really makes Google successful - the fact that they coupled it with advertising so that they could cover all the expenses that come with managing a search engine. That’s much more important than the quality of the results, in my opinion.

    And as for Chrome: well, personally I think that monopoly has been the most damaging to the internet as a whole. I would love to see it managed as part of a non-profit consortium. There should not be any profit motive whatsoever in building a web browser. If you want a profit motive, build a website - the browser should just be the tool to get to your profit model, not the profit model itself. And therefore it should be developed by multiple interest groups, not just one advertising company.

    Anyway, I know this is all an impossible fantasy. Nothing in the world is done because it’s right or wrong, it’s done because it serves whoever holds the most power. But if there were a just world, this is what I think it would look like.


  • I doubt that you’re interested in arguing in good faith, but if by some miracle you do care about having an informed opinion before opening your mouth, how would you respond to things like this?

    This essentially killed my (EU-based) startup in the project management and collaborate space. Before MSFT bundled Teams with O365 we were rapidly growing and closing enterprise customers in the automotive, energy and education industries with high retention rates. Right around the time the Teams bundling started our retention dropped, churn went through the roof, growth slowed down, we failed to raise our next round because of it and had to drastically downsize the company, causing even more churn (about 80% net churn in 2 years). This move by the EU is good, but too little too late - 99% of the companies that were hurt by this have already shut down, and the ones still running will take years to recover…


  • Interesting! Sorry, I don’t know why I thought you were using swipe keyboards, it must have been stuck in my memory from reading other comments. I definitely agree that pressing the buttons was a little annoying, but manufacturers could probably make softer buttons if they were willing to put the money into developing them.

    Anyway, I really miss the phone I had from about 2008-2010. It had two sliders that moved in orthogonal directions. One of the slide directions revealed a standard 12-button phone pad, while the other had a 4-row keyboard. And yet, I’m pretty sure it was under 1.5cm, so not too large. It was definitely easier to keep in my pocket than current phones!

    If it weren’t for reading Lemmy/RSS feeds and a camera, I’d probably be going back to dumb phones for my next one…


  • But what’s the error rate? I could type at 200 words per minute (even on a phone!!) if I didn’t care about how many typos I was making. And swiping keyboards get confused incredibly easily. The error rates are especially bad when you’re writing words that only use a single row of keys - on QWERTY keyboards for example, try writing something like “type”, and you could get that, or you might get something else, like wipe/write/ripe. Other groups could include things like tip/top, pit/pot, wit/wire and the selected word will be wrong almost as frequently as it’s right. And autocorrect systems can’t really correct for things like when you mean to press enter and hit the backspace key instead. Plus, their suggestions are generally just very stupid. So while buttons take longer to press on physical keyboards, the reduced error rate makes typing speed about the same in my experience.

    Plus, with physical buttons, you get tactile feedback, so you can tell when your fingers are slightly off and adjust them, whereas on a flat surface, you have no idea whether you pressed the correct button or not. You have to stare straight at the screen to make sure every press is correct, which is exhausting and bad for your eyesight. I feel a lot more eyestrain from simply typing on phones, whereas with physical buttons, I didn’t even have to look at the screen, and I could look at something else around me while typing. And don’t get me started on how many calls I’ve missed because I accidentally hit the hang-up button, or couldn’t find the accept call button - not a problem when you have physical buttons!

    Regarding screen real estate, all you need is a slide-out keyboard. They work great!

    There are a few downsides to physical keyboards, but in my experience, they’re far superior to non-keyboard devices. But what can you do - in the 21st century, practicality never matters, it’s just all about aesthetics and nothing else…


  • The intent is to allow companies time to implement the change. But if you’ll pardon my cynicism, in practice, what ends up happening is companies just use it as a tactic to delay the implementation and continue recording the revenue.

    At the very least they should forfeit the revenue that they earn during the period for this. I’m not sure exactly how the fines work and whether they take this into account, but I doubt Apple is seriously going to use the 12-month period to actually come clean and change their ways. I think they’ll just use it as more time to come up with some new bullshit form of non-compliance.


  • Excellent news:

    At the heart of Monday’s findings are three elements of Apple’s practices, including fees charged to app developers for every purchase made within seven days of linking out to the commercial app.

    source

    This is, in my opinion, the most egregious non-compliant practice from Apple. They have no reason whatsoever to entitle themselves to purchases made outside their repository just because the software runs on their hardware. It’s also the most asinine set of rules that they established to pretend that they were complying with the DMA.

    It’s a bit disappointing that it will take so long before the fines can be enforced, but I really hope that they get the maximum penalty over this because it’s really the most shockingly brazen breach of the DMA’s terms. In fact, I hope that they get imposed the maximum penalty multiple times - the same article I linked mentions that there are two other DMA investigations being launched into Apple, though I don’t know what grounds those other investigations are looking into.

    And I really hope Apple gets the message loud and clear: they’re gonna start making less money. And this is a good thing. They don’t deserve it, and they were never entitled to it in the first place. This is what happens when you invent new revenue streams that are criminally worthless.


  • Such a sad world we live in. When the internet was hitting the mainstream, virtually everything was standardized. There were RFCs for probably every standard the internet operated on. Email, HTTP, DNS, TCP/UDP/IP, etc.

    Today, we live in a world where we can’t even decide on a fucking chat protocol without making it a proprietary piece of garbage. The internet has been consolidated into giant companies that see interoperability as a weakness that enable their competitors and prevent them from oppressing and exploiting their users.

    A small group of gatekeepers that kill anything nice for their own short-term gains: it is sad but true that it feels like any technology that’s commercially successful will end this way.