Can we sue the USCIS for not making an interview slot available for a family based greencard application and then rejecting the application because we didn't attend the interview before the time limit?
Even thought this is downvoted and it kind of underplays the overall devops role, I understand the sentiment here.
That might be a reason why Vercel, Netlify, Render and others are picking up usage. YC has been investing in several similar companies. Big cloud is going in the same direction with AWS Amplify/App Runner, GCP Firebase/Cloud Run and Azure.
This is not an exact answer to your question, but if you run a "simple" website or web application and really want to move to react, choose an easy to use and maintain popular framework like Next.js and host it on a platform like Vercel or Netlify
Yeah, see, my concern is that I am constantly going to be porting the site over to the developer’s framework du jour. Maybe I am overestimating what a rewrite requires.
I already know what I need the web application to do. It uses Flask, which I understand to be akin to driving a Dodge Caravan, but it gets me place to place. Updating it to Next.js or similar only feels necessary to me when the Dodge needs to be abandoned by the side of the road. For the developer, I am sure it feels like working on a useless piece of junk, but the developer is not the one that has to drive it place to place.
What is your opinion about Gigya, LoginRadius and other old timers in the CIAM space? How are you changing this space? Also how does it compare to AWS Cognito, GCP CIP and others?
Two big changes:
Most players in this space treat authentication as a point in time decision and it is usually static. IE, you are about to enter an webapp, we will now authenticate you. We think authentication should be a gradient. You can be unauthenticated, authenticated but unverified, and you can be fully authenticated. The ideal user experience is that users should be able to try an app or experience prior to having to "login".
Second, we also hold account/profile data for users and make it available to apps and websites to personalize and customize their experience. This is critical as we move into "hyper customization" in the near future. We allow sites to slowly gather data through trust. At the same time, we give the end-user control over this data (they can turn it off, edit it, just like they would a profile).
The mostly same problems plague Amazon Fire TV and Amazon Prime, Prime Channels, Prime Video for purchase, Prime video included in prime account, Prime App on different platforms, SSO with TV Network Apps. Looks like Apple is trying to catch up with mess.
With Google, I don't even know where to start. Messaging is not the only product line they messed up. Play Movies offering the same thing as Youtube Movies and Google Play Music - Youtube Music (you can buy, you can subscribe). Adding podcasts to Google Play Music, then removing it for a standalone app. However if you download the podcasts from the standalone app, they show up as Albums in Google Play music (on Android)
Been a paid user for a while. I love all the UI elements, markdown support, cross-platform compatibility etc. I have used Evernote, Simple Note and Boostnote previously.
Some problems however:
Desktop app takes a while to load. I understand it's electron, but so are Slack and VSCode. I am ready to keep it open on Mac. But on pressing Cmd+W, it closes the app, though not quit. Re-opening from that state is still slow. No other electron apps do that.
Offline experience on mobile isn't good. When I am in subway and want to jot down something quickly, it searches for internet for a while before allowing me to do anything
I have similar questions if @rauchg is still reading. We just got a premium account and was setting up Dockerfiles and now.json based on Now 1.0.
All, I want to do is provide a Dockerfile that included a cross-platform build process. Including now specific build tools is not ideal for avoiding vendor-lock in.
Now has amazing for us to build prototypes, internal sites etc that we may eventually move to our standardized AWS infrastructure. Adding now specific build tools makes the process unusable for us
I understand from the docs that Now 1.0 is not deprecated yet, but it bothers me to invest more time in converting some of our internal projects to Now
I second that. Long-running docker containers are more beneficial in many use-cases. Now 1.0 was the closest thing I found to Azure Container Instances and AWS Fargate
Now offering 1.0 style deployments on an ongoing basis will be helpful.
