Semantic satiation. Or whatever it's called, i think ive officially lost it after reading this

Is "main" a valid Java identifier?

package main;

public class main {

    static main main;
    String Main;

    main(String main) {
        Main = main;
    }

    main(main main) {
        System.out.println(main.Main);
    }

    main main(main main) {
        return new main(main);
    }

    public static void main(main...Main) {
        main:
        for (main main : Main) {
            main = (main instanceof Main) ? new main(main): main.main(main);
            break main;
        }
    }

    public static void main(String[] args) {
        main = new main("main");
        main.main(main, main);
        main = main.new Main(main) {
            main main(main main) {
                return ((Main)main).main();
            }
        };
        main.main(main);
        main.main(main,main);
    }

    abstract class Main extends main {
        Main(main main) {
            super("main");
        }

        main main() {
            main.Main = "Main";
            return main;
        }
    }
}

UwUID

I can see how this may be useful. My understanding is that this is go lang and the person created a wrapper type UUID and this function takes the go standard library uuid.UUID and returns the wrapped UUID.

The wrapped UUID could be useful as you can then define methods for it like toInt() or something to make it implement some ID interface you have set up. It's a common pattern in go to create a thin wrapper around an imported type so you can implement all the methods required for some interface you defined. It does make naming those thin wrappers hard because what are you supposed to name the struct that just contains a uuid?

Where did i put that Spiderman x3 pointing meme?

UwUIDs

New Dutch programming language just dropped.

When you get a new boss at Twitter who ranks people by lines of code written

I've read so many tutorials like this. func Func Myfunc()

If you write textbooks like this you and your family should be boiled in sewage.

Why I love the Into trait in rust

If this was C:

#define uuID func
#define uuiD return

Plot twist: it returns the bios serial.

Not exactly the same, but this reminded me of the MuffinMail.MuffinHash.MuffinHash talk: https://www.youtube.com/watch?v=o9pEzgHorH0

i've now read UUID so many times i'm starting to think it's some kind of sex disease

The feeling you get when searching your codebase for references to your "uid" variable but this cheeky boy keeps popping up.

https://makimo.com/blog/scientific-perspective-on-naming-in-programming/

Shouldnt it be return UUID { uuid: uuid.uuid } ?

I think it would make more sense AND more uuid per UUID

My coworkers also introduce needless additions to the call stack