News for hackers. Stuff that matters.
Re:Why is the function SHStripMneumonic misspelled? by wildmusings on Sunday June 25, 2017 @07:08PM (#14632745)
One of the central reasons for Windows's success is backwards compatibility. 16-bit Windows 3.1 applications still work in Windows 10. There are countless teams at Microsoft whose sole purpose is to verify backwards compatibility with almost every piece of software that more than a handful of people are running.

Public API contracts are NEVER intentionally broken.

Re:Why is the function SHStripMneumonic misspelled? by TylerE on Sunday June 25, 2017 @07:15PM (#14632780)
> 16-bit Windows 3.1 applications still work in Windows 10

No they don't, unless you're somehow running Windows 10 on a 32 bit machine.

Been bitten a few times by programs bundled using ancient 16-bit InstallShield. It _does not_ work on Windows 10.

Re:Why is the function SHStripMneumonic misspelled? by TazeTSchnitzel on Sunday June 25, 2017 @07:18PM (#14632790)
“Somehow”?

32-bit Windows still exists.

Re:Why is the function SHStripMneumonic misspelled? by mappu on Sunday June 25, 2017 @07:55PM (#14632930)
Not only does it still exist, devices running 32-bit Windows 10 are still actively sold. I purchased one in 2016 (Intel compute stick) and another in 2017 (Ollee D1016W).

Both have 64-bit capable Atom CPUs, but were deliberately shipped with a 32-bit userland (presumably to save on disk space).

Re:Why is the function SHStripMneumonic misspelled? by TazeTSchnitzel on Sunday June 25, 2017 @08:08PM (#14632978)
Yep. I bought a brand new Windows tablet, what, a year ago? It runs 32-bit Windows.
Re:Why is the function SHStripMneumonic misspelled? by voltagex_ on Sunday June 25, 2017 @08:27PM (#14633061)
The interesting thing about those (Z series Atom, right?) is they're 64 bit capable, but have a 32 bit UEFI environment.
Re:Why is the function SHStripMneumonic misspelled? by TylerE on Sunday June 25, 2017 @07:51PM (#14632918)
Intel hasn't sold a 32bit chip in over 10 years.
Re:Why is the function SHStripMneumonic misspelled? by userbinator on Sunday June 25, 2017 @08:18PM (#14633017)
These are still in production: https://en.wikipedia.org/wiki/Intel_Quark

They're essentially a 486 core with some Pentium instructions added.

Re:Why is the function SHStripMneumonic misspelled? by catdog on Sunday June 25, 2017 @09:57PM (#14633483)
While technically correct sth. like the Quark is probably not what he meant but some earlier models of the Atom lineup (<= 10y, 2008 onwards) are 32bit chips. There are chips released as late as 2011 [1] which lack 64 bit support.

[1] http://ark.intel.com/products/55663/Intel-Atom-Processor-Z67...

Re:Why is the function SHStripMneumonic misspelled? by TazeTSchnitzel on Sunday June 25, 2017 @08:10PM (#14632985)
Yes, but machines with 64-bit CPUs are still being sold with 32-bit OSes for various reasons.
Re:Why is the function SHStripMneumonic misspelled? by saurik on Monday June 26, 2017 @06:13AM (#14635546)
One reason being "to run my old 32-bit software".
Re:Why is the function SHStripMneumonic misspelled? by wildmusings on Monday June 26, 2017 @12:22PM (#14637955)
You are mistaken. 32 bit software runs flawlessly on 64 bit Windows.
Re:Why is the function SHStripMneumonic misspelled? by saurik on Monday June 26, 2017 @02:17PM (#14639011)
Oh, sorry: I meant 16-bit software (which does not run flawlessly on 64-bit Windows but does run on 32-bit Window).
Re:Why is the function SHStripMneumonic misspelled? by TazeTSchnitzel on Tuesday June 27, 2017 @02:20PM (#14647846)
I assume you mean that it does not run at all. 64-bit Windows lacks NTVDM.
Re:Why is the function SHStripMneumonic misspelled? by smt88 on Sunday June 25, 2017 @07:30PM (#14632831)
That's a hardware issue, not a "Windows breaking the public API contract" issue. It's not really relevant to what GP was saying.
Re:Why is the function SHStripMneumonic misspelled? by blibble on Sunday June 25, 2017 @08:01PM (#14632952)
that's not true, virtual 8086 mode is gone but you can still execute 16-bit programs fine

Windows 10 running in 32-bit on 64-bit processors manages this without issue, so it can't be the hardware

the real reason is they couldn't be bothered to work around some of the technical issues: https://msdn.microsoft.com/en-us/library/aa384249.aspx

Re:Why is the function SHStripMneumonic misspelled? by xg15 on Sunday June 25, 2017 @07:16PM (#14632783)
I think the idea was to put the correctly-spelled version there in addition to the original one, the latter staying part of the public API.
Re:Why is the function SHStripMneumonic misspelled? by Cthulhu_ on Monday June 26, 2017 @05:15AM (#14635268)
^ this, and later on removing it from the header files so nobody can accidentally use it (e.g. reading old documentation), but existing software can still call it.
Re:Why is the function SHStripMneumonic misspelled? by hota_mazi on Sunday June 25, 2017 @07:45PM (#14632897)
The article makes it clear that the problem with renaming was not that it would break backward compatibility (because it was still a private API when this was considered) but that it would be painful to coordinate all the teams to make the change simultaneously.
Re:Why is the function SHStripMneumonic misspelled? by xxs on Sunday June 25, 2017 @07:32PM (#14632839)
No one talks of breaking existing functions/API calls. Deprecation is not the same as removal.