Readit Newsyuchi commented on <template>: The Content Template element developer.mozilla.org/en-... · Posted by u/palmfacehn
yuchi commented on Show HN: Real-Time Gaussian Splatting github.com/axbycc/LiveSpl... · Posted by u/markisus
The output looks terribly similar to what sci-fi movies envisioned as 3D reconstruction of scenes. It is absolutely awesome. Now, if we could project them in 3D… :)
yuchi commented on Nine – seemingly impossible C64 demo linusakesson.net/scene/ni... · Posted by u/appleorchard46
Posted it few days ago but didn’t get any traction. All Linus’ work on retro computing is fenomenal. Please have a look at its channel, a lot of awesome content there.
yuchi commented on JavaScript Temporal is coming developer.mozilla.org/en-... · Posted by u/SigmundurM
The vast majority of websites should be calculating dates in a server and merely presenting them to clients.
I have wondered why there isn’t a span style element which takes a UTC timestamp and presents it to the user in their preferred time zone. I even wonder if it could be done in private way so that JS cannot even access the value (made more difficult by layout and size).
Similarly a form element for date times could simply return the UTC from the local choice.
I am just wondering out loud and not an expert.
A lot of calculations may happen on the client. And the server may be written in JavaScript.
yuchi commented on JavaScript Temporal is coming developer.mozilla.org/en-... · Posted by u/SigmundurM
Very sad that .Now is not a function call. It shouldn't be a property.
Evaluating .Now multiple times in a loop will yield different values, which is unexpected.
C# did the same and it shouldn't have been:
https://ericlippert.com/2014/05/19/when-should-i-write-a-pro...
I think you got it wrong. Now is a namespace for functions that retrieve the actual values, such as Now.instant()
yuchi commented on Coding Machines (short story, 2009) teamten.com/lawrence/writ... · Posted by u/yuchi
Since the dissertation by Ken Thompson about compiler trustability was quoted today, I thought it would be a good idea to bring this short novel back from the archive. Loved it years ago and still is very enjoyable.
When you actually design interfaces you discover that there are way more states to keep in mind when implementing asynchronous loading.
1. There’s an initial state, where fetching has not happened yet
2. There may be initial cached (stale or not) data
3. Once loaded the data could be revalidated / refreshed
So the assumption that you either are loading XOR have data XOR have an error does not hold. You could have data, an error from the last revalidation, and be loading (revalidating).