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.
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.
Tanstack anything has breaking changes constantly and they all exist in perpetual alpha states. It also has jumped on the rsc train with the same complexity pitfalls.
Some libs in the stack are great but they were made pre rsc fad.
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...
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.
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.
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.
Yeah git rubbed me the wrong way from the beginning and I never learned it properly. My way makes the most sense to me. Stash? where? How do I get my files back? None of that is intuitive. I understand my way.
I love git stash, but to be fair, if you've just had Git do something unexpected to your files, I can completely understand why you would not then trust Git to keep your changes safe while you use more Git commands to get back into a sane state! Sometimes simple and well understood is the best way.
Anything can do something unexpected to your files if you don't put effort to understand it. Sure, some things require less and some more effort, but using tools without understanding them, while isn't impossible, isn't exactly a recipe for good outcomes.
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.
yeah so this means that if i want to use a page's font family but not its font size, the user has to do extra effort, and set not just `font-family: "Comic Sans"`, but also `--some-component-font-family: "Comic Sans"`. i'd love it if i could just selectively inherit stuff and not other stuff, without the user having to learn which css variables my thing supports. of course you can't do this with domain specific stuff, but you could make a thing fit kinda sorta well into its environment by default, and right now using a shadow DOM doesn't let you do that.
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...
Maybe this is obvious, but make sure to check your rate structure with your energy company. Just because market prices are high later in the day doesn’t mean that’s when your prices are highest.
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.
Sorry for the late reply. That all makes sense. And it’s definitely possible that your power company’s rate structure isn’t really optimal for them (or the market, or you). Electricity rates seem to be generally messy and a mix of big compromises, in my experience.
After giving my electricity provider access to my EV for optimal charging pretty much killed the 12v battery (they were pinging it hundreds of times an hour, meaning it never went to sleep), I'm never going to give them access to anything.
I had no idea this was a thing that could happen, I thought (naively, I suppose) that all they'd get would be the equivalent of a meter reading with a suggestion to limit load at certain hours.
You can setup the integration in the app, but disconnecting requires you to send an email with absolutely zero acknowledgment that it's not going straight into /dev/null
My rush hour went off yesterday afternoon and the temp rise made me doze off and i woke up sweating with it set to 80 degrees. I'm in the process of canceling, it's not easy. I used the chat and someone is going to send me an email (which says it's canceled?) within 24-48 hours.
Harder to turn off than anything else in recent memory. If anyone has a pro tip on an easy way to cancel let me know.
When I had them hooked into my EV, I literally had to change my Kia password when they ignored my requests to disable the feature.
Presumably they similarly have some sort of cloud permission into your thermostat, which can be disabled by changing the password, resetting the device, or worst case scenario, get a new thermostat.
Wire them both up so that your cheap thermostat provides hard upper and lower limits.
Your HVAC doesn't care where it gets a 24V signal. An open relay won't mind being energized from the "wrong" direction. AFAIK, thermostats won't tattle.
They got back to me and wanted to do a phone call to unenroll me. I told them they could do it without speaking to me since I don't have any power in the process, so we got to skip the phone call. I'm officially out of rush hour.
> 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
Either you are not reading it right, or there is a problem with your thermostat's demand response schedule, because the only way demand response makes money (hence rewards for users) is by reducing demand during net load peaks, because that completes with the high marginal cost of fossil spinning reserves.
Demand response also targets gross load because (assuming the renewables are not entirely rooftop solar) that electricity still needs to be carried by wires to consumers.
Sizing transmission for the absolute yearly peak is not cost effective, so various schemes are used to reduce that peak, including efficiency improvements and demand response.
This is entirely separate from questions of renewable cost and carbon and pollution and makes economic sense even on 100% fossil grids.
> Sizing transmission for the absolute yearly peak is not cost effective, so various schemes are used to reduce that peak, including efficiency improvements and demand response.
Nonetheless, voluntary curtailment of demand by consumers (for any objective) must be compensated, right? And generally speaking, demand response curtailment (especially on shorter notice) is compensated at a higher rate than peak energy rates (4x in my area). It shouldn't be the case that one spends more money by participating in a demand response program that not participating, which is what the OP implied.
It seems like it would be more grid efficient to use more power at 3-5pm to cool your house to temperature early while solar is still high in availability then to rush and cool from 5-6 when you get home.
The current rate structure for anyone not paying spot rate does not incentivize that of course.
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 have the Enhancer for Youtube extension which solves this problem.
And maybe I'm being an anti-change curmudgeon but the previews below seem to be putting more emphasis into engagement chasing social media by having Google try to convince users to click one more video. It's more distracting from the video you're watching than having it to the side in a widescreen monitor.
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.
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.