It's always funny to me, the more you go into the depth of windows settings, the older the UI that start to show up. Which makes sense, between the "if we change it we break it in some subtle way" and "we don't expose that in UI anymore so the new panel doesn't have it". My understanding is that windows want to move to a "you can't configure much of anything, unless you use group policy and then you set everything th…
How did the Win 95 user interface code get brought to the Windows NT code base?
61–70 of 114 posts
Re: How did the Win 95 user interface code get brought to the Windows NT code base?
#62moving changes from Windows 95 to Windows NT involved manually doing three-way merges for all of the files that changed since the last drop. I suspect that this manual process was largely automated, but it was not as simple as a git merge. The first release of git was in 2005, around a decade after Windows 95.
Re: How did the Win 95 user interface code get brought to the Windows NT code base?
#63Earlier quoted context omitted.
I wonder what percentage of people on HN have ever used subversion or cvs, let alone older systems.
CVS was released in 1990. Subversion was released in 2000. Google still uses a clone of Perforce internally (and various wrappers of it). Perforce was released in 1995.
Re: How did the Win 95 user interface code get brought to the Windows NT code base?
#64Earlier quoted context omitted.
Funnily enough the Linux Kernel still use patches (and of course Git has helpers to create and import patches)
Don’t they get emailed patch from git? Sorry if I’m super ignorant here, it’s interesting to me if they do!
Of course, `git send-email` has a plethora of options, e.g. you'd typically add a cover letter for a patch set.
Also, in the Linux kernel tree, there are some additional helper scripts that you might want to run first, like `checkpatch.pl` for some basic sanity checks and `get_maintainer.pl` that tells you the relevant maintainers for the code your patch set touches, so you can add them to `--cc`.
The patches are reviewed/discussed on the mailing list that you sent them to.
On the receiving side, as a maintainer, you'd use `git am` (apply mail) that can import the commits from a set of mbox files into your local git tree.
Re: How did the Win 95 user interface code get brought to the Windows NT code base?
#65Re: How did the Win 95 user interface code get brought to the Windows NT code base?
#66moving changes from Windows 95 to Windows NT involved manually doing three-way merges for all of the files that changed since the last drop. I suspect that this manual process was largely automated, but it was not as simple as a git merge. The first release of git was in 2005, around a decade after Windows 95.
Funny how fast Git became entrenched as the way of doing things, though. Around 2010 I said in passing, in a forum discussion about how a FOSS project was getting along, “…you’d think someone could send in a patch…”, and I immediately got flamed by several people because no one used patches any more.
> ...and I immediately got flamed by several people because no one used patches any more.
How are these ideas connected? The intent of git is that you work with patches.
Re: How did the Win 95 user interface code get brought to the Windows NT code base?
#67Earlier quoted context omitted.
Funny how fast Git became entrenched as the way of doing things, though. Around 2010 I said in passing, in a forum discussion about how a FOSS project was getting along, “…you’d think someone could send in a patch…”, and I immediately got flamed by several people because no one used patches any more.
> Funny how fast Git became entrenched as the way of doing things, though. > ...and I immediately got flamed by several people because no one used patches any more. How are these ideas connected? The intent of git is that you work with patches.
Re: How did the Win 95 user interface code get brought to the Windows NT code base?
#68Re: How did the Win 95 user interface code get brought to the Windows NT code base?
#69Really wish someone would just take the win95 UI code and tell an LLM to make it work on the win11 74 bit kernel
Re: How did the Win 95 user interface code get brought to the Windows NT code base?
#70What's the reason for moving from ASCII CHAR to UTF16 WCHAR rather than UTF8 CHAR? I wouldn't think any parts of the codebase that don't need to render the string or worry about character counts would need to be modified. Edit: https://devblogs.microsoft.com/oldnewthing/20190830-00/?p=10... seems the justification was that UTF-8 didn't exist yet? Not totally accurate, but it wasn't fully standardized. Also that other…