211–220 of 239 posts
Earlier quoted context omitted.
To be expected, given how many organisations now require employees to use AI if they want to meet their OKRs, especially all that sell AI tools.
What's dumb, on top of everything, is needing to store non special standard operating procedures in specific AI folders and files when wanting to work with AI tooling.
Earlier quoted context omitted.
I had previous experience with WASM on TEE. Just use the foreign function interface. Remember WASM isn’t native code so you still need other native code to run WASM (such as wasmtime), and you can import other native functions into WASM through the runtime.
Native functions that are no longer sandboxed, defeating the whole purpose.
The use case here was to use a KDF function from the TEE, and I assume it serves as an oracle where the actual key material cannot be revealed.
Earlier quoted context omitted.
Microsoft employ over 100,000 engineers. I'd advise against assuming that everything produced by any of them is bad because of bugs in Windows.
Not op, and I generally agree with your assumption but not for Microsoft, as I don't think it's limited to Windows: Teams, Office (especially online), One Drive, SharePoint, Azure, GitHub, LinkedIn, all became very shitty and partially unusable with increasing number of weird bugs or problems lately.
WFH, flood of Dev hiring, increasingly hostile worker relations, a bunch of web 2.0 folks finally retiring, VC money drying up...
take your pick.
Software is just crappy these days.
Earlier quoted context omitted.
NTFS will perform directory B+-tree lookups (this is where it walks the path) until it finds the requested file. The Cache Manager caches these B+-trees. From there, it hits the MFT, finds the specific record for the file, loads the MFT record, and ultimately returns the FILE_OBJECT to the I/O Manager and it bubbles up the chain back to (presumably) Win32. The MFT is just a linear array of records, which include file…
Heh, first I've heard of Windows Internals. New friends for The Linux Programming Interface!
Also worth tracking down a copy of the NT OS/2 Design Workbook on the web (another leak).
And Inside the Windows NT File System by Helen Custer is a very short book but describes the very early state of NTFS capabilities/functions.
Earlier quoted context omitted.
Yes, but the OS fundamentals are for Azure first, Windows last. Azure makes money, 50% of Windows computers are basically free and need to get you to sign up for a subscription some how. The other 50% are Windows Pro/Enterprise, but MS assumes they'll get that money forever so doesn't put any resources into that. In 10 years the kids switching to Linux on desktop today will be in charge of the business deals and swit…
They are not free. OEM costs money. Hence with every laptop with Windows preinstalled, you pay a fraction to Microsoft, even if you immediately uninstall and add Linux.
From the GitHub page: LiteBox is a sandboxing library OS that drastically cuts down the interface to the host, thereby reducing attack surface. It focuses on easy interop of various "North" shims and "South" platforms. LiteBox is designed for usage in both kernel and non-kernel scenarios. LiteBox exposes a Rust-y nix/rustix-inspired "North" interface when it is provided a Platform interface at its "South". These inte…
> - Running unmodified Linux programs on Windows This might actually be my favourite use: I always thought WSL2 was a kludge, and WSL1 to be somewhat the fulfilment of the "personality modules" promise of Windows NT.
Edit! Memory unfuzzed: It was Workplace OS, https://en.wikipedia.org/wiki/Workplace_OS
Earlier quoted context omitted.
What a ridiculous excuse. People who join ICE to brutalize minorities and protestors are just trying to feed their families too, then. No? Working for Microsoft doesn’t make them bad engineers or bad people, but it does make them Microsoft employees. And they get to bear its reputation whether they want to or not. If it makes them uncomfortable then they should make a change or grow thicker skin. Oversaturation of th…
Do you have kids? If not, I agree with you. Make the hard decision and take a loss. And thank you for your sacrifice. If you do, I can't agree with you. Also I wouldn't compare software development for a marketing company with a violent disagreeable effort. There's bad and there's worse, objectively. Anyway, not saying you're wrong, but I'm not so quick to judge someone by a job that they probably hate. Or to wrap 10…
Yeah, tech monopolist that enables genocide to contemporary gestapo isn’t an equal comparison. But my point was that you can’t ignore the moral hazards of employment by handwaving “gotta eat somehow”. There are a million ways to feed your kids. Saying you have to work a high paid job to feed them non-GMO certified organic produce from Erewhon because that’s the only standard of living you can possibly survive with, that’s a choice.
I also want to reiterate that I’m not judging the people who choose to work there. I’m just saying that by signing the employment contract they accept the reasonable public perception that the products they work on are shit. And to some marginal degree, they are complicit in all their employer’s wrongdoings.
Earlier quoted context omitted.
They are not free. OEM costs money. Hence with every laptop with Windows preinstalled, you pay a fraction to Microsoft, even if you immediately uninstall and add Linux.
But probably only $10
Earlier quoted context omitted.
Native functions that are no longer sandboxed, defeating the whole purpose.
Any pure code (WASM or otherwise) that does not perform any input/output is by definition useless. It consumes electricity to do computation and there is no way to communicate its results. The use case here was to use a KDF function from the TEE, and I assume it serves as an oracle where the actual key material cannot be revealed.
So no, they are absolutely not useless, they are just "single-shot" models of computation. Certain software fit that model very nicely (e.g. compilers), others less so.
[flagged]