battle of my life. several times i’ve had to update my agent instructions to prefer modern and usually better syntax to the old way of doing things. largely it’s worked well for me. i find that making the agents read release notes, and some official blog posts, helps them maintain a healthy and reasonably up-to-date instructions on writing go.
not in this case though. as explained elsewhere, the artist is a dying career choice in ireland owing to economic reasons. no artist == drub society therefore the incompetent government intervenes the only way incompetence approves: free money. making the state function is much harder, and that’s not what these politicians signed up for. reducing electricity bill by 50% is a herculean task so how about jacking up taxes in one place and giving it back as free money in another? this is the modus operandi of the irish government.
the irish government is adept at misplaced priorities, (very) short-term thinking, pursuers of feel-good vibes, basically everything besides running a state. incompetence here has bred the need for more and varied welfare programs just so we can have a variety of careers that cater to the needs of life. of course, necessity of the arts is undisputed. but can the artist make a career here when the money you make from a show, including tips, can’t pay your utility bills? when your income can’t afford you decent accommodation?
worked well for a bit. but then the program became popular and that’s when it hit the curb. terrible loss, imo. it was a brilliant idea to encourage open source work with a token reward. it relied heavily on good intentions, which quickly disappeared with the popularity.
There is no limit to how low someone will stoop to get even a tiny token for free. I remember a local community fun event from a couple of years ago, which was set up by the library to encourage kids to read. They would count up these reading tokens at the end of it and give some tiny $2 teddy bear to the winners, and of course a bunch of adults swooped in, gamed the system, and all the toys went to them. People are totally shameless assholes when even an insignificant free prize is on the line.
It’s still ongoing. The difference is they now no longer offer t-shirts (at one point they planted trees instead, unsure if that still happens), and projects must opt-in.
> Swag - Get an exclusive Hacktoberfest T-Shirt, but its only for ‘Super Contributors’ who contribute 6 accepted PR/MRs to a worthy repository. (T&Cs Apply | Valid only for the first 10,000 contributors completing 6 PR/MR)
spain isn’t a great example here. it has some of the most racist fans football has ever seen and yet there’s no action. only italy probably compares. if there was a government agency going after black and brown people (ie non-white) i wouldn’t bet on the spanish population to come to their rescue. lamine yamal, a young footballer of moroccan descent hasn’t been spared the vitriol of the spanish hooligans even though he was top 3 best player at the recent euro (where he helped spain to victory).
point being, given that ice is going after non-whites and is getting by, a spanish ice will get by too, with probably more ease.
I've read multiple comparisons between US groups like Patriot Front and the Proud Boys and hooliganism in terms of the culture and demographics. Similar backgrounds, similar attitudes, similar behaviors (get smashed, go start fights). It's just more overtly political here rather than being organized around a sports fandom.
Sad as it is, I think Spain only barely makes it into the top 10 on the UEFA racism ranking. Serbia, Hungary and Israel are probably the top contenders, with Albania and Poland completing the top 5.
I'm not sure that's even in the same class of issues as what's happening in the US and frankly, a bit surprising to hear. Have you seen/been with ultras in the Nordics? Even been to derbies played in Copa Libertadores? Both of those I'd immediately rank as way more violent than what we see here in Spain.
the problem i see here is that we end up treating the background job/task processor as part of the production system (e.g. the server that responds to requests, in the case of a web application) instead of a separate standalone thing. rails doesn’t make this distinction clear enough. it’s okay to back your tasks processor with a pg database (e.g. river[0]) but, as you indirectly pointed out, it shouldn’t be the same as the production database. this is why redis was preferred anyways: it was a lightweight database for the task processor to store state, etc. there’s still great arguments in favor of this setup. from what i’ve seen so far, solidqueue doesn’t make this separation.
It does not scale forever, and as you grow in throughput and job table size you will probably need to do some tuning to keep things running smoothly. But after the amount of time I've spent in my career tracking down those numerous distributed systems issues arising from a non-transactional queue, I've come to believe this model is the right starting point for the vast majority of applications. That's especially true given how high the performance ceiling is on newer / more modern job queues and hardware relative to where things were 10+ years ago.
If you are lucky enough to grow into the range of many thousands of jobs per second then you can start thinking about putting in all that extra work to build a robust multi-datastore queueing system, or even just move specific high-volume jobs into a dedicated system. Most apps will never hit this point, but if you do you'll have deferred a ton of complexity and pain until it's truly justified.
Frequently you have to couple the transactional state of the queue db and the app db, colocating them is the simplest way to achieve that without resorting to distributed transactions or patterns that involve orchestrated compensation actions.
that’s setting yourself up for trouble, imo. intermediate states solve this problem, and economically. for mature production system see temporal[0]. their magic sauce is good intermediate states.
i’m not associated with temporal, nor does the link above have any referrer nonsense in there. i don’t profit from referring to it here. in fact it may well be a household name in the hn community. that out of the way, it’s not wrong to point to a proper resource that can explain and demonstrate my argument better than a couple of words could. temporal is open source[0] so maybe a github link would have been more palatable?
solid_queue by default prefers you use a different db than app db, and will generate that out of the box (also by default with sqlite3, which, separate discussion) but makes it possible, and fairly smooth, to configure to use the same db.
Personally, I prefer the same db unless I were at a traffic scale where splitting them is necessary for load.
One advantage of same db is you can use db transaction control over enqueing jobs and app logic too, when they are dependent. But that's not the main advantage to me, I don't actually need that. I just prefer the simplicity, and as someone else said above, prefer not having to reconcile app db state with queue state if they are separate and only ONE goes down. Fewer moving parts are better in the apps I work on which are relatively small-scale, often "enterprise", etc.
I don't disagree with that call out. However, we've been through these discussions many times over the years. The solid queue of yesteryear was delayed_job which was originally created by Shopify's CEO.
Shopify however grew (as many others) and we saw a host of blog posts and talks about moving away from DB queues to Redis, RabbitMQ, Kafka etc. We saw posts about moving from Resque to SideKiq etc. All this to day storing a task queue in the db has always been the naive approach. Engineers absolutely shouldn't be shocked that approach isn't viable at higher workloads.
It's not like I'll get a choice between the task database going down and not going down. If my task database goes down, I'm either losing jobs or duplicating jobs, and I have to pick which one I want. Whether the downtime is at the same time as the production database or not is irrelevant.
In fact, I'd rather it did happen at the same time as production, so I don't have to reconcile a bunch of data on top of the tasks.
But even for the logical databases, if I want to revert to an earlier state of the database, why wouldn't I want the tasks as well? If I have a bunch of update tasks in flight at that point, wouldn't I want them to actually run? They are a part of the overall state of the system.
unfortunately this preamble doesn’t add the weight you assume it should. what has being italian got to do with having an opinion on this? this and all the other “italian here” takes below. fwiw unless eastdakota is being intentionally malicious, he, with the cloudflare legal team, understands the situation and its implications for cloudflare better than any random italian.
Cloudflare is talking about Italian law and Italian policy and making comments about his actions they will take in Italy with Italian users specifically.
“Italian here” as in “I am not a random person with no skin in the game / I live in the country and presumably am more well informed on the policy he is talking about.
If there was a post about a law in nyc, I think it would be helpful to hear takes from New Yorkers.
patiently waiting for grokipedia’s article on grokipedia. it seems to not be available at the moment. i’m interested from a philosophical perspective: on the completeness of self-description. for example, here’s wikipedia on wikipedia[0]
the pursuit of truth doesn’t work by keeping so-called falsehoods up while a debate rages on about their veracity. especially given that there’s no indication on wikipedia of contested facts. i may not be involved in the debate but i’d love some indication and perhaps a hyperlink to where the debate is happening.
the proper discussion you want will never happen. it’s an exercise in persuasion ie trying to move people from one entrenched position to another, and there’s nothing more impossible than that. the only way out is to offer competition, and that’s what grokipedia seems to be doing. check the history of christianity, heresy, reformation. when the catholic church set itself up as the object to be won over persuasively it successfully stifled doctrinal progress. until the intolerants exited.
> i may not be involved in the debate but i’d love some indication and perhaps a hyperlink to where the debate is happening.
Are you familiar with Wikipedia at all? Here, for anyone who is unfamiliar, let's take a look at an example page: https://en.wikipedia.org/wiki/Apartheid - this is guaranteed to have controversial ongoing discussions given the political climate.
Note how at the top of the page right now there are two large boxes discussing ongoing changes to the article - one indicating that it is considered too long, and another indicating that some of the content is being split into a separate draft [0] page. Both of these boxes include links to the relevant pages and policies.
The first box, indicating that the article is too long and drifting off topic, includes a direct link to the Talk page [1]. Note that this page is also linked at the top of the article, and that goes for every single article on wikipedia.
That talk page is where the proper discussion that I want happens - out in the open. Note that you can even reply to talking points without needing an account. Note that replies and criticisms are reproduced and readable directly on the page.
This is what open collaboration and truth seeking looks like. "Grokipedia" requires you to create an account and funnel a suggested correction into an black box. It's the equivalent of a suggestions box in an HR office. On wikipedia, the discussion is out in the open, while the grok version just says "Fact checked by Grok" at the top, like we're supposed to blindly trust that.
Which of these is modeling open collaboration, and which of these is just deferring to priest grok, again? The grok page gives no indication that alternative interpretations exist, they don't show any indication that sections are being criticized as inaccurate. Comparing Wikipedia to the catholic church like this is divorced from reality, doubly so in comparison to this grok project.
> especially given that there’s no indication on wikipedia of contested facts
Have you ever been to a Wikipedia Talk Page? Basically every page you can find will have some people arguing about what should be placed on the page on the Talk page.
