481–490 of 510 posts
Earlier quoted context omitted.
I too hate when companies sponsor open source projects.
[flagged]
Earlier quoted context omitted.
You're severely misinformed and parotting misinformed meme interpretations of fiduciary duty. Integrity and a healthy market align with fiduciary duty as long as one can make the argument that it's in the long term interest of the company. It's really, really difficult to find examples of a person being held liable for not upholding their fiduciary duty because what can be argued as good for the long term success of…
Since you seem so well-informed I would love any example of good-will and strictly not-for-profit activities done directly by a large corporation with shareholders which weren't done have other reasons. Examples of things which don't count: - Supporting an open source competitor to avoid getting hammered by antitrust - Giving money to a foundation (which they may or might not own) for greenwashing - Giving money to a…
What evidence would be required for you to believe that a donation to an environmental cause wasn't greenwashing?
Your list of exceptions seems fairly obviously aimed at making the task impossible because it's all based on interpretation of motives. You're essentially discounting all actions that have positive societal effects as long as doing so is motivated by money which is counter to the point I was making.
Giving money away to charity, by the meme interpretation of fiduciary duty, would be illegal. Instead, companies do it all the time because it makes them look better which might improve their business outlook in the future. That satisfies fiduciary dury despite it being a red line in the accounting books.
Wouldn't you like to live in a world where people care enough about doing good things that they'd prefer to patronize companies that do good things? That seems like an incredibly positive effect, regardless of the business' motives.
Earlier quoted context omitted.
> I don't understand why we always assume bad faith. I'm already bombarded with cloudflare captchas when using Firefox, especially on Linux. Residential IP address. I'm suspicious of everything cloudflare is doing right now.
I recently saw https://neal.fun/not-a-robot/ on the front-page but then I gave up as that's my daily reality with cloudflare and friends already. I use 3 browsers on linux with Thai IP address because at least one of them is always blocked by cloudflare. Especially if I go work on public wifi I often actually have to hotspot myself to 4g to even get stuff to load. I've started taking more extreme stance these days of…
I compare Cloudflare to border control. Open up your bag. Answer the questions. Present your papers.
I cannot for the life of me understand the Omarchy hype. The Linux community has been theming their distribution installs for decades. What distinguishes this from that?
Earlier quoted context omitted.
> I don't understand why we always assume bad faith. I'm already bombarded with cloudflare captchas when using Firefox, especially on Linux. Residential IP address. I'm suspicious of everything cloudflare is doing right now.
Anecdotally, I'm not. I always use Firefox (or Zen) and get almost no Captchas. Neither at home, nor at work. Not on Windows, not on Linux, not on macOS. I'm not going to say that Cloadflare isn't doing anything fishy, but if they are, it's probably more complicated.
Cloudflare can't determine who you are? No website for you.
Earlier quoted context omitted.
Arch linux is a great linux distro that's kinda difficult to set up (more so historically but it's got that reputation). Hyprland is a great WM that has garbage default settings and requires wading through tons of documentation, as well as a lot of effort to set up. Omarchy is a distribution that ships Arch + Hyprland with sane defaults. The whole thing installs in minutes, and is overall very easy to get going with.…
Sounds like Omarchy also ships with a bunch of bloatware. Why would I need the Hey or Basecamp apps – neither are targeted at developers, neither are commonly used, and both are just websites loosely packaged as installable apps anyway. Similarly for Steam (which runs at startup by default I believe), Spotify, Minecraft (which will bring a JVM?). It's bordering on Dell shipping Norton Antivirus to everyone and callin…
Apart from Spotify, it ships with a few app launchers for PWAs for some of 37signals' stuff. These launchers are easily removed, and basically just launch chrome windows.
It does not ship with steam or minecraft, though it has a menu where you can install it (along with various popular software, mainly development tools).
Earlier quoted context omitted.
If you feel it's not for you, then it's probably not for you. I don't think Omarchy is or needs to be for everyone. Its recipe for success is likely that it's catering to a fairly particular archetype that's generally overlooked by most distributions and OS vendors, and not trying to be or do anything else.
I don't think distributions or OS vendors focus on that because imagine the outrage if you installed Windows and it pre-installed Zoom, Spotify and 80 other apps for you out of the box. I think it's popular because DHH turned dotfiles into a product and it's being marketed as a distro. Arch + (Hyprland, Waybar, Walker and Mako) are all really popular and standlone tools that make up a reasonable looking desktop envir…
The bundled software aspect is also kinda exaggerated. It almost entirely consists of app launchers for a few chrome-based PWAs. There's like no software to speak off, it's just a .desktop-file you can remove if you don't want it (there's even a menu for that).
It's arguably more of a demo of Omarchy's excellent PWA tooling than anything else, where you can create your own PWAs with a simple TUI that blend seamlessly into the rest of the system.
This is the supposed bloatware looks like
$ cat ~/.local/user/applications/HEY.desktop
[Desktop Entry]
Version=1.0
Name=HEY
Comment=HEY
Exec=omarchy-launch-webapp "https://app.hey.com"
Terminal=false
Type=Application
Icon=/home/user/.local/share/applications/icons/HEY.png
StartupNotify=trueEarlier quoted context omitted.
CF is not magic, they have limits too. What's the point of serving cached copies to bots while real users experience unavailability?
Unless they're actually dropping the connections with a RST, I wonder how much bots repeatedly hammering at their CAPTCHA pages (which is actually relatively large in comparison to many static sites) costs them, vs. just serving the actual content which could actually be smaller.
Earlier quoted context omitted.
Anecdotally, I'm not. I always use Firefox (or Zen) and get almost no Captchas. Neither at home, nor at work. Not on Windows, not on Linux, not on macOS. I'm not going to say that Cloadflare isn't doing anything fishy, but if they are, it's probably more complicated.
I am. Try to browse anonymously. On the modern internet you're no longer allowed to do this. Cloudflare can't determine who you are? No website for you.
This doesn't resonate with me generally. How are you trying to browse anonymously?
Earlier quoted context omitted.
While I agree with you, as indicated by my comment about Google having de facto control, the terms upstream or downstream when discussing forking an open source codebase has specific meaning. Chromium is not a downstream forked that has ripped all the google pieces out. It is the upstream codebase that Google then builds all their telemetry and other Google shenanigans into. If we're discussing someone else forking C…
"upstream" and "downstream" is about the direction changes flow. Changes flow from Chrome into Chromium. The fact they arrive in the Chromium repository before they arrive in a public release of Chrome is not relevant.
It is correct that Google can and does decide that some features should remain private before they are developed. However, there are significant logistic and cultural hurdles to keeping something private, and as a result it's really only possible in certain parts of the codebase. Sometimes things that have been developed in private are eventually made public, and Chrome devs will often call that "upstreaming", but I think that's not really the same thing as what most people are talking about when they use the words upstream and downstream. And these instances are fairly uncommon in the history of the project.
Otherwise, IMO it is not really correct to say that changes flow from Chrome into Chromium. Nearly all development is done in the public repos and so they would be available simultaneously for either build. There aren't really official releases of Chromium per se, but a full build of Chromium containing a given change is basically always available before the corresponding full build of Chrome. There may be very rare exceptions for security fixes that are shipped before they are made public, but it would actually pretty hard to land such a change so I doubt it's happened more than a few times.
So, more generally speaking, in my opinion it's not really useful to talk about "upstream" and "downstream" for Chrome and Chromium, definitely not in the day-to-day sense. Chrome and Chromium are multi-repo projects, and there is only ever a single copy of a particular repo that is used for either. The same branches in a given repo are used for both Chrome and Chromium at any point in time. There is a main branch and release branches, and most of the time (but not always) a change will land in the main branch before a release branch. But I don't think most people would call "main" upstream of "release" in that sense.
[ There are rare situations where Google will develop experiments on a private branch of a repo, but those don't usually end up getting shipped to anyone. ]
This is different from how (most of?) the other Chromium-based browsers operate, where my understanding is that they usually do have true forks of (some of) the repos and changes flow downstream from the Google-maintained ones to ones under their control in the normal sense of the word.