Any question that is more than a couple of years old and applies to something under active development risks having the "bubbled up" answer being actively incorrect.
Maybe this is just because I'm not developing in Javascript.
Ziggit is indeed another active community and it's perfectly legitimate to want to stick to a platform vs another for personal preference, the people who downvoted this comment should really re-evaluate the way the approach this subject.
Mostly because liability is only a thing in some areas, when programming becomes as scrutinised as other industries, and basic stuff like returns due to failed functionality are normal instead of "try to reboot it", security and quality will have other priority.
"There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists."
LLMs are not artificial intelligence but artificial stupidity.
LLMs will happily hallucinate. LLMs will happily tell you total lies with complete confidence. LLMs will give you grammatically perfect completely vapid content. etc.
And yet that is still better than what most humans could do in the same situation.
We haven't proved that machines can have intelligence, but instead we are happily proving that most people, most of the time just aren't very intelligent at all.
> LLMs will happily hallucinate. LLMs will happily tell you total lies with complete confidence.
Perhaps we should avoid anthropomorphizing them too much. LLMs don't inhabit a "real world" where they can experiment and learn. Their training data is their universe, and it's likely filled with conflicting, peculiar, and untestable information.
Yes, the output is sometimes "a lie" if we apply it to our world, but in "their world" stuff is might be just strangely different. And it's not like the real world has only "hard simple truths" - quantum mechanics comes to mind about how strange stuff can be.
> yet that is still better than what most humans could do in the same situation
Yup. A depressing takeaway from LLMs is most humans don’t demonstrate a drive to be curious and understand, but instead, to sort of muddle through most (economic) tasks.
My condolences, the only thing Windows is actually needed for is playing games and thanks to Valve and SteamOS's work on Proton, Linux is a truly viable alternative now.
Generally specialist software for different industries will make you pick between Apple and Microsoft but I think that's a different beast because having a one-off (cracked) Windows box for say video editing meets the protest bar pretty well.
It also overlooks the fact that what Amazon was doing was outright illegal for years and they never got handed their ass on a platter.
For years, Amazon enabled everybody to bypass sales tax which gave Amazon a 4-8% advantage on books over brick and mortar that had to pay both rent and sales tax.
Quite a few of the "successful" tech companies followed this pattern: Uber, Lyft, AirBnB, etc. all engaged in blatantly illegal behavior to become big.
If you had said "were" instead of "are" this would be a true statement. Since South Dakota v. Wayfair in 2018, states have been allowed to charge sales taxes on businesses that have no operations in their state. That decision overturned 1992's Quill v. North Dakota, which held as you say. But that is no longer the law of the land.
The 5-4 majority in 2018 included two justices who were part of the unanimous holding in 1992 (Anthony Kennedy and Clarence Thomas), voting to overturn their own decision from a quarter century before.
>For years, Amazon enabled everybody to bypass sales tax which gave Amazon a 4-8% advantage on books over brick and mortar that had to pay both rent and sales tax.
In 1992, SCOTUS ruled in Quill vs. North Dakota[0] that a business must have a "nexus" in a particular state to be required to collect sales taxes. I'd note that Amazon was founded in 1994.
And so, yes Amazon did have an advantage WRT sales taxes. But it wasn't, as you said, "outright illegal" until 2018 with SCOTUS' ruling in South Dakota vs. Wayfair Inc.[1] At which time, IIRC, Amazon continued collecting sales taxes that it had already been collecting in many states, as already it had nexuses (warehouses, distribution centers, etc.) in many places.
I'd note that I'm not "defending" Amazon here. They do plenty of shady stuff WRT pricing, as well as abusing their employees, suppliers and third-party sellers.
Why don't we take them to task for that stuff instead of making stuff up? Just sayin'
> Does anyone have any effective strategies for moving along the end of this administration aside from law suits that fits a substantialy smaller budget and doesn’t create possible legal risk?
Sign on to help fix gerrymandering in your state. A combination of redistricting commission and jungle primaries would do nicely.
The big problem right now is that all the Republican congresscritters are effectively safe even with all this bullshit going on. They do not fear a general election at all--thus why none of them feel the need to engage with their constituents.
Ranked-choice voting would be nice but is insufficient by itself.
For the vast, vast, vast majority of people, if you don't have an obvious primary key, choosing UUIDv7 is going to be an absolute no-brainer choice that causes the least amount of grief.
Which of these is an amateur most likely to hit: crash caused by having too small a primary key and hitting the limit, slowdowns caused by having a primary key that is effectively unsortable (totally random), contention slowdowns caused by having a primary key that needs a lock (incrementing key), or slowdowns caused by having a key that is 16 bytes instead of 8?
Of all those issues, the slowdown from a 16 byte key is by far the least likely to be an issue. If you reach the point where that is an issue in your business, you've moved off of being a startup and you need to cough up real money and do real engineering on your database schemas.
The problem is that companies tend to only hire DB expertise when things are dire, and then, the dev teams inevitably are resistant to change.
You can monitor and predict the growth rate of a table; if you don’t know you’re going to hit the limit of an INT well in advance, you have no one to blame but yourself.
Re: auto-incrementing locks, I have never once observed that to be a source of contention. Most DBs are around 98/2% read/write. If you happen to have an extremely INSERT-heavy workload, then by all means, consider alternatives, like interleaved batches or whatever. It does not matter for most places.
I agree that UUIDv7 is miles better than v4, but you’re still storing far more data than is probably necessary. And re: 16 bytes, MySQL annoyingly doesn’t natively have a UUID type, and most people don’t seem to know about casting it to binary and storing it as BINARY(16), so instead you get a 36-byte PK. The worst.
> contention slowdowns caused by having a primary key that needs a lock (incrementing key)
This kind of problem only exists in unsophisticated databases like SQLite. Postgres reserves whole ranges of IDs at once so there is never any contention for the next ID in a serial sequence.
I think you’re thinking out the cache property of a sequence, but it defaults to 1 (not generating ranges at once). However, Postgres only needs a lightweight lock on the sequence object, since it’s separate from the table itself.
MySQL does need a special kind of table-level lock for its auto-incrementing values, but it has fairly sophisticated logic as of 8.0 as to when and how that lock is taken. IME, you’ll probably hit some other bottleneck before you experience auto-inc lock contention.
If the scientist in question doesn't get found out for 30 years but then becomes a pariah, it doesn't matter. They displaced a better scientist for their entire career. There is no retroactively fixing that.
There is a huge incentive to cough up something that will make you "famous". If it doesn't make you famous, well, you can bury it and simply be a pedestrian scientist--no harm, no foul. If it does make you "famous", well, you might make it out the other side without anybody being able to pin anything decisive on you. And, if you get caught and become a pariah in 10 years, well, you likely earned way more than you would have in 30 years anyway.
Lying, in this case, almost always comes out ahead.
A "comptime f32" is different from an "f32"
reply