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.

Glide Data Grid has that and is open source. https://grid.glideapps.com

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.

You might enjoy this site: https://jsgrids.statico.io/

We ran into the same issue! We actually implemented a feature we joking call clown-car scrolling to handle this. If you want to steal the basics of it you can see it here: https://github.com/glideapps/glide-data-grid/blob/main/packa...

Feel free to steal and improve, we only enable the clown-car mode when the desired scrollable area is larger than what a browser can support. With our implementation scrolling is still handled by the browser, but the scroll location can be subtly recomputed as you go from time to time. We only do this when interacting with the scrollbar directly to avoid weird artifacts like scrolling feeling faster than normal.

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.

I maintain https://grid.glideapps.com if you're looking for something ludicrously fast.

Glide Data Grid has a fully accessible DOM subtree. No need to sacrifice accessibility just to use a canvas. Come on, its 2022 we have the tools. What makes Canvas even nicer is I can export a subdom that is bespoke for screen readers. It is exactly what the screen readers want, nothing more, nothing less. It works wonderfully.

Disclosure: I am the primary developer of Glide Data Grid.

If you're the EU yes. Not so much if you're the US.

Nat comes from the Microsoft side, not the GitHub side.

There is no way they fired him. He is leaving by his own choice.

Many people within Microsoft felt that he was a clear contender for Satya's eventual successor.

We've been using Replay heavily here for the past 6-7 months and it's rapidly become the preferred way to do any form of debugging. Training our support staff to capture replays and submit them in tickets has made turn around time on bugs significantly faster.

Hi all, I'm one of the core authors of this project. I know it is still early and we are very excited to show off what we have even though it still has some major limitations. Just to answer some questions that have come up in the past:

- No we don't support a11y yet, but we do have a plan for it.

- Yes this is all canvas except for the overlays

- It doesn't do filtering/sorting for you, but you can implement it

- You can override rendering

- You can theme the default rendering

If you have any more questions I am happy to answer! If you need a data grid I genuinely hope this helps you and we will be maintaining and improving this grid for years to come I am sure.

There are thousands of other registrars out there. GoDaddy doesn't want them, they can move to someone who does. Once they've gone through them all and been rejected by every last one I'll accept that maybe maybe something should be done. Then again if you are being rejected by every single registrar out there maybe you should look inward for the problem.

You might not make any money and then California wouldn't get any money!

We've been using fly.io for a month now. They are amazing. The service is great, the team is great, and most importantly our apps have seen a dramatic performance uplift by leveraging fly. A++ would use again.

Full disclosure: I am another YC founder. Fly did not ask me or encourage me to post this in any way.

Seed and Series A is investment in the people always. They assume if the product doesn't work the team will pivot until they find something that does. It sounds to me like your friend failed to pivot when needed.

They already were doing this before Microsoft, so yes... yes they would.

I have been in desktop and mobile dev my entire career. Starting doing web dev 12 months ago for a new job. Never once have I thought to myself "I should figure out what float does".

Grid + Flex + Block + Absolute covers all layout needs. It's funny to me because conceptually these ideas have been around on desktop/mobile layout systems forever. That they are only now making it to the web is insane.

Its intended to fuck over Facebook. If you're charging for a service you can simply offer a discount for allowing data collection after bumping prices for everyone by the same amount, Facebook however isn't charging. Facebook can't offer a discount on free, and they can't just force only users who opt-out to go pay (because that falls afoul of the first quote you put).

Basically this puts Facebook in a real tight situation, I honestly wonder how they will survive it.