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.
> 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
I linked to the reference docs, you linked to the usage docs. They're completely divorced from each other. There's not even a link from reference to usage docs.
For the reference docs to be useful you already have to know what the thing is, what it does, why you'd need it.
You can be on the component page where `viewProviders` is documented and get nothing from it if you're coming in fresh.
Why would ever design docs like that?
Angular is the only framework I've ever struggled to learn. It's a complicated framework but that's not the problem. The docs are the problem.
Which is strange. Google knows how to write docs. Or at least I've been very happy with the flutter docs. But now working on angular frontend is awful tooling wise. I don't even get useful inline docs for a lot of libraries.
> Which is strange. Google knows how to write docs.
Oh, they don't. Some of their teams know how to write docs for some of the products. A lot of the time it's autogenerated reference with a couple of bare-bones examples
ILM used Unreal Engine to make StageCraft and kept iterating on it until it’s the awesome tech that it is. They have a vested interest in seeing the underlying engine continue to prosper.
They made a point of highlighting the use of Unreal during the production of Season 1, but then it's completely absent from their discussion of later seasons, instead only referencing an in-house renderer they call Helios. Have they specifically said anywhere that they're still using Unreal Engine?
This 2021 article mentions that external productions using StageCraft services can choose to use either Unreal or Helios for rendering, so the Unreal integration may still be available for those who want it, but obviously ILM didn't write a brand new renderer for the fun of it. Unreal must not have been cutting it for their own productions.
> StageCraft leverages Helios ILM’s real-time cinema render engine. It is a set of LED screens that work as a 360 extension digital set, allowing filmmakers to explore new ideas, communicate concepts, and execute shots in a collaborative and flexible production environment.
"Ask HN: What's the state of the art for drawing math diagrams online?" (2023) https://news.ycombinator.com/item?id=38355444 ; generative-manim, manimGPT, BlenderGPT, ipyblender, o3de, how do we teach primary math intuition with the platforms that reach them, how do we Manim in 3 or even 4D?
> Is there a way to vary the [UE] AutoLOD for longer shots?
UE5 (and other 4d graphics and physics simulators) automatically reduce the LOD Level-of-Detail for objects in the distance.
Is that LOD parametric with StageCraft software?
(For example, reportedly Cities Skyline 2 is bad slow because they included meshes for characters' teeth and expected AutoLOD to just make it work on the computers kids tend to have. It doesn't work on reasonable machines because the devs all have fast pro GPUs to develop on, so they don't know what the UX is for the average family (that would be happy to turn down the polygon count themselves for what we can learn from the gameplay). Having game devs dogfood with real-world devices that families afford would be good for these firms too.).
Hopefully they'll continue to sell games through non-Epic stores that people have already invested in.
And hopefully, they'll make sure their products work with Proton and thus popular Linux-based handheld gaming devices.
This. Virtual Set Production is almost entirely Unreal engine. Fortnite is just a marketing platform. The real meat is the digital production pipeline that made Mando cool. That enabled Star Trek’s recent series’, and provides a “holodeck” for their just unveiled holo-floor.
I don't think Fortnite is just a marketing platform. They wouldn't have bothered suing Apple and Google over app stores if it were merely a loss leader to remind film execs that Unreal Engine is a thing.
While I agree with you that Fortnite shouldn’t be considered a loss leader, the strategy behind challenging Apple in court is more nuanced. Epic also operates a rather large software/games store and I am sure they would love to see it grow.
AFAIK Unreal was only used in the first season of the Mandalorian several years ago. Disney switched to using ILM's Stagecraft software, which is what they use for their films as well.
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'm glad there's a spiritual successor to Apollo, but it's not entirely about comparing one cost to one cost.
-
Spotify: $10.99/mo ($132/yr)
YouTube: $13.99/mo ($168/yr)
Twitch: $11.99/mo ($144/yr)
Narwhal: $6/mo ($72/yr)
-
You'd be right, the $72/yr for Narwhal is less than the $100/yr developer certificate, but with all of the other sideloading opportunities it's no contest w.r.t cost.
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.
> you're just being semantic for the sake of it a bit.
No. I'm calling it as it is. I don't pretend that something isn't a framework when it has all the same things that the frameworks they so love to vilify do.
> The Lit team are huge advocates of aligning with native standards
Which of the things that lit provides are native standards current or future? Its template DSL? Its custom decorators? Its data binding system? Tasks? Directives?
reply