As for usability: It's really "raw". So you have to manually create the content/code directory and start the tool pointing it to that directly. There's no UI, remote management or any other advanced features that you might expect. That's also the reason info-beamer hosted go started in the first place: The technical knowledge required to run the software was to much. The hosted solution fixes all this and adds a complete OS, trivial installation and remote management system around info-beamer pi.
The main challenge was to understand how to use the HEVC decoder. There's no documentation at the moment, so the only source of information is this patched FFmpeg release: https://github.com/popcornmix/FFmpeg/commits/2711
Basically the decoder interacts with /dev/argon-hevcmem to control the HEVC hardware decoder. You let it decode into video core controlled memory and can then use the MMAL toolkit (http://www.jvcref.com/files/PI/documentation/html/) to feed buffers through a scheduler and finally into the dispmanx layers handled by the hardware video scaler. That way the frames end up more or less directly on the screen. Except for the decoding part, the same pipeline of scheduler and presentation can also be used with the older H264 based encoder that's directly addressable using MMAL.
On the other hand, the initial Pi firmware for earlier models came with a bunch of bundled examples in the hello_pi directory that were incredibly useful in understanding how everything worked. (see https://github.com/raspberrypi/firmware/tree/master/opt/vc/s...). Right now the forum and maybe the firmware issue tracker is the only source of information. In general, the direction of using more standardized APIs like DRM, Mesa 3D for GL and so on seems like a good idea regardless. I guess we'll just have to give all that more time.
The HEVC decoder is using a patched FFmpeg with direct communication with the hardware API. In the future there will be an V4L2 API and corresponding method in FFmpeg (see https://www.raspberrypi.org/forums/viewtopic.php?t=247897). But that's not completed yet and there's no release date announced. I would guess once that's out, the whole decoding process will be a bit cleaner than it is today. But so far I works pretty well. I ran into a ton of firmware lockups during development, but most of those are fixed now. One thing I didn't manage to do yet is to decode two videos at the same time. That's something the H264 decoder could do. See also https://www.raspberrypi.org/forums/viewtopic.php?f=70&t=2520...
These are real German words. The reason they sound like English is because they were imported and adapted like any other neologism. Denglish (or Frenglish, Ponglish, Spanglish, etc.) refers either to words that don't exist in any of the 2 languages but borrow heavily from real words (a lot of corporate lingo in most languages has these fake words adapted from English), or to using literal translations of expressions or “false friends” between that language and English even if the meaning inadvertently changes.
And "beamer" is actually used by a lot of non-native English speakers to refer to a video projector when speaking English.
For example words like "substance", "amusing", "mobile", or "confusing" are of French origin but since they are in the dictionary they're not considered Frenglish (Engch?).
It's certainly regional and probably differs down to friendship groups.