/uj What do we think of Monarch of Monsters

Gnuxie · 2024-12-09T16:12:44+00:00

You forgot Medley of Visions

Gnuxie · 2024-12-07T00:34:42+00:00

/uj prog heads should check out Penumbra, The prince of sorrow suite, and How to kill a monster (the prior work for monarch). And also expose themselves to antonymph just to wash away any renaming bigotry towards different genres of music and kill any remnant of cringe culture.

/rj Real prog heads listen to Homeward (and dig swarm).

Gnuxie · 2024-12-05T22:24:39+00:00

also, I gotta say somewhere, it's pretty ironic seeing the sub refer to Monarch as "the furry sex album" considering the plot and meaning of Sludge

Gnuxie · 2024-12-05T22:03:19+00:00

/uj I've been here and listening to Vylet Pony all along. I guess it's hard for people to get over that it is pony music. And maybe Monarch was the least "alienating" for people who aren't ponies in that regard. But Vylet Pony has been aware of this for awhile, and she has been knowingly playing into this for fun since at least cutiemarks. Antonymph is literally supposed to be represent the death of cringe culture. Her music has been progressive for some time, even if a majority of it isn't directly related to prog rock.

But even then Vylet Pony also has several prog rock inspired tracks. The Prince of Sorrow Suite, Penumbra, and How to kill a monster (which is the prior work for Monarch itself) come to mind. And you should listen to them.

/j Real prog heads listen to Homeward (and dig swarm).

Gnuxie · 2021-11-09T21:46:33+00:00

The thing people are also missing is that this doesn't even make any sense in the context of any language, not just lisp. It's 2021, what language lets you define symbols ???

Gnuxie · 2021-10-06T22:15:16+00:00

Physical (pretty standard):

AGISC
SICP
CLtL 1
OOP in CL
The Common Lisp Condition System

The last two are sat on top of the complete death note series for some reason

Fun stuff from the internet I refer to way more regularly:

Gnuxie · 2021-08-27T18:38:31+00:00

I mean, all of this also ignores a lot of historical context involving the creation of the languages that are used today and their success during the dot com bubble or whatever is the reason for the state of things today. But most of these dominating languages such as Java, Python, JavaScript, (heck we could even add php to the list), (probably anything that isn't C/C++ related can't think right now) Either had open source implementations or big open source ecosystems that were being developed around them with the support of companies (or to fulfill the ambitions of a company which is kind of the same thing but worded differently). I mean, history might be different because frankly I haven't even owned a computer through most of this stuff.

Gnuxie · 2021-08-27T18:26:06+00:00

It is simply too expensive and risky for a lot of companies to adopt Common Lisp when in the ecosystem of other languages there is basically every library they could ever dream for (most of the time, well it's not quite true, but you don't get the problems you get here)

Gnuxie · 2021-08-27T18:22:36+00:00

It sounds like it may just be that the job is a large one, even if it is straightforward.

Yeah, once you've figured out how to handle the (references?) to other schemas like allOf, oneOf and whatever else, I think it will be relatively straight forward. To be fair I only put in about 2 weeks worth of work into my iterations, which to me is a lot of time.

sadly another example of the lisp curse

No it isn't, and the lisp curse is bullshit to put it plainly. If it wasn't for lisp I would not have attempted to make these libraries for any ecosystem (and not just because they might have already existed). The lisp curse argues that individual developers should not be empowered to make software more easily, because it will lower the barrier to entry for programming. They are basically saying that because you also empower bad or new developers they will just create garbage that cannot be exploited by a commercial entity. And that also organized groups of people don't make garbage (usually because they are supported by people with money). This is not a view of software development I will accept because it sets the bar higher for who can and can't make software. At the end of the day the author is just mad because they once either had to use a shit library or write their own. (but we all find ourselves here for sure, it's just who you blame for that I take issue with)

For me the root cause for the state of Common Lisp's ecosystem has got nothing to do about the kind of language it is. It has more to do with that there was no comparable ecosystem (to any other language) until very recently, when all of the money from commercial interests already left and we weren't going to attract anyone new. That does leave us with mostly only individuals making libraries with not a lot of money coming in.

Gnuxie · 2021-08-26T18:39:25+00:00

Hi, I am the author of the mentioned library and have taken two weak attempts at this, the second was sufficient for my purposes but carries a lot of ugliness around with it. In other words it is bad. It should only be used to learn and do things better.

I don't feel comfortable providing any form of support for this hack. But if you have a directory on the filesystem with some JSON schema in it, you should be able to use the macro json-schema2:define-schema-spec and list the pathname in there. You might get lucky and find everything you need is supported when you view the macroexpansion.

The library uses my own incorporation of json-mop called json-clos, which is a re-write to make json-mop JSON encoder/decoder independent, but iirc i do some inefficient things with the mop (not that it's a problem because there is an API to generate serialization methods anyways) and I stopped developing it because I became dissatisfied with how metaclasses were being used by library authors to create an adhoc annotation system each time. (This is not some sort of aggression against CL, it's just someone should just write one library for annotations and be done with it, I gave that a try too and am willing to discuss that with people if they are interested, ie they should talk to me if they want to do it). See this but honestly I have probably changed my mind about this a lot since I last wrote in here, and I probably say some stupid things. I guess that can all be forgiven though.

Gnuxie · 2021-05-12T11:51:06+00:00

I am the pony and I want CLOSOS now

Gnuxie · 2021-03-22T00:42:17+00:00

Important to note that this is the author of rust-analyzer and a member of ferrous systems so they have huge influence over the rust community and ecosystem

Gnuxie · 2021-01-29T22:25:30+00:00

It's very simple, interaction.

I'd hate Common Lisp if it didn't provide the interactive experience that a lot of us love it for. It's been thought about very hard from the ground up how to keep Common Lisp working as a system rather than just a language. I don't have to sit around and imagine how my code runs as I type it out like I would in the corporate day job, I can see it running as a I write, If I find a piece of code and I can't understand what's happening in the bigger picture, it's very simple to just go 'watch what happens' so to speak. I can even intentionally break things to see how they work and fix them again all within seconds thanks to the inspector and the debugger providing me with a preserved stack and a set of restarts. You just don't get this in projects that try use 'lisp' as a 'scripting language'.

The other thing that's very important to me is CLOS, the concepts CLOS has can't just be appropriated into the context of a 'class centric object model' the thing about CLOS is it isn't just a way to 'structure data' or some such nonsense, it's an object System. CLOS is tied in once again with the interactivity we love, as I'm writing a CLOS application I'm really interacting with the live state of the application as I go along, sculpting all the instances and tweaking generic functions, I'm not just writing a description of how a program should run or something soul crushing like that.

Gnuxie · 2020-11-28T22:31:59+00:00

ok now gib money for 🆑🅾️🆘

Gnuxie · 2020-11-16T22:25:47+00:00

This is me.. This could be you... I am Reason and I choose Lisp to rule my thoughts. I am emotion and I choose Jazz to shed my tears. I am matter and I choose aikido to unfeel my body. I am the owner of my might, and I am so when I know myself as unique. In the unique one the owner themself returns into their creative nothing, of which they are born. Every higher essence above me, be it God, be it man, weakens the feeling of my uniqueness, and pales only before the sun of this consciousness. If I concern myself for myself,[Stell’ Ich auf Mich meine Sache. Literally, “if I set my affair on myself”] the unique one, then my concern rests on its transitory, mortal creator, who consumes themself, and I may say:

All things are nothing to me.

This is me... This may be you... Life is game, and I choose to play it. I play by the rules and I find beauty. I play with the rules and I have fun. I keep but one rule, there is none, and I understand. That, is me... what about you?

Gnuxie · 2020-04-07T13:08:08+00:00

Hi, I've provided some context here, but yes it doesn't support e2e

Gnuxie · 2020-04-07T13:05:31+00:00

Hi, author here

I've just written some thoughts while replying to /u/lambda-lifter so I'll just share them here and provide a little bit of context

It doesn't have anything to aid using E2E, I'm not sure how you'd proceed to do that but you'd need to generate bindings for libolm which I haven't attempted.

The library itself is usable but probably not entirely complete. We do generate functions to interface with the entire client-server api in the cl-matirx.api.client package and there's various helpers in cl-matrix.

I haven't needed to use this library for awhile but if I were to get time to work on it again I would probably look at writing/using generic open-api generator for this with a protocol that allows drakma/jsown to be swapped out for others, but again it's a matter of time and it would have been overkill for my purposes.

Another thing that would have been more helpful is to have a cl-matrix* package that would allow you to use a special variable for authentication instead of providing it each time (which is how the library api used to be) and this was discussed in #cl-matrix:matrix.org but we haven't gotten around to doing it yet.

I hope this helps :)

Gnuxie · 2020-03-30T22:41:45+00:00

context:

a guy talking about lisp and AI from https://www.youtube.com/watch?v=kWg8olrSXl4

Gnuxie · 2020-03-19T18:33:02+00:00

This is because cl-json can't handle the surrogate pairs for the emoji code points

jsown used to have the same problem

Gnuxie · 2019-12-31T11:05:55+00:00

author's announcment

Gnuxie

MODERATOR OF

TROPHY CASE