![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
I’ve been using Jooq to build my queries (and run them). Beats the hell out of writing prepared statements in strings.
Not sure what power I’m missing though, I’ve been able to do everything via Jooq that I want to do.
I’ve been using Jooq to build my queries (and run them). Beats the hell out of writing prepared statements in strings.
Not sure what power I’m missing though, I’ve been able to do everything via Jooq that I want to do.
Everyone loves the idea of scraping, no one likes maintaining scrapers that break once a week because the CSS or HTML changed.
Is it just me or is the article super misleading? None of the roles are for generative AI for making movies. It looks like the roles are for either research or generic product personalization stuff, none of which is necessarily generative AI. I’m not quite sure why they juxtaposed those AI roles with the ongoing strikes in Hollywood, because they have nothing to do with each other.
Quite frankly, I think the current crop of AI products have yet to take away from the real creative process.
That’s really cool! What country do you live in if you don’t mind me asking?
Not an answer, but same. I’ve been using my cast iron as a pizza stone and I’ve never managed the same results. One of the first thing I do when I get a yard is get a pizza oven, but that may be a bit down the road.
Imagine getting paid to post soyjak memes on Reddit lmao
The model works when you have high effort content (YT, Insta, TikTok, Yelp). The bar to get started is high, so the idea of a payout gets the ball rolling for some people. Contributing to Reddit (and Lemmy for that matter) probably doesn’t fit that bill.
I’ve posted about this before and I think a lot of people disagree, but some centralization is good. There has to be a no-thought option for when people want to join Lemmy. After they learn more about federation, they can move on to another instance.
The reason why kbin grew so fast is because for a lot of people, Kbin = kbin.social (See how “kbin” links to kbin.social on: list of alternatives on Reddit)
I believe this also explains Beehaw’s growth despite their onerous rules. When someone recommends Beehaw, they don’t need to think about which instance of Beehaw they want to join, they just go to Beehaw.
A lot of people are dogmatic about federation, but I quite frankly think that if you are going to die on the hill, don’t complain when you die.
Welcome to human nature.
It’s easy to look at Reddit or any other communities and pin the blame all the bad things on mods, admins, or whoever in charge. However, the truth is, anyone who gets in any position of power will make decisions that may not benefit the larger whole or reflect the community at large. Lemmy will deal with this, just as Reddit dealt with it (and succeeded in spite of it).
I think two communities can live side-by-side and even develop their own culture. With federation, someone subscribed to both essentially has no downside right? I think forcing merges would cause some issues (like, who moderates?).
The point about a binary protocol is interesting, because it would inherently solve the injection issue.
However, constructing an ad-hoc query becomes tedious, as you’re now dealing with bytes and text together. Doing so in a terminal can be pretty tedious, and most people would require a tool to do so. Compare this against SQL, where you can easily build a query in your terminal. I think the tradeoff is similar to protobuf vs json.
You could do a text representation (like textproto), but guess what? Now injection is an issue again.
Another thing would be the complexity of client libraries. With SQL client libraries, the library doesn’t need to parse or know SQL - it can send off the prepared statement as-is. With a binary protocol, the client libraries will likely need to include a query builder that builds the byte representation since no developers are going to be concatenating bytes by hand, which makes the bar higher for open-source libraries. This also means that if you add a new query feature to your DB, all client libraries will likely need to be updated to use the feature.
And you’re still going to need to tune and optimize queries for this new DB. That’s just the nature of the beast: scaling is hard especially when you can’t throw money at the problem.
Quite frankly, it’s a lot of hard tradeoffs to not need to use prepared statements or query builders. Injection is still is an issue for SQL today, but it’s been “solved” as much as it possibly can.