Fair! That'd depend on the operations right? For example, AFAIK typescript can't do much about multiple chained `map` calls, and i've seen quite a few `.filter(...).map(...).filter(Boolean).map(...)` :/
Interesting. there are some parts i like a lot here, but two things that I really dislike syntax wise. One is the lean towards a chainable syntax - this has proven to a big footgun for many devs in both java streams and typescript, making it very easy to go from O(n) to O(2n). The other part i really dislike is the first argument principle noted. If i myself define `string_and_reverse` and I can call it both through `string_and_reverse(42)` and `42.string_and_reverse()` i could definitely see this leading to some very funky looking chaining.
Perhaps it's just one point from me - not liking chaining :D
> Opus 4.7 uses an updated tokenizer that improves how the model processes text. The tradeoff is that the same input can map to more tokens—roughly 1.0–1.35× depending on the content type.
caveman[0] is becoming more relevant by the day. I already enjoy reading its output more than vanilla so suits me well.
The US being stuck in imperial is such a meme nowadays with "freedum units" and the like. It's yet another odd thing that makes it easy for the rest of the world to laugh at the US. In these isolationist times I doubt this will change soon though, but it'd definitely help international collaboration.
I find your comment a bit funny on multiple levels. "Linux" does not force anything on you right? It's the community that has by and large decided to move to maintaining other solutions. If you still want to use fvwm you can still run it on arch with x11 until x11 is not maintained and the kernel breaks it somehow
It'd be cool, but I guess the hodgepodge of different solutions in that space would make it really hard. For example, many mods for GW2 don't work in linux if you're on something like Hyprland due to them having to act as overlays. Not sure if that's a wayland issue or just a typical hyprland thing though
Not sure if that's satire or not but how would you even identify the party to sue? What do you do if they're based in a country where you can't sue them ofer relatively trivial matters as this?
We feel this at work too. We run a book streaming platform with all books, booklists, authors, narrators and publishers available as standalone web pages for SEO, in the multiple millions. Last 6 months have turned into a hellscape - for a few reasons:
1. It's become commonplace to not respect rate limits
2. Bots no longer identify themselves by UA
3. Bots use VPNs or similar tech to bypass ip rate limiting
4. Bots use tools like NobleTLS or JA3Cloak to go around ja3 rate limiting
5. Some valid LLM companies seem to also follow the above to gather training data. We want them to know about our company, so we don't necessarily want to block them
I'm close to giving up on this front tbh. There's no longer safe methods of identifying malignant traffic at scale, and with the variations we have available we can't statically generate these. Even with a CDN cache (shoutout fastly) our catalog is simply too broad to fully saturate the cache while still allowing pages to be updated in a timely manner.
I guess the solution is to just scale up the origin servers... /shrug
In all seriousness, i'd love if we somehow could tell the bots about more efficient ways of fetching the data. Use our open api for fetching book informations instead of causing all that overhead by going to marketing pages please.
Nah, most of us go browser by browser I think. I think I've been going with two browsers open at most the last 5 years, and at my current employer I'm so reliant on browserstack that I don't even have anything other than chrome running.
``` thing.doThis() thing.thenDoThat() thing.andFinallyThis()
// or
doThis(thing) thenDoThat(thing) andFinallyThis(thing) ```