When things get too complex for C, that's where C++ should be used... but I'd generally rather use something else instead. A lot of languages have been created to avoid using C++. Take your pick.
I dunno. I've been making free software for 3 decades and I still think it's fun. While I do get slop PRs sometimes, it's not frequent. And when I want to land a patch in someone else's project, I haven't really been having difficulty doing so.
The main change for me has been... if I want to send someone a patch, it's more important now to talk to them about it first. But I was doing that anyway. Join the chatroom, let people know I found an issue and am working on fixing it, maybe get their advice on how they think it should be solved (to make sure it fits with their project and goals), and then send code. And stick around to help with testing and stuff. It's not much different than how things were before everything moved to GitHub.
Talk to people. Be a part of the community. That's what made free software work in the past, and it's what makes free software work now. As the article said, it was never just the code.
It's wild that anyone still uses Adobe software these days. Adobe is one of the most famous companies for enshittification, and the open-source alternatives are generally very good.
Personally, I switched to open-source alternatives way back in the late 1900s, and they've only continued to improve ever since. Adobe has been lagging behind for over a quarter of a century, in the ways which matter to me, and they keep getting farther behind as they turn to worse and worse methods of extorting money from people.
YMMV, of course.
I can get behind almost anything which reduces lock-in for Adobe's remaining customers, but from what I see in other comments, this probably ain't it. It seems very vibey and buggy. But maybe after more work is put in, it could be good. It looks like it wasn't supposed to go public yet, and they're aware that it's not ready yet.
Network effects like presets and plugin ecosystem, tutorials and books, team knowledge (you can ask a colleague how to do things).
Switching costs like lightroom catalogues, learning new programs, if it works why fixit.
And the price is not that high if your company pays for it. Open stuff would have to be much better and Adobe much more buggy before most people consider switching.
i personally like affinity better than the FOSS photoshop alternatives, mostly for UX reasons. what i still haven’t found a good replacement for is Lightroom. i use darktable but the way the interface is laid out is antithetical to getting into an efficient flow state. and i say this despite the fact that i consider the output strictly superior to Lightroom (or in fact anything i’ve ever used).
It’s actually quite simple, give me any open source alternative and I can give you ten major features it lacks that Photoshop has.
If you just use Photoshop as a pixel editing tool, sure, but it does a lot more than that.
I’ve tried getting rid of creative suite for years, but when it comes down to it no competitor has actually come close.
Sure, anyone can list ten features Photoshop has that GIMP, for example, lacks. But it's just as easy to list ten features GIMP has that Photoshop lacks. They're not trying to be the same program.
I see the same argument all the time about Windows vs Linux. Linux lacks this, Linux lacks that, etc... but somehow, people fail to notice that Windows lacks a whole lot of important things that Linux has. Because a Windows user won't be aware of what they're missing. But for me, coming from a Linux background, Windows is missing so much I would view it as unusable.
Changing from one to the other is painful, because of the differences. It's not a drop-in replacement you can keep using exactly the same way. But that doesn't make either one better or worse. They're different, and that's a good thing. But different requires learning, and learning is hard.
Anyway, you're correct that $FreeProgram isn't a drop-in replacement for $ProprietaryProgram. But that's not a valid argument on the relative value of the two programs.
The interesting parts are what is lacking though, not just any feature. A life without smart objects is terrible in photo editing as an example, at least once you’ve seen the upsides.
That and Camera Raw actually being an incredibly capable raw conversion engine.
But I’m not trying to convince anyone here, just saying it makes sense people are paying for Adobe software.
I would like my extensions to support every browser possible, but if a browser only runs on Mac, I won't be able to test my stuff in it. I've had users asking me for Orion support for ages, and I keep telling them I'll add it once I can run it... but now it looks like that's not going to happen.
Dropping the ports doesn't necessarily make the Mac version better. It makes the entire browser unsupportable by developers who want to make their sites/programs/extensions work in Orion but can't run it.
So my support list now is...
- Supported: Firefox, Chrome, Edge, Floorp, Chromium, Brave, Vivaldi, Librewolf, Waterfox, Ungoogled Chromium, Thorium, Mullvad, Tor, DuckDuckGo, Yandex, ...
- Impractical to support: Orion
- Impossible to support: Zen Browser
Dang, looking at this later, I realize I forgot again that HN doesn't support common list formatting. If I put one "- item" per line, it joins them all into a single paragraph. And now it's too late to edit. It should work if I put a blank line between each item though.
This probably won't be the last time I trip over that. I use lists a lot, and almost every other platform allows them to be one per line without anything between.
The full answer for this is a long, wild ride which would fill entire chapters... but the short answer is: Zen's author broke the extension API so badly it's literally impossible to do a lot of what my extension needs to do... and the author is aggressively opposed to fixing it or even admitting that he broke it.
More generally, Zen Browser is the buggiest browser I've ever encountered... by a wide margin. Some of the issues are jaw-dropping. It's notorious for losing user data. And looking at its history, it has mostly just kept getting worse over time. Extensions which used to work don't any more, because he keeps breaking more and more stuff.
I tried to support it. But instead, I got a quick education on why nothing supports Zen Browser. They can't... because of the guy behind it. Sometimes due to his incompetence, sometimes because he actively intervenes when people try to support it.
So... my experience with Zen Browser rapidly went from "hey this seems neat" to "wouldn't touch this with a ten meter pole".
I used to think task bars were pretty neat, back in the 1990s. But once I started keeping more than a dozen windows open, it became a waste of space. And now that I typically have 200+ windows open, the concept of a taskbar is ... like trying to get a fish to ride a bicycle, or like having a rock in my shoe. It gets in my way and provides no benefit to me.
But that's okay. I don't have to use one. Different people have different needs and preferences, and their choice to use a taskbar-free workflow doesn't interfere with their ability to get serious work done.
Same... ish. 2D grid of desktops. Can add/remove them with a hotkey, but I normally have a 3x5 grid. Hyper+Arrows to navigate them. Hyper-s to stick/unstick a window, which also works for moving a window to a different desktop. Hyper-g to group/ungroup windows into a single shared frame with tabs. Hyper+Alt+Arrows to move a window, Hyper+Shift+Arrows to resize, Hyper+PgUp/PgDn to raise/lower, Hyper+Tab to change tabs in the current frame, etc. Lots of other keys, mostly Hyper+something.
Each desktop has a project or something, a related group of windows which I leave open until I'm done with it. Some desktops have remained more or less the same since the 1900s since they've been relevant and useful for that long.
Over time, my desktop hasn't gotten fancier... it has gotten simpler. Bells and whistles are inversely proportional to useful life span. Similarly, over time I've relied less and less on big, full-featured, specialized applications and databases... and more on plain text files, a text editor, short scripts, clean filesystem organization, and a whole lotta terminals.
> Don't make me explicitly keep track of things, just hold onto it all for me!
>
> There's some universe where my desktop is basically a Notion-like thing, and I can just throw things into semi-persistent workspaces (that I close out when I'm done). Desktop Environments that make this work nicely will be quite cool IMO
>
> (A simple and dumb version of this is the BeOS "group various windows together, even though they aren't from the same application" stuff. Very cool stuff IMO
What you're describing sounds like it has been possible for a long time.
I've been doing it on my Linux desktop for decades. I throw things into workspaces which just ... stay open until I'm done with it. The same windows with the same layout and the same history and state, everything right where I left it. They stick around as long as they need to, which can be weeks, months, even years. I even have some desktops which have stuck around since the 1900s, though they do gradually change and evolve over time.
... and any windows from any program can be grouped together. Grouped into a desktop, or even grouped into a single window frame with tabs.
And nearly everything is automatically logged, so I have detailed history going back well into the past.
This stuff isn't in the big mainstream UIs, but it is at least possible with a bit of work to set it all up.
- Basically never logging out. Everything just stays running.
- Lots of desktops, usually one per project or task or ... whatever grouping makes sense.
- No minimizing windows. No taskbar, tray, dock, etc. Things just stay open, and I change desktops when I want to change to a different project or task or whatever.
- Logging at multiple levels. Like, there's a script which checks the complete session state every 15 seconds, and logs it if it has changed. It's exported as a tree or outline of each desktop, each tab group, and each window... with the title and size+position. Archived daily. That way, if the computer crashes or something, I have a recent snapshot I can restore.
- Also, detailed logging of what I'm doing. Like, every 100ms or so, a daemon checks the title of the focused window. If it has changed, it logs the new title and the timestamp, and how many input events happened since the last log entry. If the time of day changes to a new minute, it logs the number of input events since the last log entry. These logs can then be used for all sorts of useful things. Like analyzing my erratic sleep schedule and predicting when I'll be awake so I can schedule appointments. Or automatic time tracking for billing clients.
- I make sure to put useful info into my window titles, in each program. This makes the logs way more useful.
- Also, whatever other logging is relevant... like zsh history, autojump for getting to oft-used directories easily, a todo list / calendar text file with one heading per day and a list of stuff relevant to that day, a new directory each day for miscellaneous files which are worth saving but don't fit elsewhere, a lot of screenshots, an entire web archiving system to save copies of pages I view, etc.
On a side note... a lot of this stuff is explicitly forbidden in Wayland. It doesn't allow these features to exist, because most of this stuff is viewed as a security risk. So if you're using Wayland, entire categories of useful features are off limits. Their reason is basically "what if a hacker collected data about you? what if a hacker wanted to remotely control your computer?" ... but they ignored the case of "what if the user wants to collect data about themself? what if the user wants to remotely control their own computer?".
I was at Canonical during the Ubuntu Phone thing, and it was wild to watch that play out. It started out with a bunch of good ideas... but somehow, every last one of those good ideas got overturned and reversed.
Like, "let's put the buttons at the bottom so the user can reach it with their thumb while holding the phone" got turned into "let's put every important button at the top left where it's literally the hardest place on the whole screen for an average user to reach during typical use".
Or, more importantly, it started out as something like... "Debian/Ubuntu has a rich repository of high-quality full-featured battle-tested popular programs curated by community experts, designed by and for users to empower themselves, so lets give users a way to run all those beloved programs on mobile devices". And then it became "let's get rid of the package repository and forbid users from running anything from it, and build a brand new system which is incompatible with everything, and instead has a commercial app store where corps can sell proprietary software and Canonical gets a big cut of each sale, and the OS has only a small set of proof-of-concept placeholder programs, and is designed to restrict the user so corporate partners can have more profit and control".
And then when it didn't work out, the company kinda doubled down on some of the worst parts of it and went all-in on Snappy.
Instead of bringing phones up to the level of a desktop, as promised... the company tried to bring desktops down to the level of a phone. And that trend has been increasingly popular in the corporate Linux world lately... "Androidifying" desktop Linux.
From an insider's perspective, the Ubuntu Touch thing looked pretty promising... and then management pushed everything sideways. The regular developers kept trying to fix it and make it good, but then upper management would step in and forbid it. The VP of "Future Engineering" in particular. Lots of stuff was forbidden because it "goes against the vision". So things didn't work, and couldn't be fixed.
The worst was one day at a big sprint... the VP of Business gave an all-hands powerpoint presentation right after the workday ended, with a catered dinner afterward. He looked and spoke like a caricature of an Italian mobster, and spent 45 minutes gleefully explaining exactly how we were going to screw the user to make more profit, by taking control away from the user and giving that control to phone corporations. Like, selling corps the ability to place ads directly onto the user's home screen. He was so excited he was practically vibrating.
Afterward, I just went straight to my hotel room and cried.
Eventually, the phone project was cancelled because it had failed pretty spectacularly, for exactly the reasons everyone said it would... and upper management laid off nearly the entire Ubuntu Engineering business unit, about a third or a quarter of the company. The people in charge had decided the problem wasn't a bad design... it was just all those uppity devs who wouldn't follow orders. They kept the managers who were responsible for making it fail, and got rid of all the devs who tried to warn management that the "vision" was broken.
At least sabdfl seemed somewhat aware of the situation... aware of how bad it was. A day or two beforehand, he started the day by giving everyone a pep talk. The talk was pretty somber, talking about how we were supposed to have a mature product to launch by now, but instead we were cancelling the launch and hoping for an optimistic scenario where some tech magazines would at least say it "showed potential". The best case scenario he could muster for the team's motivation was ... we might get a couple reviews stating that it could eventually be good someday, with enough work.
When things get too complex for C, that's where C++ should be used... but I'd generally rather use something else instead. A lot of languages have been created to avoid using C++. Take your pick.
reply