We use the simulator to generate test data that can be used to train an emulator. The emulator can be deployed as a model that provides the CRT effect in real time. We already have things like neural upscaling and denoising. This could be a similar idea.

How to live like a king.

Putting material like rockwool in the dead spaces can make an incredible difference in acoustic performance.

Automating browsers with LLM agents properly requires a lot more work than Process.Start into powershell, but the advantages can be immense once you have achieved integration this way. Incrementally maintaining this integration is generally easy because human users cannot tolerate rapid changes either.

It's a hell of a lot easier to convince management to adopt a robot that looks and acts like a human employee than one that looks like a combine harvester. The combine is far more efficient, but it is also totally indiscriminate. Nothing constrains its appetite except for the invisible fence imposed by GPS. The amount of infrastructure required to keep farm equipment from running astray is incredible. In the context of agriculture, the added complexity is definitely worth it. We don't want to have to recreate the same thing with our technology if it can be avoided. Sandboxes and security isolation boundaries are not things to aspire to. These are costs to be paid for admission to something more valuable.

The naive approach has the LLM interacting with the DOM using raw locators and javascript. If a human curates all logical views of the DOM and exposes tools that are only relevant for each, the search space for each agent iteration is reduced by many dimensions. I have achieved deterministic results over hundreds of actions in complex business workflows. Without the human curated layer we barely make it 10-20 actions before things get weird.

Most of my thoughts are currently occupied with possibility that this works in the general case. I think an LLM exercising a tool like GitHub via properly curated browser automation might be superior to direct API access in some ways.

The merge queue does provide serialization over change sets, but the ordering of these changes is very particular. Often, one change needs to go in before another change. The most common example I've experienced being database migrations.

It is a problem that ultimately must be solved externally. Speculatively deriving arbitrary order is likely to generate far more noise than signal in meaningfully complex merge scenarios. How many speculative orderings are we going to spend energy investigating before we find one we like / trust?

If you are in a situation where you have so much conflicting work that you think a specialized robot needs to be employed to sort it out, then you need to back the hell away from the technology and have a human conversation about the business and everyone's role in it.

Unity can literally deploy scenes to web canvases with its webgl target.

If you are going to use canvas, why not use the most extreme form of it with the most complete tooling available? You can put the universal render pipeline in anyone's browser in 5 minutes. These deployed web assets are surprisingly small if we are responsible with art.

Accessibility is even an option because we are leveraging a gigantic corporate engineering team and actually have time to try and solve this rather than reinventing basic layout and rendering concerns.

https://github.com/mikrima/UnityAccessibilityPlugin

Because programmers have generally been forced to wear additional, invisible hats that are essential to making the code happen in the first place.

Writing code is not hard. Writing correct code is. Knowing what is correct in a setting with paying customers generally involves interacting with those customers. Either directly or worse. The gigantic salaries paid to the most prolific employees is not due to their ability to write code. It is due to their ability to interrogate the shit out of the customer until they finally reveal the true requirements.

The problem is very few (none?) of them actually were. He was just a wizard at applying them. This furthers the utilitarian argument.

Comments URL: https://news.ycombinator.com/item?id=49222274

Points: 1

# Comments: 0

I could sit down with one other level designer / environmental artist and create something that would be visually competitive with Myst in record time using modern tools.

AI assistance is most dangerous (for your competition) when you mostly need it for the scripting and code, and not for the art or direction. You don't need an AI disclosure on steam if you use AI responsibly.

https://www.chevron.com/newsroom/2026/q2/chevron-signs-20-ye...

The transmission of energy is very expensive. Transmission of information is effectively free by comparison.

> As discussed previously, the ramp of HBM production will constrain industry supply growth in non-HBM products. Industrywide, HBM3E consumes approximately three times the wafer supply as D5 to produce a given number of bits in the same technology node. With increased performance and packaging complexity, across the industry, we expect this trade ratio for HBM4 to be even higher than the trade ratio for HBM3E. We anticipate strong HBM demand due to AI, combined with increasing silicon intensity of the HBM roadmap, to contribute to tight supply conditions for DRAM across all end markets. As the memory industry is still recovering from the challenging environment in 2023, this tight supply environment will help drive the considerable improvements in profitability and ROI (return on investment) that are needed to enable the investments required to support future growth.

https://investors.micron.com/static-files/4550f98c-1054-4847...

This is almost always the problem.

This is currently the problem that GitHub is having too. If they had remained with their crusty old rails architecture, very little of this mess [0] would be occurring right now. They would have been able to focus all their engineering talent on scaling the product rather than inventing elaborate client side state synchronization mechanisms.

[0]: https://www.githubstatus.com/incidents/qcvjkzcs7j74

I'm looking forward to the IIHS test results.

> Data received at each antenna in the array include arrival times from a local atomic clock, such as a hydrogen maser. At a later time, the data are correlated with data from other antennas that recorded the same radio signal, to produce the resulting image. The resolution achievable using interferometry is proportional to the observing frequency.

https://en.wikipedia.org/wiki/Very-long-baseline_interferome...

I think you would be amazed at how cost insensitive some Americans are and how large that cohort is. Ground beef would have to exceed $20/lb before I would consider altering my routine.

If you are buying one cut at a time and not being very efficient with it, the prices are certainly ridiculous. If each gram of beef is carefully prepared and allocated across weeks of meal prep, the economic situation changes pretty substantially. Batching effects can make it easier to afford expensive ingredients.

Going from 81GB of weights to 79GB of weights can mean a 50% reduction in GPU capacity required.

If you can fit a model in just one GPU (or rack) as opposed to across an entire datacenter, the latency gains can be substantial too. If you can reduce token latency by half, that would double the amount of customers you could support.

If you want the most 'optimal' form of this (aka, hell on earth), you should purchase a rowing machine. Being able to engage with very aggressive, full-body exercise every single day without exceptions is almost like cheating biology. You can maintain a 2-3x VO2 max premium over your peers with very little risk of injury.