Can someone explain how Claude Code can instantly determine what file I have open and what lines I have selected in VS Code even if it's just running in a VS Code terminal instance, yet I cannot for the life of me get OpenCode to come anywhere close to that same experience?
The OpenCode docs suggest its possible, but it only works with their extension (not in an already open VS Code terminal) with a very specific keyboard shortcut and only barely at that.
If you're using an alpha library then that's on you for not expecting breaking changes. They have plenty of 1.0+ libraries that do not receive any breaking changes between major releases and have remained stable for well over a year.
Also, you're just wrong? You literally cannot serve RSC components _at all_ even in TanStack Start yet. Even when support for them is added it will be opt-in for only certain kinds of RPC functions and they will work slightly differently than they do in Next.js app router(where they are the default everywhere). RPC != RSC.
Plus you can always stick to using TanStack Router exclusively (zero server at all) and you never will even have to worry about anything to do with RSCs...
I would highly recommend just checking out TanStack Router/Start instead. It fills a different niche, with a slightly different approach, that the Next.js app router just hasn't prioritized enabling anymore.
What app router has become has its ideal uses, but if you explicitly preferred the DX of the pages router, you might enjoy TanStack Router/Start even more.
If you're happy with tRPC and don't need proper REST functionality it might not be worth it.
However, if you want to lean that direction where it is a helpful addition they recently added some tRPC integrations that actually let you add oRPC alongside an existing tRPC setup so you can do so or support a longer term migration.
ts-rest doesn't see a lot of support these days. It's lack of adoption of modern tanstack query integration patterns finally drove us look for alternatives.
Luckily, oRPC had progressed enough to be viable now. I cannot recommend it over ts-rest enough. It's essentially tRPC but with support for ts-rest style contracts that enable standard OpenAPI REST endpoints.
This going to sound out of left field, but I would venture to guess you have very high spatial reasoning skills. I operate much this same way and only recently connected these dots that that skill might be what my brain leans on so heavily while programming and debugging.
Pair programming is endlessly frustrating beyond just rubber duckying because I’m having to exit my mental model, communicate it to someone else, and then translate and relate their inputs back into my mental model which is not exactly rooted in language in my head.
The later CRT models you are describing here are not coveted by retro gaming enthusiasts (which the people involved here clearly are) since the digital nature of them meant they introduced a ton of processing that negates the near zero input lag all earlier analog CRTs benefit from. Many of the later digital models can actually be had for much cheaper these days than the full analog ones despite looking more powerful on spec sheets.
While this is true for much of Texas. I happen to live in a city that still has a public operator. So we just get more generalized flatter rates. I haven't looked into the details of my plan closely in a while as a result though, so you might be right.
En masse though, it seems not ideal from a cost perspective the way things have been scheduled up until now. I'll give them the benefit of the doubt that it might be adjusted better in the future.
If I'm reading this right, my thermostat's "rush hours" seem to be scheduled for gross load peak. They then seem to usually end (and kick my AC back to a desired temp causing a ton of usage) right around net load peak...which this is now reporting is when energy prices go through the roof.
So basically the "rush hour" program has likely been costing me more money than if I just ignored them to begin with up to this point. I do realize these programs are primarily about limiting peak gross load and not saving individuals money but maybe I won't go out of my way to abide by them now...
Agreed, I always need to scroll to see video description content and comments which I would rather be able to see while still watching the video.
While, instinctively, the previews below the video feel odd because they've been to the right for so long. Logically, I can see the improvement they are going for here and would welcome it.
I mean would you rather the browser handle this at a lower level where it can do so efficiently or libraries continue to solve these things on the main thread with pure javascript? The defacto way to handle anchoring views today is with something like Floating UI [1] and that doesn't even handle portaling content to root of the DOM except for in React.
> Have a reasonable developer tell me what a component viewProvider is and how it’s different from a provider using the @Component docs. It’s impossible. https://angular.io/api/core/Component#viewProviders
The recent overhaul of Narwhal for version 2 reworked the entire app to operate pretty close to what Apollo was at its core. It's extremely customizable as well. Their new subscription plan for covering the API costs is pretty fair and would be cheaper than what you are doing here.
I mean they have to be for now - you're just being semantic for the sake of it a bit. I will say as a team that utilizes Lit for our design system web components (which none of our users even need to know or care about no matter their framework btw). The Lit team are huge advocates of aligning with native standards (now or what they might be in the future) and working to establish or push them forward. The goal of the project for a lot of these issues truly seems to be to eventually not need them to be a part of Lit at all.
So your gripe is essentially you don't like reading the documentation of the libraries you use, just, in general?
Template literals are just a feature of javascript, it's not even anything that bespoke. That's why it's called "lit". The output of those tag functions are just rendered with standard DOM features too.