okteto VS sdk

There are dedicated tools just for that. Apart from skaffold check also tilt.dev, garden.io, devspace.sh, okteto.com

Check also devspace.sh and okteto.com

You can consider using okteto for development environments, it lets you deploy your local code directly to k8s replacing the existing pods, our team uses it and it works pretty well with Golang.

Okteto is an application that allows you to develop inside a container, along with many features it permit the user to start a development environment and provide an automatic SSL Endpoints for k8s.

With Infrastructure as Code at its current state of maturity, it’s now easier than ever to replicate microservice environments in the cloud. This unlocked a new approach of having a personal production-like cloud environment for every developer, which they can use freely and in isolation. It comes in two flavors - persistent environments, or ephemeral environments created on demand with products like Okteto or Bunnyshell (also sometimes called Environment as a Service)1. This approach overcomes the resource limitations of the local environment but substitutes them for some new difficulties:

Remote development will be popular? Yes.

But developing in a monolithic machine may be not. The development environment should be clean and isolated, and products like gitpod and coder is promising.

Besides this, maybe you can have a look at https://github.com/tensorchord/envd and https://github.com/okteto/okteto

Okteto accelerates the development workflow of Kubernetes applications. You write your code locally and okteto detects the changes and instantly updates your Kubernetes applications.

Hey! Recently, I’ve been playing around with [Okteto](https://www.okteto.com/) to see how it helps with the local development of apps that will run in Kubernetes. It seems to be quite a good option for developers who don’t want to spend their time dealing with setting up and maintaining clusters. Moreover, you can use a development environment from Okteto without thinking about CI/CD pipelines for delivering the app.So, instead of working on your code locally and deploying it then to the cluster, the whole development process is shifted straight to K8s. That makes Okteto approach a bit different from what other projects, like Skaffold and werf, do. To implement this idea, they offer a [CLI tool](https://github.com/okteto/okteto) and their own cloud provided as both SaaS and self-hosted (it has a limited free option).Here is [my overview](https://blog.flant.com/okteto-cloud-for-local-development-in-kubernetes/) of Okteto; any feedback — especially, your own experience — is more than welcome.

There's a long long route to cloudification, but works like Okteto[1] seem like a nice early pass at doing what Docker-Compose was capable of for fast local development, but modern. Pursuing remote-development makes a lot of sense. There's already solid VSCode integration[2].

If you just need a terminal like thing to local-dev in, toolbx[3] is probably the first choice.

[1] https://github.com/okteto/okteto

[2] https://marketplace.visualstudio.com/items?itemName=okteto.r...

[3] https://containertoolbx.org/

Hi Jacob. I am one of the founders of Okteto (https://okteto.com/), a remote development platform for Compose and Kubernetes applications. We use Syncthing to sync code between the developer laptop and pods running in Kubernetes. I would love to know your thoughts on the strengths and weak points of Mutagen vs Syncthing for this use case.

[DllImport("libc")] private static extern uint geteuid(); public bool IsCurrentProcessElevated() { if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows)) { // https://github.com/dotnet/sdk/blob/v6.0.100/src/Cli/dotnet/Installer/Windows/WindowsUtils.cs#L38 using var identity = WindowsIdentity.GetCurrent(); var principal = new WindowsPrincipal(identity); return principal.IsInRole(WindowsBuiltInRole.Administrator); } // https://github.com/dotnet/maintenance-packages/blob/62823150914410d43a3fd9de246d882f2a21d5ef/src/Common/tests/TestUtilities/System/PlatformDetection.Unix.cs#L58 // 0 is the ID of the root user return geteuid() == 0; }

> There's definitely things they tried to improve on that... weren't really improvements. The way "assemblies" are matched in .NET is much more sophisticated- the goal there was to try to kill DLL hell. It evolved into the Global Assembly Cache, which is sort of the Windows Registry of DLLs. Not a huge fan of those bits.

The Global Assembly Cache did not make the jump to the modern .NET (Core). There was the thing called `dotnet store`, but it’s broken since .NET 6: https://github.com/dotnet/sdk/issues/24752

The assembly redirection hell has also been greatly reduced there.

I do the same.

I have a small write-up here: https://chrlschn.dev/blog/2023/10/end-to-end-type-safety-wit...

You get end-to-end type safety (even better once you connect it to EF Core since you get it all ways to your DB).

With this setup with hot-reload (currently broken in .NET 8 [0]), productivity is really, really good. Like tRPC but with one of the most powerful ORMs out there right now.

[0] https://github.com/dotnet/sdk/issues/36918

Noticed an open issue just now.

You're thinking of https://github.com/dotnet/sdk/issues/22247

That's a twisted and wrong narrative

Unity like refers to a Editor driven approach

Unity became popular with its moonscript language (javascript like), they then ditched it to focus on C#, but what propelled unity to what it is today is the Editor driven approach, not c#, not DOTS

They are forced to transpile C# to C++ via IL2CPP as a result to target consoles/mobiles

C# is a disease when it comes to console/mobile support

It's a substantial dependency, quite heavy

And you are not free of unity like fuck ups, it's a microsoft language after all:

https://github.com/dotnet/sdk/issues/22247

And let's not forget when they changed the license of their debugger overnight to prevent people from using it in their products (jetbrains for example)

And them deprecating open source tooling to a proprietary/closed one for vscode (c# devkit)

Let's be careful when we recommend evil as an alternative to evil ;)

The script can be found at the end of the thread here https://github.com/dotnet/sdk/issues/8742

Another difference you might be surprised by is that the .NET tooling by default collects various data from your system and sends it to Microsoft [1]. If you want to avoid this (and still want to use .NET) you'll have to make sure that the environment variable DOTNET_CLI_TELEMETRY_OPTOUT is set in all contexts before touching anything.

[1] https://github.com/dotnet/sdk/issues/6145

SDK Pull Request

Pretty sure the final file referenced here https://github.com/dotnet/sdk/issues/8742 is the one I am thinking of.