• 0 Posts
  • 1.56K Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle









  • There’s definitely nothing about humans that is irreproducible - but the machines aren’t even close yet. You clearly didn’t read the article.

    The entire point here was that the poetry written by LLMs is valid, shallow and has appeal only to the uninformed.

    Article:

    In my view, the results of the study are less testaments to the “quality” of machine poetry than to the wider difficulty of giving life to poetry. It takes reading and rereading to experience what literary critic Derek Attridge has called the “event” of literature, where “new possibilities of meaning and feeling” open within us. In the most significant kinds of literary experiences, “we feel pulled along by the work as we push ourselves through it”.

    [ … ]

    When readers say they prefer AI poetry, then, they would seem to be registering their frustration when faced with writing that does not yield to their attention. If we do not know how to begin with poems, we end up relying on conventional “poetic” signs to make determinations about quality and preference.

    This is also true of AI art.

    The pattern matching machines will give us more of the same: glossy and regurgitated.

    You will not find a machine that will output excellent work that when found 20 years later will become a sensation. They produce gold painted dross.

    This is another condemnation of art and cultural education in the West.


  • I’ve been an android developer for a decade at this point, I’m aware of how app deep links work.

    The comparison is not “what LOE is call linking from scratch” but rather “how does call linking meshing into existing production codebases across all platforms compare in LOE to 3 buttons?” And the answer is self evidently more.

    You’re minimizing the amount of effort and we’re comparing it to buttons. Adding “a few buttons” is very different than setting up 3 platforms to all use a new protocol (calls from links will require new handling - previously all calls were just based on authenticated users being allowed into webrtc calls based on their tokens. Now you have to have a new handler which joins a call with the token in the URL - that can’t be handled identically). Then we get into the Android app, much of which is still in Java, which uses multi-activity-srchitrcgure meaning you’ve gotta pass data through each layer manually, rewriting each of these activities to accept the new deep link and route to the right end.

    And then you’ve got to be sure it all coordinates across iOS, Android and your backend.

    It’s not hard but it’s not “a few buttons”. It’s probably 2 weeks of work for skilled and competent engineers, 1 per platform.

    Do you actually have any experience in Mobile dev? You sound like a fresh outta college junior eng - cocky and confident that everyone else is wrong, making it harder than it needs to be etc.

    Just like that cocky junior eng you’re too unaware of what you don’t know to realize you’re wrong. Wade through the grass a few times and you’ll realize the flowery meadow is full of snakes.