In my experience, everything from Jupiter Broadcasting [0] is extrememly top-notch and informative. I'd highly recommend all of their shows (including BSD Now!)
Yeah, I've been Jupiter listerner for some time now mainly "Linux Action Show" http://www.jupiterbroadcasting.com/show/linuxactionshow/ they have a lot of useful info. Highly recommended podcast, and if you can support them with anything you can. I'm also thinking on building my own next DIY router. I'm tired of how limited the routers you buy off the shelf are. Currently running Asus RT-N56U with Padavan F/W https://code.google.com/p/rt-n56u/ I've also always wanted to switch to BSD distro but ports are not updated as often as "Arch Linux". If there where BSD rolling distro similar to well updated Arch Linux packages, I would consider switching.
Which ports system? I can't say anything about OpenBSD ports, but aside from some stuff that gets very little love from people, most of the FreeBSD ports tree is kept bang up to date, and binary packages appear shortly thereafter. pkgsrc, OTOH, is only released quarterly, though if you want, you can sync with their CVS repo, though, y'know, CVS.
The BSDs aren't distros, though some do have what might be called distros, such as PC BSD, pfSense, &c. being distros of FreeBSD, EdgeBSD being a distro of NetBSD.
The ports system is a rolling release system for non-base software though, though the base OS isn't. The closest BSD to come to having a rolling release schedule for the base OS is OpenBSD, with its six-month release cycle. The thing is that the BSDs can't have a rolling release schedule as is found in some Linux distros because the base OS is managed separately from the ports/packages: the core OS components aren't packaged, so there's no sense in which they can 'roll'.
Personally, I'd never use an OS with a rolling release cycle on a server. Too much can go wrong.
GNOME has had systemd as a hard dependency since 2012: it uses systemd-logind and a few other systemd services for its basic functionality. systemd is only available on Linux systems, therefore it's a pretty great achievement to get it running on OpenBSD.
That sounds a bit misleading. I remember running Gnome 3.2/3.4 in 2012, while still using SysV init. I'm not sure whether logind or ConsoleKit was used, but the init system (what most people associate with the name "systemd") was definitely not the one from systemd.
The unpatched GNOME post 3.12 or so does have a hard dependency, which is why platforms like OpenBSD or Slackware have to patch. If it requires a patch to work around, it's a hard dependency.
There's an organization in Minneapolis which does a similar thing. It's called Free Geek Twin Cities, and they recycle old PCs and put Ubuntu on them. It's about $40 for a computer, or one can earn one by volunteering for 24 hours. I used to volunteer there when I was less busy.
When I first moved to Portland I volunteered at Free Geek. But it was mostly because I didn't know anyone and it seemed like a good way to make like-minded people.
I've used keepass ona a daily basis. Auto type failed with my usage patterns - essentially I have multiple entry points per site (enterprise app) and each has a different titlebar text.
I've switched from OS X a few months ago and I'm actually happier with KeePassX than with 1Password. I hated AgileBits for the 4.0 bloat redesign which made everything slower (this is a constant on OS X it seems). I have a pretty simple use case with KeePassX (no sync) and here are the solutions I've found to problems mentioned in this thread. Hope they're helpful!
Hide KeePassX's window:
Just open the settings, click the first two checkboxes ("system tray icon", "minimize to tray instead of taskbar") and add `keepassx -min` to your login script. It'll ask for your password and disappear.
Title bar:
KeePassX does use the browser title bar and it's sometimes not reliable. It's easily fixable, though. Install a Greasemonkey plugin to your browser and add scripts such as this one:
I like how I could type "gmail" in Alfred and have 1Password do everything for me. I was able to reproduce that with a bash script that I call from my own launcher and it works just as well, if not faster.
SDL supports OpenGL. So you can have SDL handle all the boring stuff with window handles, keyboard and mouse movement, system events etc, and you are given an empty OpenGL context so you can draw literally anything you want in it. It doesn't get much simpler than that.
"a decent, simple 3D C++ rendering library " - 3D rendering doesn't really get any more simple than a blank OpenGL context window. If you want "simple" as in "easy to use" then Unity/Unreal Engine are both very easy to use.
Those are massive engines, with plenty of features I don't need. I can't rely on those engines because they're just made to make full fledged games, and often they force many paradigm or methods of working I don't really like. Not to mention the freedom thing, and how those engines are supported.
> 3D rendering doesn't really get any more simple than a blank OpenGL context window.
OpenGL is pretty low level. It's a bare standard bridge to make use of a GPU. What I mean is that there are either very high level engines, or a very low level graphics API, which requires a lot of work if you want to make anything decent with it. There are things like glfw glew, but nothing like a very simple to use 3D rendering library, that just does the bare minimum, like a camera, quaternions, some text rendering, inputs, offers some simpler access to what opengl has to offer, etc.
3D engines are always being made obsolete. Except irrlicht and ogre3d, which are still fat enough in my opinion, there are no general-purpose, light 3D renderer, that are not necessarily trying to do it all. This kind of engine might serve as a thin wrapper to opengl to just avoid the work with the high quantity of opengl calls.
I've used libgdx[1] before, it's still fully supported and is being developed further. It is still fairly low level,but it has just enough things in it to make things like draw calls, vbos and shader management easier. That being said, I still ended up writing my own shaders for lighting and shadows, as far as I know there isn't anything in between libraries like this and huge engines like Unity/UE.
https://minnesota.repair.org/
I really like this idea and would like to see it come to fruition. It's a nice check on consumerism and planned obsolescence.