You can write selects with many joins, as long they are regular and either add a column or reduce the result set. You have to write the joins explicitly though. Just shoving all of the restrictions into the where clause will definitely confuse everybody.

Well, you can still have the up-to-date plugin, you just have to pay for it now.

Since working with SQLAlchemy a lot (specifically it’s SQL compiler, not it’s ORM), I don’t want to work with SQL any other way. I want to have the possibility to extract column definitions into named variables, reuse queries as columns in other queries, etc. I don’t want to concatenate SQL strings ever again.

Having a DSL or even a full language which compiles to SQL is clearly the superior way to work with SQL.

I’m wondering if a field with more detailed information would be helpful for the users. Moderators might want to clarify or explain in more detail the function or intention behind a tag. This doesn’t seem to be considered in the RFC.

Depends on how large your Python projects are. If you have a million lines of Python code, navigating quickly and directed is invaluable.

I used plain vim before for Python projects, but these never grew above 50k lines of code.

I never got so far, but had a system built which some parts of what you described. It was incredibly relaxing to develop with it. Our take as a team was: boring is better, we don’t want to be paged on weekends.

It teaches you to think about data in a different way. Even if you never will use it in your products, the mental facilities you have to build for it will definitely benefit you.

Completely agree. I really love SQL, but I hate it’s syntactic limitations. SQLAlchemy was my band-aid with an after-burner to make it bearable (and maintainable).

Python development without PyCharm (or IntelliJ) and the IdeaVim plugin is unbearable. List usages is a game changer. Don’t care much for anything else.

You could be onto something. On of my first language was “dBase” (early 90s) which, through it’s style, enabled you to build complex user interfaces with data storage very quickly. I only built small things with it at the time, but it influenced my desire for some better solutions than we have to today.

The way I perceive PRQL is somewhat like SQLAlchemy-Core (the SQL expression layer, not the ORM). Almost a 1:1 mapping to SQL but softening the rough edges in SQL when constructing more complex queries dynamically, in particular: no function calls, no real variables, only string concatenation. While SQLAlchemy-Core lets you even extract sub-queries into variables, I don’t know about how powerful PRQL is in this regard.

From what I see from the docs I’m rather hopeful though.

First I thought you were writing incoherently, but now I understand your point.

I agree with what you said, that our “art” is most likely just something akin to bird song. Maybe even less or something else entirely.

My point of view: Birds also have a “rebellious phase” where their songs differ from the songs of the general population. They are experimenting with new and unorthodox songs. These go away after they come of age and have to find a mate. My hypothesis (well, I’m no bird) is that there is a lot of emotional impact in these bird songs, whereas in some songs humans produce, much which previously required emotional awareness or emotional connection is now being replaced by templates, methods and formulas to make music. It’s some sort of depersonalization or objectification of the process of making music. This is probably what you meant by “it isn’t art anymore”.

Did I get right, what you were trying to convey?

Are you one? Over the years I’ve gotten quite paranoid on Reddit. Now, with LLMs, it’s even harder to spot them.

I’m not even sure if including a hashcash scheme into the software would actually help, because they are so targeted.

I feel like I’m back in the early 2000s, where it was so bad that “the brightest minds of the generation were spending their time writing spam filters”.

Once federated with Meta, not only “valid Meta users” would join the network, but also bots which would nudge the users, influencing the narrative.

Do you have a link? I’d like to know that sorry too.

It’s not cynicism if the other party has a track record of behaving in an anti-competitive manner. The Fediverse became a competitor once it showed non-negligible growth.

It’s not cynicism, it’s weariness.

I like to think they see the rapid growth as an opportunity to grab some Reddit refugees. I’m not sure they see the Fediverse as a viable threat YET. They could hedge it though and try to snuff it out while they still can.

Their idea is likely to eventually present themselves as the “better part of the network” and make migrating to their servers very easy.

This must be prevented at all costs.

We should bake it into the software (Lemmy, Kbin, Mastodon, etc.) as a first line of defense. If you want to federate, you’d have to fork the server first.