Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)SP
Spyros @programming.dev
Posts 40
Comments 30

How .NET 8.0 boosted AIS.NET performance by 27%

endjin.com How .NET 8.0 boosted AIS.NET performance by 27% | endjin

When we benchmarked endjin's AIS.NET library on .NET 8.0, we were delighted to see substantial performance gains, with no extra work required.

How .NET 8.0 boosted AIS.NET performance by 27% | endjin
0
avaloniaui.net Introducing Hybrid XPF: Bridging Avalonia and WPF Controls

Hybrid XPF enables the integration of 700+ WPF controls into Avalonia apps, easing the transition for companies migrating to Avalonia while maintaining essential WPF elements.

Introducing Hybrid XPF: Bridging Avalonia and WPF Controls
0
devblogs.microsoft.com The convenience of System.IO - .NET Blog

File I/O APIs are used pervasively in apps. .NET has great API for reading and writing files. They are a great example of the convenience of .NET.

The convenience of System.IO - .NET Blog
0
devblogs.microsoft.com The convenience of System.Text.Json - .NET Blog

JSON is one of the most common formats in apps today and .NET has great APIs for reading and writing JSON documents. It's a great example of the convenience of .NET.

The convenience of System.Text.Json - .NET Blog
1
devblogs.microsoft.com Debugging Enhancements in .NET 8 - .NET Blog

.NET 8 introduces debugging enhancements to many commonly used types. Check out what is new and discover how .NET debugging is better than ever.

Debugging Enhancements in .NET 8 - .NET Blog
0
devblogs.microsoft.com Performance Improvements in .NET 8 - .NET Blog

.NET 7 was super fast, .NET 8 is faster. Take an in-depth tour through over 500 pull requests that make that a reality.

Performance Improvements in .NET 8 - .NET Blog
1
devblogs.microsoft.com Performance Improvements in .NET 8 - .NET Blog

.NET 7 was super fast, .NET 8 is faster. Take an in-depth tour through over 500 pull requests that make that a reality.

Performance Improvements in .NET 8 - .NET Blog

The yearly Stephen Toub blog post we were waiting for is finally here

3
devblogs.microsoft.com Announcing .NET 8 RC1 - .NET Blog

.NET 8 RC1 is now available with improvements to System.Text.Json, a new AOT mode for Android and WASM, Azure Managed Identity support for containers, and more!

Announcing .NET 8 RC1 - .NET Blog
0
devblogs.microsoft.com Demystifying Retrieval Augmented Generation with .NET - .NET Blog

Build a chat-based console app with Retrieval Augmented Generation (RAG) from scratch.

Demystifying Retrieval Augmented Generation with .NET - .NET Blog
1
blog.jetbrains.com Wayland Support for IntelliJ-based IDEs | The JetBrains Platform Blog

For Linux users of IntelliJ-based IDEs, an exciting advancement is on the horizon – the upcoming support of the Wayland display server protocol. This update

Wayland Support for IntelliJ-based IDEs | The JetBrains Platform Blog
2
Visual Studio for Mac Retirement Announcement - Visual Studio Blog
  • MonoDevelop died for this.

    (Disclaimer: I haven't used MonoDevelop to know its quality, I'm just tempted by the idea of a free cross-platform .NET IDE. Microsoft took MonoDevelop, forked it into VS for Mac, left the former stagnate, and now is killing its closed-source descendant.)

  • devblogs.microsoft.com Visual Studio for Mac Retirement Announcement - Visual Studio Blog

    Today we are announcing the retirement of the Visual Studio for Mac IDE. Visual Studio for Mac 17.6 will continue to be supported for another 12 months, until August 31st, 2024, with servicing updates for security issues and updated platforms from Apple.

    Visual Studio for Mac Retirement Announcement - Visual Studio Blog
    55
    devblogs.microsoft.com Visual Studio for Mac Retirement Announcement - Visual Studio Blog

    Today we are announcing the retirement of the Visual Studio for Mac IDE. Visual Studio for Mac 17.6 will continue to be supported for another 12 months, until August 31st, 2024, with servicing updates for security issues and updated platforms from Apple.

    Visual Studio for Mac Retirement Announcement - Visual Studio Blog
    10
    devblogs.microsoft.com Announcing the New Foundational C# Certification with freeCodeCamp - .NET Blog

    The Foundational C# Certification with freeCodeCamp is now available! The certification is free, globally available, and includes a full training course.

    Announcing the New Foundational C# Certification with freeCodeCamp - .NET Blog
    0

    Avalonia XPF pricing is now publicly available: starting from €4,999 per app, per platform, perpetual license

    This is not to be confused with the Avalonia UI framework which remains free and open source.

    XPF is a new project by the same team that allows existing WPF apps to be cross-platform (so enterprises can take their existing Windows-only apps and run them on MacOS, Linux and maybe WebAssembly). It's in early stages so I don't know how well it works.

    1
    devblogs.microsoft.com New C# 12 preview features - .NET Blog

    .NET 8 Preview 6 adds three new features for C# 12: interceptors, inline arrays, and enhancements to the nameof expression.

    New C# 12 preview features - .NET Blog
    0

    GIMP - GIMP 2.99.16 Released: Wilber Week 2023 edition!

    Tangentially related to the Linux ecosystem, since it's a major software that's used by many of the platform's users

    1
    Avalonia v11
  • Well, for starters, WinUI 3 is Windows only (correct me if I'm wrong), while Avalonia supports Windows, MacOS, Linux, Android, iOS and WebAssembly.

    The cross-platform solution that Microsoft advocates for is MAUI, which doesn't support Linux. And it uses native controls, meaning you may encounter platform-specific bugs, while Avalonia renders the controls the same way everywhere using Skia (same approach with Flutter).

  • *Permanently Deleted*
  • Please be civil towards other users. Language on the internet can be misrepresented resulting in hostility in an otherwise technical discussion. This goes to everyone involved, I'm just replying in this specific comment.

  • On the road to Plasma 6
  • Correct me if I 'm wrong, but I think it's still the same situation since January 2020: the long-term-supported (LTS) Qt releases are available to commercial licensees only and KDE supports collections of patches for them. Which is a hassle for sure. But nothing has changed because a fork of Qt (worst case scenario) would demand massive manpower from KDE.

    And the KDE Free Qt Foundation exists, so the Qt Company can't close down the framework.

    The Foundation has license agreements with The Qt Company, Digia and Nokia. The agreements ensure that the Qt will continue to be available as Free Software. Should The Qt Company discontinue the development of the Qt Free Edition under the required licenses, then the Foundation has the right to release Qt under a BSD-style license or under other open source licenses. The agreements stay valid in case of a buy-out, a merger or bankruptcy.

  • Community Request Thread
  • I have no experience with it, but I noticed there is no community for Julia (both url and display name). The locked down subreddit had almost 23,000 subscribers (if you build it, they will come ;) ).

  • A fully self-contained natively compiled C# Hello World, including GC and everything can be as small as ~440 kB
  • Does it effectively output a single binary?

    Yes, that's one of the points of NativeAOT, a self-contained single binary, exactly as Go does it.

    Does it create some kind of clusterf*k and awkward packaging formats like other MS solutions such as UWP?

    No, you can create .exe files.

    Will it actually be deployable to a random fresh install of Debian 12 or Windows 10?

    Yes, NativeAOT supports Windows, Linux and MacOS, x64 and Arm64.

    What about compatibility with older systems?

    Not sure about that, I suppose it depends on the targets each .NET version support. For example, .NET 8 will drop RHEL 7 and only RHEL 8 and later.

    And to play devil's advocate: this won't work for all existing .NET applications. If you use reflection (which is AOT unfriendly), chances are that you will have to rework a ton of stuff in order to get to a point where NativeAOT works. There's a middle solution though, called ReadyToRun, which has some advantages compared to running fully with the JIT compiler.

  • *Permanently Deleted*
  • does lemmy have pinned posts?

    Yes, we can add one if needed. I created a poll in this thread: https://programming.dev/post/71137

    Btw, I just found out how to add a user as mod to a community, there is a button between each post / comment that is visible to moderators of that community. So, if you post to /c/dotnet, I can make you a mod there.

  • *Permanently Deleted*
  • Right now obviously the content feed and the users contributing are low enough so they could be merged effectively.

    In case the Fediverse and this instance grow rapidly though, I think that 2 communities would be more beneficial: having a more active community about C#, with questions about the language, its syntax, each new feature introduced etc, while the .NET community would undoubtly see less content and focus more on the underlying framework, the toolchain, language-agnostic discussions... In my experience, this is how it worked on the subreddits of the same names.

    Do you want to have a banner added on the sidebar, redirecting to /c/dotnet until we grow larger? Does Lemmy have a polling functionality (to ask the user opinions)? I couldn't find anything.