I can recommend watching the free documentary "The Microsoft Dilemma - Europe as a software colony" which highlights and explains how they target corrupt branches of the government, with under the table deals for specific threats and doxxes against politicians, up until "shilling" as government officials when they are not even working there, creating fake email addresses on their tenant's email domains to make it look like they have an administrative say in decisions in other teams of the projects.
Imagine this being an automated workflow. Where the microSD card is both a bootable image and also an encrypted recovery / LUKS partition, which includes the BIOS flashing mechanisms and OS install mechanisms.
The temporary OS must keep some personal data in tact, otherwise you'll end up with a full search. So the "not so private data" has to be discoverable.
That would be tails on steroids, and help a lot of journalists and reporters while crossing borders.
Flashing the BIOS would probably be the hardest part, considering that libreboot will raise suspicions.
> Rust, Go and others have been building WASM 0.2 support for many years, they currently have a “just works” support...
Can confirm. I was pretty stubborn and wanted to use Go to build a UI in a webview/webview using local app, but oh my, js.Value in Go is so much pain to deal with. A lot of things in the JS world don't integrate nicely with Go as a language (e.g. the difference of Go channels and JS Promises, or magical enum values _and_ URL patterns on the same properties like in the Fetch API)
Long story short, I am now around 3 months into building a WebASM bindings and components framework, and it's still a lot of work until I am on the functionality level of TSX files. [1] All those Web/DOM/Browser APIs are kinda hard to integrate into the Go world, especially if you're as stubborn as me and want to have a real typed bindings API that uses Go's native data types.
I am not sure if you have seen that there's a flagging war going on on HN lately. The commenter probably didn't link on purpose to prevent that.
Just saying that we need a more neutral medium for the HN crowd if that kind of discussions afen't allowed. Turning a blind eye to what's going on is what got us into this mess.
Linking – or better still, quoting – makes me more comfortable vouching for comments. (I vouched here, because the discussion below the comment is worthwhile, but the comment itself is practically unreadable.)
I couldn't find anything related MCP servers or tools that were offered to the agents. Wouldn't it be much more likely to succeed if there was e.g. a gdb server or an sqli/http server running for debugging purposes? That way the thinking process could succeed more easily, no?
Note that it was an almost 4 year old already disclosed CVE which was used. Oracle messed up, big time. That's why they're trying to get rid of all incriminating evidence for potential lawsuits.
I am just thinking out loud. Wouldn't it be better then to just share the reproducible recipes similar to sharing Dockerfiles? For wine, specifically, it could be similar to just using FROM wine-1.23. As long as we keep the recipes maintained and "pinned" to their old dependencies.
I think this could work as a translation layer because containers already abstract away everything on syscall level.
There must be just a GUI for that, which can create multiple sandboxes easily, per application, and remember what you configured and installed there (and add it to the Winefile).
In regards to the sharing serials problem: You can easily diff the .reg file that wine adds there and if anything pops out in \\software, you can assume this is a custom field and offer it as an environment variable for the container?
I would add in second place Skunkworks and the A12, which is the perfection of aviation technology in my opinion. It's just such an insane piece of technology, in every part you take a look at it gets more and more absurd of what's in that plane.
And if you build an airplane so absurdly advanced that 70+ years later people still think it was aliens that built it, you've set your mark in the history books.
Third place in my heart takes the Rutan Voyager [2] which essentially pushed its efficiency so hard that it coincidentally invented the design for modern delivery drones.
Last year I was also in a Windows 7 rabbit hole. There's lots of ongoing stuff in the community, and even huge driver packs for Ryzen hardware.
The website that led me down that hole was the one from "spacedrone808" [1] who appeared regularly in /r/windows7 mod posts and issue trackers.
There's also the snappy driver installer project [2] which shares a 44GB torrent with all kinds of drivers, from SATA controllers to NIC to GPU. There's also driverpacks which is sometimes down, sometimes not. In the web archive of either of those you can still find the torrent links though.
Oh and there's driveroff [4] which led me down the rabbit hole of Russian hacking communities that backport software to win7, which is amazing to see that there's this isolated modding community on the internet that uses hardcore win7 modded variants, with self-built firewall software, backported hash file databases for antivirus tools etc.
I’ve long suspected that a Linux desktop environment designed to closely mimic Windows 7 (with light modernization where it makes sense) would prove popular, and the existence of all this reinforces that idea. A rough facsimile can be built using KDE, Cinnamon, or XFCE, but many details will still be wrong (and aren’t practically fixable without forking) and I think that’s enough to prevent many users from considering Linux as a viable alternative.
Windows Vista/7 screwed up file associations badly, you can do far less with them than you could under Windows 95. Under Windows 95, you could customize the right click menu for any file type, and add all your favorite programs to that menu as a different option. That's gone since Vista, which added in the buggy "Open With" submenu.
The worst is that today, if you associate Icon files with an icon editor, Icons suddenly lose their ability to display themselves, and instead turn into pictures of the associated application!
I am not claiming Compiz was first. It's just the one I still use so it happens to spring to my mind. (My own laptops run Ubuntu with the Unity desktop.)
As far as know, Apple invented the concept of a display compositor using 3D hardware. If anyone has prior art from before 2002 I'd love to know.
I am not sure I personally consider that closely enough related to count.
It often seems to me that even today Amiga fans are so passionate about the machine that they make rather exaggerated claims that do not really stand up.
For instance in many places I have read the claim that AmigaOS was a microkernel OS, or closely-related claims such as that it was the first widespread microkernel, or the first GUI microkernel, and so on.
The point of a microkernel is that only the microkernel runs in kernel space (in x86 terms, in Ring 0) and the rest of the OS is divided into multiple "servers" which run in user space (again in x86 terms, in ring 2 to 3). This in turn brings a problem, which is how to make comms between the microkernel and the servers fast. IPC is the big problem and that is what microkernel OSes struggle with, which has shaped the design of Mach, XNU, L4, seL4 etc.
AmigaOS is small but everything runs in ring 0. There is no division and so there is no need for tricky performance-critical IPC and all processes can read and write each others' RAM. That makes it (1) easy (2) fast (3) not a microkernel.
I would regard direct blitting into 2D windows as not unique, not the first such implementation, and not the same as 3D compositing.
In AmigaOS, everything runs in unprivileged mode, except for some specific critical code within exec.library which runs in supervisor mode or interrupt mode.
What's true is that exec.library does offer a call to run code as supervisor[0], and that there's no memory protection.
FWIW I am also linking to AmigaOS 4, MorphOS and AROS...
I wish "Notch" Persson or some other billionaire nerd would just buy the things and declare the whole lot freeware. There surely cannot be much residual value to extract any more.
Maybe, but there’s no reason why a thoughtfully engineered Win7 clone DE on a lightweight Linux couldn’t run just as well or better on the same hardware.
Your opinion. Win 7 was the best Windows UI, both in looks (Aero) and usability. It was abandoned primarily because Microsoft was trying to achieve some hybrid desktop/tablet/mobile UI that worked poorly for all form factors. Win 11+ (or whatever the next version is called) would be well-suited to return to an Aero-like UI.
Similarly I went on an XP odyssey late last year. I acquired a retired workstation from $dayjob that I decided to turn into a retro XP game machine. It was very late for XP but within a generation or two before Intel, Nvidia and the motherboard provided drivers (Ivy bridge and GTX 660 GPU).
But that didn't get you through the installer... I discovered a plethora of alternative install media with built in community drivers providing support for nvme drives, modern ACPI extensions etc.
It's so complete you can install it on today's current hardware.
GFE and its replacement "nVidia App" are bloated and large, but the drivers themselves are still 600-900MBs each.
That "optimized for Game X" thing where GFE/nVidia App brags that the driver has all sorts of custom relationships with all the recent exciting games is strangely literal in most cases because the drivers include a frankly wild amount of application/game-specific microcode/optimizations.
https://m.youtube.com/watch?v=duaYLW7LQvg
Yt-dlp while it's hot. Microsoft sure sends DMCA takedowns after this one.
reply