2,141 karma · joined March 18, 2011
I will also challenge you on the idea that silicon valley is still disruptive as opposed to the status quo now. The largest companies in the world (by far) are tech companies now. These large companies are actively stifling competition, and they've been caught stifling wages.
Wealth and income inequality are at terrible levels now and climate change's adverse effects are really only starting to be seen. The Gilets Jaune movement in France is ultimately a proletarian battle against the global oligarchy, of which tech is certainly a part of.
We should not consider ourselves 'disruptors' or outsiders anymore. We are the elite.
quick summary of the acronyms... STUN/TURN/ICE are all related to NAT traversal (ie. when you are behind a router or firewall of some kind and your computer's IP is different from your public IP). The reason you need this is because UDP is not connection-based like TCP. So STUN is a service that helps your computer find its public IP. ICE is a protocol for finding and reporting peer candidates (after they've learned their public IPs via STUN) so they can establish a peer-to-peer connection. TURN is when you reflect the connection off a public server instead of establishing a peer-to-peer connection.
SDP is session description...basically information on what media formats and other things each client will accept.
RTP is how the media (or other data) packets are framed RTCP is out of band reporting for things like packet loss and other info so that each side can adjust media properties
The nice thing about WebRTC is it takes care most of this stuff for you. If you're always connecting to a server with a public IP you'll just need a few things:
1) WebRTC server that can accept media data (like janus or aiortc) 2) Some signalling mechanism, Websockets work well for this 3) you _may_ need a STUN server, google has stun servers available but you could also use coturn for this.
The rest you shouldn't need to worry as much about because webrtc handles it all under the hood
What would be interesting to see are work visas, entrepreneur/freelance visas, working holiday visas, and so on. Obviously a much more complicated ask but that is what I have not yet seen from a site.
Main reason being this: If you want to travel somewhere you can pretty much go on government websites (either yours or theirs) and see what the visa requirements are. If you're looking to relocate to another country but perhaps don't have a good idea where you want to (or can) relocate to or how, it can be a steep hill to climb. Having something with a bit of a hint as to where to start looking would be nice for people I think.
That said, I think the complaint maybe comes down to coding style and architecture of the thing they're coding. They seem to make a joke we'd maybe more closely associate with Java than C++ these days. Also Microsoft's C++ style is awful. So if that's the only experience you have with C++ I would be hard-pressed to blame you for hating it.
The problem of trying to get Canadian tech up to par with the US is much deeper than pulling some tax/incentive levers, I think. There are some really deep cultural issues that I don't think can be solved for a few generations.
1. It’s in its own repo
2. The build instructions are concise and clear. Dependencies are listed. You have to follow a total of 0 links.
3. They use a common build system and not an in-house thing.
I actually really liked the way Apple did it for Objective-C. Don't use exceptions unless something is really going sideways, instead use NSError. I'm not saying this is the correct pattern for C++, but I don't personally think exceptions are the correct pattern either.
Going through all that's required to get a green card and then have the government take that away from me as if it's nothing, and for such a stupid reason? I would cry too.