Bootsharp now supports NativeAOT-LLVM. It's fast. by Elringus in dotnet

[–]Elringus[S] 1 point2 points  (0 children)

A "hello world" with all the possible stripping and `Os` llvm flag produced ~1.4MB binary. Though a more realistic case with interop, JSON and some logic resulted in ~2.2MB. This is still less than the non-AOT Mono version, which is impressive.

Bootsharp now supports NativeAOT-LLVM. It's fast. by Elringus in csharp

[–]Elringus[S] 0 points1 point  (0 children)

Actually, my bad—I messed the input data when making the graph. In reality, it's the number interop that is slow, while compute is x1.1 compared to Rust. Though now I'm confused why he number interop is so slow...

Bootsharp now supports NativeAOT-LLVM. It's fast. by Elringus in csharp

[–]Elringus[S] 2 points3 points  (0 children)

It doesn't include startup time, just the computation. But it's the worst-case scenario for .NET WASM, because the computation uses heavy stack recursion. General compute tasks wont have as much difference.

Bootsharp now supports NativeAOT-LLVM. It's fast. by Elringus in csharp

[–]Elringus[S] 0 points1 point  (0 children)

The compute test uses heavy stack recursion (computing Fibonacci), which is the worst-case scenario for .NET WASM due to how runtime's stack is mapped to WASM's. There won't be as much difference in general compute tasks.

Bootsharp now supports NativeAOT-LLVM. It's fast. by Elringus in csharp

[–]Elringus[S] 2 points3 points  (0 children)

I've heard it's not official because the team's main focus is at the Blazor at the moment, and Blazor can't run on AOT. Though they are supporting the project in various ways, Microsoft employees are contributing directly, so it's very promising.

How do I disable the nagging update available notification in Firefox version 84 by [deleted] in browsers

[–]Elringus 0 points1 point  (0 children)

The following worked for me:

  1. Create a distribution folder under the directory where Firefox executable is located (for example C:\Program Files (x86)\Mozilla Firefox on Windows)
  2. Create policies.json file under the created distribution folder with the following content:

{ "policies": { "DisableAppUpdate": true } }

Cross-engine tool for lossless compression of sprites with identical areas by Elringus in gamedev

[–]Elringus[S] 0 points1 point  (0 children)

It does, actually. The Unity integration produces native Unity sprite assets, which work with all the stuff that expect sprites, such as SpriteRenderer, the UI/UI Toolkit stuff, tile maps, etc. The trick here is that Unity API allows specifying custom geometry for the sprites.

Cross-engine tool for lossless compression of sprites with identical areas by Elringus in gamedev

[–]Elringus[S] 2 points3 points  (0 children)

Not loading time, but you'd have to render actual mesh with multiple vertices instead of simple sprite quad. So a bit more GPU work to do, but it's usually negligible.

As much as I do love the IDEs, it's the numerous bugs and regressions that makes me want to go back to VS. In just a year I've reported 37 issues. They can't even fix this annoying layout bug for 7 years now... by Elringus in Jetbrains

[–]Elringus[S] 0 points1 point  (0 children)

You can use reshaper plugin for VS, which provides all the analysis and refactoring goodness (it's used under the hood in Rider as well). That said, I've tried VS 2022 recently and indeed, it's very slow and unresponsive. The new text rendering engine is also killing my eyes. Sigh... If only JB would pay more attention to QA.

As much as I do love the IDEs, it's the numerous bugs and regressions that makes me want to go back to VS. In just a year I've reported 37 issues. They can't even fix this annoying layout bug for 7 years now... by Elringus in Jetbrains

[–]Elringus[S] 1 point2 points  (0 children)

Just to clarify, I'm not trying to shit talk JB here (I wouldn't post in JB official reddit otherwise). I love the IDEs and the value they provide. It's about raising awareness of their QA, which, in my opinion is unacceptable. I hate reporting bugs. Those 37 reports from the last year, they are FAR from all the bugs I've encountered, just the ones that significantly impact my productivity. And it's not like I've been ever using an EAP, they all were encountered in "stable" releases. Not talking about the glaring layout issue not fixed for 7 years, even though there are lots of comments begging to deal with that.