Zed’s agent ui is the most confusing ui I have ever seen. Tiny and vague icons, clicking on ‘x’ sometimes closes the editor, sometimes an agent and sometimes a panel, hard to figure out what it will do. I wanted to try zed with new features but this unpredictable behaviour made me uninstall it. It also doesn’t support opencode Go which I am subscribed to.
Can you please share what kind of issues you have faced with each tech stack choice and how the next one resolved it?
The reason I am asking because recently after getting tired of plumbing different npm packages I decided to use blazor server with dotnet 10 to leverage high quality first party packages (e.g. efcore, identity etc) to build a product. I am halfway there, sometimes I miss React & Typescript due to enterprisey nature of dotnet but AI helps me to overcome it. So far doing well with it.
I think nowadays they are perfectly fine. Blazor Server had lots of disconnects because our customers typically don't have a stable Wi-Fi connection. Blazor WASM had next to no tooling. It was dotnet 5 or 6, so still very early on the WASM journey of dotnet, not much or no documentation and no AI to overcome initial hurdles.
tbh I sometimes miss React & TS too, for the frontend React is just straightforward, and TS is no bad language at all
I started learnig rails a couple of months ago. I took a ruby crash course and opened rails guides.
The thing discouraged me to go further was that many sections has work in progress label. I thought I might be looking at the beta docs, but no. I checked the same page down to multiple major version and the work in progress was label was still there.
Coming from Django/Laravel world, incomplete docs discouraged me to try rails.
Hi! The documentation team commissioned by the Rails Foundation is working on tackling and editing the guides one by one, and removing these WIP tags once a guide is complete.
We should see a huge reduction by the time the project wraps, but because Rails itself is constantly evolving, so to is the documentation, so you will continue to see them from time to time. Consider it a sign of growth, not stagnation.
I develop company's internal tooling using Blazor Server, and have developed moderately complex and data intensive applications. As a former React Developer who has spent most of his time working with Node.js and JavaScript tooling, Using Blazor WA and Server felt like a breath of fresh air. C# is joy to write and everything fits very well with existing enterprisy Microsoft services.
State management is pain in React, until you install 3rd party libraries (Jotai, Zustand etc.), each value needs to be bound individually.
Dotnet command line felt very snappy compared to npm/pnpm.On my crappy company laptop, when a nextjs application dev server starts, my blazor server app has already opened a browser tab with website running locally. efcore is also good.
Overall working with blazor felt like working with Vue/Svelte, but with faster performance on backend. Nowadays I only touch React if strictly necessary.
I would actually suggest buying the Hays translation of Meditations instead of reading the free versions. The language in every other version is overly verbose and archaic.
Indeed, I agree. I'm ~70% through the translation by Gregory Hays. FWIW I've picked up this translation after some research; there are several of them. Hays' translation also as a nice reference on related reading in the book's introduction chapter.
Laws of power is nice but what always bothered me about it is that there doesn’t seem to be a system to the laws, it merely sums up a bunch of them without investigating underlaying foundations.
