How do you edit them once it becomes complicated? Should everyone have access to everything, or do different teams own different toggles? How do you know they're unused and can be cleaned up? How do you roll out to 1 % but keep it persistent so that the same user has the feature on throughout?
All of these are of course possible to solve. But at some point just use something battle tested..
For one app and one team, honestly not much. It starts to matter when you want gradual rollouts where the same user stays in or out across services, different rules per environment or customer, an audit log of who flipped what when something breaks, and a way to find dead flags. And then the boring parts: not doing a network call on every check, and what happens when the store is down.
There only needs to be one working exploit, and yet even with thousands of people working either manually or with LLMs, no one managed to get one so far.
Again, obvs you should patch your servers, but the point that this is not an easy exploit stands.
How do you know there is none? Because both the PHP devs themselves and the companies involved in the patches said they had working PoCs.
Do note that commonly a blackhat, or state operative will not chuck their code on github, but either try to sell it, or try to use it to quietly get footholds on strategic places.
The crucial piece of my statement and my question is that such an exploit doesn't have to be on GitHub to exist.
Again: such exploits are typically not distributed, hosted or published on platforms like GitHub. But on forums, boards and shops on the dark or deep web.
Yeah, it's going to be hard for someone to pick an arbitrary target and get into a position to exploit it, but there are an enormous number of people who are in the position to exploit someone.
One rogue employee at Cloudflare could MITM half the Internet if they are able to get around whatever internal safeguards exist.
Very weird thing for you to complain about when the writer did list multiple PoCs he tried, and here you are saying there's one that works but you won't share the link.
Ain't nothing new, most AI-related posts have been like this for a while.
The fact that these come from bots at least gives me hope that the fact a few good posts come up every day from the sea of slop means the actual humans still appreciate good writing.
What about the fact that there isn't a single 'parseInt' function in JS that can reliably only convert number strings to numbers?
They each have different quirks (some will parse 'a123' as 123, others will handle scientific notation etc). The only reliable way of doing this is doing a regex followed by parseInt... which is definitely a footgun IMO.
Unary "+" returns NaN for strings that don't contain exactly a number (except for empty string which standard type conversion turns into 0). It even works for scientific notation like +'1e3' === 1000.
You can have that with generic functions, although Go's lambda syntax is too verbose. The slices package has DeleteFunc, which is kind of the opposite. I don't know why they have Filter.
While Go has first-class functions and the like, functional programming is discouraged in Go; it's not optimized for it in either the language or the compiled result. It doesn't have tail call optimization for example, and naive functional coding may look "nice" (especially if it had for example arrow function syntax), but it won't have "mechanical sympathy". That is, no functional code (in Go) will be as fast as just iterating over a slice.
And I don't see how Go design patterns would be any worse. The main issue people have with it is the repetition/verbosity, which LLMs handle just fine.
The repetition and verbosity makes it more expensive for the LLM to write. You'd want a language that is expressive and dense if you're optimizing for token usage.
I guess their frontend for managing these is 'nice', but at the end of the day it's a static page that sets flags on redis.
reply