It was simply "Ghost" before Norton bought it and made it more terrible and bloated over time. We (at a computer shop I worked at) used Ghost to build a pre-OOBE image for several common Windows configurations and then just image them to new PCs in a few minutes, then apply the license key afterward.
Symantec left our team - which was basically identical before and after acquisition - pretty much alone beyond adding in some (badly needed) release process and i18n requirements.
Almost the entirety of the growth in the size of the imaging executable, which did get hugely bigger, came from a constant drive to add capability to the NTFS support to match the FAT support, most crucially to allow the images to be edited in Ghost Explorer. The initial NTFS support that Ghost had prior to the Symantec releases was really crude, basically the content in the .GHO file wasn't files, but a raw-ish dump of used disk extents that it tried to always put back in the same place to avoid having to fix up attribute runs, whereas the FAT16/FAT32 content was basically a file archive where all the filesystem allocation metadata got recreated on the fly.
Customers wanted and pushed hard to have NTFS images editable, and that made life really hard - the approach that was ultimately taken meant creating a full read/write NTFS implementation, and those aren't small. And the design of that code interacted really badly with the C++ exception implementation in DJGPP (which before that work had begun, I had warned them about), so that eventually exception frame information was taking up ~25% of the on-disk size of the UPX-compressed binary!
> For the crows, the spikes seem purely structural, a material used to fashion a solid foundation. In both crow nests, the wires were incorporated into the base–interwoven with the points facing inward, below where a softer nest cup would sit. But for the magpies, there was an additional layer of intrigue; not only were the birds using the spikes to build nests, but it’s possible they were also employing the devices for their intended purpose—to ward off other birds.
It's not interesting in a "wow, Macbooks can finally support two external displays" as much as "this does make this intentionally-small form factor slightly more tolerable."
Comparing the port count/capabilities of the two isn't a fully fair comparison though. The Apple Silicon Macbook Air models are likely 1) much faster than that corporate-issued laptop (even if it's workstation class), and 2) much smaller and quieter (no fan noise even under load).
Though I'm not sure why all the griping about how many monitors an Air can support; users can buy a Macbook Pro if they want more monitors? I don't understand the logic behind buying a tiny, thin laptop only to dock it as a workstation.
And if you'd like to read it later, bookmark it! You can organize bookmarks into groups, give them custom names, and they don't require the browser to be constantly hoarding multiple gigabytes of RAM.
Neither do the tabs, autosleep/unload exists, you know
And bookmark organization is worse since it's a separate UI breaking your mental connection to the physical layout that you spend most of the time with
It seems to me that one of the strengths of LLMs is their ability to _not_ differentiate between (human) languages, because to a statistical model, (for lack of a better term) people gonna people, no matter their culture or background.
Figma's press release doesn't mention it, but they've now got an extra $1bn from the merger termination fee to bank, so presumably they could reinvest that into the company and stakeholders.
This does not matter in the slightest; your only obligations to other entities are self-imposed. Using a developer's piece of code does not confer an additional right to that developer's time.
> The bad parts are that there’s a dozen issues that I haven’t even reviewed much less triaged, investigated, and fixed
If those 3/4 million downloaders really found it that useful, aren't there code contributions?
> time = passion + money
I didn't _start_ writing code because of money, and I'd still be writing code on my own even if I weren't being paid to do it. I know this because I code on my own without being paid to do it, only work on things that are interesting to me, and I don't have a problem dropping a project if I'm no longer interested in it.
> Those companies in that list are contributing to the success of those projects
Go work for one of those companies then? Seems like a win-win.
