Recently I’ve had the best results with Gemini; with this I’ll have to go back to Codex for my next project. It takes time to get a feel for the capabilities of a model it’s sort of tedious having new ones come out so frequently.
C#'s runtime (dotnet runtime) adds overhead compared to Rust with GC and other stuff too. This is true even with single-binary AOT compilation, the runtime is still there (just like Go). So it will never be suitable for some scenarios.
You can definitely implement manual ownership tracking in C#, this is quite common for non-memory resources and does have some language syntactic sugar with the Dispose pattern for example. But you can't truly roll your own memory management/ownership unless you do something with "unsafe" which seems counter-productive in this case :P.
This isn't true at all anymore for years! Microsoft acknowledged Linux won for server-side and since C# is primarily used as a server-side language they made everything work incredibly well on Linux.
I find that modern versions of dotnet seem to run better on Linux. And from what I see from Azure and from MSFT engineer blog posts, I'm assuming dotnet support on Linux is a higher priority than on Windows.
In any case, their claim that dotnet is a bad framework made me chuckle out loud. I'd like to see their impression of what a better framework looks like.
I have the same result : performances on Linux are better and this is a real focus for MSFT engineer (Azure has a tons of linux instances running dotnet)
I can’t handle the swipe up to switch apps gesture with reduced motion it becomes too jarring. I set the glass to “tinted” and that’s about it. I wish they had a stronger disablement of just the glass.
I love unstyled UI components since you get complete visual control but accessibility still works and that's so easy to screw up and not notice it's broken.
I've used Tailwind headless UI (https://headlessui.com/) and it's great, I'll take a look at this one too for future stuff.
When a data tree is tightly coupled (like a complex sample of nested data with some arrays from a sensor) and the entire tree is treated like a single thing by writes, the JSON column just keeps things easier. Reads can be accelerated with indexes as demonstrated here.
This is the typical practice for most index types in SingleStore as well except with the Multi-Value Hash Index which is defined over a JSON or BSON path
reply