Get off your high horse. Not everybody studied to write prose, not everybody was born American to begin with. If LLMs helps programmers get heard - good. That's probably the best usage for them anyway.

In fact I employed the same idea for the slide stack site I use for teaching. Not exactly "URL is an app" but "URL is a slide"

https://okaleniuk.codeberg.page/blackboard/_1.html?sequence=...

The same consideration applies. No backend, no storage, also no user data collection, no authorization, no hurdles in general. Everyone can use it.

Or... add some noise. Just align the last bit of every pixel channel with a random bit sequence - and Bob's your uncle.

https://www.linkedin.com/posts/okaleniuk_isosurface-mesh-stl...

The lattice configuration comes from a conventional triangle mesh, so you can prepare it with any STL editor of your choice, and the lattice shape comes from a precalculated Fourier polynomial in barycentric coordinates.

https://okaleniuk.codeberg.page/blackboard/barycentric_fouri...

And if you play by the spirit and not by the rules, you're fucked. Because, with masters, it takes about a year to get to the first publishable result, and about a year to publish it in a respected journal. And that's the happy pass. You might get an extra rejection, or fall into the back of the publishing queue. This could cost you three or six month easily.

The masters program in our uni is 1.5 years long.

I coauthored 4 papers this Summer. All bona fide: no AI slop, no fake data, all genuine research papers. But the substance of each is barely enough for a paragraph in a paper I would have gladly written instead.

But I have KPIs. And KPIs don't care about quality, quality is unaccountable. So it is in my best interest to publish a lot of "barely science" instead of spending a year or two writing a good paper that will take another year to publish, and by then my contract will end, and I'll have no numbers to show.

I don't have AC at home. Some think I don't install it because I somehow don't get hot in summer or cold at winter. It's the other way around. We, people, have one of the best thermoregulation systems among animals, our whole skin is essentially a huge cooling system. The only way to render it incapable is... stop using it for a prolonged amount of time. It's use it or lose it all over again.

If you don't believe me, read what ultra-marathon runners have to say. If a trained athlete can survive Badwater, almost everyone can train themselves to survive a European heatwave.

Sure, some people can't. Some need AC because of cardiovascular conditions. It's fine, let them have it. But some people can't walk because of musculoskeletal conditions, but no one would argue that a wheelchair is a necessity.

Triply periodic minimal surfaces are the golden standard in thermal management, acoustics, and even medical applications. But minimality itself doesn't contribute much to practicality. We use them because they are simply studied better than the non-minimal surfaces.

So I'm studying the non-minimals. They are much more governable, what I link to is a demo of a surface builder with two levels of control. Next, they are conjugatable including conjugations with different period of self (that will be the following paper), they generalize nicely to non-periodic or partially periodic surfaces, and they work in other space configurations. E. g. I'm now playing with bi-periodic curves that cover the 2D space with self-replicating hexagons.

If all that I'm experimenting on today in 2D will turn out well in 3D too, we'll have a whole new direction in implicit modeling.

There is a different take on Lisp in Python - fakelisp. It's literally Lisp in Python, not an interpreter, but a syntax sugar library that allows embedding Lisp snippets into valid Python.

https://codeberg.org/okaleniuk/fakelisp

    from fakelisp import *

    # And now you can start mixing Python and LISP
    X = (BEGIN
        (SET (F) (LAMBDA (X)
            (IF (EQ (X) (1))
                (1)
                (MUL (X) (F (SUB (X) (1)))))))

        (LIST (F (4)) (42)))

    # Back to Python any time
    print "x: ", str(X)

There are no obvious flows in the original design, and there were no endemic wrongdoings in the governance either. It just rotted slowly like any other community does. And nobody in the world knows how to keep communities from becoming toxic. There is simply no recipe. And that's why StackOverflow doesn't serve as a lesson either.

Students are lazy, in a good way, so they are more likely to run things on their own and play with interactive bits if the whole lecture is just one link.