103 karma · joined August 23, 2019
Perhaps she or someone on her team (the camera work suggests at least a +1) thinks that this geeky/ditsy persona gets more clicks. Other successful YTers behave similarly. I don't find it useful or entertaining, but others might.
Having said this, I, myself, would've liked the video to be a bit more succinct
Not sure how ~2-8x hardware costs needed to implement this reasonably would compare with costs of specialized hardware.
One thing that I'd think about improving is the boundary search. It seems to me at mere first glance that binary search would usually be much faster. Also, knowing what architecture is used, e.g. channel width, could further optimize the search.
On the other hand, there is plenty of badly written networked software. I bet most of the networked software developers have no idea how to correctly plumb their software. They just open whatever connection, e.g. sockets, their OS provides and just run with it without care of the underlying layers. The OSI model theory in fact encourages this ignorance.
I don't recall whether you could technically open listening ports, at least for a single connection, using slirp, but many, if not all systems, limited opening ports under 1024 to superusers, which (would have?) made running servers on standard ports more difficult.
In any case, I'm glad that you pointed out ACM's apparent revisionist history. They should know better.
It's not a binary choice. I prefer the developers releasing the software under a permissive license. I agree that relying on freemium maintenance is naive. The community source lives on, perhaps the community should fork and run with it for the common good absorbing the real costs of maintenance.
The choice of AGPL tells you that they wanted to be the only commercial source of the software from the beginning.