Any benefit to having a graph database component alongside the SQL? Maybe add some Apache Age to Postgres?
“””
Apache AGE™
Graph Database for PostgreSQL
Apache AGE™ is a PostgreSQL Graph database compatible with PostgreSQL's distributed assets and leverages graph data structures to analyze and use relationships and patterns in data.
“””
Among the deluge of github notifications, I noticed Mike Perham of Sidekiq fame working https://github.com/mperham/ratomic -- "Ratomic provides mutable data structures for use with Ruby's Ractors. This allows Ruby code to scale beyond the infamous GVL."
"""
After months of work on 8.0, I’ve been trying to prototype a Ractor-based job system using Redis Cluster so the system can scale to hundreds of Redises with minimal effort.
The hardest part is Ractors. They are quite difficult to program as they don’t allow lexical scope or closure variable access. I haven’t yet figured out the code patterns necessary for them. I would call it a dialect of Ruby.
To be fair, I think I had the same struggles when learning goroutines and channels.
"""
The combination of high and climbing price to earnings ratios for a smaller subset of tech firms, outsize retail investment in tech (cloaked by people buying crypto), and macro environment factors like high interest rates stimulating risky lending has me swapping this bubble toward the top of the list.
Last time, in 2016, SoftBank announced a $50B investment in the US...what were the results of that? Granted, SB announced an up-selled $100B investment earlier, is this not similar in "announcement"?
"""
SoftBank’s CEO Masayoshi Son has previously made large-scale investment commitments in the US off the back of Trump winning a presidential election. In 2016, Son announced a $50 billion SoftBank investment in the US, alongside a similar pledge to create 50,000 jobs in the country.
...
However, as reported by Reuters, it’s unclear if the new jobs pledged back in 2016 ever came to fruition and questions have been raised about how SoftBank, which had $29 billion in cash on its balance sheet according to its September earnings report, might fund the investment.
"""
Generative UI seems interesting to note as it's presented here as a way to create personalized UIs. Which means... that Generative AI creates a UI for each user? What are the implications of such a world? How does support work with this? How does a knowledge base get created to educate customers? How do you have a standardized way of discussing the UI?
The simplest and most direct and useful implementation Generative UI is to have a settings / form react to the context — e.g. an email form, or a bunch of sliders. I have a zod-based form schema, and set of forms and schemas. If there's a new schema (e.g. if I want to add name and comments) I can just have the AI generate and save a new schema, and the UI will know how to handle the changes. This makes updating interfaces really easy. (this is personalized to the dev)
For UIs generated per user, ideally you'd have a lot of guardrails around what it's able to generate and what the underlying data and use case is. I haven't built any of this in production yet, but I think accessibility may get a boost. Some video games already have a "verbose mode" for new players, and a "bare bones" mode for players who already get the mechanisms. One might consider building an "explanation" layer where some of the concepts can be explained to the user dynamically, and some more complex options can be either revealed under an "advanced mode" or when the UI determines the user "understands" the underlying concepts, as not to overwhelm them. I'm currently experimenting and designing/thinking through some bioinformatics (gene annotation) tools with this approach, but it's early days.
This sounds exceedingly unintuitive. Users hate having settings change / appear and disappear. It sounds like it would make interfaces broadly unteachable and difficult to document.
While i think it's possible that contextualized UX has value, it's seem way too easy for builders to go ham doing what they love: building more things.
i'm a cursor LLM editor convert. Pretty amazing. Thing is, being capable of building N versions of a thing doesn't mean it's a good idea. Technical debt has gone up dramatically on a team of 2.
And its not realistic that higher iteration velocity will yield the greatest version. easy to say but you need data and users to test through all of them. that's not happening in real life.
> "bare bones" mode for players who already get the mechanisms.
I've wanted this in monster hunter for years. Spare me the cutscenes and dialog and just gimme a menu full of quests so I can decide which monster I want to fight without having to listen to a damn audiobook.
gen UI could look like a completely custom interface integrating hundreds of apps to one. that is if an Agentic system is completely multi-modal it can collect all digital information the user owns (in a safe way ofc)
but that means when an agent generates a ui it is JUST to make decisions on the data is has access too.
E.g. new email received asking for a file and a small change, agent finds the file and makes the change, then a UI is generated confirming the correct file and changes.
this is what generative ui looks like to me, far off, but definitely in the future.
- a stock photography collection to make your site seem full of content
- organize the labor to shoot photography and video around editorial content and empower them to sell their own assets with tooling
- as an indexer you only take a 30% which is much lower than the aggressive everyone loses shutterstock-getty cut
———
Personally I imagine a decentralized approach where contributors host the content or purchase hosting space from the indexer. The indexer just provides a search platform. Transparent costs will keep people at your doorstep and maintain exclusivity.
It is important to understand that Shutterstock does not sell assets, they sell the licenses to use the assets.
First, you can't "organize labor" to take an iconic photo of a shuttle landing that happened 30 years ago. That is, there is enormous value in their existing library.
Second, decentralized photography is called Instagram, yet those photos aren't worth anything. Instagram has no interest in licensing them. Instead, they monetize around the photo (engagement) and not the photo itself. The real value has been in the content produced by professional photojournalists.
Whether Getty/Shutterstock is a good business is a different topic. They've been around for a long time, despite your claim they are "easily disrupted." You both underestimate the value of indexing (distribution) and mislabel them as being merely an indexer (they protect rights, organize deals, bundle and package, centralize relationships, to name a few).
I never claimed they were an indexer, I claimed that is how a company to displace them would work. Everything you’re telling me is misguided is a misinterpretation about my claims of a non-existent competitor. Your interpretation of my response is misguided.
You don’t need a back catalog for a 30 year old photo of a shuttle launch, that wouldn’t sell to recent news outfits looking for latest editorial content.
The fact that Shutterstock has spent the last decade switching from php to react to nextjs and only acquiring their competitors is more than enough evidence they are easily displaced. The only thing your competitor has to do differently is not sell out to Shutterstock.
This piqued my interest too. I found a few adjacent papers but couldn't find a source that made as comprehensive of a claim.
The closest were:
- "In constant battle with insurers, doctors reach for a cudgel: AI" from NYT (via Salt Lake Tribune), 2024 July, which is mostly on doctors using law-compliant LLMs to draft prior authorizations and has a passing one-graf mention of insurers likely doing the same: https://www.sltrib.com/news/nation-world/2024/07/11/constant...
"Large Language Models to Help Appeal Denied Radiotherapy Services" from JCO Clinical Cancer Information, 2024 Sept. (abstract only; full-text paywalled) https://pubmed.ncbi.nlm.nih.gov/39250740/
“””
Apache AGE™ Graph Database for PostgreSQL Apache AGE™ is a PostgreSQL Graph database compatible with PostgreSQL's distributed assets and leverages graph data structures to analyze and use relationships and patterns in data. “””
https://age.apache.org/
reply