I'm not against a tax on AI or robots, but I think this may be the big chance we have to look at universal income with new eyes. If jobs are to disappear, why not soften the blow and get rid of some of the inefficiencies many government processes mean in terms of other citizen benefits?

What I worry about more however is the malevolent actors across the AI space. I'd argue that most companies mean well, but chasing profit at all costs can very easily turn into malevolence. Both these and actors being malevolent on purpose needs to have a control function.

``` thing.doThis() thing.thenDoThat() thing.andFinallyThis()

// or

doThis(thing) thenDoThat(thing) andFinallyThis(thing) ```

Perhaps it's just one point from me - not liking chaining :D

caveman[0] is becoming more relevant by the day. I already enjoy reading its output more than vanilla so suits me well.

[0] https://github.com/JuliusBrussee/caveman/tree/main

One thing I am certain about is that javascript has gone through a very large amount of changes in it's lifetime – it doesn't look at all like it did when it was released and its' intended usages have changed a lot.

I can't help to think that there has to be a better way. Are we stuck with supporting mutable prototypes forever or what could an alternative look like?

Personally I'd still want a scripting language, but one that would be a lot stricter. No binaries like wasm, less globals, preferably type safe. I'd also prefer if we could go a route that didn't rely on the event loop and supported multiple threads.

Comments URL: https://news.ycombinator.com/item?id=46392217

Points: 3

# Comments: 1

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.

100%. I used to work at a studio specifically targeting winning awards with awwwards and it's definitely not the same as working on the normal web. Flashiness is way more important than performance there, be it in UX, conversions or load times.

It was a good space to play around with things like animations and webgl, but turns out that if your business needs to convert, those things can often come in the way of that.