GerjanDev (@GerjanDev) header
GerjanDev (@GerjanDev) profile picture

MSc CompSci, Software Architect & SAAS creator. Background in C# but liking functional programming like F#, Scala, TypeScript. Looking at Rust, Go, Elm

Nederland
Joined March 2016
Photo by GerjanDev (@GerjanDev)Photo by GerjanDev (@GerjanDev)Photo by GerjanDev (@GerjanDev)Photo by GerjanDev (@GerjanDev)Photo by GerjanDev (@GerjanDev)
Next idea for @davidfowl: create a code first build system in Aspire. Mark MSBuild as legacy/obsolete. Stop the XML magic, way too complex resolvers and relative slow build times.
1
1
2
243
Make it crazy fast, cs based instead is csproj based (dotnet build MyBuildInAspire.cs). Free lunch: Finally the equivalent of javac, gcc, go build, rustc, swift [srcfile] Yes, this would be a breaking change and I am totally fine with it. Make .NET cool/modern, with Aspire
2
65
Replying to @nthonyChu
@nthonyChu @bradygaster We have built a brand new Blazor app and we want to deploy it to Azure Container Apps but we are running into very weird issues. Locally and in docker everything runs fine, but in ACA we get weird blazor javascript errors.
1
76
My guess is that is has something to do with ingress, websockets or auth. What is the best way to get help here? I can file an issue but its very hard to explain :(
1
60
Personal (maybe unpopular) opinion after @TechoramaNL: Sessions at developer conferences should be always deep dives (level advanced, 300+). #techorama #techoramaNL
1
To end on a positive note: I really liked the venue, I liked the atmosphere, I liked the networking, seeing old collegues and seeiing familiar faces that I only know from Twitter or GitHub (also real engineers ;)). Big big thanks @TechoramaNL
1
My favorite talks were from @Aaronontheweb, @kenny_baas, @ecampidoglio and ofcourse Bart de Smet. Sorry @jfversluis 😉, I do like your YT videos though! #techorama #Microsoft
1
1
2
Replying to @davidfowl
@davidfowl I know you are looking into auth, maybe this can be helpfull to improve some things.
1
The only thing I want to do is to create a JWT token for api access, but there are a *lot* of ways to do this (I have 3 versions here, but I think there are more ways). On the internet there does not seem any consensus about this and I cannot find anything on MS Docs
I really hope that MS is working on this in some kind of (secret) working group (virtual/green threads/coroutines). Async/await as a concept was great and .NET pioneered it in some way but the current implementation really feels outdated @davidfowl @jaredpar @MadsTorgersen
And here it comes. Virtual threads with no dummy await. Just some methods augmented to capture the stack and restore. I know I know, fair scheduling, and yielding and... XYZ The direction though! It just runs! #Java #JVM #OpenJDK 😍
1
I know the limitations in the old days, that it was too hard and too risky to build it in the runtime because of .NET Framework etc, but I really hope now is the time to build this in the runtime instead of all the compiler machinery and trickery.
1
I think the hardest question will be: how on earth will you make this fit? New keywords, new concepts or try to reuse existing ones? In a perfect world you do not want to change the prog lang at all and 'just' bring the implementation one level deeper (from compiler to runtime)
1
I love the work MS is doing on a platform level and I love the great convergence and great release of .NET 6. The only thing that's left now is "MSBuild Core". .NET really needs a new/modern build system, not relying on ancient XML magic //cc @davidfowl @DamianEdwards
1
Also the missing build conventions are a pity in the .NET ecosystem (=> poor mans build.cmd/sh) and then my last wish: please kill sln files 😁
1
I know its insanely complex and I know something about props, targets, SDKs, RAR etc but I'm confident you can do this. I'm fine with breaking changes as long as we can have a hybrid solution.
1
So nice!! Also the inverted mode thats suggested. Please make this happen for VS @gotheap @shanselman
Excuse me for complimenting our own stuff, but this looks really nice in @intellijidea
1