Readit NewsThe reason this is true is because at a higher weight, you'll stall at max deflection before you can put enough stress on the airframe to be a problem. That is to say, at a given speed a heavier airplane will fall out of the air [hyperbole, it will merely stall - significantly reduced lift] before it can rip the wings/elevator off [hyperbole - damage the airframe]. That makes it questionable whether heavier is safer - just changes the failure mode.
Turbulence, especially generated by thunderstorms, or close to it.
> "Measuring software productivity by lines of code is like measuring progress on an airplane by how much it weighs." -- Bill Gates
Do we reward the employee who has added the most weight? Do we celebrate when the AI has added a lot of weight?
At first, it seems like, no, we shouldn't, but actually, it depends. If a person or AI is adding a lot of weight, but it is really important weight, like the engines or the main structure of the plane, then yeah, even though it adds a lot of weight, it's still doing genuinely impressive work. A heavy airplane is more impressive than a light weight one (usually).
I completely understand your analogy and you are right. However just to nitpick, it is actually super important to have a weight on the airplane at the right place. You have to make sure that your aeroplane does not become tail heavy or it is not recoverable from a stall. Also a heavier aeroplane, within its gross weight, is actually safer as the safe manoeuverable speed increases with weight.
Deleted Comment
This is equivalent to something I called the "QWERTY paradox" more than a decade ago:
Back when the Smartphone market exploded, people disliked typing on a touchscreen and repeatedly stated that they want a device with a physical keyboard.
There was plenty of evidence, surveys, market studies, trend predictions, devices for these "Messaging-centric" use-cases were always part of this market-demand roster.
But whenever someone answered the call and built a Smartphone with QWERTY keyboard, the product failed commercially, simply because also to people claiming they want such a phone, at the point of sale they were less attractive than their slimmer, lighter, all-screen counterparts.
Every major vendor went through this cycle of learning that lesson, usually with an iteration like "it needs to be a premium high-spec device" --> (didn't sell) --> "ah, it should be mass-market" --> (also didn't sell).
You can find this journey for every vendor. Samsung, LG, HTC, Motorola, Sony.
The same lessons were already learnt for small-screen devices: There was a "Mini" series of Samsung Galaxy, LG G-series, HTC One, Sony Xperia. It didn't sell, the numbers showed that it didn't attract additional customers, at best it only fragmented the existing customer-base.
Source: I work in that industry for a long time now
Blackberries? Granted, they failed but for a completely different reason.
SignalWire is the primary sponsor of Freeswitch but is mainly geared towards HUGE installations. BulkVS is cheaper and better in my opinion. You can also look at AnveoDirect, which is more raw than BulkVS, but you can become really really fancy with it. Like, call center fancy.
VoIP nerds out there, is there any simple PFSense equivalent for VoIP that would allow you to DIY this? Basically restrict inbound and outbound calls to a whitelist?
There are other comments about providers, but my way is way cheaper and you can run you EPBAX on a pi or even get a pre made VM from Azure, Amazon, etc.
Damn I hate paying rent.