HN readers are not average people. elsewhere i see people using AI to write without any blowback. maybe they don't want to ruffle feathers, but they are engaging, whereas i prefer to just skip over AI generated posts.
this. My not-at-all technical partner often comments to me that whatever youtuber is reading from an ai script and just turns off whatever we're watching. I assume similar happens in other areas.
For her its rarely the specific tells ("not-x-but-y" etc) but rather its bad metaphors and analogies that get her.
Most people don't care what the other person thinks about their email so long as their boss thinks they are doing their job (and their boss is usually the one paying/telling them to use AI) and the other side responds. Should they? Probably, but everyone should probably do a lot of things we don't.
I feel a tinge when I see an AI written email that is longer than it needs to be/boring to read but I still need to engage whatever it was they were emailing about anyways.
that's what i do, but the posts still get engagement, and it's the same level of engagement as the non-AI posts by the same people, which tells me they are not put off by the AI-writing.
Not my experience at all on non-technical online spaces. For example, people try posting AI garbage on sports message boards and everyone dunks on them for posting slop.
These spaces are filled with people barely technically literate enough to post and AI is still viewed very negatively
i guess that for now only the default will change for new repositories. support for sha1 is not going to be dropped, so most existing repositories won't switch any time soon. if you want to switch then yes, it sounds like a force push might be needed, although it could also be that simply switching is not possible, but that instead you have to create a new repo and import the history from the old repo, forcing everyone to clone the new repo intentionally.
make everyone's voice matter. actually listening to peoples concerns and try to address them. but also, treat everyone as being on the same side. we all want a better life. we should cooperate to achieve that. globally. it takes education. not just STEM, but also moral education. teach people to care about each other and to listen. we need to eliminate prejudice and racism and make it possible to resolve conflicts.
it's a long road to get there. but it's the only way that is going to work.
you are not going to find a city where no such people want to live. or, if you do then forget anyone there wanting to do any minimum wage jobs. because they can't afford to live there. that includes waiters and teachers among many others.
you could of course pay them more, and everything would become more expensive. might work. but i bet you don't want that either.
unlikely. reference please. btrfs was the default filesystem on fedora installs last time i checked. to remove it they would have to first change that, then give it a few years before even considering removing it from the kernel. redhat could remove it because it was never default and never recommended.
This is what I read here and elsewhere bunch of times, which is why I said "supposedly". A quick search did not reveal any meaningful proof, though. I'll ask next time I hear someone say this.
the downside of a stable API is more non-free drivers. the API being unstable is a strength in that it forces driver developers to use a GPL compatible license in order to get their drivers into the kernel, or it motivates the FOSS community to develop alternative drivers that are GPL compatible.
and, i believe i read somewhere that this is not an inability to stabilize the API but a conscious decision to not promise a stable API expressly because it creates the effect i described.
There's also not a lot of money in Canonical for someone (Oracle) to sue for. Red Hat (now IBM/Red Hat) and I guess even SUSE is a different equation. Red Hat just wouldn't touch ZFS because of licensing.
> Why do you care if other distros consider it too risky given different business positions/models?
I don't know. Why do people comment on HN? :shrug:? It's fun and interesting to have a conversion?
I was mainly responding to a GP post that said "zfs is shunned. can't really get around that copyright issue". It didn't have a subject in there. As in "I can't really get around" or "anyone can't get around". And I read it as the second version and pointed that at least one distro did get around it.
it is big enough that it prevents distributions to include zfs. and that in reality is the problem. i would not care much if all distributions decided to ignore the copyright issue like canonical does and i could therefore get reliable support for zfs. but alone the thought of having to boot a rescue system to fix my broken computer and then not having zfs support because no one built a rescue system with it included is making the risk to high.
Distributions aren't locked from distributing ZFS, the only group that actually is suing is few kernel developers w/ their lawyers who have non-standard understanding of copyright (including one that isn't norm for the linux kernel, including for filesystems).
who is at fault doesn't really matter. the end result is that distributions aren't including it, and that kills it. unlike almost anything else which i can add to a system after booting it, filesystems need to be available from the start. until debian, fedora, suse, etc are convinced that there is no threat this just won't happen.
because with that kind of camera you are showing that photography is your hobby/passion and not just trying to shoot pictures of people who don't want to be photographed. (there was a conference recently where you could choose a different color lanyard indicating whether you didn't want to be photographed or whether you didn't mind. i think a very good approach to the issue. don't take photos of anyone with a red lanyard)
reply