Industry-led content regulation has been very effective at staving off legal regulation in the United States. The MPA rating system and ESRB are very imperfect but nonetheless are success stories.
Okay, I'll give you that. Let me rephrase: Industry-led regulation can work, in industries that won't kill anyone or even realistically lose anyone a bunch of money for non-compliance, if-and-only-if government regulation exists as a real and powerful enough alternative to make it stick.
Not as far as I can tell. You're right that China does seem to be in a fairly unique position to actually do this though - it is interesting to consider what would happen if they did. Looking at recent engineering failures at Boeing, Tesla, Volkswagen etc., such enforcement of engineering standards could even give them a competitive advantage on the world stage in a way that markets captured by lobbyists could never realistically achieve.
Unless that smell is oil. Or gasoline. Or burning rubber. Or petrichor. Or just plain old smoke.
Or the touch is the feeling of road surface changing, or the steering wheel getting harder to turn / having no effect at all, or the rush of air if a door flies open...
Ask this to someone who remembers when Google first appeared.
I am not a Kagi user, but am seriously considering it after a number of months having to dig through at least 8 results of paywalled or possibly AI-generated pages for almost every Google query; seriously, I just did a search for 'python concatenate list' on google and it was worse than I expected - the official docs weren't even on the first two pages and even the helpful Stack Overflow answers were the 5th result down - give it a go, the results are trash.
I google things at least 20 times a day, and probably so do you. I would pay for something that can cut out the bollocks - if Kagi can follow through, they'll have a customer.
Yep, I think I’m going to try Kagi. I am so, so tired and exhausted of every search result on Google being “the top X in ${this_month_of_this_year}” with a list of Amazon affiliate links. I append Reddit to the searches for products now, but notice on higher margin items you can click into Reddit user history of people giving their “opinion” and see that every post they make is about that particular product.
Just tried that same query without the quote marks on Kagi.
The first result is an info box from Stack Overflow showing use of the + operator to join two lists (with a link to source).
Then 4 more relevant SO posts (which are more nuanced and specific than the generic query, like concatenating into a single string, or concatenating without creating a copy.
Then a small inset box as a "blast from the past" with 4 older blog posts, at least 2 of which look pretty relevant here just from the title.
Then 5 more SO posts (again more nuanced and specific variants of the underlying question), and a digital ocean post on 6 ways to concatenate a list in Python.
Odd choice of words. I'd say that perl, awk, regex etc are great ergonomic tools - if anything too ergonomic. The main problem with them - and the probable source of their bad reputations - is that the ease and comfort (the 'ergonomics') of just cobbling something together something that works and then throwing it out there does not encourage good engineering practices.
Do I need good engineering practices in my day-to-day text editing? Mostly not for what I do myself, but I'm grateful that the maintainers of the emacs packages I use have better tools to work with.
or something that works... sometimes, and is indecipherable, so all the "ergonomics" of the initial cobbling phase disappears to reveal how unergonomic this really is
I feel you've missed my point - 'ergonomics' literally means 'efficiency and comfort', not 'future maintainability'. Regex does comfort. AWK does it. If you need to do a specific thing right now, and you know them, then those tools are about as good as it gets. I'm not denying that those solutions will be horrible to grow and maintain, but that wasn't your point - that's why I said your choice of saying they weren't "ergonomic" was a bit odd. They are. That's the problem.
Most of the custom text editing operations I do on a daily basis only need to work once. For that, a Regex is very 'ergonomic'. If I were writing an emacs package, I'd probably use something better - something less ergonomic, but easier to maintain.
As an aside, I used to work in a machine shop and we had a well-designed system of pneumatic tubes throughout the warehouse powering spartan steel-handled drills that would give me calluses but reliably get the same jobs done the same way every day. At home, for the odd job I need to do, I use a cheap lithium drill with a nice grippy handle. Sometimes the ergonomic option is better because, right now, I just don't need to buy a compressor and run tubes through my house.
There is no comfort in poorly readable regex that seems to work, but really doesn't with a subtle bug.
And it's only efficient if you consider the time to write the bugged version, not the time to write the correct version
This would have taken you less time to Google that than it did to type the question in this public forum (the answer is very obviously 'yes', by the way).
