> Your DB isn't going any faster by switching to something else, if that's what you think.
Only true if none of the DB accesses are about stuff that could live as state across requests in a server that wasn't php. Sure, for some of that the DB's caching will be just as good, but for others, not at all.
In most cases you could add a shared cache to fix the problem - e.g. put your shared state in Redis, or in a file that is synced across servers (if its kept as state in a long running process it cannot need to be updated frequently).
These days my vote would go to a quad. Impeller fore, impeller aft and one in each wing. Behind doors, obviously, like the bays for retractable landing gear - this is a solved problem.
They don't have to be efficient, because how much hovering time would you really need? Battery could even exist only in mission specific pods (internal perhaps, when it's a cargo carrier), trade-off as needed.
Thats the point, the more efficient the less supply line you need, which means more autonomy.
I cant find the source but in Afghanistan a large proportion of the Allied casualties were from protecting supply lines.
The thing about quad copters is that they work at small scale because the rotor have almost no inertia. When you scale that up to 2m, then inertia is a bitch. That means you need tilting blades to make up for that lack of control.
BUT
You also need something to be powerful enough to alter the speed of the rotors to get yaw.
Plus you then also need to get them all to rotate so that you can get the efficiency of normal flight.
The reason why the osprey exists is because it has longer range than a helicopter (~1200 miles vs 400) its also faster.
> Plus you then also need to get them all to rotate so that you can get the efficiency of normal flight.
Not when you simply don't use them for horizontal flight. You just shut the VTOL hatches and forget that you aren't a conventional airplane until you want to land but there isn't an airstrip.
Winged operation has to be efficient, no doubt about that. But hovering does not need much endurance when it's only for getting away from the ground and setting down.
Electric has the power density, even more so when you don't need the power for a long time (heat buildup, no need for an equilibrium). Electric suffers from energy density, but that's where the winged mode comes in (old fashioned jet turbine, with the generator slightly larger than usual so that you'll have full batteries for the short landing hover)
If it slows down Rust development it's not pragmatic. And if it creates a cultural schism between full commitment and pragmatic approaches, it's also trouble. Remember Scala?
>If it slows down Rust development it's not pragmatic.
I truly don't understand. If you don't want rust to become complex, you don't want it to "develop" fast anyways. Unless you mean you think it will be slower to write code?
> And if it creates a cultural schism between full commitment and pragmatic approaches, it's also trouble.
Zero clue what this is supposed to mean. WTF is "full commitment" here?
> Remember Scala?
Scala, haskell, and others are high level languages in "academic terms." They have high levels of abstraction. The proposals are the opposite of high level abstractions, they instead formalize very important low level properties of code. If anything they decrease abstraction.
Rust is nowhere near the complexity of Scala wrt. seemingly arbitrary high-level features. There's a low-level, systems programming featureset that involves quite a bit of complexity but that's also less arbitrary when comparing across similarly low-level languages.
Counterpoint: if any language could thrive in that valley of despair between pragmatic and theoretical excellence you're referring to, it would be Rust. Because so much of the cost is already paid for once you have satisfied the borrow checker. At least that's what I'd imagine, I could certainly be wrong.
What if the CEO isn't just telling the company how much to invest, but also has influence on how that money is used? Google's relative success, if it exists, I'd rather not judge, isn't from investing more than everybody else. Because the money just keeps pouring into these things, for all contenders.
Valuable in what metric? I'm very much in the brownfield-has-the-lessons camp, but one of the lessons is that this experience has a very low market value. In fact it's so impossible to downgrade from "senior in $outdated" to "junior in $whateverisconsideredhotrightnow" that any brownfield experience could easily be considered to have negative market value.
Only true if none of the DB accesses are about stuff that could live as state across requests in a server that wasn't php. Sure, for some of that the DB's caching will be just as good, but for others, not at all.
reply