algorithmsRcool

11 ms·

31.
by algorithmsRcool 1y ago
It looks like Coyote[0], which is used in azure, was an evolution of P# which was an evolution of P [0] https://www.microsoft.com/en-us/research/wp-content/uploads/...
32.
by algorithmsRcool 1y ago
Microsoft has a flavor of this for .NET called Coyote[0] [0] https://microsoft.github.io/coyote/#overview/how/
33.
by algorithmsRcool 1y ago
Acutally it can be a lot more if you are talking about pause latency, I've seen >200x improvements on max pause time on some syntethic benchmarks
34.
A week with Satori, the experimental low-latency GC for .NET(blog.applied-algorithms.tech)
4 points by algorithmsRcool 1y ago|0 comments
35.
by algorithmsRcool 1y ago
Definetly interested to hear your results. The synthetics suggest that it is just winning in everything except raw allocation performance, but unless you're allocating millions of objects per second then that shouldn't matter.
36.
A sub-millisecond GC for .NET?(blog.applied-algorithms.tech)
29 points by algorithmsRcool 1y ago|4 comments
37.
by algorithmsRcool 1y ago
This is a github discussion about an experimental Garbage Collector for .NET that dramatically reduces pause durations, total pause time without significantly damaging throughput The new GC is introduced in this comment: https://
38.
Pauseless Garbage Collector(github.com)
6 points by algorithmsRcool 1y ago|2 comments
39.
by algorithmsRcool 1y ago
I recall reading that our ability to measure time accurately exceeds that of any other quantity. According to the NIST, the newest Optical Lattice clocks would drift by less than 1 second if they were started 13 billion years ago at the big
40.
by algorithmsRcool 1y ago
The Naval Observatory in Washington DC has quite a few also
41.
by algorithmsRcool 1y ago
Well, I could just enrich the trace/event with sample data from CPU, RAM, Disk I/O, etc...
42.
by algorithmsRcool 1y ago
> Most sysadmins at this point would just configure a new filtered metric and start collecting data… for a month. While the system is broken. Wrong needle? Start looking through the haystack again with another new custom metric for anoth
43.
by algorithmsRcool 1y ago
If I understand correctly the "big idea" here is: 1. Juice up your Traces with every attribute possible 2. Use a telemetry backend that relies on cheap object storage so that your costs don't explode. 3. ...profit? Ok, but no
44.
Getting started with Dafny: Your first formal proof(blog.applied-algorithms.tech)
3 points by algorithmsRcool 1y ago|0 comments
45.
So what is Model Based Testing anyway?(blog.applied-algorithms.tech)
1 points by algorithmsRcool 1y ago|0 comments
46.
So what is Model Based Testing anyway?(blog.applied-algorithms.tech)
2 points by algorithmsRcool 1y ago|0 comments
47.
by algorithmsRcool 2y ago
I am actually shocked that Anders chose Go over C# for this port.
48.
by algorithmsRcool 2y ago
I didn't realize that the GC copied the surviving objects to a separate location. Come to think of it, i don't actually know how the GC keeps track of what object lies in what generation.
49.
by algorithmsRcool 2y ago
Yes, but now you are going through another translation (aka V8) layer in order to get down to x86 or ARM. You just have to hope that the optimizer of this translation layer is at least as smart as what you had before.
50.
by algorithmsRcool 2y ago
I just don't see it. WASM requires throwing away all the decades of x86/ARM compiler work in ecosystems like Java, .NET and C++ and placing all trust in the WASM runtime/V8 to perform as well as them.
51.
by algorithmsRcool 2y ago
Just going to plug the excellent .NET PBT library, CsCheck [0]. I have used it quite a bit to excersize strange corners of my program logic and found several exotic bugs with it. [0]: https://github.com/AnthonyLloyd/CsC
52.
by algorithmsRcool 2y ago
I'm happy at the prospect of more accurate readings. But honestly, the Libre 3 is already simply excellent and I would personally prefer the back of the arm location to more wrist based tech. I wear a traditional (Citizen) mechanical w
53.
by algorithmsRcool 2y ago
I go a little back and forth on this with my experience in F#, which relies heavily on inferred types. You can write a lot of F# before you need to add type annotations, but eventually, things become a spiderweb. The key issue is when you
54.
by algorithmsRcool 2y ago
This article undermines itself a bit by introducing an optimistic concurrency primitive that it calls "fence tokens", aka content hashes, data versions or etags which are all the same concept. Distributed locking, like all pessimi
55.
by algorithmsRcool 2y ago
Another related effect of this is Protocol Ossification [0] which happens when implementers of a public API/Protocol surface area take implicit dependencies on common but not standardized behaviors of the API/Protocol implementati
56.
What's New in C# 13(learn.microsoft.com)
7 points by algorithmsRcool 2y ago|0 comments
57.
by algorithmsRcool 2y ago
The F# team has done a great job of building compatibility bridges back to the C# way of doing things so the actual impact isn't bad.
58.
by algorithmsRcool 2y ago
F# has chosen this approach of implementing compatibility with newer C# features such as support for ValueTuple<T> and Span<T>. It has been pretty successful at keeping F# inside the compatibility story. ---EDIT--- Mean to post
59.
by algorithmsRcool 2y ago
F# is full supported on Windows, MacOS and Linux via CoreCLR and several more platforms via Mono, just like C# is
60.
by algorithmsRcool 2y ago
C# these days is GREAT, but F# still has features that C# doesn't like unions and much more powerful (and ergonomic) pattern matching. And line for line, F# is more effective at getting things done (and i would argue with less bugs)

More ›