Maybe it's masochism, but I like Arch because it forces me to make mistakes and learn. No default DE, several network management choices, lots of configuration for non-defaults. These are all decisions I have to make, and if I try to cut corners I usually get punished for it.
However, I think the real reason I stick with arch is because this paradigm means that I always feel capable of fixing issues. As people solve the issues they face, forum posts and wiki articles (and sometimes big fixes) get pushed out, and knowledge is shared. That sense of community and building on something I feel like Arch promotes.
My optimistic side is imagining a truck filled with a small town's worth of nutrient-rich groceries, making one trip to replace dozens of individual trip to a less-than-convenient grocery store.
My pessimistic side is imagining a truck with one or two people's worth of shitty "American" groceries, making the same trip they would have made to a grocery store down the street.
I feel like the reality heavily leans to latter, but I only have anecdotal data to back that up.
I feel like it’s almost too generic to be useful. All the “standard” attachments make it a thing that already exists (and those things are usually much stable and supported). If they get enough 3rd party attention prior to launch, that could change.
I wish they would have spent the time and effort just committing to the smartphone idea. Linux and the Linux community could greatly benefit from more open source smartphone devices.
I played the demo for a few hours. Might be a solo dev, but his experience is definitely noticeable. Game looks great, albeit unoptimized. Progression is simple and fair. Artwork is incredible for a solo dev. Combat is decent, and unexpectedly satisfying.
Someone else mentioned the excessive blood explosion - it’s the best feeling when you land one of those shots from across a field.
If you’re going to point fingers, point at the problem, not something you don’t understand.
Wayland has problems; it is not the problem. X needs a replacement and I strongly encourage you to research why if you don’t understand why. Wayland is relatively new, and has large shoes to fill.
It will be many years before it has matured enough to fill your and everyone else’s needs, and by then there will a new replacement for someone else to gripe about on the internet.
As with most professions, nothing can replace experience. Senior engineers, laborers, scientists, doctors, etc. all become seniors through years of learning, and arguably more importantly, failing.
Rookies will try “method A” until it fails, then learn “method B”, then try A and B until a C is needed. Rinse and repeat. Being self-critical and observant will help.
In the short term, “in 6 months”: Practice. Every. Single. Day. If you need to break for day, make sure you come back the next. There are thousands of educational tools out there: Online lectures, free tests, public forums, problem sets (i.e. leetcode) etc. Don’t skip the fundamentals, even if it seems boring. It will mean less memorization, and you’ll understand more complex topics easier.
If you plan and commit to it, you still won’t be a “pro”, but you’ll likely have a chance in an interview, where you might land a job. There, over years, you can hone your skills.
Even if it was relevant, there’s still no story here. NSA employee/contractor brought home classified files to an uncontrolled laptop lol. That’s the security leak, not some random consumer software stealing files. If you work for any security oriented company you should just assume that is going happen.
Maybe it's masochism, but I like Arch because it forces me to make mistakes and learn. No default DE, several network management choices, lots of configuration for non-defaults. These are all decisions I have to make, and if I try to cut corners I usually get punished for it.
However, I think the real reason I stick with arch is because this paradigm means that I always feel capable of fixing issues. As people solve the issues they face, forum posts and wiki articles (and sometimes big fixes) get pushed out, and knowledge is shared. That sense of community and building on something I feel like Arch promotes.