That's not true. Significant amounts of lobbying and palm greasing happen in person, explicitly off of cell phones. It's not a coincidence that all of the companies that receive massive amounts of federal government money have headquarters around DC.
Yes, and if you move the capitol all of that moves with it. You literally admitted that those headquarters are located for the purpose of in-person meetings, not a love of DC. So unless the location you intend to move the capitol to is top secret, it's irrelevant.
>What neighborhoods are there where rich people reside who have no more social or political influence than people living in The Projects?
Compared to this one? Nearly all of them. The neighborhoods in Mountain View are filled with affluent people that have no connection to federal politicians and no influence over the FBI at all.
Exactly. Surely wealthier people have more political influence all else equal. But busting down the door of a wealthy person in Mountain View is pretty unlikely to get anyone fired at the FBI. Go ahead, shoot their dog for good measure-- no problem.
The Zumwalt class started out as a requirement from the armed forces committee in congress for a replacement for the old battleship Naval Gunfire Support mission. That is sit a bit off the coast and go boom with big guns to help the boots on the ground.
Just one wee little problem with that: anti ship missiles have made that a suicide mission since approximately the late 60s. And no, all the stealth in the world wasn't going to make a difference in that when a simple counter battery radar would spot you, not to mention other means.
The Navy tried to get out of it but couldn't, so we got stuck building 3 rather useless boats and then canceling the program. Some neat naval design and engineering went into them which may be useful in the future, but it wasn't worth it for the sticker price at all.
The people created this fuster cluck are the same folks that kept the battleships operational or semi operational post WW2 when it was clear they were obsolete, at non trivial cost to taxpayers.
Prime example of why military spending needs to be cut in half at least to focus on what's important. Not to weaken the military but to stop bullshit like this in its track.
Speaking of tracks, apparently production of M1 tanks is going at full pace, thanks to the factories being located in the districts of influential politicians. The military has no need for them though, so they are going straight to storage.
Despite, as far as I know, even the Army saying they don't want nor need these Abrams. Keeping the factories running is good, one never knows when that industrial base might needed at scale. and we no longer in the 40s when car factories could easily converted to tank production. You don't need full capacity production for that, so.
The ships float fine. There's a sort of internet forum meme about them having poor seakeeping due to the unusual tumblehome hull. That's 100% imagined by forum warriors. The boats have remarkable stability and superior seakeeping. That's not the problem with them at all. The problem with them is they they were designed for a mission that was boneheaded from the beginning, and that costs ballooned tremendously to build them.
The Navy's plan for them now is to convert them into missile boats for the new hypersonic missiles, if/when those are ready, so they main end up being somewhat useful eventually. But again, you'd not want to spend money the way we had to get to this result if you had some way to rewind the errors.
Rust and Go pull in some stuff from functional programming (first class functions) but are not really designed around functional programming as the way to get things done.
Most go programming I've seen is like python where you are slinging around maps that are getting modified all over the place. Very antithetical to functional programming.
You are confusing functional programming for pure functional programming. This is like confusing Smalltalk-style OOP with OOP in general and then complaining about C++.
Mutability and functionalness are orthogonal, although the immutable style lends itself well to functional programming and mutability is more kludgy in FP.
But given that both Rust and Go have first class closures, they qualify as a functional programming language. The definition of FP is that functions are data. Python, Rust, Go, etc all fit this definition. Modern c++ does as well.
There is no reason not to include these languages, not only they support functions as data, they also support higher order functions (functions that take callbacks accepting callbacks accepting callbacks, ad infinitum).
It's not difficult, it's reckless bordering on incompetence. The shared kernel is just way to much attack space and shared resources to make it tenable in the face of adversaries.
A shit ton of people apply to FAANG companies because of the money on the table despite having no professional experience as a software engineer nor writing any code.
