Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

RONIN

ronin.co

Post reply on HN
Print view View original

1–10 of 12 posts

Re: RONIN

#3

Post by dash2 » 

    get.account.with.id = 'acc_fa0k5kkw35fik9pu';

    get.account.with = {
      lastName: 'Elaine',
      email: 'elaine@kojima-productions.com'
    };
I can't decide whether this is genius simplicity, or a terrible leaky-abstraction hack. Interesting.

Re: RONIN

#4

Post by catlifeonmars »

I’m very confused as to what this actually is. Not sure if OP is affiliated with the linked site or not, but it would be useful to have some documentation that explains: (1) the problem statement, (2) how this product solves the stated problem better than other solutions.

Basically why should someone click the “Get started” button.

Re: RONIN

#5

Post by pphysch »

dash2 wrote: post #3

get.account.with.id = 'acc_fa0k5kkw35fik9pu'; get.account.with = { lastName: 'Elaine', email: 'elaine@kojima-productions.com' }; I can't decide whether this is genius simplicity, or a terrible leaky-abstraction hack. Interesting.

I'm no fan of LISPs but this is taking paren-phobia to a new level.

Re: RONIN

#6

Post by yodon »

catlifeonmars wrote: post #4

I’m very confused as to what this actually is. Not sure if OP is affiliated with the linked site or not, but it would be useful to have some documentation that explains: (1) the problem statement, (2) how this product solves the stated problem better than other solutions. Basically why should someone click the “Get started” button.

Far too many engineers think creating a startup is about writing code. Writing the code is the easy part. Communicating why someone else should care about the code or the product is the hard part.

Re: RONIN

#7

Post by Animats »

yodon wrote: post #6
catlifeonmars wrote: post #4

I’m very confused as to what this actually is. Not sure if OP is affiliated with the linked site or not, but it would be useful to have some documentation that explains: (1) the problem statement, (2) how this product solves the stated problem better than other solutions. Basically why should someone click the “Get started” button.

Far too many engineers think creating a startup is about writing code. Writing the code is the easy part. Communicating why someone else should care about the code or the product is the hard part.

But it's fully buzzword compatible!

"Enjoy a collaborative editing experience, while taking advantage of true serverless scalability, strong consistency, ACID-compliance, sharding, and other database properties."

"Programmatically interacting with records on RONIN is made possible through its unique query syntax, designed to allow for accessing data in the most “humane” way possible, as it closely mimics the English language."

Here's the syntax:

    get.blogPosts = {
        'where.author.handle.is': 'elaine',
        'where.ronin.createdAt.isLessThan': new Date(),
        including: ['author']
    };
This is SQL made hard.

Re: RONIN

#8

Post by phpnode »

dash2 wrote: post #3

get.account.with.id = 'acc_fa0k5kkw35fik9pu'; get.account.with = { lastName: 'Elaine', email: 'elaine@kojima-productions.com' }; I can't decide whether this is genius simplicity, or a terrible leaky-abstraction hack. Interesting.

There's this and a few other magical things in the client that give me pause, in particular:

    const [post, comments] = await query(({ get }) => {
      get.post.with.slug = 'new-pricing';
      get.comments;
    });
there is simply no way to make that type safe without wrapping or forking TypeScript, and consumers really don't want that. Why make that tradeoff? Especially when it's so easy to accomplish with a more normal syntax:

    const [post, comments] = await query(({ get }) => [
      get('post').with({slug: 'new-pricing'}),
      get('comments')
    ]);

Re: RONIN

#10

Post by knorker »

Animats wrote: post #7
yodon wrote: post #6

Earlier quoted context omitted.

Far too many engineers think creating a startup is about writing code. Writing the code is the easy part. Communicating why someone else should care about the code or the product is the hard part.

But it's fully buzzword compatible! "Enjoy a collaborative editing experience, while taking advantage of true serverless scalability, strong consistency, ACID-compliance, sharding, and other database properties." "Programmatically interacting with records on RONIN is made possible through its unique query syntax, designed to allow for accessing data in the most “humane” way possible, as it closely mimics the English…

Ugh. Yeah "unique query syntax" is not a feature.

I suspect this whole thing may be GPT generated buzzword bullshit.

Post reply on HN