benaadams

Um, wrong topic?

This one is about "Some notes on high speed networking on PCs" - not sure how Apple comes into it?

SQLServer might be in next round https://github.com/TechEmpower/FrameworkBenchmarks/pull/3807

> SF is only available from one vendor, whereas K8S is available almost anywhere.

SF is open source on GitHub and you can run it on-premise or on any cloud, Windows or Linux.

The tooling is probably easier on Azure; but you can also happily run it on AWS; as well as the Service Mesh variant which is sort of "Serverless Clusters" or "Clusterless Clusters", applying the strange naming of "Serverless".

> Also, we need a GUI, of some kind.

Would be .NET Core 3 you'd be waiting for then:

https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-...

If you take substrings of strings; using string.AsSpan() then allows you to work it as a Span<T> and take windows of the string without allocating an new string for the substrings.

Also it means you can now pass readonly arrays (the elements) to things using ReadOnlySpan<T>; so don't have to do defensive copies

There is a dangerous form https://docs.microsoft.com/en-us/dotnet/standard/serializati...

> Binary serialization can be dangerous. Never deserialize data from an untrusted source and never round-trip serialized data to systems not under your control.

The killed it in .NET Core 1.x; but brought it back in .NET Core 2.x due to back compat and interop complaints

> Azure Service Fabric Mesh, which offers the same reliability, mission-critical performance and scale customers get with Service Fabric, but no more overhead of cluster management and patching operations. Service Fabric Mesh supports both Windows and Linux containers allowing you to develop with any programming language and framework of your choice.

> Whether it be modernizing existing workloads or building highly available, cloud native applications with stateful services, Service Fabric Mesh allows you to deploy microservices running in containers [...] It also offers intelligent routing between microservices using Envoy.

Looks to be quite a huge release

> The reason? Their fundamentally unreliable nature. Both solar and wind produce too much energy when societies don’t need it, and not enough when they do.

> Solar and wind thus require that natural gas plants, hydro-electric dams, batteries or some other form of reliable power be ready at a moment’s notice to start churning out electricity when the wind stops blowing and the sun stops shining.

> And unreliability requires solar- and/or wind-heavy places like Germany, California and Denmark to pay neighboring nations or states to take their solar and wind energy when they are producing too much of it.

And you want more correct then you should be using double or decimal - you shouldn't really be expecting that all the calculations for a float are done in double then converted back to float.

Decimal in .NET is 128bit, range (-7.9 x 10^28 to 7.9 x 10^28) / (10^0 to 10^28), 28-29 significant digits

No; but twitter will likely get a better conversion rate if they tell people what it is they are buying and the cost, prior to handing over their payment details

Twitters advertising flow is messed up

Promote Tweet -> Give card details -> Lets see what can do and cost $

Should be

Promote Tweet -> Lets see what can do and cost $ -> Give card details

Kestrel was "more suitable as an Internet-facing server" at 2.0 https://blogs.msdn.microsoft.com/webdev/2017/08/25/asp-net-c...

Section: Kestrel Hardening

System.Data.Odbc? https://www.nuget.org/packages/System.Data.Odbc/

Wouldn't low dose antibiotics be more likely to create antibiotic resistant bacteria than high dose?

The pain every .NET developer has felt from async stack traces is now gone :)

Very different; glucose is metabolized by all cells in the body; fructose only by the liver.

Fructose isn't good for you (or sucrose 50% fructose, high fructose corn syrup 42%-65% fructose etc) https://www.youtube.com/watch?v=dBnniua6-oM

But its sweeter than glucose; and has side-effects like switching of appetite suppression and prolonged exposure does similar damage to the liver as alcohol. Glucose doesn't do that.

0-based offsets

> as long as they pay those workers at least the minimum wage

Do US employeers not have to pay workers the minimum wage?

> It's almost like planned obsolescence. Msybe it was orchestrated.

Since 1995? 23 years seems a long time to wait

> Selling more products for the same amount of ad cost should allow for cheaper products.

If the ad companies are making less money; it doesn't suggest that the ad cost is going up

Also says

> The .NET runtime supports a wide variety of high performance applications. As such, performance is a key design element for every change.

https://github.com/dotnet/coreclr/blob/master/Documentation/...

Pinch of salt with all benchmarks, but "The Computer Language Benchmarks Game"?

http://benchmarksgame.alioth.debian.org/u64q/csharp.html

.NET does better in most of them, but falls down vs Java on Regex and k-nucleotide

The JVM jit _has_ to do a lot more for performance.

Lack of value types means greater allocation by default - so it needs escape analysis to avoid it.

Type erasure for generic types means speculative optimisation and deoptimisation steps for types.

etc

Doesn't mean the .NET Jit can't improve in these areas (e.g. now its doing devirtualization for .NET Core 2.1, and escape analysis would be great) - but it does start in a better place.

Span<T> is safer than ArraySegement<T> as it only allows access to a window of array, rather than full array with a "request" to only look at offset->length

Span<T> is better than Array as it also comes with ReaOnlySpan<T> for a view with readonly array elements; whereas Array is always read/write.

Also Alea GPU [1]

[1] http://www.aleagpu.com/release/3_0_4/doc/introduction.html

And it expired 8 - 10 years ago

> Microsoft's obligations under the settlement, as originally drafted, expired on November 12, 2007. However, Microsoft later "agreed to consent to a two-year extension of part of the Final Judgments" dealing with communications protocol licensing.

built in 4G LTE2/Gigabit LTE and week long battery life

> Performance: In this update we continued to improve performance. Solution load times for large C# and Visual Basic projects is nearly cut by half. The time to switch between debug and release is significantly reduced. It is faster to add, remove, and rename files and folders in .NET Core projects. Project templates should now unfold much faster than before. In the most exceptional cases, you can see up to a 40x improvement in unfold time.

tl;dr much faster