I guess half the internet?

I don't think Zeta is quite up to windsurf's completion quality/speed.

I get that this would go against their business model, but maybe people would pay for this - it could in theory be the fastest completion since it would run locally.

My hunch is that typing 5 words could be faster than going through 3 menus and screens. I don't see this as a replacement for normal UI, but as an optional shortcut - if you're happy typing.

Main differentiator here is as-you-type UI customization, and also in this case the UI isn't generative in the sense the options are hard coded - the LLM just chooses between them.

I think we'll see a mix of all of the above in the future as we take full advantage of LLMs.

Comments URL: https://news.ycombinator.com/item?id=43303309

Points: 63

# Comments: 23

Comments URL: https://news.ycombinator.com/item?id=42642971

Points: 291

# Comments: 135

Comments URL: https://news.ycombinator.com/item?id=40340163

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=39545120

Points: 2

# Comments: 0

The main point is, Spotify has a platform, like Apple, but is throwing stones from a glass house when it comes to trying to build on the platform.

Most of the integrations do not have anything to do with using the copyrighted music, e.g. a playlist export app.

The main issue was if you want to make a commercial app, there are no publicly available commercial terms, and it is easy for Spotify to not offer commercial terms to apps/companies that may in some way increase the chance of competition with Spotify. For example, if you wanted to make an app that would allow you to export your playlists, Spotify may offer you terrible commercial terms or none at all.

This is more restrictive than Apple.

https://www.iorad.com/player/2097656/Spotify---How-to-view-S...

Rather than a published set of rules and fees for commercial apps, instead Spotify requires you contact them, and fees and rules are done behind closed doors, if you even get that far.

Since Spotify is throwing stones here, what are Spotify’s commercial rates for Spotify integrated apps in their App Store?

Rather than a published set of rules and fees for commercial apps, instead Spotify requires you contact them, and fees and rules are done behind closed doors, if you even get that far.

Since Spotify is throwing stones here, what are Spotify’s commercial rates for Spotify integrated apps in their App Store?

Comments URL: https://news.ycombinator.com/item?id=34619680

Points: 6

# Comments: 6

> And that seems like a far cry from things like "rejecting transfers if the accounts involved would exceed their net debit or credit balances".

The READEME needs to be updated[1] for clarity. It doesn't enforce "accounting" rules, however The DoubleEntry gem has rules to optionally ensure a balance cannot go negative, and it also has an allowlist of allowed transfers ( which are defined by source account, dest account and code ).

[1] https://github.com/envato/double_entry/pull/216/files

> I think they key part is "distributed financial accounting database". For anything that didn't need to be distributed to handle massive volume of transactions I'd also pick Postgres, but I can imagine there's a limit where that wouldn't work, and as soon as you need to do this in a distributed database things get exciting.

That is why I qualified my statement with "you're using Postgres for your main app db".

For every financial transaction you'd likely have many more business logic level transactions, and you would want your business transactions to be as consistent as your financial transactions. No point storing a financial transfer if you can't match it up with a purchase on your business db.

Advantages for using Postgres ( assuming a double entry schema[1] ) and you're using Postgres for your main app db;

  - You can do financial transactions inside business db transactions, and roll back both atomically

  - Adding up numbers is one of the things computers are best at, and Postgres can easily handle a huge amount of financial transactions

  - Re-use PaaS Postgres hosting/scaling/clustering/backups

  - Easier integration with the rest of your app with foreign keys to relevant records relating to the financial transaction

  - Easy integration with BI tools given Postgres is well connectable

This gem does literally billions of dollars worth of financial accounting for various companies at scale: https://github.com/envato/double_entry

It's dated, the API is a bit messy and needs work, as it was initially written 10+ years ago, but for a web based app I would choose a v2 of it over a non-postgres ( assuming you are using Postgres for your app ) solution.

Tried for months / years to get in touch with someone at Spotify who could discuss a commercial licence agreement, so the app could have a business model. Stonewalled.

Turns out Spotify instead of working with us, made their own version - Spotify Blend, launched 2 years after our app.

The thing that bugs me the most is Spotify is a member of https://appfairness.org which states

> App store gatekeepers have carefully crafted their mobile device ecosystems to eliminate competition and maximize their own control and profits, to the detriment of developers and consumers.

However Spotify's own App Store did exactly the behaviour they are complaining about.