I haven't tried to the web app part but I've tried Toasty. The API seemed to be a little simpler and nicer to use than SeaORM for me. Here are a few things I liked in Toasty:
- In SQLite UUIDs are default stored as compact blobs instead of inefficient varchar/text (SeaORM)
- Timestamps were easier via jiff instead of chrono (SeaORM)
- Model structs use the actual name of the $table instead of being named like $tablemodule.(Model|ActiveModel) (SeaORM) they are just $Table. This makes writing libraries a little simpler that need to use entity struct's from two separate modules/crates otherwise you get a name collision on Model/ActiveModel and need to do alias imports.
- There's an API to fetch related data to a query similar to Django ORM. IIRC this is missing from SeaORM
- The query expression language doesn't cover as much of SQL as SeaORM but seems to be enough for most web apps.
- I didn't like how the migration system works. I would skip that part of the library
Do you have feedback on what you don’t like re: the migration system? It is inspired by drizzle. Is it something we missed or just not a fan of that style entirely?
It's a distinct blue/red state issue. Blue states go out of their way to register as many of their residents as possible and allow same day registration.
The red states, Republicans use it as a tool to reduce participation of urban, non-white voters and reduce overall participation. They don't consider systematic, passive voter suppression techniques to be voter fraud.
Outside of the US spectrum, there are countries that require all citizens to vote or face fines (Peru for example). I find this interesting, because it's so out of sample compared to the typical political fights within the US about voter registration.
> Outside of the US spectrum, there are countries that require all citizens to vote or face fines (Peru for example).
Right, but even for Peruvians, you show up at the both, make your vote and leave, that's it. No thresholds for registering or other stuff, just you and your ID making a vote, even when outside the country. It again makes the US system seem intentionally designed to make less people vote.
This is also seen in the actual voting process itself. Stories about Americans having to stand in the scorching sun for hours are just absolutely mind-boggling to me: you should expect everyone to vote, and provide enough capacity for everyone to cast a vote during their daily commute or grocery trip without a significant delay!
If a bunch of politicians can make voting quasi-impossible for certain groups of people by meddling with their polling stations, then you don't have a functioning democracy.
Australia has both compulsory voting, like Peru, and a separate electoral roll that you have to (and must) apply to get on, like the US. It's not a US thing, it's a common law anglosphere thing.
A website to register doesn't prove it's easy. Texas has one of those too, but obviously it's not proof of it being easy since we're here discussing it.
But I'll give you the benefit of the doubt and assume it's actually easy in Australia. That still doesn't really explain why it's necessary.
It's necessary because we have elections with geographically based electorates, so your address determines which ballot you should receive (and so they know how to fairly resize the electorates). So you need to tell them somehow where you live. Also, the roll of voters has to be printed out many times to use at "check-in" on voting day, so you need to tell them in advance of this printing. They need consistent rolls because after the election they reconcile the various copies after the election to question/fine people who either didn't vote or voted more than once.
For people not on the roll, there is a special secondary method of voting called a declaration vote that allows you e.g. to vote even if you haven't enrolled. But this process wouldn't scale very well - these votes aren't counted for days after as they need to check the details you declared - and is intended as a safety net.
I'm not sure it's strictly red state/blue state. I've live in Massachusetts and Minnesota for a while, where they made it very easy to vote so that tracks.
However, now I live in New York, where they seem to go out of their way to make it difficult. The registration cutoff is several weeks before the election and for at least one election, I found myself wrongfully expunged from the voter roles.
I think it may just be how corrupt the state government is.
Arbitration can be more efficient, but both parties should have an option to choose it, a direct settlement or public court. The average consumer is denied the choice by using these everyday services that have non-negotiable contracts.
Many places have a ‘small claims court’, which is very similar to arbitration. The issue is that class action lawsuits are very profitable for plaintiff lawyers working on contingency, so those are the cases that get brought.
Small claims is great in that in most states lawyers generally aren't allowed so right out the gate you remove the wealth asymmetry issue. The downside is the dollar amount is very small. I'd like to see small claims limits expanded tbh.
They are very profitable when they win, what is the win rate of class action cases. Also what is the win rate of chosen class action cases versus all potential class action cases.
The 'tipping point' for class actions is usually the class certification, not a final judgement by the court. Class actions are absurdly expensive for defendants, largely due to the scope of discovery, and they also cause problems for public companies (for reporting and other reasons), so public companies almost always settle them after the class is certified. On the other side, these settlements often don't offer much benefit to the class, because the plaintiff counsel take a massive fee off the top, pay off the lead plaintiff, and don't have much incentive to do anything for the remainder of the class.
Eh, class action lawsuits are more about altering the large companies behavior in bulk because the individual harm to any plaintiff is rather small and nearly impossible to justify the expense and complexity of the suit. The plaintiff themselves would not profit off of it.
You're describing the 'private attorney general' theory/idea, which I'd believe if class-action lawyers were taking less remunerative cases that offered more public benefit.
I don't believe it is (someone who knows two languages isn't remarkable, someone who can teach others isn't remarkable), but there should probably be a visa for that if we need it. I personally don't believe even a lot of the software/IT industry jobs merit H1Bs.
They work abroad under the respective country's work visa. H1B is US specific, specific visa. The US has plenty of other work visas.
> I don't believe it is...I personally don't believe even a lot of the software/IT industry jobs merit H1Bs.
The law doesn't work based on your beliefs.
> someone who knows two languages isn't remarkable, someone who can teach others isn't remarkable
First: it depends on the language.
Second: the combination of two relatively commonplace skills in one person isn't commonplace. "Be top 20% in two things instead of top 5% in one thing" is standard career advice.
Foreign language teachers is the one category where it's easy to believe it's hard to find local talent. I've seen them in small towns across the country. Sure, you may have a Vietnamese speaking US citizen in New York, but they don't want to move to a small town in the Midwest.
Consolidation seems to have lead to massive price leverage for the winners and fewer choices for consumers, huge barriers to entry for small grocers and manufacturers
I think it's notable that Apple is vague about what was actually stolen and what OpenAI has actually received.
I read into these PR blasts, lawsuits that Apple is sour about losing employees to higher salary opportunities, and is likely using lawsuits instead of higher salaries to retain them.
- In SQLite UUIDs are default stored as compact blobs instead of inefficient varchar/text (SeaORM)
- Timestamps were easier via jiff instead of chrono (SeaORM)
- Model structs use the actual name of the $table instead of being named like $tablemodule.(Model|ActiveModel) (SeaORM) they are just $Table. This makes writing libraries a little simpler that need to use entity struct's from two separate modules/crates otherwise you get a name collision on Model/ActiveModel and need to do alias imports.
- There's an API to fetch related data to a query similar to Django ORM. IIRC this is missing from SeaORM
- The query expression language doesn't cover as much of SQL as SeaORM but seems to be enough for most web apps.
- I didn't like how the migration system works. I would skip that part of the library
reply