I think they're creating enough trouble for themselves anyway just by constantly shooting themselves in the head. Also moving on is probably the least good thing for them. Losing users gradually will bleed them to death.
mfz
joined 1 year ago
OMG! Some great quotes in there: "The real disease is VIM" and "I spend more time customising my computer than actual using it" and of course "I treat my whole life as a text buffer"! (EDIT: Fixed spelling)
It is a conversational tool that can generate decent code if properly prompted but it lacks for the most part enough context. For it to be really useful it has to be able to be trained on my entire project that I'm working with, not just a single file or function.
What I miss is the ability to "chat with my project". I.e. have the whole project in the trained context, and then reason about architectural changes, pros and cons, have suggestions for refactoring, help with complex renaming schemes and moving code, etc.
It would be super interesting to be able to give instructions like:
- Organise my files by dependency and the logic they implement.
- Or something like, create web components from common input elements in my html pages.
- Where is the user auth code implemented?
Things like that.
I’ve been thinking a bit about this lately since the Reddit migration started. I believe it could be solved at the client level at least. Unifying magazines over instances and behind the scenes pull in and follows twin magazines at other instances and presents them in a single abstract magazine.
There are probably reasons why you at the server level or user level want the low level community access and behavior we have today but judging of all comments and how we typically behave as humans I would say that is rather the unusual case not the mainstream.
Such users could easily then opt in at the instance level and everyone else looking for a more “centralized” experience can still have that through the client app.
No doubt it would take some work but I believe it is very doable given my understanding of the Activity Pub protocol and how it works today.
First rule of fediverse: Don’t talk about the fediverse.
Signup and there is also an intangible more positive feeling here at kbin.
The instance name is part of your handle. Think of it like an email address. With a domain part.
Yes, yes, and someone else's problem will be your problem after the job hop! :)