Otterkit COBOL, a new free and open source COBOL compiler for .NET

• otterkit

  24 5 3.2 C

  A free and open source Standard COBOL compiler for 64-bit environments

  

• ikvm

  15 724 9.4 C#

  Discontinued A Java Virtual Machine and Bytecode-to-IL Converter for .NET [Moved to: https://github.com/ikvmnet/ikvm] (by ikvm-revived)

  

This reminded me of the IKVM project: https://github.com/ikvm-revived/ikvm

This is a converter that allows Java bytecode to run on the .NET Framework.

It allows horrific, unnatural things such as a C# class that is a derived type from a Java class!

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• awt2048_csharp

  1 0 10.0 C#

  C# port of awt2048, using the Visual J# standard library

Seeing code like that reminds me a lot of the J# days, when you basically had a Java 1.1 standard library implemented on top of .NET. I played with it a bit a few years back, even ported an AWT to it (imagine using AWT in C#): https://github.com/zdimension/awt2048_csharp/blob/master/Pro...

• carbon-lang

  174 32,188 9.8 C++

  Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)

  

>Google invented yet another programming language, [...] just to gain access to features that are probably coming down the pipe in C++ in due time anyway.

That's the opposite of what Google perceives. There is no timetable for a future C++23 or even a later version that will make their experiments with Carbon redundant.

Are you already familiar with the Chandler Carruth blog post?

https://github.com/carbon-language/carbon-lang/blob/trunk/do...

That post also has a link to the Titus Winters pdf explaining some of the ABI breakage that the committee does not currently want to prioritize.

I don't think Carbon will spur industry-wide usage outside of Google's internal work but their rationale for Carbon is in response to the current committee's position of prioritizing ABI backward compatibility over performance improvements.

Suggest a related project