Raised Catholic. Don’t believe in hell. Lost my mom recently so i hope there’s a heaven. If there is i assume it would be accepting of all. I try not to do things that hurt people because i don’t like to see people hurt.
Apart from RHEL, RedHat contributes to hundreds of FOSS projects and hires a lot of FOSS devs. So their contribution in progressing the desktop linux is huge. You can see the contributions to the various project here: www.redhat.com/en/about/…/contributions
Believe it or not corporates play a big role in making Linux what it is and their enshittification is bad for Linux ecosystem.
RedHat contributes to hundreds of FOSS projects and hires a lot of FOSS devs.
They don’t do this because they like the idea of free software (as recently proven - again) but because of thy need the software and doing it like this is the easiest way.
corporates play a big role in making Linux what it is
Same with Microsoft, for example. I’m still not going to use any of their software just because they support FOSS they need because it’s easier this way.
Of course they need the software and that’s why they contribute to make it better. That’s how most of the FOSS development works anyway. People have an ‘itch’ to fix the issues or add a feature and they do it and the license makes sure that others benefit from that itch.
Just a warning about community grabbing because there was a post somewhere which I can’t recall about them grabbing up communities that existed on reddit for the sole purpose of power tripping
I and others don’t want to have the same power mod issue where mods control a bunch of subreddits
As in the post we mention corruption of bad mods/power mods. Members of the C3 community do not share mods always either.
Those who do not maintain these rules within their community will be removed from the collaboration.
Fortunately with Lemmy, seeing bad mod behaviour is easy as the modlog is very transparent. You can see when action has been taken against a post within this collective. Then also notice when it doesn’t fall under our guidelines.
We are only removing posts which break the rules as seen in the sidebar
None of the other answers I’m seeing are the actual reasons you shouldn’t trust more specifically. The reason you shouldn’t trust them is because a few years ago they had a data breach. It was relatively small and wouldn’t have effected many if any people but the problem was they didn’t disclose it and tried to bury it. It wasn’t found out about until a few years later. That should tell you if they had a major data breach that did affect you they would try to hide that from you and you would never know unless a you were made aware through other means.
Its one of the best farming games I’ve ever played, but it’s also like… a real ass simulation game. You don’t get to grow whatever you want, you will grow rice and you’ll either like it or leave. Kept your paddy’s water level too high? Mold. Didn’t get rid of pests? Disease. Didn’t keep enough water in on a hot day? Uh oh, water evaporated and now your rice is under watered. If the waters too cold it won’t absorb nutrients right.
It’s also 50 percent a action rpg platformer, but don’t think you can get around doing the bare minimum in the farming just to play it: your stats are directly reliant on how good you rice farm. No level grinding through combat.
I really enjoyed it but I’m still not sure who the target demographic for this game was. How big is the overlap between “traditional rice farmers” and “action rpg enjoyers”? At any rate, I high key reccomend it if you think you could be interested in rice farming whatsoever, because the story is great too.
With my track record at killing even cacti, I am going to suck at this game. It does sound interesting, though (and “great story” is enough to make me face the rice farming).
It definitely sounds unique, which is exactly was I was hoping for when I made the post! Thank you!
TLDR: He doesn't forgive anyone who sins, he forgives those who repent. Repent not meaning "feeling sorry" as many seem to explain, but actually meaning "to turn away" which means changing fundamentally as a human being. From a bad person to a good person.
Someone who doesn't change and act good most of the time isn't repentant, so isn't forgiven. So basically, you prove it with your actions and how you live your life, not with just words only. By this measurement, Republican "Christians" aren't repentant and so aren't forgiven.
Not a Christian anymore, but I used to be for a very long time. Sidebar: "You will know a tree by it's fruit" AKA you'll know what kind of person someone is by what they do. Anyone who's even skimmed the bible (especially the new testament) would easily understand that most conservative "christians" aren't Christian at all, but rather like the Pharisees (phony religious types) that Jesus constantly argued with and condemned.
Other note: Sikhs actually live the way Christian claim to. I could easily make a "hard to swallow pill" meme which said: "Sikhs are better Christians than actual Christians are."
Nah, it’s fine. Boot times are considerably faster than sys.v in most cases, and it has a huge amount of functionality. Most people I work with have adopted it and much prefer it to the old init.d and sys.v systems.
People’s problem with systemd (and there are fewer people strongly against it than before) seem to break down into two groups:
They were happy with sys.v and didn’t like change. Some were unhappy with how distros adopted it. (The debian wars in particular were really quite vicious)
It does too much. systemd is modular, but even so does break one of the core linux tenets - “do one thing well”. Despite the modularity, it’s easy to see it as monolithic.
But regardless of feelings, systemd has achieved what it set out to do and is the defacto choice for the vast majority of distros, and they adopted it because it’s better. Nobody really cares if a user tries to make a point by not using it any more, they’re just isolating themselves. The battle was fought and systemd won it.
How so? I like the systemctl syntax more, since it allows for starting/stopping many units at once. It also supports a much richer set of commands than service ever did.
it just feels like a manager decided the command should read like english, made the decision then went back to never entering a command again in the terminal again. every day, i get to decide, should i enter “systemctl restart problem_service” all again or hit up on the keyboard and and hold back, then rewrite over the previous status command. bit less work if the status/stop/start/restart bit was on the end like it used to be.
In BASH ALT+T will swap the last white spaced separated strings… It’s still annoying but makes “systemctl problem_server start/status/restart” a bit easier. CTRL+W will clear the current string to whitespace, so up arrow, ALT+T, CTRL+W, status, ALT+T, Enter.
One of my biggest problems with critics of systemd is that a lot of the same people who make that second point also argue against wayland adoption when xorg does the exact same thing as systemd. It makes me feel like they’re just grumpy stubborn old Linux nerds from the 90s who just hate anything that’s not what they learned Linux with.
Which is sad, because honestly I think it’s kind of not great that an unnecessarily massive project has gained such an overwhelming share of users when the vast majority of those users don’t need or use most of what it does. Yeah, the init systems from before systemd sucked, but modern alternatives like runit or openrc work really well. Unfortunately they get poorly supported because everyone just assumes you have systemd. I don’t like the lack of diversity. I think it’s a problem that any init system “won”.
Unfortunately they get poorly supported because everyone just assumes you have systemd.
No, they get poorly supported because they were a pain to support even before systemd ever showed up. I for one was extremely tired of writing the same shit over and over again in every init script and then going through the tedious process of porting the script to every platform for minor idiosyncrasies of the various distros (start-stop-daemon available or not was one I remember, the general bash/GNU vs. BSD stuff you get with any script was another) from 10 year old RHEL to modern ones.
Xorg, or X11, “used to” do the “minimum necessary” for a remote display system… in the 80s. Graphics tech has changed A LOT in the last 40 years, with most of the stuff getting offloaded to GPUs, so the whole X11 protocol became more and more bloated as it kept getting new and optional features without dropping backwards compatibility.
The point against Wayland, was dropping support for remote displays, while kind of having an existential crysis for several years during which it didn’t know what it wanted to become. Hopefully that’s clear now.
OpenRC and runit are indeed working alternatives, but OpenRC is kind of a hack over init.rd, while runit relies a bit too much on storing all its status in the filesystem. Systemd has a cleaner approach and a more flexible service configuration.
Arguably, Systemd does exactly that: orchestrate the parallel starting of services, and do it well.
The problem with init.d and sys.v is they were not designed for multi-core systems where multiple services can start at once, and had no concept of which service depended on which, other than a lineal “this before that”. Over the years, they got extended with very dirty hacks and tons of support functions that were not consistent between distributions, and still barely functional.
Systemd cleaned all of that up, added parallel starting taking into account service dependencies, which meant adding an enhanced journaling system to pull status responses from multiple services at once, same for pulling device updates, and security and isolation configs.
It’s really the minimum that can be done (well) for a parallel start system.
systemd is modular, but even so does break one of the core linux tenets - “do one thing well”.
Linux itself (i.e. the kernel) breaks the hell out of that so-called core tenet. Have you looked at make menuconfig at any point? There’s everything but the kitchen sink in there.
I started https://programming.dev because I am a moderator of several 100k+ subs over on Reddit and I didn’t want my communities to not have a place to go if Reddit crashed and burned (even though it’s incredibly unlikely). The main sub I moderated (/r/ExperiencedDevs) for years wanted user verification to combat the spam that was newbies commenting and posting about things they didn’t really know or understand. This will be possible to actually implement on Lemmy, whereas reddit was closed source, and didn’t really care about their communities.
I am also a strong supporter of pulling control away from megacorps. We need more small to medium sized businesses on the planet.
For selfish reasons? I wanted to work on something new and have true ownership over it, the ability to build a community that worked together to build something without capitalism standing in the way. It might seem strange, but one of the first things I did was bring multiple other people on board to help me maintain the server, even going so far as to add domain managers to the domain name. This was all to counter the major questions people were asking around “what if the host decides they don’t want to host anymore?”. Well hopefully the programming.dev community is willing to take that burden if the time ever comes, even though I hope it doesn’t. I also wanted to start something similar to a coop, where ownership is shared, meaning users have incentives to make the platform better. I have lots of ideas around this, but this will never be possible on Reddit. It is quite feasible here.
I also had the chance to buy an incredibly dope domain name! programming.dev! Why wouldn’t I jump at that chance? And I get to even use it instead of let it flounder. So many reasons to host something like this, to build a trusting community, a safe space to have to let people talk about a shared love/topic/hobby.
It’s a massive question, and I think quite a lot of the argument comes from the fact that it depends what direction you’re answering it from.
As a user, do I like being able to just systemctl enable --now whatever.service , and have a nice overview of ‘how’s my computer’ in systemctl status ? Yes, that’s a big step up from symlinking run levels and other nonsense, much easier.
As an administrator, do I like having services, mounts and timers all managed in one way? Yes, that is very nice - can do more with less, and have to spend less time hunting for where things are configured. Do I think that the configuration files for these are a fucking mess of ‘just keep adding new features in’ and the override system is lunacy? Also yes.
As a developer trying to do post-mortem debugging, who just wants all the logs in front of him for some server that’s gone wrong somehow, which I often have to request via an insane daisy-chain of emails and ‘Salesforce nonsense that our tech support use’ from our often fairly non-technical end users, on some server that I’ve no other access to? No, I do not find having logs spread between /var/log and journalctl (and various CloudFormation logs in a web console) makes my life easier. I would be pleased if that got sorted out.
I'm pretty sure Lemmy has been designed specifically so it can't me monetized. If you try to place ads people can just switch to another instance. If you try to split off from the fediverse I'm pretty sure there's enough data on other instances in order to clone your server along with its content (and mind that you don't own the copyright for posts made by users).
I think it's more than just "not for profit" - there was actual effort to make this platform as difficult to monetize as possible (probably as a lesson learned from Reddit lol). Let's begin with the code - it's under AGPL, which means you can't set up a public Lemmy instance without making its code public. This prevents you from creating an improved version and keeping it to yourself to gain an advantage over other instances. Second, the fediverse means that it's less likely for a single instance to become so big that it can unfederate itself without consequences, and while you're federated you can't really place ads - people would just view your community on another instance.
A greater percentage of reddit is younger than some of them realise. So many redditors are going to be used to new reddit, and plug-and-play services in general. Kbin and Lemmy look like old.reddit, and they require them to understand the concept of what a 'server' is to even get started. This is knowledge they've never needed before to use the services they want to use.
Imagine spending all your life eating McDonald's and then somebody told you homemade burgers are way better quality, taste better, cheaper, etc; then when you ask how to get a taste of those bad boys they start with informing you that you'd need to grill them. It's not hard, it's just new.
they require them to understand the concept of what a 'server' is to even get started.
I've known 5 year olds start minecraft servers. And understand that each "world" is an "instance". But that's aside the point, as you're right that even Help-Desk IT people struggle to understand the difference between computer and server.
It's not hard, it's just new.
The "new" part is what gets people. All of this is new. Even the implementation of all of this "fediverse" is new. It will come with time! People probably didn't understand email vs snailmail, and probably had an even harder time with SMS/IM vs email when all of that came about just over 20-30 years ago. Most of these "complications" are from people that grew up knowing that the "internet" is basically 5 or 6 social media sites for very specific uses, and those 5 or 6 sites are older than most of the people using them, so that's all they know. Even for a dude in IT, the fediverse was a new concept to understand, and even difficult to understand how it could best be implemented for the masses.
kbin.life
Oldest