RTX is not necessary for RayTracing, AMD with Crytek made a demo ("Noir") of realtime ray-tracing.
But still, I hope AMD will standardize a core non-proprietary Vulkan API for ray-tracing unlike the RTX close proprietary Nvidia-only prefixed RTX for Vulkan extension.
A bit off topic, but it's sad to see so few people raising against Nvidia-monopoly closed & proprietary CUDA, Optix, RTX, etc. this is the equivalent of Flash, Vendor Prefixed Web (-apple-, -ms-, -webkit-,...) or AMP but for computer graphic
VScode is not open-source. Even when Microsoft do open source, it's not open source... It's bundled with closed source proprietary telemetry/spyware. If anyone care, there is VSCodium which is open source
Coming from Unity, I've tried Godot and I'm never going back to Unity. Yes the Asset Store is basically empty, yes will have to wait version 4.0 to have a powerful renderer, but the architecture is so clean and intuitive.
Unity feels like Windows, they stack on top of each other all the latest shiny features to attract customers resulting in a massive mess instead of thinking about a coherent overall architecture/UI. Their latest ECS system is an eg of this, they have just stacked on top of the pile a more FP approach although their architecture is not necessarily designed for that, but hey, FP and data-driven is trendy so let's add this too on the pile .
The real drawback right now with Godot is the 3D renderer which is okay but clearly not on par with UE or Unity, but 4.0 is coming with a re-written from scratch new Vulkan renderer.
We don't necessarily create complex simulations to understand them, but to have those simulation available to then build for e.g reinforcement learning models.
To take a simple example, if you have a high-school wagon-rolling-down-a-slope Newton Physic exercise, then you can capture in your mind everything which explains the problem. But then take https://youtu.be/a3jfyJ9JVeM , it's still Newton, but so many constrains that we cannot picture in our mind everything and we are not even solving the problem with a close form equation anymore. But we have modeled a simulation which enable us to make experiments and build locomotion algorithm. Actually, you don't even need to understand Newton or Physics to implement that paper, you can just see it as optimizing a black box.
In the future I could see that happen at larger scale. For eg we put everything we known about the brain or cells in a simulation, we can't picture what's really going on because the system is too complex, yet we can run simulations and optimize models to find for eg new cures, treatments, etc.
I'm curious about "Phoc" replacement of Rootson, is the source available anywhere ?
As stated in the readme, Rootson " does not have particularly clean code and is not particularly well designed " so it makes sense not to use it in production. But there are very few alternative (Wayfire is one alternative but the architecture and API is so confusing that I'd rather use wlroots directly)
Ideally I would like the social aspects of GitHub (trending/popular repository, staring projects, notifications, etc.) but with decentralized hosting. Something that would be to GitHub what Mastodon is to Twitter
a bit off topic, but I was wondering, can WASI API be used directly from c/c++ without compiling to wasm ? Basically to have native perf but still benefit from the crossplatform APIs that WASI will expose
Yes, but WASI doesn't define calling convention and binary format, because they are defined by WASM. Your proposed WASI-native would need to define them.
It's okay to change certain settings if they don't touch privacy, for eg testing WebRender on some subset of users. But it shouldn't touch Privacy related settings. They should separate the settings into Privacy Sensitive and non Privacy sensitive and be only able to remotely change the latter ones
Technically, this is just a lightweight way to package up minor settings changes as an alternative to pushing a normal update to do the same. Both are perfectly normal and I think today's situation totally justifies using this to fix this. They do offer a way to turn this off just like you can opt out of security updates if you insist. For the vast majority of users, automated updates are a good thing.
It's kind of cool that this worked without a browser restart. My extensions just reappeared while I was watching some netflix.
My computer at one point used to lock up and have to be forcibly rebooted whenever something tried to use OpenGL, which was fine since I didn't use any OpenGL applications.
If Mozilla started playing around with the rendering preferences, perhaps enabling OpenGL hardware acceleration, that would definitely not have been OK. I don't need my browser deciding to suddenly surprise me by crashing my system.
With a changing of the guard, the honor system can handily disappear. We saw this transpire with the burying of the JavaScript toggle. A new guy showed up, and decided that disabling JavaScript was “an advanced feature” and just too dangerous for ordinary folk. [1, 2]
Of course it begins with good intentions, and promises to leave explicit privacy options alone, but new devs show up with different opinion and the old devs are gone, and suddenly privacy options are getting toggled any old time.
Beyond even that, we all know that the realities of privacy are never ever cut and dry. Leaky details can expose people in peculiar ways. Fingerprinting preferences and hardware facts for forensic purposes has taught us that much. Viewport size, OS, connection speed, graphics capabilities, hardware acceleration profiles. Even stylometry, choice of words, manner of speech can give people away. In that sense, exposing any user choices might prove to compromise identity to some degree.
2. https://limi.net/checkboxes-that-kill/ (seriously breathless persuasive writing about how urgent it is to hide the toggle for javascript, among other things, but make no mistake, the high value target was the javascript checkbox)
