Did someone say... Xonsh?! It's tough to give up the niceties of zsh and it's various plug-in ecosystems, but I would love to be able to use Xonsh [1] as a daily driver for exactly the reasons stated. It is already the language I lean on over bash for most utility scripts with its kitchen sink built-ins.
Infamous for it's bad UX? This thread is genuinely the first time I've ever heard this, all of my extended circles were overjoyed when Discord came onto the scene and displaced the patchy, hodgepodge UI's of Mumble, Ventrilo, IRC, Skype simultaneously. Both from a feature and a visual perspective it was a breath of fresh air for the programmers, gamers, and casuals alike for everyone I know. Maybe the only thing that still survives alongside it for the folks I know as a preferred communication channel is sporadic Whatsapp among the EU guys and iOS group chats for the Americans locked into the Apple ecosystem.
What about it makes it terrible UX for you? Feature set seems to get better every year as far as I'm concerned, inclusion of ads aside.
My single biggest complaint, other than it being an Electron app, is their insistence on changing the notification sounds seasonally. I do not want surprise Halloween music when I'm trying to start a video call with someone, nor do I want it themed. You can offer it, sure - I get that it's free, and they're trying to keep users on their platform - but it's just grating to me.
I love Mumble and IRC. You could put a gun to my head and I still wouldn't use Discord. When all these proprietary chats are dead and the kids have moved on to something else, Mumble and IRC will still work. They are eternal. Anything proprietary and centralized can't compete with that. IRC outlived AIM and MSN and so on.
my latest annoyance is the way they keep making the gift nitro button bigger and more likely to be where you tap when trying to send a message. I don't know what their PMs are smoking to think that gifting nitro is something people do so often that there needs to be a permanent flashing button on screen to do it.
To be honest, I don't think most people's first interpretation of someone's claim to a "Discord-esque feel" when describing the UX of their open-source IRC client is that it's therefore riddled with dark patterns to sell an upgraded version of the service. I think it's probably more likely that they were referring to the general layout (eg: having circular server icons as a vertical list on the left hand side). I'm guessing that that's also why they mentioned Slack, since that has the same layout too.
If it performs the overall function but the code is a mess, then you can ask the model to describe parts of it, the structures and what the structures are for. When it shows you something that is messed up, suggest a better framing for the same thing and ask the model to implement the better framing without regressing on already passing tests.
I'm going through this right now on a very difficult to implement task, the original was python and very verbose. But had facilitated a rust implementation that produced byte identical outputs. Then I asked it for what data was being passed around, placing restrictions on what passed between interfaces I could tell it what parts should be immutable and what parts should have no presence outside it's local context. Placing those limitations while having a exemplar of what it should be doing gives it little choice but to make better code if it meets the conditions set while at the same time not regressing.
I say things like 'this field is a implementation detail in a declarative data structure, it should not exist here.
This can mean hours of work with no observable change in program function, yet it is directly addressing the limitations that prevents it from being used in larger tasks.
Yes, how does the LLM make a difference there? Inexperienced developers write bad code. Hell, experienced developers who are outside their domain write bad code too, then you later realize that it's hard to read, or that it leads to architectural problems or such, and hopefully learn from the experience.
> This is a chicken and egg problem I find hard to resolve with LLMs. If we're pushed to delegate most work to them, how do you build that expertise?
Learning from LLM written code is significantly and meaningfully different from struggling on your own or learning from more experienced human co-contributors. Especially in a large, complex, iteratively developed codebase.
Worse, once you're in that situation you are now at the juxtaposition of:
"I did this. I understand what my reasoning was, and now I know why it is wrong and how to fix it" vs. "An LLM did this, I don't know why it did this, I'm not sure what it was trying to do or what pattern it followed and I'm not sure how to make it better because I didn't write or understand the original implementation either"
Is it impossible to learn and gain experience this way? Not at all. But it's definitely not equivalent.
Will second this, as someone that took the same path. Alternatives like Fastmail are so, so cheap when compared to the headache of building, maintaining, and troubleshooting a DIY stack. For something as fundamental as email you really want to choose the solution that gives you NO problems, rather than some solvable but troublesome problems at regular intervals.
Just too critical of a component in most people's lives to accept any level of unknowns in.
Hats off to the folks behind this for keeping such a cool project alive! This, ReactOS, and TempleOS have been my answer to the question of: "what should I install if I'm looking for something interesting?" for at least a decade. Obviously for vastly different reasons.
Did someone say... Xonsh?! It's tough to give up the niceties of zsh and it's various plug-in ecosystems, but I would love to be able to use Xonsh [1] as a daily driver for exactly the reasons stated. It is already the language I lean on over bash for most utility scripts with its kitchen sink built-ins.
[1] https://xon.sh/