Notes about initial setup and comparison to macOS about pi-dev-playbook HOT 10 CLOSED

The way the bash profile is set up is a little confusing with the default Terminal app (which is a bit lacking in some areas, but is generally adequate. I had to manually add the following bit to ~/.bashrc because ~/.profile is not loaded by the Terminal, nor could I figure out a way to get it to load (there is no ~/.bash_profile` in my home dir):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/.local/bin" ] ; then
    PATH="$HOME/.local/bin:$PATH"
fi

Without that block, installs inside ~/.local/bin are not found (e.g. Ansible installed via pip3).

from pi-dev-playbook.

While setting up my iCloud email account through Evolution, I had to Set an app-specific password, otherwise Evolution just kept prompting me for my password over and over again.

from pi-dev-playbook.

How the heck do you type an em-dash in Linux??

Hold down one of the Alt keys and type on the numeric keypad: 0150 for an en dash or 0151 for an em dash.

That doesn't work. I'm so used to special characters being something like Shift + option + dash on the Mac, this 'hold a key and type a character code' voodoo doesn't make any sense. No wonder nobody knows the difference between a dash, en dash, or em dash!

from pi-dev-playbook.

In terms of speed, most things are fine so far. Slack in Chromium is tolerable after it loads, but first load/paint takes like 5-10 seconds.

from pi-dev-playbook.

I also futzed around with the system appearance and attempted to automate the selection of a 'darker' theme (though it's not Dark/Night mode) in GTK 3.0 but (a) I can't make it be a true dark/night mode, and that is not something that trickles down, e.g. to Chromium's prefers-dark-mode media query, and (b) I tried many methods of automating the switch, but in the end I still have to run lxappearance to switch themes.

Ugh... and yes, I know "I could just choose one of 20 other GUI interfaces for Linux", but that's not a fun thing to do for someone who just wants to have a not-glaringly-bright interface all the time :P

from pi-dev-playbook.

I was testing out Zoom, Slack, and Google Hangouts in Chromium (since none of the native apps for the first two are available on ARM64, though they do have Linux AMD/X86 builds). Try as I might, I could not get any of the apps to recognize audio either through my attached Logitech C920 webcam, nor through my Behringer U-Phoria UMC202HD audio interface (both plugged in through a powered Amazon Basics USB 3.0 powered hub, which has not exhibited problems with either my MacBook Pro or my Dell XPS 13 in the past).

Bluejeans at least tried to let me select a mic, though it failed after a couple seconds saying I needed to allow it access via the browser (I had, the first time, and I confirmed in Chromium's settings that Bluejeans had access to the camera and microphone, and I even tried setting the default microphone input in Chromium's settings). Zoom wouldn't even let me attempt to enable computer audio. And Bluejeans also bailed on my when I tried doing phone audio.

All three services seemed to be fine with my webcam for video, at least, though Zoom recognized it the first try, then failed from there on out.

In other words... A/V in Linux is still annoyingly difficult years later (I remember having similar flaky issues on a super old Red Hat box back in the day). On my XPS 13 running Fedora, it seems the drivers for at least the built-in devices were good enough to work consistently.

Anyways, I'm going to see if I can do some Audio/Video recording with my mic and webcam, at least.

from pi-dev-playbook.

Video discussion moved to #4

from pi-dev-playbook.

All right. One day in... I can do some of my open source dev work, but not much of my other productivity work, at least not with tools that make it quick and easy.

I think I'm going to have to call it a day on this project. I was planning on going a few days, but there are enough rough edges in my desktop workflow that I could not live with the limitations and constant pressure of having some apps work sometimes and not others.

Now: for a person who really only needs an editor, terminal, browser, and Docker? This is a totally workable workstation. If you don't need to do multimedia work, and if you don't rely on some apps which are strongly tied to macOS or Windows and have a fancy/nice GUI, then you could be very productive with a Raspberry Pi setup that costs around $150 or less.

But you have to be willing to go through a pretty severe learning curve. For kids and beginners, I would recommend a Pi for learning purposes, but not as a standard "pick this up and start being creative / have fun" type of tool. Unless you're like me. I would've been totally into a Pi when I was a kid. But I'm the type of kid who spent New Years Eve getting DOS upgraded on a hacked-together 386 so I could play Doom one year...

from pi-dev-playbook.

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

from pi-dev-playbook.

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

from pi-dev-playbook.