HN user

doophus

25 karma
Posts0
Comments16
View on HN
No posts found.

Why though? What does changing `and` to `&&` actually achieve? Were people confused?

Also consider AI, that has a greater training base of JavaScript than Lua. So making Lua look more like JS, should improve output and reduce mistakes.

What was the missing piece for "shader sharing"?

Would it be possible to build a web-hosted database of encountered shader configs against a game id, and have Dolphin fetch that list when a game launches and start doing async compilation?

When Dolphin encounters a new shader that wasn't in the db, it phones home to request it to be added it to the list.

I feel an automated sharing solution would build up coverage pretty quickly, and finding a stutter would eventually be considered an achievement - "no-one's been here before!"

2. Store metadata about the current a* search in the graph nodes themselves so you don't have to maintain in a separate associative array.

This might be suitable in some circumstances, but it mixes your hot & cold data, prevents concurrent searches from being performed. Personally I'd steer away from this without an extremely good reason.

Yeah. In workrooms non-VR people can still join in. They appear as a video feed in the environment, and they see a rendering of the meeting from that perspective. It's still quite rich for everyone, eg you can tell when VR people are listening to you because they instinctively all turn their heads to look at your video.