Apart from echoing other comments that this appears to be vaporware, it's also a little odd to use the sharp suffix on a language that doesn't target the CLR. I mean obviously Microsoft doesn't own the character, but after 20+ years of C# it definitely comes with some expectations
Related to C#, "M. de Champlain, Ph.D., Chief Architect of the B#" and "B. G. Patrick, Ph.D." are listed. They wrote a C# book: C# 2.0: Practical Guide for Programmers.
Going to de Champlain's website [0], he lists himself as the creator of B#, and his Google Scholar page [1] lists articles and a book about B#. In the articles they say B# is similar to C# and list some examples.
I can't find a copy of the book, though. Brian Patrick also lists the book [2], so I'd think it must be somewhere.
Does this actually exist? Page was updated in 2019, and the SDK is "coming soon". There is supposedly a book, but with no information about how to get it.
Looks to be some sort of vaporware, there is no example code, no links to the book, documentation, or SDK, or if it is proprietary, contact information for licensing or whatever.
I feel like it's supposed to be a joke but I don't get it.
The Twitter is pretty much abandoned, just a few tweets spread from 2010~2016.
Well, you could say also something like “most modern hardware is little-endian, so it would make more sense to go the other way.” For those who don’t know, you know?
It just demonstrates being thoroughly out of touch with the hardware platforms that people are actually using: not a quality to seek out in infrastructure for your embedded-system project.
It is hard to imagine any reader who might consider an embedded project being unaware that all current hardware (excepting rare MIPS variants) is little-endian.
A microcontroller meant for use in a network router might reasonably be big-endian, just because most IP protocols are. That is the only place I can think of where one might deliberately choose it.
