I think cloudflare is down right now: https://www.isitdownrightnow.com/cloudflare.com.html
Readit Newszubspace commented on Amazon Down – unable to view order history or make orders downdetector.co.uk/status... · Posted by u/tom-9999
It's so sad that we're the ones who have to tell the agent how to improve by extending agent.md or whatever. I constantly have to tell it what I don't like or what can be improved or need to request clarifications or alternative solutions.
This is what's so annoying about it. It's like a child that does the same errors again and again.
But couldn't it adjust itself with the goal of reducing the error bit by bit? Wouldn't this lead to the ultimate agent who can read your mind? That would be awesome.
It will never be fast enough to work in real time without compromising some aspect of the player's experience.
Ray tracing is solving the light transport problem in the hardest way possible. Each additional bounce adds exponentially more computational complexity. The control flows are also very branchy when you start getting into the wild indirect lighting scenarios. GPUs prefer straight SIMD flows, not wild, hierarchical rabbit hole exploration. Disney still uses CPU based render farms. There's no way you are reasonably emulating that experience in <16ms.
The closest thing we have to functional ray tracing for gaming is light mapping. This is effectively just ray tracing done ahead of time, but the advantage is you can bake for hours to get insanely accurate light maps and then push 200+ fps on moderate hardware. It's almost like you are cheating the universe when this is done well.
The human brain has a built in TAA solution that excels as frame latencies drop into single digit milliseconds.
The problem is the demand for dynamic content in AAA games. Large exterior and interior worlds with dynamic lights, day and night cycle, glass and translucent objects, mirrors, water, fog and smoke. Everything should be interactable and destructable. And everything should be easy to setup by artists.
I would say, the closest we can get are workarounds like radiance cascades. But everything else than raytracing is just an ugly workaround which falls apart in dynamic scenarios. And don't forget that baking times and storing those results, leading to massive game sizes, are a huge negative.
Funnily enough raytracing is also just an approximation to the real world, but at least artists and devs can expect it to work everywhere without hacks (in theory).
zubspace commented on Starlink is currently experiencing a service outage starlink.com/... · Posted by u/thallium205
Maybe I'm missinformed, but doesn't starlink have to comply with rules made by local authorities? Afaik, when the internet goes down, like it happened in Thailand, Starlink can't be used too, because it always roots traffic to a ground station near the source.
If this would not happen, I would agree that Starlink is the future. But as it is right now, I don't see the point, unless you are living in or travelling to remote places.
zubspace commented on You’re a slow thinker. Now what? chillphysicsenjoyer.subst... · Posted by u/sebg
I also thought about this a lot. Some things about slow thinking are great. I truly believe that it helped me thrive as a software developer.
But social interactions are awkward. I can't really come up with things to say easily and lots of times I can't respond in ways to keep the conversation going. Only after the fact I get lots of ideas of what I could have said. I'm truly impressed about others who can just come up with interesting or funny things to say on the spot.
I'm a tad older, so I stopped caring about it and just accepted my slow thinking. But I'm sure that I also missed out on a lot of opportunities regarding friendships or work. I still think, that others perceive me as awkward or just not fun and it's hard to just ignore that.
Funnily my wife is completely opposite to me and we have the greatest time.
They only need to succeed one time. People are generally preoccupied with a lot of other things right now, so maybe this is their lucky shot…
It's a shitty system, if one side just needs to succeed one time while the other side needs to succeed over and over again.
What really should be done is to disallow proposals, which are kinda the same. Once a mass surveillance proposal like this is defeated, it shouldn't be allowed to be constantly rebranded and reintroduced. We need a firewall in our legislative process that automatically rejects any future attempts at scanning private communications.
I get relentlessly obsessed until the thing works, or at least until some major milestone is met and the big problems solved. Not just for five minutes but days weeks months even years.
It’s really unhealthy behavior.
I know this behavior all to well. I definitely think that this can be used to your advantage: You learn alot in the struggle and get a deep understanding of the problem.
But you really need to step back once in a while and contemplate, if the thing you're doing is really worthwhile.
One of the most precious resources is time. I didn't appreciate this insight a lot while I was young. But as I grew older I needed to be more careful how you I was spending it. In this regard like I like the saying "youth is wasted on the young". But this also enables you to be more focused in your approach. Fail fast is a lot better than spending years on a problem with bo end in sight
zubspace commented on Why I no longer have an old-school cert on my HTTPS site rachelbythebay.com/w/2025... · Posted by u/mcbain
> So, yes, instead of saying that "e" equals "65537", you're saying that "e" equals "AQAB". Aren't you glad you did those extra steps?
Oh JSON.
For those unfamiliar with the reason here, it’s that JSON parsers cannot be relied upon to treat numbers properly. Is 4723476276172647362476274672164762476438 a valid JSON number? Yes, of course it is. What will a JSON parser due with it? Silently truncate it to a 64-bit or 63-bit integer, or a float, probably or if you’re very lucky emit an error (a good JSON decoder written in a sane language like Common Lisp would of course just return the number, but few of us are so lucky).
So the only way to reliably get large integers into and out of JSON is to encode them as something else. Base64-encoded big-endian bytes is not a terrible choice. Silently doing the wrong thing is the root of many security errors, so it not wrong to treat every number in the protocol this way. Of course, then one loses the readability of JSON.
JSON is better than XML, but it really isn’t great. Canonical S-expressions would have been far preferable, but for whatever reason the world didn’t go that way.
Wouldn't it just solve a whole lot of problems if we could just add optional type declarations to json? It seems so simple and obvious that I'm kinda dumbfounded that this is not a thing yet. Most of the time you would not need it, but it would prevent the parser from making a wrong guess in all those edge cases.
Probably there are types not every parser/language can accept, but at least it could throw a meaningful error instead of guessing or even truncating the value.