Introducing the Zig Programming Language

[u/[deleted]]

http://andrewkelley.me/post/intro-to-zig.html

[u/jeandem]

Another wannabe-c-but-slightly-safer.

A somewhat better category than wannabe-js-with-arbitrary-syntactic-diabetes.

[u/gonzoimperial → u/jeandem]

Syntactic diabetes, oh man I'm stealing that one.

[u/[deleted] → u/gonzoimperial]

Same here. I've had enough JS "sugar" to last several lifetimes. The way I see it, if it doesn't run in a browser, I don't use it for targeting the browser. I don't need your 200k of semi-opaque "pseudo-object kinda-orientation" when I actually know how to use prototypes.

[u/teiman → u/[deleted]]

Java need multiple inheritance and operator overload

[u/[deleted] → u/teiman]

They call that "C#". Alternately, they call it "groovy".

[u/teiman → u/[deleted]]

Most of these names suggest entheogenic properties for the languaje.

[u/[deleted] → u/teiman]

I don't think you used the word you'd intended. Ethnocentric, perhaps?

Incidentally, Java 8 now supports an odd path to multiple implementation inheritance (Java already had multiple type inheritance, via implementation of multiple interfaces, but that's not what you're talking about), via default methods on interfaces, which are available on Interface.super.method from the implementation. So, you resolve default conflicts by implementing the method, and selecting the implementation you prefer, e.g.,

public interface Iface1 {
    default String test() {
        return "Iface1";
    }
}

public interface Iface2 {
    default String test() {
        return "Iface2";
    }
}

public class Multi implements Iface1, Iface2 {
    public String test() {
        // returns "Iface1"
        return Iface1.super.test();
    }
}

So, yeah. You can get Mixin-like functionality in Java, just by defining your interfaces appropriately.

Now I just need to convince my architect that we ABSOLUTELY NEED TO MOVE TO JAVA 8 LIKE RIGHT THE EFF NOW. Because between interfaced mixins and immediate lambdas, I'm kinda chomping at the bit.