This was hard to read through because it felt like the author took a lot of the recent writings about the lack of accessibility in Linux (more accurately, Wayland) as a personal attack. It’s understandable given that they are actively working to improve accessibility, but the way the article was presented didn’t make me feel sympathetic. Instead, it made me more sympathetic to those who have written about these problems and doubly so for those who suffer from disabilities and are dealing with the push to Wayland.
Even before Wayland I get the sense that the screen reader desktop Linux experience was "this is just about usable if you're an expert". You just can't blame people for not wanting to put up with that, or giving up before they get far into it.
Yup, and now it’s regressing so totally understandable that for those who somehow made it work, this is the straw that breaks the camel’s back. Personally, when I developed RSI and other health issues (that made me seriously consider giving up programming or anything computer related as a career), I found that I didn’t want to put up with the state of a11y in Linux and switched to macOS. That was worlds better even though I missed a ton of features from Linux. After a lot of time and money, I’ve made my way back to being able to continue my career, and thankfully don’t need those tools anymore. I still give Linux a try for a few months every year to see if it’s time to switch back. For certain users, I can understand why Linux feels like it’s not there and even regressing.
How well does this (e.g., Tauri) perform on Linux? When I last looked at it, the WebKit implementation is uses performed very poorly to the point where it was a deal breaker. I remember there was some talk of switching the implementation to something else, but I haven't followed it since I abandoned the idea of using Tauri for my toy projects.
Have they managed to fix the bug where applying changes to a file moves the file to the first in your list of open files? And even pinning it if you have other files pinned? Overall, while I've liked using Cursor, it has many bugs like this that I haven't experienced in other VSCode forks and makes me wonder what they consider to be 1.0 quality.
I think Meet replaced Duo which replaced Hangouts; the latter of which was a good competitor to iMessage. I’m not even sure of the history of all their chat apps anymore because they always have multiple alive at the same time competing with each other. All I know is that they have had chat apps that were pretty good but Google could never stick to just one.
I flagged this article and later saw it dead, so I’m quite surprised it came back. I found the content extremely shallow and lacking nuance. Others have mentioned, but it leaves out huge caveats because it would destroy the the conclusion - the cost of moving to the place in the first place, social connections, health (even worse for those with disabilities), emergency services, retirement, etc etc. The list of obvious hurdles that immediately disqualify most people is a glaring omission and I really don’t understand why this article garnered upvotes aside from affirming confirmation bias. This is the first time I’ve been greatly soured by the response from the HN community. What substance are people finding in this article?
Thank you for posting your reasons for flagging it! I'm on the exact opposite side. I thought it was a decent article, flawed but worthy of discussion. I was surprised to see it flagged dead, so I vouched for it. When this didn't bring it back alive, I emailed Dan to see if he could resuscitate it. He said that it was already alive due to enough other people having vouched for it.
Your criticisms are all reasonable, but they are exactly the sort of things I'd hope to see discussed in the comments. And they are! I think the article is a good starting point for a discussion on what's possible. I'm nowhere near as extreme as the author of the piece, but I live a life much closer to what he describes than most people here.
Rather than being soured by the response, I'm glad to see both the pros and the cons being discussed. Yes, there are lots of ethical issues about living the way he suggests. There are lots of things you'll be doing without. But there are also lots of upsides about living in a way that you have time to do things besides just work and sleep. Which parts of the response did you find souring?
> the cost of moving to the place in the first place, social connections, health (even worse for those with disabilities), emergency services, retirement, etc etc
Anyone moving to bay area for a higher income job would have most of these issues.
A forum full of people willing to migrate for better income and lifestyle should not be criticizing "cost of moving", "social connections", "health disabilities" and "retirement".
I might be misreading your reply, but what you’re keying in on and singling out is a tiny fraction of the audience the article is arguing for. My problem is with how shallow this article is and how it throws a wide net that doesn’t cover a ton of situations that prevent people from doing what he claims is possible for just about anyone if they change their mindset. If the argument were just for the subset of users you’re using as an example, then sure? But that’s isn’t as clickbaity and certainly doesn’t support the claim that any young person can just up and do what the writer claims.
I’ve been running this alongside Audiobookshelf for podcasts to compare the two. AFAIK, Pinepods doesn’t have a native iOS app. Has that changed recently?
Tried to look at their website and docs on my phone and the stuttering is painfully noticeable. I’ll read a bit more but that doesn’t inspire confidence.
This sums up my experience with everything Firefox. It's why it slowly fell behind in UX and stopped being my primary browser ages ago. I keep giving it a try every year, but the gap between FF and other browsers just keeps getting wider and wider. This is a nice small step, but FF has a long way to go to catchup.
1. Organizing threads of research into context groups. Usually doing heavy deep dives where it’s uncertain if I need to revisit a previous branch, so rather than closing, it’s much more beneficial to group and collapse. It’s also easier to reopen and glance at the topics you looked at.
2. Similarly, grouping tabs by purpose while developing. It lets me organize tabs in a way that makes it so they I don’t need multiple browser windows open. It makes for a much more zen-like development environment.
3. Testing across dev, staging, and prod. Want the same tabs open but grouped so that I don’t accidentally do something destructive on prod that I meant to do locally. Now that this is in Firefox, I can also combine it with multi-account containers for more workflows.
This sounds correct? I think I’m living evidence of it. The sad reality is that sometimes you can’t hold out long enough and you just gotta take what puts a roof over your head and food on the table. Everyone graduating now just got unlucky with when they were born.
Edit: that said, I think the majority of what the parent wrote is good. Esp the part about negativity. That hits hard and is good to be aware of.
reply