Currently conflict is a really good sales pitch for buying more interceptors.
You could expect order books to get so thick that production increases.
I mean looking from the side lines, I could see why many countries might want to have a few interceptors on hand. Just in case, it's certainly a nice way to buy some time.
As a casual observer who has written perhaps a dozen lines of Scala in his life, I feel like Scala approaches any “pick one” decision with “why not both?”.
Dunno about Xcode, but if you put a go compiler in there, I doubt it will compile or run slowly. Some dependencies may require C, but you could avoid that mostly.
Have you ever looked at a dollar bill in your life.
Who do you think printed it. Who signed the bill?
The US can just print money and receive goods in exchange of literal paper. Or just put an extra zero in a bank account and receive goods in exchange.
And if a certain yahoo decides they want in the money printing scheme...who do you think is going to send the goons with guns to prevent the government monopoly in creating literal wealth.
Until recently, no private company wanted to go to the Moon.
And it is particularly ironic to select that since the government’s attempt to return is the most expensive, slowest, least tested launch system possible, and still needs help to get to the Moon.
Conservatives discovered a cheat code to get: (a) people to have to identify on the computer everywhere and (b) control what they can do with and without this identification.
This whole thing is the problem. AngularJS was released in 2010. If in 2010 I'd know that the damn thing would die in 2021, and that I would have to rewrite it all by that date, I would not have used the damn thing in the first place.
I also at some point inherited an app written in Vue 2. By the time I got it, Vue 3 was already out and a couple of years later, Vue 4, completely different to Vue 2, was out. Rewriting was not an option, so I had to create a docker image that can compile the damn thing offline, cause if some part of the supply chain breaks, well, that's it.
Ten or eleven years is not a super long time in enterprise software. Having to keep upgrading and changing libraries just cause the devs of the libraries get bored should not be a thing.
This is why I struggled and struggled to omit JS at all costs on a greenfield project - many apps from even 5 years ago by now fired teams fail to build with cryptic npm messages. And if you get past that you have to deal with webpack or some such junk. We settled with go fyne which compiles to wasm to handle both local and remotely accessible use cases. Trade off is not as much freedom and a fixed feature set but I know it's gonna work after 5 godamn years.
> If in 2010 I'd know that the damn thing would die in 2021
Was it obvious back then? I had to work on an AngularJS site for a while and it was the most confusing thing ever. Having come from React I couldn't understand the complexity but maybe it was still better than callback hell in jQuery?
A problem I found was that getting at a local bus station at London, showed all their destinations as London, but without any precise place of where I would arrive. At one point I traveled from one part of London, to Bash, a completely different city, back to another part of London.
reply