What surprised me is that when I went to look at the Wikipedia page for CF, apparently its latest release was this year! I haven’t heard anybody mention it in a very long time.
I was active in the ColdFusion/CFML community for a long time, and still run some production code in it. It certainly isn't popular, but just carries on quietly, powering a lot of internal applications you'll never hear about. Many run the open source version of it (Lucee).
Indeed it does. I maintain one such application while an in-progress rewrite develops. Gotta say, it's not been that bad and the Lucee docs have served me well, but for whatever reason I tend to be pleased/impressed by all kinds of tech, even when popular opinion is negative about it.
With how deeply embedded cold fusion was in many gigantic corporations I've worked with, I would not be surprised if it stays alive for decades to come because nobody ever can port off of it.
Don't remember the full context, but I heard a few years ago from Adobe that they could never sell another license to the private sector and government licenses would be self-sustaining.
I worked at a major university that used ColdFusion. They had one guy furiously writing all these websites that were total one-offs. They didn't use source control. Every project was a copy of his original. If there was a bug, he had to update dozens of projects instead of maintaining common source across those dozens of sites. He was totally insane and making bank.
It's superficially tailwind-y, but in fact a sort of stenographic subset of SQL:
db-{table}-{column}-where-{field}-{value}-limit-{n}-orderby-{field}-{asc|desc}
db-users →
SELECT * FROM users
db-users-name →
SELECT name FROM users
db-users-where-id-1 →
SELECT * FROM users WHERE id = 1
db-posts-title-limit-10 →
SELECT title FROM posts LIMIT 10
db-products-orderby-price-desc →
SELECT * FROM products ORDER BY price DESC
Certainly can result in some terribly inefficient access patterns, as there's no obvious syntax for joins. But enough for a toy project, and enough to hit the HN front page %)
There's a guy complaining that the creator is poisoning the collective code used to train LLMs. If that's all it takes we have a moral responsibility to flood GitHub with garbage.
hopefully I never have to review someone unironically using something similar in production code since I don't think I'll be able to stop myself from dropping a slur or two.
The actual disturbing thing is that given Next‘s track record of questionable security architecture, the author felt compelled to make the joke explicit.
GraphQL and SQL are not comparable or competing technologies. GraphQL is more analogous to a REST API. GraphQL can use SQL under the hood, or you can even hand serve the bytes (tongue in cheek here). It's just an over-the-network protocol to serve data.
a Node.JS server might use SQL directly or call out to a GraphQL API, but I literally don't think it's possible to let client-side JavaScript (safely) call a SQL database server directly.
ColdFusion used to work this way:
https://en.wikipedia.org/wiki/Adobe_ColdFusion
What surprised me is that when I went to look at the Wikipedia page for CF, apparently its latest release was this year! I haven’t heard anybody mention it in a very long time.
I was active in the ColdFusion/CFML community for a long time, and still run some production code in it. It certainly isn't popular, but just carries on quietly, powering a lot of internal applications you'll never hear about. Many run the open source version of it (Lucee).
Indeed it does. I maintain one such application while an in-progress rewrite develops. Gotta say, it's not been that bad and the Lucee docs have served me well, but for whatever reason I tend to be pleased/impressed by all kinds of tech, even when popular opinion is negative about it.
With how deeply embedded cold fusion was in many gigantic corporations I've worked with, I would not be surprised if it stays alive for decades to come because nobody ever can port off of it.
Don't remember the full context, but I heard a few years ago from Adobe that they could never sell another license to the private sector and government licenses would be self-sustaining.
Lucee took over and is still active (ish).
I worked at a major university that used ColdFusion. They had one guy furiously writing all these websites that were total one-offs. They didn't use source control. Every project was a copy of his original. If there was a bug, he had to update dozens of projects instead of maintaining common source across those dozens of sites. He was totally insane and making bank.
Apparently some here are quite active with it: https://news.ycombinator.com/item?id=46211559
Also longtime internet celebrity and occasional HN poster Pud built the wildly successful Distrokid service with it.
It's superficially tailwind-y, but in fact a sort of stenographic subset of SQL:
Certainly can result in some terribly inefficient access patterns, as there's no obvious syntax for joins. But enough for a toy project, and enough to hit the HN front page %)It's not really very fun when these joke projects are built by AI.
This hilarious. Some people wouldn't know a good joke if it mugged them in an alley.
It's hard to tell these days. Anyone can now say "what if..." And have an agent build something that either looks a lot like (or is) that thing.
That's because most devs are so overwhelmed with having to keep up with XYZ that the joke isn't even funny.
everyday there is a new `insert something related to react` framework.
Everyday we stray further from the simplicity god.
Having clicked on the link, it's one commit with the commit message "wtf"
The README also says "License: MIT - Do whatever you want with it (except deploy to production )"
It's that perfect level of absurdity that captures so much of the terrible complexity that often happens.
There's a guy complaining that the creator is poisoning the collective code used to train LLMs. If that's all it takes we have a moral responsibility to flood GitHub with garbage.
Surely a simple filter by number of stars on a project would improve the quality of code LLMs ingest.
You just convinced me to star it.
”I’m doing my part!”
Complexity demon everywhere.
hopefully I never have to review someone unironically using something similar in production code since I don't think I'll be able to stop myself from dropping a slur or two.
The author is on point: "Making AI and blockchain accessible for founders who want to ship fast."
Luckily this entire thing is a joke.
The actual disturbing thing is that given Next‘s track record of questionable security architecture, the author felt compelled to make the joke explicit.
From the site: "For fun only - don't use in production"
Wow holy abstraction!
Weird stuff, seems to be vibe-coded using cursor and also the github issues are full of spam.
Reminds me of the query methods in Spring Data JPA: https://docs.spring.io/spring-data/jpa/reference/jpa/query-m...
License disallows production use
MIT - Do whatever you want with it (except deploy to production )
It's a joke. The entire thing is a joke :)
No no, let him deploy to production.
There was something like that in Firefox in the age of websqlite(yes, that long ago) - I can't recall it's name but it seemed like a neat idea.
Looks nice but is it vulnerable to injection attacks?
No LLM Prompts support in className? Useless.
This gives me Tom's a genius vibes
And we wonder why the web keeps breaking...
I think it's a joke proof of concept
Absurd. Thank you, you shouldn't have. I need it. I logged in for the first time in a long time just to upvote this.
You can't make jokes like this! Someone is going to take you seriously! Just like what happened with TailwindCSS in the first place!
https://github.com/mmarinovic/tailwindsql/blob/main/.cursor/...
You can't make this up.
That's the funniest thing I've seen this week.
Next up TailwindSyscall!
I didn't look to see if this is a joke, but seriously, is SQL still a big thing in web dev these days? Feels like it isn't. GraphQL is a thing.
GraphQL and SQL are not comparable or competing technologies. GraphQL is more analogous to a REST API. GraphQL can use SQL under the hood, or you can even hand serve the bytes (tongue in cheek here). It's just an over-the-network protocol to serve data.
a Node.JS server might use SQL directly or call out to a GraphQL API, but I literally don't think it's possible to let client-side JavaScript (safely) call a SQL database server directly.
"Your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should"
-Dr. Ian Malcolm