notnullorvoid

6 ms·

91.
by notnullorvoid 4mo ago
The one time I did run into coloring being an issue was when working with gevent/greenlets (green threads) in Python nearly a decade ago. Implicit management of async operations is something I hope I never have to deal with again.
92.
by notnullorvoid 4mo ago
I'm surprised we still let Jony Ive design anything.
93.
by notnullorvoid 4mo ago
Ive's style may be inspired by Dieter Rams, but he ultimately fails to emulate it in any positive way. Ive's work is bubbly symmetric bland crap.
94.
by notnullorvoid 4mo ago
Good time to focus on more memory efficient means of training and inference. SeedLM from Apple is an interesting approach for inference memory efficiency. I'd like to see someone try and build that into training so that it's not a
95.
by notnullorvoid 4mo ago
Their interests and morality have been evident for a long time.
96.
by notnullorvoid 4mo ago
As others have noted only the div is allowed. This isn't a unique situation either, the HTML spec despite being lenient in syntax is quite restrictive in behavior. It's unfortunate that XHTML (and XML parsing) didn't become t
97.
by notnullorvoid 5mo ago
A lot of these changes seem geared toward adopting Node/NPM default DX. To the point where Deno DX (or what it was previously) now comes second. The worst of the changes is "lib.node included by default", if I'm writing
98.
by notnullorvoid 5mo ago
This is a really odd change. Deno already supported installing npm packages, this only removes the "npm:" prefix requirement for cli commands. Considering the nightmare that is npm, I was quite happy for jsr to become the defacto
99.
by notnullorvoid 5mo ago
It sounds a lot like DNT ( https://github.com/denoland/dnt ) which has existed for a long time, but having it in Deno cli does bring significant visibility.
100.
by notnullorvoid 5mo ago
They may share some goals, but also have differing and opposing goals. But it's possible that all 3 Deno, Node, and Bun could share some code in the future considering they now all require Rust as part of their build process.
101.
by notnullorvoid 5mo ago
No I don't mean like that. Explicit permissions control what the extension can do, similar to websites needing explicit permission to access a users camera. An example is a theme extension with permission to change the theme, but havin
102.
by notnullorvoid 5mo ago
Running binaries I already have installed in a containerized environment is fine, automatically installing them on host machine and/or container is not. I should be able to limit what binaries extensions have access to though.
103.
by notnullorvoid 5mo ago
Thanks, after seeing this and others talk about it silently installing node and other tools that's enough for me to dismiss it as a viable option.
104.
by notnullorvoid 5mo ago
How so? Part of what seemed good about Zed was that extensions have explicit permission controls.
105.
by notnullorvoid 5mo ago
> Migrate off vscode already. Zed is the closest thing I've found to meet my needs, and I do plan to try it. However it's dev container support looks to be lacking in some important ways so we'll see.
106.
by notnullorvoid 5mo ago
In my testing Bun wasn't much faster most of the time, usually on par for all non-IO related stuff, and there were some cases with scheduling where Bun was noticable slower.
107.
by notnullorvoid 5mo ago
Yeah, the only thing that gives me hope is the optics of this happening to GitHub. Though it seems possible VS Code team could double down on the opinion that this isn't a permission/sandboxing problem, and is instead a scanning&
108.
by notnullorvoid 5mo ago
I said limit post install, not remove them. Having an allow list in package.json of packages which can run post install would work fine. Pnpm already does this. Having said that I'm not against full on removal of post install either. I
109.
by notnullorvoid 5mo ago
I really hope this pushes Microsoft to add a explicit permission system to VS Code extensions, and improve security of dev containers.
110.
by notnullorvoid 5mo ago
Wow that was way more Apple simping than I expected. It'll be funny when WWDC happens and Apple has even less of substance to say.
111.
by notnullorvoid 5mo ago
Limiting post install as an attack vector is still a good thing. Node is working on a similar permission model to Deno that allows explicitly granting certain system resource permissions https://nodejs.org/api/permissio
112.
by notnullorvoid 5mo ago
All of the videos have rather glaring consistency issues when direction shifts back to areas previously shown.
113.
by notnullorvoid 5mo ago
Judging by the examples it wouldn't be useful for that, the environments show little physical consistency.
114.
by notnullorvoid 5mo ago
Same reason people work at any of these big companies, money and prestige. You can be a terrible engineer, but if you have a few years experience at Meta it's going to make people think you must be a great one.
115.
by notnullorvoid 5mo ago
I've been gaming on Linux (Fedora) exclusively for ~10 years, and in that time able to play any new release that interests me so long as it doesn't have egregious client side anti-cheat.
116.
by notnullorvoid 5mo ago
Either. If you want Nvidia features like DLSS then go with NVidia.
117.
by notnullorvoid 5mo ago
Nvidia on laptops is fine. There was a time that it was really difficult and the easiest route to success was to disable the Intel iGPU, and force Nvidia GPU to handle everything in BIOS. That hasn't been the case for a while, and you
118.
by notnullorvoid 5mo ago
You can still use the old drivers they work fine. This also isn't unique to Linux, Nvidia's latest Windows drivers also don't support 10 series cards anymore.
119.
by notnullorvoid 5mo ago
Again it's not about typing speed. High level plans simply don't work very well, especially for big tasks where the optimal solution actually would take 2k lines. Unless you are building something that is extremely generic, AI com
120.
by notnullorvoid 5mo ago
> Bad engineers continue being bad, good engineers continue being good. Unfortunately I have seen some really good software engineering peers regress into bad engineers through a increasing reliance on AI. Conversely some very bad engine

More ›