I wrote and maintained an IP/UDP stack for an expensive, reliable, industrial packet radio, so you should back off your presumptive, elitist tone.
Sure, they maintain a control TCP channel like ftp but that's a normal pattern. Falling back to other protocols is a necessity because some environments literally lock down everything apart from ARP, DHCP, DNS, HTTP/S and email.
Writing an application-level protocol to make UDP act like TCP or SCTP is a sign of failure to fix issues lower down.
Worse, UDP often gets dropped first when a network is saturated, and it's harder troubleshoot to because it's not connection-oriented stateful and doesn't work with existing tools... debugging now requires nonstandard knowledge inside an app. (Turning a browser into an OS is a metastasizing cancer.)
There are better ways to solve efficient, low-latency content distribution and bidirectional state RPC without reinventing everything every other year.
Exactly. Seems like a specious strawman when the attack on personal use and viewing experience is much broader. Corporate control seeks to pervade every aspect of life and shake down people at every opportunity.
Greedy corporations leaning on governments to drive people away from their content, criminalizing remixing and making content unusable by the blind and others speaking different languages not approved. Plus, they probably want to charge a fee for alternate language or requiring purchasing the content again in that language. F that!
We used Lustre, pNFS and GPFS at Stanford on HPC gear (DDN, Panasas and some enterprise COTS). Luster has a lot of moving parts and config. Most folks tend to use Puppet/Chef and/or Rocks distro to deploy clusters in a somewhat sane manner. (Sometimes AFS too but not much.)
These days, Ceph/Gluster might work, but Lustre's proven.
Mudge at DefCon IIRC had a good point about MIC contractors having Intellectual Property repeatedly stolen, govt gives more money each time and disincentives to root-cause analysis and patching vulns/0days.
They're crooks whom subvert democracy and exploit people and businesses with obsfucated trickery. Who cares? Next financial crisis brought closer because coworker competition in performance reviews means legitimized stealing even more money, faster.
The fundamental failure of most SJW and some populist attitudes: committing varying levels of disproportionately evil behaviors in the name of self-righteousness, when a decent person aims to be relatively consistent no matter what other people do.
Chris Hedges was shoutted down for opposing the Iraq war, and Phil Donahue push out of mainstream media.
Perhaps it would be like Ubuntu going back RHEL/CentOS vs. Fedora churn, or turning something like iOS into something like Android.
Sometimes, projects need to leave things that are working alone instead of churn-for-churns' sake.
This move needs more substantive explanation than "we're renaming and duplicating projects, creating the Paradox of Choice." It's already open source.
Plus, being too open, other companies can just come in like with W3 and drive features and complexity that aren't always positive.
Next, one Tragedy of the Commons problem with Android is companies aren't motivated to invest significantly into making the overall platform better because it helps the competition. Sure some
do, but they usually make their fork of it slick and shiny on the outside but the upstream/inside doesn't always get the same love.
Finally, a poor execution of an open platform makes the whole platform look bad to customers.
It's not the end of the world if docker pivots oddly but I hope it goes well.
UDP shouldn't be used for content traffic, it has no guarantees. Plus, this is what happens when reinventing emperors new clothes protocols... greater attack surface for marginal benefit.
Yup. More mental "shortcuts" that seek magic "signals" to avoid both evidence and pragmatic interviewing effort testing both business problem-solving critical thinking and cultural fit. There are no shortcuts. Furthermore, "competitive" programming has little to do with the real world, and it's more about showing off and ego inflation.
REI usually has fantastic gear good enough to not have to seek out specialty stores. Just one example: I got a better, rugged water bottle (7 gal) for less that the cost of the crappy (3 gal) one offered by the local water store. If you needed an ultracompact sleeping-bag and tent for protesting in North Dakota winters, REI probably carries it. Or climbing gear. Or a titanium spork.
Affliate link and content sales capitalizing on trendy animosity. Hard to say if the story actually happened or it's more of a tall tale to make money.
Port knocking and some even obscurity are valid additional layers of defense-in-depth if combined fundamentals of A3E.
State actors can afford millions to spend on build/buying sploits for [insert technology]. For example, use different standard for OS at edges where possible to reduce attack surface. Preferably scrub network traffic at edges (not just web traffic) and really lock down traffic to remote access boxes.
Critical infrastructure demands solid, understandable security (ie defense-in-depend). Throwing around shiny, new, unprovens things to "give the emperor new clothes" increases risks for major security breaches.
Plus, this commercial thing doesn't do anything pam ldap and config mgmt can't do. Just reinventing the wheel yet again to charge people money for proprietary "solutions."
Yup. Open ports to the world is a terrible idea for anything real. This is why SSH jumpboxes (say a roundrobin pair of OpenBSD VMs with ssh rbash &| strongswan. Add secure portknocking to the pf firewall for bonus points.)
Plus, there's already plenty of ways to AAA OpenSSH using puppet/chef, PAM, RFC 4255, google authenticator (via pam plugin). It's really easy to set up if you've done it before.
Sure, they maintain a control TCP channel like ftp but that's a normal pattern. Falling back to other protocols is a necessity because some environments literally lock down everything apart from ARP, DHCP, DNS, HTTP/S and email.
Writing an application-level protocol to make UDP act like TCP or SCTP is a sign of failure to fix issues lower down.
Worse, UDP often gets dropped first when a network is saturated, and it's harder troubleshoot to because it's not connection-oriented stateful and doesn't work with existing tools... debugging now requires nonstandard knowledge inside an app. (Turning a browser into an OS is a metastasizing cancer.)
There are better ways to solve efficient, low-latency content distribution and bidirectional state RPC without reinventing everything every other year.