jassmith87

You can turn all the interop and mounting of the windows FS with ease. I run claude in yolo mode using this exact setup. Just role out a new WSL env for each claude I want yoloing and away it goes. I suppose we could try to theorize how this is still dangerous buts its getting into extremely silly territory.

Regret implies you wouldn't have regretted the other option, which is often not the case. It is entirely possible, and sometimes likely that you will regret your decision no matter which decision you make.

I am the author of GDG. If you have any questions feel free to let em rip.

r/wellactually

Why settle? There is a reasonable shot of forcing musk to pay a 200% premium. $3-5 billion is a steep discount. Twitter should settle for nothing short of specific performance.

It’s used for the overlay editors. It’s on our list for things to remove in the next major release.

Even ag-grid isn’t accessible by default. You have to turn on their accessibility mode for it to play nice with screen readers which obviously has negative implications elsewhere or it wouldn’t be an option.

The problem is you have it plugged into a macbook. Apple doesn't support subpixel anti-aliasing in any of its latest releases. Your monitor looks so fuzzy because Apple has removed the capability to make it not look so fuzzy.

It can be done if you are using a Canvas to provide the rendering. The canvas can then be provided with a subdom that does not render but is visible/interactive to screen readers which matches exactly what the screen reader requires. Canvas's actually have the advantage here if they put the effort into being accessible.

You could do the same trick by hiding the visible DOM from the screen reader and creating an invisible DOM explicitly for the screen reader. If your DOM structure is wrong for the screen reader I would suggest doing this.

Would you mind taking a look at grid.glideapps.com and letting me know if/where it doesn't work for you? We are always looking for feedback. Development is done entirely in the open, feel free to just file issues and open discussions on github.

Thank you! DataGridXL has been my text only benchmark for a long time because of how ludicrously fast it is! Downright creative problem solving!

I've done a lot of work on data grid accessibility. In fact, DataGridXL is one of the many grids I considered for our own needs a couple years ago. The reality here is unless you somehow export out a DOM structure which has an element per cell, for at least the cells that are on screen, you will never be able to get the screen reader to behave correctly. If you were using a canvas you could export a subdom on the canvas, but with the approach y'all take with the line-height + dom node per column I don't see how you get there.

The cell nodes need be browsable and selectable by the screen readers caret. You could do what many other DOM based grids do and add an "accessibility mode" but I believe accessibility should be the default and not a mode people turn on as a checkbox. Let me know if you want to chat, I'm always happy to share what I know. I'm by no means an expert but I've definitely picked up a thing or two.