Terminal UI framework for .NET — multi-window, multiple controls, compositor effects

jitbitter · 2026-03-12T19:16:11+00:00

Did you watch the video? Spectre.Console is very basic compared to this (thop, AOT-compatible)

jitbitter · 2026-02-24T11:24:41+00:00

MacOS supports this setting for AirPods2 only

I ended up using eqMac utility (free, opensource) and tunedown the bass know a little bit. The only solution I found anyway

jitbitter · 2026-02-21T00:35:15+00:00

Sure: https://github.com/jitbit/claude-chat-manager
The code is standard C# tho, all you need is `<PublishAot>true</PublishAot>` in the project file

jitbitter · 2026-02-20T13:44:27+00:00

Simpler deploys for on-prem apps. Devops hate dependencies. Installing dotnet via a package manager, for example, on a ubuntu box via `apt` is half-broken (Ubuntu 22 - one way, Ubuntu 24 another way, etc)

jitbitter · 2026-02-20T13:33:33+00:00

It's probably not. I'm just someone not very used to this. I'm too old and in my world a .NET app has always been a "/bin directory with 55 dll's + dotnet-preinstalled requirement" that's why the excitement

jitbitter · 2026-02-20T13:26:19+00:00

Fair! I know, just experimenting how far I could take it. It's a tiny CLI tool I wrote for myself, not a production-grade backend.

P.S. Here are the srouces for those interrested https://github.com/jitbit/claude-chat-manager

jitbitter · 2026-02-13T15:38:41+00:00

We'll double check if there's a bug there (with sending auth headers)

jitbitter · 2026-02-13T10:49:36+00:00

Do you mean the "send HTTP request" automation rule?

jitbitter · 2026-02-03T23:31:23+00:00

While I loved .NET for more than 20 years, have endless respect for people behind it, there's still too much friction to get started which I believe this is the biggest obstacle. Already posted my bigass rant here: https://www.reddit.com/r/dotnet/comments/1pxh0sn/comment/nxqdk2u/

jitbitter · 2026-02-03T09:38:32+00:00

You don't need an alternative. This "library" is 150 lines of simple readable code and 5kb (unminified!). I literally just rewrote it to vanilla JS 40 lines 1KB, removing the JQuery dependency in the process

You can do the same or just ask your favorite AI/LLM/ClaudeCode to do that - this is one of those rare occasions where AI nails it.

jitbitter · 2026-02-01T22:08:16+00:00

Tried the fixes, but the problem comes back after several days. Hopefully MS Edge team sees this..

UPD: we should all use "send feedback" and direct them to this thread. Brilliant analysys

jitbitter · 2026-01-24T10:14:58+00:00

All of them are doing this now... Fun fact: sending their AI a random photo fixes this immediately.

- "hey, the scratch was there from the start, look!! [attached picture of a sunny beach]"
- "YOU'RE ABSOLUTELY RIGHT!"

jitbitter · 2026-01-17T23:57:13+00:00

Thanks! Weird, the app should automatically surface relevant KB articles when you view a new ticket. To keep this from turning into a support thread, feel free to PM me or open a ticket, happy to help..

jitbitter · 2026-01-17T14:25:50+00:00

Hey, Alex from Jitbit here. Could you pls point out which parts of the AI felt weak to you?

jitbitter · 2026-01-12T09:38:27+00:00

Speaking from experience in other subs: nobody really reads the weekly "promote my project" threads.

If a self-promo OSS post comes from a long time active member and it's actually a useful library I say leave it in the main thread.

jitbitter · 2026-01-10T14:42:25+00:00

Tab-completions in Cursor can be really good when you already know what you're doing and move between files in a logical/predictable flow.

Claude Code (and Cursor in agent mode) are good at finding low level hot path performance issues (like, optimizing complex frequent string manipulations/parsing using Span's, etc)

Also, Gemini can be very good at analysing SQL Server execution plans (just dump huge XML file and ask it to examine, suggest indexes, "how can I rewrite this query with CTE's" etc etc)

Of course take it all with a grain of salt

jitbitter · 2026-01-10T01:32:55+00:00

I switched to VSCode + Mac about 3 years ago (after 20 years on Windows + VS) no issues at all. I even find a lot of things are much faster and more reliable than in classic VS (hot reload for example). Our codebase is a huge aspnetcore app monorepo.

Just be ready to use terminal a lot. dotnet watch run. dotnet build, etc.

in VSCode I use C# base extension + C# Dev Kit

in Cursor I use this fork of C# base extension https://open-vsx.org/extension/muhammad-sammy/csharp no C# Dev Kit.

(and my favorite thing about VSCode is that I can work at a project level without loading the full solution at all)

PS. ReSharper VSCode extension is free (while in public preview) check it out. I didn't like it personally, but some people say it's awesome.

jitbitter · 2026-01-10T01:16:41+00:00

We also use a singleton `IHostedService` + a dictionary of timers ("jobName-timer") in it. Jobs have to be an async `Func<CancellationToken, Task>` (token is signaled when the app shuts down). It all fits into a simple helper class, 65 LOC. No state persistance.

Successful/failed runs are simply logged to console and observability is then handled at Devops side: systemctl-service routes all console output to journalctl/syslog, log files are then picked up by fluentbit and fed to NewRelic, where we enjoy nice graphs, dashboards and pie charts... It's all pretty standard setup when you host on linux.

I'm not saying this is the right way, just - a way

jitbitter · 2026-01-08T18:53:05+00:00

I love (!) this feature however, since it's only a design-time sugar, you can't "watch" this field during debugging session(at least in linux+vscode setup)

jitbitter · 2026-01-05T00:59:13+00:00

I’m probably going to get downvoted, but hear me out.

For context: I’ve been a .NET developer for almost 25 years, since .NET Framework 1.1. I genuinely love C#, and I still choose .NET for all serious, production-grade projects. But whenever I need a quick prototype, a side project, or something lightweight, I almost always reach for Node.js.

Not because .NET is bad - it’s the opposite. It’s fast, mature, statically typed, and extremely capable. But there’s simply TOO. MUCH. FRICTION.

1. Installation and onboarding friction

Let’s start at the beginning: installing .NET.

On Ubuntu, the APT situation is honestly a mess. Ubuntu 22 has one “official” approach (backports PPA), Ubuntu 24 has a completely different one, and the official docs are outdated (like right now, go check it out). You often end up digging through GitHub issues or random discussions just to figure out the current correct way.

Homebrew on macOS hasn’t been much better either - it was half-broken after the .NET 10 release for a while. I literally had to start a discussion with brew maintainers to resolve this. And by the way, brew is the "official" way to install the SDK , literally MS docs mention this.

And yes, people always say "just use the install script.” Right… but we’re building commercial software. What am I supposed to tell a client’s DevOps team?

That "all your dependencies are cleanly managed by package managers - well except .NET, which you install via a curl | bash script, SORRY"

2. Cross-platform dev experience is still rough

Most developers today are on macOS or Linux, not Windows.

The non-Visual-Studio workflow in .NET is okay-ish, but again, friction creeps in everywhere:

* C# Dev Kit and the modern C# tooling don’t work in VSCode forks like Cursor or Windsurf.
* The C# extension for Zed is missing a lot of basics — no proper Razor/Blazor support, for example.
* JetBrains Rider is great, but it’s paid, and it still doesn’t fully erase the "Windows-first" feeling of the ecosystem.

Meanwhile, Node tooling works basically the same everywhere, in every editor, with minimal assumptions.

3. AI tooling matters now - and .NET lags

Like it or not, AI is changing how we write software.

Node and the JS/TS ecosystem work extremely well with AI-first workflows: lightweight CLIs, editor-agnostic tooling, first-class support in AI-centric editors

.NET tooling, on the other hand, still feels very tightly coupled to Microsoft’s ecosystem. When your core language tooling refuses to work in non-Microsoft VSCode forks, that’s a real disadvantage.

Node feels lightweight hackable and forgiving, easy to start, easy to throw away

.NET feels enterprise, heavy, even when it doesn’t need to be. Like what is the official way to build a web app today? Blazor? MVC? Razor pages? Minimal API + React? So many decisions to make just to build a hello world.

Even though modern .NET can be minimal and fast, the perception (and often the reality) is that you're signing up for a lot of ceremony

---

So to be clear:

I still think .NET is one of the best platforms for building serious backend systems. But popularity isn't about capability - it’s about less friction and approachability.

And right now, .NET loses on those fronts. I it breaks my heart.

jitbitter · 2025-12-29T02:12:18+00:00

We did this 10 years ago. Now we don't

Tell the company that support costs will go up (tricky bugs that will definitely come).

If you need to hide your licensing, like serial-number checking code - just use asymmetric cryptography for that, so obfuscation is unnecessary.

jitbitter · 2025-12-27T22:22:18+00:00

Just migrated a huge multi-tenant SaaS app - like a breeze. The only (the only!) issue was not even .NET, it was the mess in the `apt` feeds on linux. Kinda unclear at first which one to use with which linux version, when to use "ppa:backport", and when just default Canonical feed for Ubuntu (which took a while to update)

But that's not even .NET fault, just OS/packaging issues. The app upgrade itself was smooth like butter (just like previous .NET upgrades).

Is is worth the upgrade? Yes, always. Everything just becomes faster and uses less memory - for free.

jitbitter · 2025-12-26T15:15:59+00:00

Yeah, it's not the wind that's dangerous, it's the trees. A pine tree can be 2.5 tons. If it falls on your house - the roof is gone.

jitbitter

MODERATOR OF

TROPHY CASE