scripts VS .NET Runtime

Check out Vermaden's site: https://vermaden.wordpress.com/

I mostly do interesting stuff on FreeBSD and its all documented in as detailed form as possible here:

- https://vermaden.wordpress.com/

Regards,

You might want to check out Vermaden https://vermaden.wordpress.com/ And Robonuggie https://youtube.com/@RoboNuggie Both excellent resources on how to get things done on the desktop in FreeBSD. Salute

I always wanted to start and write on my blog - just to share some things that other may find useful.

I started with something simple - entirely preloaded (all howtos) and static:

1. http://www.strony.toya.net.pl/~vermaden/links.htm

I assume no one ever entered it ... besides me of course.

Then some time later - I though that having that 'static' links site is pointless - lets start 'proper' blog this time. I have chosen Gogle Blogspot this time.

2. https://vermaden.blogspot.com/

... and after several posts I generally abandoned it.

Several years later I made a decision to make another blog ... but this time with some strategy behind.

3. https://vermaden.wordpress.com/

This (3rd) attempt was 'successful' and people sometimes actually visit my blog - sometimes even comment. In March of 2023 I will 'celebrate' the 5th year of that blog. I have made about 100 posts there and I made about 100,000+ views per year:

- https://i.imgur.com/raWvrZj.png

What is the secret of [3.] being successful and [1.] and [2.] definitely not? Sharing.

I do not know what blog (subject matter) you are trying to share - but for IT/UNIX/BSD/Linux related blogs (as mine) you need to share each post on these mediums:

- mastodon

- twitter

- lobsters

- hacker news

- FreeBSD forums

- reddit (r/BSD)

- reddit (r/FreeBSD)

- reddit (r/unix)

- reddit (r/linux)

- linkedin

Not sure about Facebook/Meta as their 'ecosystem' definitely does not suit my needs.

You need to ask yourself where and how people would try to find your content. They would definitely not browse a catalog of blogs. Maybe they wil ltry the search engine ... but search engines only pick up sites that are somewhat popular. They omit pages/blogs that are 'unknown'. How blogs are known? By many links pointing to them.

In other words - if you do not share your work/posts on all 'relevant' platforms - then you will 'die' in a 'non-known' hell.

If you believe your work - and it is work, you 'waste' your time to write/share these things you do - is valuable - then share them in all possible mediums/medias. If your content is good - you have to do nothing else. If your content is crap - You will immediately get feedback about it :D

One of the things that I really appreciate was the feedback I got. I often assumed that I know a lot about 'X' topic - just to change my mind after several comments later and providing and UPDATE to my blog post :)

I do not know what should I add here more so I will end my comment - but feel free to ask if You have any questions.

Regards,

After you get it all running using the cooltrainer site, then go to https://vermaden.wordpress.com/ which has some most excellent tasty config changes to make your boot time shorter, and your desktop work better. ALONG with tons of configs to help you configure different desktops and desktop apps/configs.

Any suggestions on how to get resume to work after suspending on a Thinkpad X260? I have read https://vermaden.wordpress.com/ and got suspend to work it just locks and have to reboot.

It's an interesting "time is a circle" problem given that a century only has 100 years and then we loop around again. 2-digit years is convenient for people in many situations but they are very lossy, and horrible for machines.

It reminds me of this breaking change to .Net from last year.[1][2] Maybe AA just needs to update .Net which would pad them out until the 2050's when someone born in the 1950s would be having...exactly the same problem in the article. (It is configurable now so you could just keep pushing it each decade, until it wraps again).

Or they could use 4-digit years.

[1] https://github.com/dotnet/runtime/issues/75148

These can also be passed as arguments to `dotnet publish` if necessary.

Reference:

- https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...

- https://github.com/dotnet/runtime/blob/main/src/coreclr/nati...

- https://github.com/dotnet/runtime/blob/5b4e770daa190ce69f402... (full list of recognized keys for IlcInstructionSet)

Yes, that is true. I'm not sure about JVM implementation details but the reason the comment says "virtual and interface" calls is to outline the difference. Virtual calls in .NET are sufficiently close[0] to virtual calls in C++. Interface calls, however, are coded differently[1].

Also you are correct - virtual calls are not terribly expensive, but they encroach on ever limited* CPU resources like indirect jump and load predictors and, as noted in parent comments, block inlining, which is highly undesirable for small and frequently called methods, particularly when they are in a loop.

* through great effort of our industry to take back whatever performance wins each generation brings with even more abstractions that fail to improve our productivity

[0] https://github.com/dotnet/coreclr/blob/4895a06c/src/vm/amd64...

[1] https://github.com/dotnet/runtime/blob/main/docs/design/core... (mind you, the text was initially written 18 ago, wow)

If you care about portable SIMD and performance, you may want to save yourself trouble and skip to C# instead, it also has an extensive guide to using it: https://github.com/dotnet/runtime/blob/69110bfdcf5590db1d32c...

CoreLib and many new libraries are using it heavily to match performance of manually intensified C++ code.

DEBUG: packageFiles with updates (repository=local) "config": { "nuget": [ { "deps": [ { "datasource": "nuget", "depType": "nuget", "depName": "Microsoft.Extensions.Hosting", "currentValue": "7.0.0", "updates": [ { "bucket": "non-major", "newVersion": "7.0.1", "newValue": "7.0.1", "releaseTimestamp": "2023-02-14T13:21:52.713Z", "newMajor": 7, "newMinor": 0, "updateType": "patch", "branchName": "renovate/dotnet-monorepo" }, { "bucket": "major", "newVersion": "8.0.0", "newValue": "8.0.0", "releaseTimestamp": "2023-11-14T13:23:17.653Z", "newMajor": 8, "newMinor": 0, "updateType": "major", "branchName": "renovate/major-dotnet-monorepo" } ], "packageName": "Microsoft.Extensions.Hosting", "versioning": "nuget", "warnings": [], "sourceUrl": "https://github.com/dotnet/runtime", "registryUrl": "https://api.nuget.org/v3/index.json", "homepage": "https://dot.net/", "currentVersion": "7.0.0", "isSingleVersion": true, "fixedVersion": "7.0.0" } ], "packageFile": "RenovateDemo.csproj" } ] }

https://github.com/dotnet/runtime/issues/59591

Support zstd Content-Encoding:

We might not be that far away already. There is this issue[1] on Github, where Microsoft and the community discuss some significant changes.

There is still a lot of questions unanswered, but initial tests look promising.

Ref: https://github.com/dotnet/runtime/issues/94620

https://github.com/dotnet/dotnet exists for source build that stitches together SDK, Roslyn, runtime and other dependencies. A lot of them can be built and used individually, which is what contributors usually do. For example, you can clone and build https://github.com/dotnet/runtime and use the produced artifacts to execute .NET assemblies or build .NET binaries.

Yeah, it kind of is. There are quite a few of experiments that are conducted to see if they show promise in the prototype form and then are taken further for proper integration if they do.

Unfortunately, object stack allocation was not one of them even though DOTNET_JitObjectStackAllocation configuration knob exists today, enabling it makes zero impact as it almost never kicks in. By the end of the experiment[0], it was concluded that before investing effort in this kind of feature becomes profitable given how a lot of C# code is written, there are many other lower hanging fruits.

To contrast this, in continuation to green threads experiment, a runtime handled tasks experiment[1] which moves async state machine handling from IL emitted by Roslyn to special-cased methods and then handling purely in runtime code has been a massive success and is now being worked on to be integrated in one of the future version of .NET (hopefully 10?)

[0] https://github.com/dotnet/runtime/issues/11192

[1] https://github.com/dotnet/runtimelab/blob/feature/async2-exp...