this post was submitted on 29 Jul 2023
62 points (93.1% liked)

Programming

17028 readers
289 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] christophski 17 points 1 year ago (2 children)

It's mind boggling that having an easy to use local environment wasn't the first thing cloud providers did

[–] UFODivebomb@programming.dev 5 points 1 year ago

Not mine boggling imo when you think of it from the angle of "then they'll have to spend more money!"

Otoh I had an argument with an AWS rep who just didn't understand why I wanted an isolated local dev environment.

[–] TehPers@beehaw.org 4 points 1 year ago* (last edited 1 year ago) (1 children)

As someone who's worked a lot with Azure Functions, the experience for me in Visual Studio has always been:

  • Create C# function app
  • Write the code
  • Hit F5

The Functions runtime can be ran locally as a standalone as well, and I was able to get Rust function apps working locally using a custom handler. There's also a vscode plugin to run them.

Things might be different for Lambdas/GCP's Functions?

[–] christophski 3 points 1 year ago

I'm thinking more about being able to run your entire environment locally. We use GCP and we have a combination of appengine, cloud run and cloud functions tied together with api requests and pubsub. The cloud functions are the main bit missing from our local environment as we've not been able to spend the time to set it up yet.