1,838 karma · joined May 14, 2020
Machines isn't that. From the documentation, it appears as though it's "just" a VM pinned to a single region and none of the "magic" of Fly really applies. If the server your VM is hosted on goes down, Fly won't redeploy your container. It's just downtime. Spinning up in other regions is something you have to think about and actually do. It seems closer to Heroku than it does Fly.
Maybe I am totally misunderstanding Fly Machines and their use-case, maybe they're aiming to close the gap between Machines and Fly apps. It's just a bit of a bummer to see something that looks like walking back the original "promise" of Fly and makes me question whether or not Fly is going to just become like every other PaaS (even if it's a really good one).
> Customer: Your service is bad and I had a bad experience > Vendor: Okay > C: I've given you multiple chances but you're still not up to my standards > V: (assuming C was done with the product) Sorry to hear that, but here is a refund
Am I missing something here?
I'm looking forward to the day that I can write validation decorators for intersections, unions, and generics without doing any crazy hacks.
For example, in Skullgirls you can actually tune GGPO on a sliding scale to add more input delay buffering. You can essentially simulate delay-based netcode within a rollback based game by pumping up the input delay to the max. Players will find their personal preference on the spectrum of "near-zero input lag, more rollbacks" to "high input lag, no rollbacks."
Also, if your game is running at 60FPS you're going to have a lower bound of roughly 3 frames input lag anyway, even if you were playing local. So if you tune your rollback to a 3 frame delay as a default value, the experience for most players is going to be pretty much perfect.
Their whole game plan seemed to be to appeal to the high school students in the area based on their location and the fact that they had a couple of Xbox 360s and TVs you could use. It was cool at first, but most of us just went back to picking up a couple of slices at Rocky and Nicky's across the street and going home to play Modern Warfare. I'm not sure they lasted more than six months to be honest.
Say I want to connect a SQL client to my production DB do I expose a port on my production app that speaks the protocol? Or maybe I have a separate container that is basically just the Sqlite replica that I can connect to? Or maybe there is some other approach that I'm just not seeing?
Fly, Sqlite, and LiteFS is definitely an interesting combination but I'm still sort of mentally stuck in the managed (and standalone) DB model.
- Generic Associated Types - Let-else - Labelled break - Stable Backtrace API - Split debug info on Linux
Huge thanks to all the contributors and maintainers!
At the time Parag was CTO, did the VP of product report to him? If so, then you can absolutely make the claim that Parag is ultimately responsible here.
Whether or not that's actually what is happening here is a different story.
New Java versions are cut every six months since 2017 and since then has added a significant amount of new features, syntactical sugar, APIs, et cetera. Not only that, but they've also have been pretty aggressive IMO in deprecating and removing legacy. Very very different than the Java I remember working in years ago.
However this was last year, not sure what the current status of all this is.
Besides those dedicated enough to fly to tournaments and compete with the best, FGs still seem to be generally popular among the mainstream; SFV sold 6.6m copies, MK11 sold 12m, and GG Strive sold 1m. The 2010s were a total revival of the genre, which had a bit of a dead period in the early aughts.