Ashwinning | 1 year ago | on: Show HN: Quadratic – native JavaScript support in a spreadsheet
Ashwinning's comments
Ashwinning | 2 years ago | on: Show HN: Unity like game editor running in pure WASM
Gotta give this a shot on desktop later.
Ashwinning | 3 years ago | on: Electric vehicle battery capable of 98% charge in less than ten minutes
Ashwinning | 4 years ago | on: Belarus 'diverts Ryanair flight to arrest journalist', opposition says
Ashwinning | 5 years ago | on: Ask HN: What's your quarantine side project?
Ashwinning | 9 years ago | on: Ask HN: Who is firing?
Ashwinning | 9 years ago | on: Ask HN: Who is firing?
Ashwinning | 11 years ago | on: Pin-pointing China's attack against GitHub
Ashwinning | 11 years ago | on: The Web Is Dying; Apps Are Killing It
Ashwinning | 11 years ago | on: Cascaded Displays: Spatiotemporal Superresolution using Offset Pixel Layers
Ashwinning | 11 years ago | on: UK Police placing anti-piracy warning ads on illegal sites
Ashwinning | 11 years ago | on: Cascaded Displays: Spatiotemporal Superresolution using Offset Pixel Layers
Personally, if this takes off, I can see it saving the XBox One's ass, as a lot of the complaints from gamers have been regarding it's inferior capabilities for rendering high-end games (It renders many games at 720p 30 frames/second, while Playstation 4 is able to crank out 1080p for the same titles), and also, play another factor in prolonging the shelf life of the present generation of consoles, by enabling them to deliver much better graphics with the same hardware. Kind of like what Normal Maps (among other things) did for Xbox 360 & PS3, you can see the difference in graphics between a game released in 2005 vs a game released in 2013 on the same hardware. Among a lot of other factors, that was why it took 7 years before we saw the next generation of consoles being released. Comparatively, the Xbox 360 came out within 4 years of the release of the original Xbox.
TL;DR - It's not about the display hardware itself, it's about the ease of rendering graphics to meet the demands of high-end display.
GSheets has let me write JS (Google Script) in the spreadsheet (w/ multiplayer, free db & API hosting like features with a little bit of JS, ++) and now has some Gemini support rolling in.
Excel is rolling out support for Python and Jupyter as well.
I'm trying to wrap my head around who the ideal user/customer is here w/ a hair on fire problem, and what problems are being addressed that are overlooked by the 2 most popular spreadsheet tools.