loom
sdk
loom | sdk | |
---|---|---|
10 | 113 | |
1,826 | 2,540 | |
0.4% | 1.1% | |
10.0 | 10.0 | |
5 days ago | 4 days ago | |
Java | C# | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
loom
-
Using Java's Project Loom to build more reliable distributed systems
It's more accurate to say Loom is [a particular type of] continuations in the JVM, which can be used to implement green threads / fibers.
You can see the implementation of VirtualThread here: https://github.com/openjdk/loom/blob/fibers/src/java.base/sh...
This uses the internal 'one-shot delimited continuation': https://github.com/openjdk/loom/blob/fibers/src/java.base/sh...
So, at least in principle, there is scope for other styles of concurrency to be implemented over this.
- Virtual thread (along with Structured concurrency and Scope Local) is previewing in JDK19?
-
6 .NET Myths Dispelled — Celebrating (Almost) 21 Years of .NET
Loom is actively developed https://github.com/openjdk/loom
- Project Valhalla status summary
-
Brian Goetz: "I think Project Loom is going to kill Reactive Programming"
Currently the Thread public constructor defaults to platform threads to be fully backwards compatible. So all libraries must be updated to support the new model.
-
Java’s Project Loom, Virtual Threads and Structured Concurrency with Ron Pressler
I've been casually following the repo ( https://github.com/openjdk/loom ) and the mailing list ( https://mail.openjdk.java.net/mailman/listinfo/loom-dev ) over the last 18 months or so, and it definitely appears that things are ramping up as of late. The implication (as I see it) is that they are relatively happy with the general design are and are at the point where they want help from experts in the various areas of the JDK (GC, Debugging, etc) to make sure that their pieces play well with Loom.
-
[Project Loom] New ea build based on jdk-17+13 is available for download.
https://github.com/openjdk/loom/blob/fibers/src/java.base/share/classes/sun/nio/ch/NioSocketImpl.java#L177
- [project loom] New thread builder API.
-
Have created a short and practical intro into what project loom is all about.
[1] https://github.com/openjdk/loom/blob/fibers/src/java.base/share/classes/java/lang/VirtualThread.java#L933
- Loom adds a feature to generate thread dump in JSON format.
sdk
-
Programmatically elevate a .NET application on any platform
[DllImport("libc")] private static extern uint geteuid(); public bool IsCurrentProcessElevated() { if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows)) { // https://github.com/dotnet/sdk/blob/v6.0.100/src/Cli/dotnet/Installer/Windows/WindowsUtils.cs#L38 using var identity = WindowsIdentity.GetCurrent(); var principal = new WindowsPrincipal(identity); return principal.IsInRole(WindowsBuiltInRole.Administrator); } // https://github.com/dotnet/maintenance-packages/blob/62823150914410d43a3fd9de246d882f2a21d5ef/src/Common/tests/TestUtilities/System/PlatformDetection.Unix.cs#L58 // 0 is the ID of the root user return geteuid() == 0; }
-
Swift was always going to be part of the OS
> There's definitely things they tried to improve on that... weren't really improvements. The way "assemblies" are matched in .NET is much more sophisticated- the goal there was to try to kill DLL hell. It evolved into the Global Assembly Cache, which is sort of the Windows Registry of DLLs. Not a huge fan of those bits.
The Global Assembly Cache did not make the jump to the modern .NET (Core). There was the thing called `dotnet store`, but it’s broken since .NET 6: https://github.com/dotnet/sdk/issues/24752
The assembly redirection hell has also been greatly reduced there.
-
.NET Blazor
I do the same.
I have a small write-up here: https://chrlschn.dev/blog/2023/10/end-to-end-type-safety-wit...
You get end-to-end type safety (even better once you connect it to EF Core since you get it all ways to your DB).
With this setup with hot-reload (currently broken in .NET 8 [0]), productivity is really, really good. Like tRPC but with one of the most powerful ORMs out there right now.
[0] https://github.com/dotnet/sdk/issues/36918
-
Why does dotnet cli not support updating sdk's?
Noticed an open issue just now.
-
.NET 8 – .NET Blog
You're thinking of https://github.com/dotnet/sdk/issues/22247
-
LÖVE: a framework to make 2D games in Lua
That's a twisted and wrong narrative
Unity like refers to a Editor driven approach
Unity became popular with its moonscript language (javascript like), they then ditched it to focus on C#, but what propelled unity to what it is today is the Editor driven approach, not c#, not DOTS
They are forced to transpile C# to C++ via IL2CPP as a result to target consoles/mobiles
C# is a disease when it comes to console/mobile support
It's a substantial dependency, quite heavy
And you are not free of unity like fuck ups, it's a microsoft language after all:
https://github.com/dotnet/sdk/issues/22247
And let's not forget when they changed the license of their debugger overnight to prevent people from using it in their products (jetbrains for example)
And them deprecating open source tooling to a proprietary/closed one for vscode (c# devkit)
Let's be careful when we recommend evil as an alternative to evil ;)
-
How to run multiple programs like python3 filename.py???
The script can be found at the end of the thread here https://github.com/dotnet/sdk/issues/8742
-
Writing Python like it's Rust
Another difference you might be surprised by is that the .NET tooling by default collects various data from your system and sends it to Microsoft [1]. If you want to avoid this (and still want to use .NET) you'll have to make sure that the environment variable DOTNET_CLI_TELEMETRY_OPTOUT is set in all contexts before touching anything.
[1] https://github.com/dotnet/sdk/issues/6145
-
.NET 8 is on the way! +10 Features that will blow your mind 🤯
SDK Pull Request
-
Disadvantages of using F# with Mono?
Pretty sure the final file referenced here https://github.com/dotnet/sdk/issues/8742 is the one I am thinking of.
What are some alternatives?
MQTTnet - MQTTnet is a high performance .NET library for MQTT based communication. It provides a MQTT client and a MQTT server (broker). The implementation is based on the documentation from http://mqtt.org/.
kdmapper - KDMapper is a simple tool that exploits iqvw64e.sys Intel driver to manually map non-signed drivers in memory
cats - Lightweight, modular, and extensible library for functional programming.
rpi-projects - Drivers and home automation projects for Raspberry PI.
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
csharplang - The official repo for the design of the C# programming language
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
coyote - Coyote is a library and tool for testing concurrent C# code and deterministically reproducing bugs.
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
JDK - JDK main-line development https://openjdk.org/projects/jdk
CoreCLR - CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.