We all know Twitch and Youtube streaming, and some may know Hitbox. But what if you wanted to implement your own streaming server?
So what are the actual benefits to just using the mentioned services?
- Private streams, no one can see them, no one can find them
- Record everything without additional cost
- Define which qualities the stream will be transcoded to
- Embed streams on your own websites
- May run "offline" just in your home for surveilance uses.
But there are disadvantages too:
- Needs to run on a rented or owned box (so does probably cost something)
- Machine with the server needs to be powerful
- Probably does not scale to many viewers
Wow this was harder than i thought.
I just wanted to get a modern VPN on all my devices without the hassle to install third-party VPN clients on all of them (hello OpenVPN o/). The protocol of choice seems to be IKEv2 as all devices that I own seem to support this and it is more secure than the old PPTP or L2TP protocols the devices could support natively.
xhyve is a port of
bhyve a qemu equivalent for FreeBSD to the Mac OS X Hypervisor framework. This means it has zero dependencies that are not already installed on every Mac that runs at least OS X Yosemite (10.10). The cool thing though is that Mac OS X has full control of the system all the time as no third party kernel driver hijacks the CPU when a VM is running, so the full power management that OS X provides is always in charge of everything. No more battery draining VMs \o/.
Just a very quick idea of how you could handle server side crashes of a Swift binary. Swift itself has no Stack unwinding functions that you could use for debugging purposes but
So what if the currently crashing program would attach
lldb to itself and create stack traces before vanishing into nirvana?