The word "most" is doing a lot here. Europe guarantees consumer rights by law, while the US relies on companies adopting the practices voluntarily. Most do, but larger companies more universally than smaller, and it's by no means universal.
It may be only a matter of time before all devs remember to append ", and make no mistakes" to the end of their LLM prompts, but I don't think we as an industry will ever reach a point at which every release of every package/library/application is scanned with the most capable model available.
I mean, we've had tooling like fuzzers available for a very long time, and most devs haven't run one against their software ever, let alone before each release.
It's the human factor I think will keep this a problem essentially-forever.
Sorry for the late response; it's been a busy week.
As a user, I don't care how complicated is the means of displaying images in a terminal session. I would only want to do so when I'm deep in a text-oriented context and there is a suddenly a need for an image. Not a chart or a graph, but an actual image. As a user, whatever contortions are necessary at that point are fine, because it's an unusual circumstance.
I set Siri to a masculine voice, because I disliked the gendered assumptions I felt with the default.
I gave my Claw Discord bot a feminine identity (Ada, with a pfp of Ada Lovelace) for the same reason. But then I set up a separate Discord bot for an LLM outside of Claw, and gave it a masculine identity so I could easily distinguish between the two mentally and expressively.
All still clankers, but "it" is too general for my dual-bot config.
Sure, of course sometimes an image conveys things better than a thousand words. But a very large percentage of what most people do with computers is primarily text, with more images in ads than useful content. By and large GUIs don't use images to convey information better, they just make text worse.
Modern terminal software supports displaying images, for what it's worth.
I use actualbudget.org to track all spending, but only update investment accounts ("off-budget" in Actual Budget terms) once a month. Completely deterministic, as all things related to numbers should be.
I have pointed my LLM at the SQLite DB and asked it to tell me what it could see from my last five years of transactions, and I was impressed with the things it picked up, and what it reminded me of, but I'm not sure I saw any value in the sense of anything I would change.
I'm going to have it review things monthly to see if that helps me, but I'm not sure it will. I'm generally already aware of how my finances are going because of my budget updates.
I kept asking this question last year, especially after that initial METR report showing people believed themselves to be faster when they were slower. Then I decided to dive in feet-first for a few weeks so that nobody could say I hadn't tried all I could.
At work, what I see happening is that tickets that would have lingered in a backlog "forever" are getting done. Ideas that would have come up in conversation but never been turned into scoped work is getting done, too. Some things are no faster at all, and some things are slower, mostly because the clankers can't be trusted and human understanding can't be sped up, or because input is needed from product team, etc. But the sorts of things that don't make it into release notes, and are never announced to customers, those are happening faster, and more of them are happening.
We review server logs, create tickets for every error message we see, and chase them down, either fixing the cause or mitigating and downgrading the error message, or however is appropriate to the issue. This was already a practice, but it used to feel like we were falling farther behind every week, as the backlog of such tickets grew longer. Most low-priority stuff, since obviously we prioritized errors based on user impact, but now remediation is so fast that we've eliminated almost the entire backlog. It's the sort of things that if we were a mobile app, would be described as "improvement and bug fixes" generically. It's a lot of quality-of-life issues for use as backend devs.
At home, I'm creating projects I don't intend for anyone outside my family to see. So far things I could theoretically have done myself, even related to things I've done myself before, but at a scale I wouldn't bother. Like a price-checker that tracks a watchlist of grocery items at nine local stores and notifies me in discord of sales on items and in categories I care about. It's a little agent posting to a discord channel that I can check before heading out for groceries.
Or several projects related to my hobbies, automating the parts I don't enjoy so much to give me more time for the parts I do. My collection of a half-dozen python scripts and three cron jobs related to those hobbies has grown to just over 20 such scripts and 14 cron jobs. Plus some that are used by an agent as part of a skill, although still scripts I can call manually, because I'll go back to cron jobs for everything if the price of tokens rises a bit more.
I was super-skeptical, and now I'm not. I think companies laying off employees are delusional or using LLMs as an excuse, but there is zero question in my mind that these things can be a huge boon to productivity for some categories of coding.
You could double or quadruple the number of pixels, and it wouldn't make any difference in how much information humans comprehend easily. You would be using more computing power and more memory to deliver the same amount of useful information less efficiently.
A "proper GUI" is rarely better than a well-designed TUI for communicating textual information, IMO. And the TUI constraints keep the failure-states for badly-designed UI tightly bound, unlike GUI constraints.
Every year or so, I look into alternative to my Paperwhite, which has been in "airplane mode" since I bought it. So far, nothing else seems to be quite up to the level of my existing device for my use case, let alone better.
It's possible I needed to log into Amazon in 2016 and 2020 when I bought my two Paperwhites, but I haven't needed to do so again since, so I'm not sure this will affect me at all. If it does, I'll have to check my notes for what was closest last year when I last checked.
Something seems wrong. A half-million tokens is almost five times larger than I allow even long-running conversations to get too. I've manually disabled the 1M context, so my limit is 200K, and I don't like it to get above 50%.
Is it... not aware of its current directory? Is its current directory not the root of your repo? Have you maybe disabled all tool use? I don't even know how I could get it to do what you're describing.
Maybe spend more time in /plan mode, so it uses tools and the Explore sub-agent to see what the current state of things is?
It sounds like we are not seeing the same banners. You keep paraphrasing, definitely not quoting, what sound like dire pleas for survival, and yet any banner I see lacks any of that.
On your point 1, it is incredible normal for non-profit organizations to spend quite a bit of money on fundraising. They do this because spending less brings in less, and bringing in less means they cease to exist. As weird as it is to spend a million throwing a party to bring in five million, it works, and it brings in money from different people than letters in the mail or banners on a website do. 12% is half of what Charity Watch still deems "highly efficient" and earns them an A-[0].
On your points 0 and 2, I'm puzzled about what you suggest as an alternative. Should they fire all but a skeleton staff and only operate the website as-is on as little as possible with no expansion into other languages or areas of interest? Maybe that's your implied suggestion, but they clearly disagree.
If the once-a-week banners bother you that much, it suggests that you are using the site very, very frequently. You can either support their mission or not, as you wish, and all of the banners are easily dismissed or ignored. I don't think they're nearly as dishonest as you do, but then, I've worked for non-profits in the past and can read a Charity Watch page.
For the US, Google Trends reveals that Clojure's heyday came in 2013, and it has been on a decline since[0]. It never really reached the interest level of Scala, and of course recently Rust is consuming all the air in the room.
Except, just for kicks I add Golang, and it turns out that all of the above are marginal compared to Go[1].
HN posts are very different from general interest, but yeah, I'd go with "Clojure has sadly missed on its shot to become a popular general-purpose language" rather than "Clojure is dead," but your instincts seem right.
Are you saying you would prefer all blog posts to be header by the same undifferentiated photo of a blue sky? I'm not quite getting what you're saying here.
I mean, if a person is only ever going to write a single blog post, then yes, absolutely, post a personal photo of something beautiful. Why not? But if a person might post more than one blog post, then presumably there's some motivation to tying each (required) photo to the post in question in some way, even if tangential, right?
A lot of blog templates, as well as tools that syndicate blog content, require some sort of image. They'll take the first image they encounter, no matter what it is. If you want to avoid it being some sort of sidebar glyph, or the page looking wonky, you have to supply an image. What image would possible have fit this article? And so we end up with AI-generated filler.
That doesn't make it desirable, but I hope it helps to explain it.