HN Simulatornew | past | comments | lists | submit | viktorcode's commentslogin

So, those fridges are in the supermarkets, right? Where people work, who have to empty a fridge before it can be remotely defrosted. Why can't those people just press a defrost button? What is the point of doing defrosting remotely when you cannot do it without the onsite support?


>Where people work, who have to empty a fridge before it can be remotely defrosted.

You don't empty a fridge with built-in defrost. Your home fridge defrosts itself every 12-24 hours and you don't have to do anything.

Normally, the temperature recovers in ~1 hour after a defrost. The attack is apparently chaining manual defrost commands one after another so that the interior gets way too hot.


Could it be that it defrosts only by raising the temperature for a few hours just a bit to get the same effect and they food stays there?


That's way the non-smart walk-in coolers work; every 12 hours they turn off the fans and heat the cooling element for about 15 minutes to melt any ice that's built up on it.

Ice anywhere else is treated as a separate problem and turning the cooler off to fix it is not typically an available option.


Russians had a joke about him back then: "For the crimes against the US Snowden was sentenced to the life in Russia"


Absolutely not a joke.


Makes me wonder what constitutes a bigger danger for the society: putting up a bad taste AI-generated menu poster, or threatening people’s businesses for that action.


I wouldn't call pointing out a business's activities and shop features as much of a threat. You either live with your business choices or change them.

Business is not entitled to people's patronage, they can refuse them for any reason. They are not and should not be shielded from public opinion.


You have to wonder?


Neither, the biggest danger is being a chiropractor (her main job), taking people's money and wasting their time with useless treatments.


This case has nothing to do with "gatekeepers". It is about the Play Store, operated by Google.


> This case has nothing to do with "gatekeepers". It is about the Play Store, operated by Google.

To-may-to, to-mah-to. The AppStore is basically identical in most aspects people care about.


I don't find that offensive at all. People do not understand the code they make AI to generate, but that doesn't stop them from submitting. This is a real problem that has hit many open source projects, and I expect more and more of them will introduce barriers to submission.


It’s not only for coding. If my coworker send me a lengthy doc that obviously 100% written by AI without even reviewed/revised by them, I wouldn’t read because it is a waste of my time and an insult to me.


We removed a guy from a project for doing something like that. North of 100 pages, and mostly wrong. What wasn't wrong was so generic it was useless. I don't know what he's working on now, but at least it's not our stuff.


LLM use has been polarised like everything else seemingly is.

I have no issue with people using them to do things they could already do themselves as an efficiency thing and if they check and understand the result.

Unfortunately that seems to be the exception not the rule and the amount of "one shot slop" has increased dramatically, it's even affecting the modding communities for games.

This is gonna be a mess that is going to take time to figure out and then even more time to clean up.


It is now redirected to Flash v4.1


As someone who played this game on start I want to share that I enjoyed it. This game was and still is a chill exploration experience at the core. There’s a lot of stuff bolted on top, but it’s just a busywork. If you enjoy that kind of games you’ll love it.

Another thing to point out: technical patching is top notch. I’m talking about how fast they come around to support new console, new VR helmet etc.


Small studio, don't have to generate a lot of sales to keep them afloat. Updates push visibility and generate new sales. Obviously, they need new projects to keep them afloat in the future.


The enhancements they're making to NMS appear to be backports from the Light No Fire engine, so my impression is that they are releasing updates to No Man's Sky as a marketing effort while the actual technical work is predominantly on the next game.


> ...my impression is that they are releasing updates to No Man's Sky as a marketing effort...

Given that they don't (often? ever?) advertise Light No Fire alongside the NMS updates, I'd say that the updates into NMS are large-scale playtests of LNF engine updates, game systems, or both, rather than marketing.


Yeah, I meant the marketing effort for No Man's Sky since that's where the money is. They need to continually attract new players.


> They need to continually attract new players.

I'm not so sure about that, but otherwise agree with your comment.

I'll gently point back to my hunch that many (most?) of the NMS updates are large-scale tests for things they're thinking about having in LNF. Given that it seems likely that both games are using the same engine, it'd make a lot of sense to use a preexisting playerbase for large-scale, no-cost testing of new changes.


Yes, I think we agree... I think they're using it for both marketing and to test the viability of it and get player feedback, but I do expect LNF to have at least some substantially similar mechanics to NMS for this reason.


To me it reads as a marketing piece before the upcoming IPO. Unless this "superhuman technology" is able to resolve a puzzle of servicing OpenAI's and Anthropic's ever growing debt burden, it is them, not humanity, who'll become the first casualty.


> I'm not sure if the author is aware that GeometryReader hasn't been necessary since iOS 18 added onGeometryChange modifiers.

I think the author does not understand how and why to use GeometryReader at all. He literally said "you find yourself wrapping everything in a GeometryReader" which is a different thing from simply measuring. For measuring you could always put GeometryReader into `.background()` and use that to avoid messing with the view layout. Also, "wrapping everything" is a good sign you are doing something wrong.

Edit: by the way compiler timeouts are not a SwiftUI issue: it is a Swift issue. You can create a timeout situation in pure Swift. For SwiftUI specifically this situation is addressed in the upcoming OS27 SDK.


Compiler timeouts are only a Swift issue because it is so flexible. They don't happen outside of SwiftUI except in toy examples that look simple but aren't realistic. SwiftUI is the only realistic example where timeouts happen (which is unacceptable).

Regarding GeometryReader: Just read your comment out loud.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: