christoff12

I think the jury's still out on whether Muse will be sticky. My guess is that it won't be that good relative to the field.

Seems I'm perfectly random.

  The house called 8 of your 76 scored numbers: 11%.

  Blind guessing would average about 8.4 of them (11%).

  Only 4 of the 206 people in a psychology study were more random than you. The house found you extremely hard to read.

I have yet to use sandboxes though have some experimentation planned for a new gig I'm starting in a week.

How would you compare what you do to fly.io's Sprites (which is currently atop my To Try list)?

Yeah, I thought it was interesting that both of these[0] were on the front page.

[0] - the other one: https://news.ycombinator.com/item?id=50051573

Fair enough. But I am also curious if you'd like to share your rationale.

Indeed, seems like it should be pretty straightforward.

I understand why the venture-backed entity couldn't do this, but given the reactions here, could a new maintainer not take over and simply charge for support and future enterprise features like the Sidekiq guy?

Very nice. I really like the design.

I got tired of spinning up repos for basic pages, so made my own host last year - https://pageplane.app.

I think the SEO/AEO agencies are using them to seed content for clients.

Did you check out the post? Supabase sees Turso as the answer to workloads not well-suited for Postgres. This seems like a decent Yes, And proposition.

It's an unfortunate name collision. I definitely assumed the meaning was implied.

At the time, were you aware that you could borrow against your portfolio?

I love reading all of the DuckDB love here. It's good software.

Remember duckdb is for OLAP, not OLTP!

The claim of "built for teams that measure latency in microseconds" is conflicted by the pseudo demo showing a simple query that takes 4 seconds. I could assume that this is slowed down for effect, but the glowing green label[1] tells me this is a "real engine run" so now I'm confused.

My core question is why would I use this instead of duckdb and writing SQL as God intended[2]?

---

[1] A clear indication of AI generation

[2] This is a joke.

Funnily enough, I didn't even have the speaking aspect in mind.

I don't like how the "times" symbol floats off the line -- it's a visual thing for me (again, irrational).

Ah, yes. My gripe is certainly US American flavored.

An irrational gripe of mine is how GPT uses 7× instead of 7x.

I recognize that the former is the multiplication symbol, but I don't think it should be used that way.

'Tis a good workhouse, indeed. I hope they give us a 4.0 Pro that can use Flash subagents soon.

Knowing what I know now, I definitely would've opted for dual-credit rather than honors/AP classes, and CLEPed out of the remainder of freshman year basics.

Thanks for the candor.

I like this a lot. Do you handle scenarios where the data and context live in a data warehouse (Snowflake, etc)?

There are a lot of operational needs that exist downstream from dbt models that combine data from the various source systems.

How would we rate this revised version on a scale from 1-10?

"""

Totally fair. You can build the first 10-minute demo with an LLM now.

The hard part is usually what comes after. You need editable state, templates, and email-safe HTML. Then come export pipelines, custom blocks, permissions, and all the rendering edge cases that show up with real usage.

AI makes structure more important, not less. That’s why we launched Unlayer Elements. Instead of having an LLM generate a static blob of HTML, it can target structured components that map back into an editable email, web page, or document.

So I'd use AI to prototype it. I'd use Unlayer when that content layer becomes production infrastructure you don't want to maintain yourself.

"""

I made a deslopper[1] tool based on a new skill[2] I saw on twitter earlier. It's still a little smelly imo, but better.

---

[1] https://deslop.btst.workers.dev

[2] https://github.com/petergyang/no-ai-slop

I have no affiliations with the team or product, but Superconductor reminded me of Jules when I tried it a couple of months ago.

It might be overkill features-wise, but there's a free tier and it likely won't be left for dead anytime soon.

No prob

Re: difference -- Ok, I think I understand. Ultimately, we need a "permissions" layer and you've built a solve for that.

Re: README -- I can't recall a specific repo with one off the top of my head so took a stab at editing yours[1] instead of hunting around. It's not perfect -- I'd want to trim the bullet lists further, for example -- but is much more scannable in my opinion.

---

[1] https://gist.github.com/thedatadavis/fbbe556348eb43731659456...

I'm biased since I built a dbt[1] inspired utility[2] that turns markdown into a runnable DAG, but I think a new language is the wrong abstraction.

In a time where people are reading less and less code, introducing a new surface area -- that you don't have a good feel for -- to handle orchestration feels risky.

---

[1] https://github.com/dbt-labs/dbt-core

[2] https://github.com/pdthq/pdt

> The runtime holds the credential and only lets it through the skillscript I approved.

What about skillscript is unique that couldn't be done with bash or python as a permissioned tool? (Trying to understand where you see the difference.)

---

My original impression from the repo was that the language/toolkit is overengineered, but then I saw on the website that the intention is for the agents to write their own tools. That helps explain some of the complexity.

I think the rest of the perceived complexity is the over-explaining in the README.

I don't think anyone's going to really engage with all of that so you might have better luck chopping it down 80% to only highlight the stuff that matters.

I like canned beans because sometimes I forget to soak the ones in the bag.

this one? https://www.artic.edu/artworks/192466/floating-chairs-flying...

I just burned 20 minutes because I wanted to play hex minesweeper: https://hexabomb.pgpln.app

Source: https://chatgpt.com/share/6a42dd8a-4e28-83e8-9ef7-6ba56d665c...

> Due to the way Bibtex works, you may need to compile at least three times to see correct reference numbers in the PDF.

I'm not sure I understand why the second or third compile would work, but not the first.