> The profit does not come from the source code, but from the assets.
The source code enables the profitability of the assets. In the end the distinction is irrelevant to this matter. This is like saying Facebook doesn’t make money from its platform but from its deals with advertisers.
Just a note that he is speaking from the perspective of someone who already profited immensely from the source code in question before the source was released. Most developers of FOSS never see a single dime and actually do it at net negative monetary benefit not to mention personal cost. All of that purely for the benefit of the collective.
Why do people feel entitled to GPL-licensed work? If you are producing code for a commercial purpose then you have the resources to pay for the code to be written.
Just because GPL code is in the open does not mean it’s wasted if companies can’t use it for their own profit.
In what context? You are planning on commercializing Copilot and in that case the calculus on whether or not using copyright protected material for your own benefit changes drastically.
> It's not anymore unusable over high latency links than most website.
That’s false. Not all web applications suffer equally from high latency links. Depends on how reliant the web application is on independent requests. Making one request and receiving a single bulk download is much less bad than making many dependent requests on a high latency link.
> you need it in client memory which can also be a dealbreaker
Most workstations have GBs of available memory. If not you can dump it in indexeddb as a raw data store.
I never disputed that it would be useful for some use cases. I only said it would be unusable with high latency links. If you have a low latency link and aren’t running very complex queries with lots of random seeks, then this should work fine for you.
Right but that is an artificially created demo by the author to justify the solution being presented (no offense). The question is how common are ~GB large SQLite databases in the real world relative to databases that are ~MB large?
In my experience SQLite databases of millions of rows of raw tabular data tend to compress very well into dozens of megabytes. Indeed SQLite is often touted as a file format for applications.
It’s not hilariously wrong or wrong at all that over high latency links this would be virtually unusable.
It’s certainly possible that people are using SQLite databases with sizes on the order of gigabytes but in my experience those are the exception not the rule.
Over high latency links this would be virtually unusable. Why not just download the entire database into memory over XHR on page load? SQLite databases of pure data usually aren’t over 10MB in size.
The source code enables the profitability of the assets. In the end the distinction is irrelevant to this matter. This is like saying Facebook doesn’t make money from its platform but from its deals with advertisers.