Hacker Newsnew | past | comments | ask | show | jobs | submit | jassmith87's commentslogin

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.


That's great to know! And important to clarify because by default WSL has access to all disks.


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.


are hackernews commenters legally obligated to chime in with intense pedantry that is completely irrelevant to the larger point in order to feel like they are smarter than the person theyre responding to?


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


r/wellactually


This exists too! O.o


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.


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


why is styled components required? seems like concerns arent well separated in this one


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


Thanks!


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.


This is only part of the reason. The other reason is that Apple doesn't actually do fractional UI scaling, they only ever render into a framebuffer at whole integer multiples of an internal "native" resolution and then scale down this framebuffer to the actual monitor resolution afaik (they still render natively to this multiplied resolution - no doubled pixels or anything like that).

This results in less crisp output than you would get if you actually rendered vector based UI at the exact monitor resolution or if you natively rendered bitmap art 1:1 with the monitor resolution.

This approach makes sense when you're only using Apples monitors because they can optimize their internal "native" resolutions for the handful of actual native resolutions they offer, but it falls apart when you start plugging in external third party lower dpi monitors.

(I believe this is also the same approach that Gnome 3 uses to do (experimental, with a toggle) non integer multiple UI scaling.)



Oh interesting, I was wondering why my HP (Ubuntu) laptop looked sharper than my Macbook on a QHD monitor.


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.


would be so awesome if Glide was easy to package into a Svelte project!!


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


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: