Seems like repopack only packs the repo. How do you apply the refactors back to the project? Is it something that Claude projects does automatically somehow?
The numbers are debatable as usual but they're not taken from thin air
> A 2023 survey conducted by Payroll.org highlighted that 78% of Americans live paycheck to paycheck, a 6% increase from the previous year. In other words, more than three-quarters of Americans struggle to save or invest after paying for their monthly expenses.
> Similarly, a 2023 Forbes Advisor survey revealed that nearly 70% of respondents either identified as living paycheck to paycheck (40%) or—even more concerning—reported that their income doesn’t even cover their standard expenses (29%).
The numbers are debatable as usual but they're not taken from thin air
> A 2023 survey conducted by Payroll.org highlighted that 78% of Americans live paycheck to paycheck, a 6% increase from the previous year. In other words, more than three-quarters of Americans struggle to save or invest after paying for their monthly expenses.
> Similarly, a 2023 Forbes Advisor survey revealed that nearly 70% of respondents either identified as living paycheck to paycheck (40%) or—even more concerning—reported that their income doesn’t even cover their standard expenses (29%).
Many examples abound. Don't be lazy and do a google search. Granted, many of those opinions that create grounds for legal sanction in the EU are disagreeable ones, but that's how freedom of expression as a real right works, it applies to the shit you don't like or want to hear, not just socially condoned opinions.
Multiple EU countries in the Union as well as the statutes of the EU itself condemn and prohibit a wide range of speech under the grounds of offensiveness. This includes hate speech laws with very broadly defined wording, laws against holocaust denial and laws against speech that is offensive to certain identifiable groups. Misinformation laws are also being formulated. However much you might think that many of the above forms of expression are repulsive (I'd likely agree with you on much of that repulsion by the way), such laws can easily be contorted to include all sorts of censorship. Aside from the censorship, free expression really should absolutely also include legally protected free expression in a public context to espouse views that are repulsive and intolerant too.
Not OP of that particular statement, but in Germany you can get imprisoned for denying that holocaust has happened.
However, I would question whether denying historical facts is an opinion. There seem to be fewer cases of people demanding that the holocaust should be resumed. That I would call an opinion. I assume that it would lead to prison if repeated often enough, albeit based on a different law. Still, I am more willing to travel to such country than to a country requesting my passwords at the border. Call it illogical or not, it's my preference.
> However, I would question whether denying historical facts is an opinion.
Historical facs have a tendency to change based on the current political climate. Which is to say, they are always more like opinions.
Although a better example would be insulting a police officer or politician, which can include as bening things as making fun of them on twitter. Granted, this is more a concern for citizens than it is for tourists so I agree with your assessment that the US border controls are a bigger threat to you as a traveller.
Didn't a former Greek finance minister recently get banned from Germany for political reasons? In France it is illegal to deny the holocaust but legal to deny the Armenian genocide.
One noteworthy example of how absurdly politicized these kinds of speech restriction laws can be. Was the mass slaughter of up to 1.5 million Armenian men, women and even little children and babies somehow qualitatively less grotesque? Or perhaps the speech law itself is a muddled, politically oriented idiocy.
I don't read it as _bypassing tests_. They have tested the interpreter (`template type`) when it was first released, and they have _validated_ the new template instance (via `content validator`) and assumed this is enough, because it was enough in the past. None of the steps in the usual process were bypassed, and everything was done by the (their) book.
But it looks to me there's no integration test in the process at all. They're effectively unit testing the interpreter (template type), unit testing (validating) the "code" (template instance), but their testing strategy never actually runs the code on the interpreter (or, executes the template instance against the template type).
You can't bypass the tests if you don't have them? <insert meme here>
They don't even bother to do the most simple smoke test ever of running their software on a vanilla configuration and remind me again because I have trouble understanding what we're exactly trying to argue here.
> Why don't you grow your own food? Why don't you just write your own payment processor?
I find that usually if someone says "why don't X _just_ do Y", they haven't really considered what it takes to _just do Y_. Similarly,
> I know the UI/UX isn't the best, but that could probably be fixed pretty easily
could be expanded into 50 points of why exactly it wouldn't be _pretty easy_ to to "fix IRC UI/UX".
Honestly I don't know what answer OP expected here. If it's easy to set up/maintain Slack alternative based on IRC, with fixed UI/UX and appropriate for _most companies_, they should simply start a Slack competition for half the price and rake the profits, I guess
I don't understand this argument, how is it "remade REST" if you still don't need to implement and maintain an endpoint with exactly the data that clients need? Persisted/whitelisted queries require much less backend effort, and are decidedly different from REST, the only similarity is in having a closed set of possible actions.
Perhaps you're thinking in terms of public APIs where I agree limiting available GraphQL queries makes little sense. But for internal APIs, whitelisting whatever queries current clients need isn't any less convenient
I might be thinking about this the wrong way, but with GraphQL you're writing a query (in the GraphQL syntax) on the frontend which gets whatever data the frontend needs for whatever it's doing, and that query is interpreted by the backend to fetch specific data. But if you're whitelisting specific queries, which has to be done on the backend, what if you just move the queries themselves to the backend, and call them from the frontend by specific names for shorthand? And then from there, what if you refactored it so that each "query" was just a function with an associated endpoint?
You would have a more permissive development environment where all queries are permitted. Then, once the change to FE code and related queries are finalized, you could automatically have the production whitelist updated before the FE is deployed to prod.
> A single tool to replace pip, pip-tools, pipx, poetry, pyenv, twine, virtualenv, and more.