Anti-Ultimate Wrote:You should just use any decent distro. I haven't needed to edit config files since I installed Antergos last year.
Complaining mode = true:
Ahahahahaha. I wish that were true. Take last week for example. I literally spent two hours trying to get teamviewer running on my raspberry pi running raspbian os (debian based) before finally giving up and using rdp. Installing and configuring software on linux is just painful compared to windows. Oh and you can't get it to start with the OS without WRITING A 50+ LINE SCRIPT. Good lord most server apps are useless without that basic functionality.
I also had to change a bunch of graphic config options to get it to scale correctly and output RGB instead of YPbPr so that it would display correctly on my hdtv. There were a bunch of other config issues that I don't even remember.
Anti-Ultimate Wrote:Try RetroPie, specifically their x86 flavor
Does it come as an OS? I only see a raspberry pi OS and a frontend application.
(04-12-2017, 04:40 AM)NaturalViolence Wrote: [ -> ]Installing and configuring software on linux is just painful compared to windows. Â
No, it is literally the same. The only difference is the format your applications come with.
If you have a .deb, that's quite the same as an MSI installer for Windows. Application gets installed to X directory, end of story (it can even contain scripts so you don't have to write that 50 line script, I don't know why Raspbian wouldn't use systemd, which has literally 3 lines to start a application on boot)).Â
If all the developers give you is a script and a folder, the experience will be the same on Windows and Linux.
This is why distributions like Arch and Manjaro, which allow users to create to create packages manually with a simple script and one (!!!) command will always be more user friendly than Ubuntu, which depends mostly on sudo make install and adding ppa's you will not get rid of cleanly until you reinstall the fucking OS.
In 2017, I cannot recommend debian based anymore.
(04-12-2017, 04:40 AM)NaturalViolence Wrote: [ -> ]Oh and you can't get it to start with the OS without WRITING A 50+ LINE SCRIPT.
Using the Arch aur package, this is simply (and yes, you have to use the terminal for this):
Code:
sudo systemctl enable teamviewerd.service
Any distribution that does not use systemd or a similiar system should be thrown out of this solar system.
Gonna have to agree with @Anti-Ultimate, especially since Arch makes life so much easier with how its package manager works. Of course, Arch takes some time to set it up how you would like since it is very bare bones once freshly installed, but well worth it once you have all fo the stuff you want. Installing packages is simple to the point where it typically isn't that hard to get your graphical environment and other things running within a few minutes after downloading all of it (unless you have driver problems, which I've run into far less than anything based on Ubuntu, especially since Arch plays nice in my experience with Nvidia's proprietary drivers, while anything on the Debian/Ubuntu spectrum of distros has always had problems whenever I tried using them). Manjaro pretty sure makes it a lot more simple. I didn't end up using it on my new laptop due to it not supporting my Kaby Lake CPU a few months ago since it was using the LTS Linux Kernal at the time, while Arch is bleeding edge so it ran without a hiccup, even when dealing with the whole dual GPU situation in my laptop.
Of course, these are just my experiences, so it isn't completely definitive of what may happen for you. Hopefully, you find a distro you like @NaturalViolence.
You can simply use Antergos, which is like Arch. The only difference is an actual installer, an additional repository with some packages from Antergos, and a different distro name.
Anti-Ultimate Wrote:No, it is literally the same. The only difference is the format your applications come with.
More b**ching by me:
Typical experience installing app from .deb for a newbie like me:
>double click .deb file
>opens a "open with" page instead of installing it
>google around
>find I have to manually do open with the package installer app since apparently .deb isn't associated with it by default for some reason
>look through list, no package installer app
>closest thing is synaptic package manager so I try that
>opens app but nothing happens
>use import package from package manager
>it gives me a browse window but doesn't let me navigate outside whatever the default directory is which is doesn't show, even if I open it as root
>give up
>more googling
>find multi-line commands to run .deb file from terminal
>throws missing dependency errors
>more googling
>more commands to install dependencies, some of them give me errors
>more googling
>more commands to fix those errors
>finally install app
>open app, half the functions don't work because they need to be configured but can't be configured from the gui
>spend more hours on google finding config files and edited them
>app finally works
>repeat process several more times until some of the apps I need just refuse to install correctly no matter what I do, despite forum-goers saying they work fine and insisting that the things I'm watching happen in front of my are impossible
>give up, uninstall linux
>several years pass, need linux again for a pet project
>install linux, repeat from step 1 and immediately remember again why I stopped using linux
I have tried nearly every linux distro that you can think of, the experience is pretty much the same on all of them just with different file extensions. Â Other distros might actually open it in an app installer but then throw a vague error. Â Which is technically an improvement.
Typical experience installing app from .exe for a newbie like me:
>double click .exe
>it installs
>everything works perfectly out of the box
I really want to like Linux but it doesn't seem to want to like me.
Shonumi Wrote:@NaturalViolence - I remember seeing a lot of good stuff about Lakka. I haven't tried it, but it looks pretty good.
According to google a lot of people are frustrated with how much configuring it requires to actually do anything. So I will probably have that one pretty low on the list of distros to try.
(04-13-2017, 04:30 AM)NaturalViolence Wrote: [ -> ]According to google a lot of people are frustrated with how much configuring it requires to actually do anything. Â So I will probably have that one pretty low on the list of distros to try.
Huh, sounds like a classic RetroArch complaint. I'd have thought Lakka might have smoothed over things. Guess not.
(04-13-2017, 04:30 AM)NaturalViolence Wrote: [ -> ]Typical experience installing app from .exe for a newbie like me:
>double click .exe
>it installs
>everything works perfectly out of the box
Major linux software distribution rant below
Spoiler:
That would be doable very easily. But it's not happening because people are too stupid to bundle dependencies and a simple glibc check into a installer.
I had something planned that would solve this (aka a Installer which install AppImages ), but I figured Flatpak would be good enough to solve it.Â
However, those projects have gone into the completely wrong direction. I don't care about anything these tools have to offer. I don't want to build every little dependency for my application from source. Why can't I use the distros defaults? Why is the NVIDIA driver not supported while it works completely fine on AppImages? Why sandboxing? What if my application needs udev access? I tried building dolphin in Flatpak, but most of the features were entirely broken and the theme wasn't even working "because the themes aren't guaranteed to work with each GTK version (stable GTK ABI since 3.20, do they even know about their own product? Seriously).Â
On an AppImage, all it does is take the libraries from your build system, bundle them and it works literally anywhere where the glibc is same or newer. There is even a daemon which checks for AppImages and adds desktop entries to your DE.
The Linux market share is too low, so the user base and developers have no idea what people want since there is no clear majority. Everyone does their own thing, which sometimes works, but in most of the times you end up with shit in a cup. And then there's a fork of that shit in a cup which aims to change it to be more useful, and suceeds in doing so, but then they remove all useful features from the original so it's completely different.
Seriously, this centralized software crap is completely hated on Windows. Why do they think it would work on Linux?Â
Imagine you are a software developer. You test your software on several distros, it works. Now, you release an update, which also works on all distros. On Windows, you ask the user if he wants to update. On Linux?
A MONTH LATER, IT STILL ISN'T IN THE DISTRO. WHY? ONLY GOD KNOWS. You get bug reports of people using a fucking old version, because that's the only one available in their distros PPA. Every single one of them gets a response, telling the user to get a newer version, only for them to respond "It is the newest version".
What would you do with an AppImage? Download and execute. If it doesn't work, contact the software developer, who also distributed the software. WHY CAN'T IT BE THIS EASY EVERYWHERE.
(04-13-2017, 03:15 PM)Shonumi Wrote: [ -> ]Huh, sounds like a classic RetroArch complaint. I'd have thought Lakka might have smoothed over things. Guess not.
Tested it some time ago. Obviously this is literally RetroArch but with even more pain. You have to put your roms inside the shared folders though your local network, Lakka had no WiFi support back then, idk if they implemented it now.
Looks like they added WiFi support some time last fall. But you should really just be able to stick any kind of storage into the computer and have Lakka scan from wherever you tell it to (you know, like Dolphin does). If it doesn't do that, yeah, that's dumb.