blourvim

was pretty good

It reads really well

You can also hire teams to create data for you for higher quality.

As is your right, I don't understand the negative sentiment around this. This is an MIT license,

"... Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software..."

A maintainer is all within their rights to decide what code to accept, and it is your right to fork it. If you decide to share your fork with the world with a similar license, the world too can fork your software. That is how it worked for decades now.

People don't usually patch their software on their own, as it takes resources to do that. Even for a small change, one usually will have to recompile now and for every update,Also operating within a fork, you will get much limited help from the upstream whether that is further patches, or community support, it tradeoff within authors rights.

You could have limited-instruction llms where the model does one thing, for example summaries. It could accept a limited amount of instructions for example, first token for verbosity, second for style etc...

These models rely on knowledge that are embedded in their weights, if a new library is released, a new linux version comes out, some new protocol succeeds the previous one, you want your llm to know about it. Sure you can just add that into the context window, but that has its own problems.

Unless new research, there are a few which look promising, gives a new method, training is going to be a constant cost sink.

On top of this, if you stop training, it is 6 months until someone releases an open weights model and now you are competing to give the lowest price for the same product.

Also we can't forget that this is a business that *has to* be in the global labor industry, not just a tech tool, they have to have much better models to justify the trillion dollar evaluation

The web server is able to detect and change the response of a curl | sh thus a malicious actor could avoid some detection.

Having a binary also allows for antivirus software to be ran on it before deciding to run the binary itself or not.

I am not sure if curl | sh bypass sandboxing by default, but definitely is the case when compared to flatpak or just regular packaging

Training is expensive, to keep selling tokens, they have to have the best model. They have to keep spending money on model training

A product or a platform could give them a moat, but they don't quite have that yet although I think they are looking to get there

quite satisfying to hear the clicks

What I don't understand is that if a lawsuit happens, then must the plaintiff produce their source code for verification ? Even so a git tree is trivial to change into some other arbitrary code even if a license violation has occurred. I also heard if proven the consequences are that they would lose all revenue starting from when the violation has occured

Thats a big sometimes for me. I am unfamiliar with the app development process. For backend,I would rather design the whole thing from scratch rather than try to fix a broken architecture. For frontend, maybe that is true, but I haven't had the chance to build anything complex, just forms and tables.

I am a backend dev, and building a mobile app for the first time, It is a toy sized project right now and it works, would have indeed taken me 5x the time to get to that point on my own.

I know from experience that to make it a non-toy project I am probably going to need to spend some, if not most of that saved time cleaning up in the future due to technical debt.

For backend, it is mildly useful at best, helpful with boilerplate and when I know exactly what needs to be built. I have not yet firsthand experienced these 10x, 100x productivity gains.

Frontend, forms,tables and generic dashboards is pretty good, I am sure one could get it done faster and better over the long term with proper technique and methods, but I just hate css

Ah, wise words. There is still time indeed

Mildly disappointed that it is not the dystopian adpocalypse we were warned against