Why does Wordpad open large files so much faster than notepad?
I thought notepad, being the most simple text reader is also the fastest, but I discovered when I tried to open very large text files that Wordpad opens them much much more quickly.
What could be the reason for this?
windows-7 windows text-editors notepad wordpad
add a comment |
I thought notepad, being the most simple text reader is also the fastest, but I discovered when I tried to open very large text files that Wordpad opens them much much more quickly.
What could be the reason for this?
windows-7 windows text-editors notepad wordpad
2
No. Notepad isn't one of the fastest. It's one of the most poorly written.
– TOOGAM
Nov 22 '16 at 2:12
Open a big files like hundreds of MBs or a few GBs with notepad and see. Other editors have no trouble opening it in a blink of an eye while notepad still have problem opening it
– phuclv
Nov 22 '16 at 2:40
add a comment |
I thought notepad, being the most simple text reader is also the fastest, but I discovered when I tried to open very large text files that Wordpad opens them much much more quickly.
What could be the reason for this?
windows-7 windows text-editors notepad wordpad
I thought notepad, being the most simple text reader is also the fastest, but I discovered when I tried to open very large text files that Wordpad opens them much much more quickly.
What could be the reason for this?
windows-7 windows text-editors notepad wordpad
windows-7 windows text-editors notepad wordpad
edited Nov 22 '16 at 8:48
C.W.
1625
1625
asked Nov 22 '16 at 1:54
yoyo_funyoyo_fun
75611237
75611237
2
No. Notepad isn't one of the fastest. It's one of the most poorly written.
– TOOGAM
Nov 22 '16 at 2:12
Open a big files like hundreds of MBs or a few GBs with notepad and see. Other editors have no trouble opening it in a blink of an eye while notepad still have problem opening it
– phuclv
Nov 22 '16 at 2:40
add a comment |
2
No. Notepad isn't one of the fastest. It's one of the most poorly written.
– TOOGAM
Nov 22 '16 at 2:12
Open a big files like hundreds of MBs or a few GBs with notepad and see. Other editors have no trouble opening it in a blink of an eye while notepad still have problem opening it
– phuclv
Nov 22 '16 at 2:40
2
2
No. Notepad isn't one of the fastest. It's one of the most poorly written.
– TOOGAM
Nov 22 '16 at 2:12
No. Notepad isn't one of the fastest. It's one of the most poorly written.
– TOOGAM
Nov 22 '16 at 2:12
Open a big files like hundreds of MBs or a few GBs with notepad and see. Other editors have no trouble opening it in a blink of an eye while notepad still have problem opening it
– phuclv
Nov 22 '16 at 2:40
Open a big files like hundreds of MBs or a few GBs with notepad and see. Other editors have no trouble opening it in a blink of an eye while notepad still have problem opening it
– phuclv
Nov 22 '16 at 2:40
add a comment |
2 Answers
2
active
oldest
votes
Simple ≠ Fast
A plain basic editor like Notepad might be so simple that it doesn't have the ability to deal with complex situations, because it's only used for easy use cases.
A smart editor will determine many factors to decide which strategy is the best to use. For example instead of reading the file line-by-line or byte-by-byte like a stupid editor it'll load into a big buffer for fast reading later. Or it can map the file to memory. But how big should the buffer or the map area be? It depends on each specific case and the editor should also account for that. Instead of loading a whole several-GB file into memory and stuck because that simply doesn't fit in, a smart editor just checks the file size and loads only the currently viewing part then seek later when needed.
All of that require a more careful design with a lot of logic that doesn't exist in Notepad, since its source code hasn't changed much for a decade.
See Why can Vim open large files faster than some other text editors?
Update
Windows 10 build 17713 introduced a lot of changes to Notepad, one of which improves Notepad's behavior on large files
- We’ve improved the performance when opening large files in Notepad.
- Notepad now supports Ctrl+Backspace to delete the previous word.
- Arrow keys now correctly unselect text first and then move the cursor.
- When saving a file in Notepad, the line and column number no longer reset to 1.
- Notepad now correctly displays lines that don’t fit entirely on the screen.
Now there are also Unix line ending support, text zooming ability and status bar in word wrap mode
Announcing Windows 10 Insider Preview Build 17713
It's also confirmed that Notepad does use memory-mapped file, but that's the beginning part. The difficult thing is to parse the line and do the line wrapping. Even Notepad++ sucks when opening super huge files
I have to correct you. Most windows code hasn't changed for a decade. (Closer to 17 years for a lot of it, actually). Notepad hasn't changed much since windows 1.0 (their first GUI, although it was available in MS-DOS), which is coming on 31 yearls old.
– user657451
Nov 22 '16 at 4:44
1
@user657451 No, since Vista there has been a lot of rewrites, that's why it took MS 5 years to release Vista. And Notepad got a significant change in (IIRC) XP for Unicode and big file support. Before that it can't open files larger than 64KB
– phuclv
Nov 22 '16 at 5:31
That's funny, because in 10 there's still most of the NT4.0 snap-ins and .mscs. unchanged. And that registry thing. I'm pretty sure all they've really been doing is trying to work out how to port Mac's DE to work with Windows' APIs. And when that failed they went back and skinned CE3.0, and called it 8.
– user657451
Nov 22 '16 at 7:10
1
@user657451 I'm sure there's a lot of legacy code in every Windows version because of compatibility, but in Vista there's significant changes like DWM, UAC... which were never there before. The basic structure obviously still be the same, because how can you drop the registry without breaking compatibilty. In what sense CE is similar to 8? It doesn't even have NT kernel
– phuclv
Nov 22 '16 at 8:06
no it's not even legacy code for compatibility, that's what the heinous winsxs folder is about. The number of W10 (98, NT, Vista, 7, 8) threads here would suggest "compatibility" isn't. s3.amazonaws.com/neowin/forum/uploads/monthly_04_2012/…
– user657451
Nov 22 '16 at 8:15
|
show 1 more comment
Notepad is little more than a shell around the Windows Edit control. It was designed for editing small amounts of text and was optimized for such. Early versions had to run in systems with very limited resources where these optimizations were important. Windows 95 had an official requirement of only 4 MB RAM and for technical reasons the Edit control was limited to 64K of text. The NT platform was not so limited but it too had to work with limited resources.
Designing an editor for small files is relatively simple. Designing one that works efficiently with large files is anything but simple and requires a great deal of complex code. Small and simple editors do not work well with large files. All such editors, not just notepad, will choke on multi gigabyte files, even on a powerful computer. Some advanced editors can handle this with ease.
Notepad still works well for it's intended purpose and has had few changes over the years. The Windows Edit control is used in some form in most Windows applications so the potential for incompatibilities is great if major changes were made. Why take the chance of making unnecessary changes? Experience has shown that the most trivial of changes can cause incompatibilities in applications
If you need to edit larger files there are plenty of other editors available. Notepad was never designed for this.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1148399%2fwhy-does-wordpad-open-large-files-so-much-faster-than-notepad%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Simple ≠ Fast
A plain basic editor like Notepad might be so simple that it doesn't have the ability to deal with complex situations, because it's only used for easy use cases.
A smart editor will determine many factors to decide which strategy is the best to use. For example instead of reading the file line-by-line or byte-by-byte like a stupid editor it'll load into a big buffer for fast reading later. Or it can map the file to memory. But how big should the buffer or the map area be? It depends on each specific case and the editor should also account for that. Instead of loading a whole several-GB file into memory and stuck because that simply doesn't fit in, a smart editor just checks the file size and loads only the currently viewing part then seek later when needed.
All of that require a more careful design with a lot of logic that doesn't exist in Notepad, since its source code hasn't changed much for a decade.
See Why can Vim open large files faster than some other text editors?
Update
Windows 10 build 17713 introduced a lot of changes to Notepad, one of which improves Notepad's behavior on large files
- We’ve improved the performance when opening large files in Notepad.
- Notepad now supports Ctrl+Backspace to delete the previous word.
- Arrow keys now correctly unselect text first and then move the cursor.
- When saving a file in Notepad, the line and column number no longer reset to 1.
- Notepad now correctly displays lines that don’t fit entirely on the screen.
Now there are also Unix line ending support, text zooming ability and status bar in word wrap mode
Announcing Windows 10 Insider Preview Build 17713
It's also confirmed that Notepad does use memory-mapped file, but that's the beginning part. The difficult thing is to parse the line and do the line wrapping. Even Notepad++ sucks when opening super huge files
I have to correct you. Most windows code hasn't changed for a decade. (Closer to 17 years for a lot of it, actually). Notepad hasn't changed much since windows 1.0 (their first GUI, although it was available in MS-DOS), which is coming on 31 yearls old.
– user657451
Nov 22 '16 at 4:44
1
@user657451 No, since Vista there has been a lot of rewrites, that's why it took MS 5 years to release Vista. And Notepad got a significant change in (IIRC) XP for Unicode and big file support. Before that it can't open files larger than 64KB
– phuclv
Nov 22 '16 at 5:31
That's funny, because in 10 there's still most of the NT4.0 snap-ins and .mscs. unchanged. And that registry thing. I'm pretty sure all they've really been doing is trying to work out how to port Mac's DE to work with Windows' APIs. And when that failed they went back and skinned CE3.0, and called it 8.
– user657451
Nov 22 '16 at 7:10
1
@user657451 I'm sure there's a lot of legacy code in every Windows version because of compatibility, but in Vista there's significant changes like DWM, UAC... which were never there before. The basic structure obviously still be the same, because how can you drop the registry without breaking compatibilty. In what sense CE is similar to 8? It doesn't even have NT kernel
– phuclv
Nov 22 '16 at 8:06
no it's not even legacy code for compatibility, that's what the heinous winsxs folder is about. The number of W10 (98, NT, Vista, 7, 8) threads here would suggest "compatibility" isn't. s3.amazonaws.com/neowin/forum/uploads/monthly_04_2012/…
– user657451
Nov 22 '16 at 8:15
|
show 1 more comment
Simple ≠ Fast
A plain basic editor like Notepad might be so simple that it doesn't have the ability to deal with complex situations, because it's only used for easy use cases.
A smart editor will determine many factors to decide which strategy is the best to use. For example instead of reading the file line-by-line or byte-by-byte like a stupid editor it'll load into a big buffer for fast reading later. Or it can map the file to memory. But how big should the buffer or the map area be? It depends on each specific case and the editor should also account for that. Instead of loading a whole several-GB file into memory and stuck because that simply doesn't fit in, a smart editor just checks the file size and loads only the currently viewing part then seek later when needed.
All of that require a more careful design with a lot of logic that doesn't exist in Notepad, since its source code hasn't changed much for a decade.
See Why can Vim open large files faster than some other text editors?
Update
Windows 10 build 17713 introduced a lot of changes to Notepad, one of which improves Notepad's behavior on large files
- We’ve improved the performance when opening large files in Notepad.
- Notepad now supports Ctrl+Backspace to delete the previous word.
- Arrow keys now correctly unselect text first and then move the cursor.
- When saving a file in Notepad, the line and column number no longer reset to 1.
- Notepad now correctly displays lines that don’t fit entirely on the screen.
Now there are also Unix line ending support, text zooming ability and status bar in word wrap mode
Announcing Windows 10 Insider Preview Build 17713
It's also confirmed that Notepad does use memory-mapped file, but that's the beginning part. The difficult thing is to parse the line and do the line wrapping. Even Notepad++ sucks when opening super huge files
I have to correct you. Most windows code hasn't changed for a decade. (Closer to 17 years for a lot of it, actually). Notepad hasn't changed much since windows 1.0 (their first GUI, although it was available in MS-DOS), which is coming on 31 yearls old.
– user657451
Nov 22 '16 at 4:44
1
@user657451 No, since Vista there has been a lot of rewrites, that's why it took MS 5 years to release Vista. And Notepad got a significant change in (IIRC) XP for Unicode and big file support. Before that it can't open files larger than 64KB
– phuclv
Nov 22 '16 at 5:31
That's funny, because in 10 there's still most of the NT4.0 snap-ins and .mscs. unchanged. And that registry thing. I'm pretty sure all they've really been doing is trying to work out how to port Mac's DE to work with Windows' APIs. And when that failed they went back and skinned CE3.0, and called it 8.
– user657451
Nov 22 '16 at 7:10
1
@user657451 I'm sure there's a lot of legacy code in every Windows version because of compatibility, but in Vista there's significant changes like DWM, UAC... which were never there before. The basic structure obviously still be the same, because how can you drop the registry without breaking compatibilty. In what sense CE is similar to 8? It doesn't even have NT kernel
– phuclv
Nov 22 '16 at 8:06
no it's not even legacy code for compatibility, that's what the heinous winsxs folder is about. The number of W10 (98, NT, Vista, 7, 8) threads here would suggest "compatibility" isn't. s3.amazonaws.com/neowin/forum/uploads/monthly_04_2012/…
– user657451
Nov 22 '16 at 8:15
|
show 1 more comment
Simple ≠ Fast
A plain basic editor like Notepad might be so simple that it doesn't have the ability to deal with complex situations, because it's only used for easy use cases.
A smart editor will determine many factors to decide which strategy is the best to use. For example instead of reading the file line-by-line or byte-by-byte like a stupid editor it'll load into a big buffer for fast reading later. Or it can map the file to memory. But how big should the buffer or the map area be? It depends on each specific case and the editor should also account for that. Instead of loading a whole several-GB file into memory and stuck because that simply doesn't fit in, a smart editor just checks the file size and loads only the currently viewing part then seek later when needed.
All of that require a more careful design with a lot of logic that doesn't exist in Notepad, since its source code hasn't changed much for a decade.
See Why can Vim open large files faster than some other text editors?
Update
Windows 10 build 17713 introduced a lot of changes to Notepad, one of which improves Notepad's behavior on large files
- We’ve improved the performance when opening large files in Notepad.
- Notepad now supports Ctrl+Backspace to delete the previous word.
- Arrow keys now correctly unselect text first and then move the cursor.
- When saving a file in Notepad, the line and column number no longer reset to 1.
- Notepad now correctly displays lines that don’t fit entirely on the screen.
Now there are also Unix line ending support, text zooming ability and status bar in word wrap mode
Announcing Windows 10 Insider Preview Build 17713
It's also confirmed that Notepad does use memory-mapped file, but that's the beginning part. The difficult thing is to parse the line and do the line wrapping. Even Notepad++ sucks when opening super huge files
Simple ≠ Fast
A plain basic editor like Notepad might be so simple that it doesn't have the ability to deal with complex situations, because it's only used for easy use cases.
A smart editor will determine many factors to decide which strategy is the best to use. For example instead of reading the file line-by-line or byte-by-byte like a stupid editor it'll load into a big buffer for fast reading later. Or it can map the file to memory. But how big should the buffer or the map area be? It depends on each specific case and the editor should also account for that. Instead of loading a whole several-GB file into memory and stuck because that simply doesn't fit in, a smart editor just checks the file size and loads only the currently viewing part then seek later when needed.
All of that require a more careful design with a lot of logic that doesn't exist in Notepad, since its source code hasn't changed much for a decade.
See Why can Vim open large files faster than some other text editors?
Update
Windows 10 build 17713 introduced a lot of changes to Notepad, one of which improves Notepad's behavior on large files
- We’ve improved the performance when opening large files in Notepad.
- Notepad now supports Ctrl+Backspace to delete the previous word.
- Arrow keys now correctly unselect text first and then move the cursor.
- When saving a file in Notepad, the line and column number no longer reset to 1.
- Notepad now correctly displays lines that don’t fit entirely on the screen.
Now there are also Unix line ending support, text zooming ability and status bar in word wrap mode
Announcing Windows 10 Insider Preview Build 17713
It's also confirmed that Notepad does use memory-mapped file, but that's the beginning part. The difficult thing is to parse the line and do the line wrapping. Even Notepad++ sucks when opening super huge files
edited Feb 25 at 10:01
answered Nov 22 '16 at 2:56
phuclvphuclv
10.4k64295
10.4k64295
I have to correct you. Most windows code hasn't changed for a decade. (Closer to 17 years for a lot of it, actually). Notepad hasn't changed much since windows 1.0 (their first GUI, although it was available in MS-DOS), which is coming on 31 yearls old.
– user657451
Nov 22 '16 at 4:44
1
@user657451 No, since Vista there has been a lot of rewrites, that's why it took MS 5 years to release Vista. And Notepad got a significant change in (IIRC) XP for Unicode and big file support. Before that it can't open files larger than 64KB
– phuclv
Nov 22 '16 at 5:31
That's funny, because in 10 there's still most of the NT4.0 snap-ins and .mscs. unchanged. And that registry thing. I'm pretty sure all they've really been doing is trying to work out how to port Mac's DE to work with Windows' APIs. And when that failed they went back and skinned CE3.0, and called it 8.
– user657451
Nov 22 '16 at 7:10
1
@user657451 I'm sure there's a lot of legacy code in every Windows version because of compatibility, but in Vista there's significant changes like DWM, UAC... which were never there before. The basic structure obviously still be the same, because how can you drop the registry without breaking compatibilty. In what sense CE is similar to 8? It doesn't even have NT kernel
– phuclv
Nov 22 '16 at 8:06
no it's not even legacy code for compatibility, that's what the heinous winsxs folder is about. The number of W10 (98, NT, Vista, 7, 8) threads here would suggest "compatibility" isn't. s3.amazonaws.com/neowin/forum/uploads/monthly_04_2012/…
– user657451
Nov 22 '16 at 8:15
|
show 1 more comment
I have to correct you. Most windows code hasn't changed for a decade. (Closer to 17 years for a lot of it, actually). Notepad hasn't changed much since windows 1.0 (their first GUI, although it was available in MS-DOS), which is coming on 31 yearls old.
– user657451
Nov 22 '16 at 4:44
1
@user657451 No, since Vista there has been a lot of rewrites, that's why it took MS 5 years to release Vista. And Notepad got a significant change in (IIRC) XP for Unicode and big file support. Before that it can't open files larger than 64KB
– phuclv
Nov 22 '16 at 5:31
That's funny, because in 10 there's still most of the NT4.0 snap-ins and .mscs. unchanged. And that registry thing. I'm pretty sure all they've really been doing is trying to work out how to port Mac's DE to work with Windows' APIs. And when that failed they went back and skinned CE3.0, and called it 8.
– user657451
Nov 22 '16 at 7:10
1
@user657451 I'm sure there's a lot of legacy code in every Windows version because of compatibility, but in Vista there's significant changes like DWM, UAC... which were never there before. The basic structure obviously still be the same, because how can you drop the registry without breaking compatibilty. In what sense CE is similar to 8? It doesn't even have NT kernel
– phuclv
Nov 22 '16 at 8:06
no it's not even legacy code for compatibility, that's what the heinous winsxs folder is about. The number of W10 (98, NT, Vista, 7, 8) threads here would suggest "compatibility" isn't. s3.amazonaws.com/neowin/forum/uploads/monthly_04_2012/…
– user657451
Nov 22 '16 at 8:15
I have to correct you. Most windows code hasn't changed for a decade. (Closer to 17 years for a lot of it, actually). Notepad hasn't changed much since windows 1.0 (their first GUI, although it was available in MS-DOS), which is coming on 31 yearls old.
– user657451
Nov 22 '16 at 4:44
I have to correct you. Most windows code hasn't changed for a decade. (Closer to 17 years for a lot of it, actually). Notepad hasn't changed much since windows 1.0 (their first GUI, although it was available in MS-DOS), which is coming on 31 yearls old.
– user657451
Nov 22 '16 at 4:44
1
1
@user657451 No, since Vista there has been a lot of rewrites, that's why it took MS 5 years to release Vista. And Notepad got a significant change in (IIRC) XP for Unicode and big file support. Before that it can't open files larger than 64KB
– phuclv
Nov 22 '16 at 5:31
@user657451 No, since Vista there has been a lot of rewrites, that's why it took MS 5 years to release Vista. And Notepad got a significant change in (IIRC) XP for Unicode and big file support. Before that it can't open files larger than 64KB
– phuclv
Nov 22 '16 at 5:31
That's funny, because in 10 there's still most of the NT4.0 snap-ins and .mscs. unchanged. And that registry thing. I'm pretty sure all they've really been doing is trying to work out how to port Mac's DE to work with Windows' APIs. And when that failed they went back and skinned CE3.0, and called it 8.
– user657451
Nov 22 '16 at 7:10
That's funny, because in 10 there's still most of the NT4.0 snap-ins and .mscs. unchanged. And that registry thing. I'm pretty sure all they've really been doing is trying to work out how to port Mac's DE to work with Windows' APIs. And when that failed they went back and skinned CE3.0, and called it 8.
– user657451
Nov 22 '16 at 7:10
1
1
@user657451 I'm sure there's a lot of legacy code in every Windows version because of compatibility, but in Vista there's significant changes like DWM, UAC... which were never there before. The basic structure obviously still be the same, because how can you drop the registry without breaking compatibilty. In what sense CE is similar to 8? It doesn't even have NT kernel
– phuclv
Nov 22 '16 at 8:06
@user657451 I'm sure there's a lot of legacy code in every Windows version because of compatibility, but in Vista there's significant changes like DWM, UAC... which were never there before. The basic structure obviously still be the same, because how can you drop the registry without breaking compatibilty. In what sense CE is similar to 8? It doesn't even have NT kernel
– phuclv
Nov 22 '16 at 8:06
no it's not even legacy code for compatibility, that's what the heinous winsxs folder is about. The number of W10 (98, NT, Vista, 7, 8) threads here would suggest "compatibility" isn't. s3.amazonaws.com/neowin/forum/uploads/monthly_04_2012/…
– user657451
Nov 22 '16 at 8:15
no it's not even legacy code for compatibility, that's what the heinous winsxs folder is about. The number of W10 (98, NT, Vista, 7, 8) threads here would suggest "compatibility" isn't. s3.amazonaws.com/neowin/forum/uploads/monthly_04_2012/…
– user657451
Nov 22 '16 at 8:15
|
show 1 more comment
Notepad is little more than a shell around the Windows Edit control. It was designed for editing small amounts of text and was optimized for such. Early versions had to run in systems with very limited resources where these optimizations were important. Windows 95 had an official requirement of only 4 MB RAM and for technical reasons the Edit control was limited to 64K of text. The NT platform was not so limited but it too had to work with limited resources.
Designing an editor for small files is relatively simple. Designing one that works efficiently with large files is anything but simple and requires a great deal of complex code. Small and simple editors do not work well with large files. All such editors, not just notepad, will choke on multi gigabyte files, even on a powerful computer. Some advanced editors can handle this with ease.
Notepad still works well for it's intended purpose and has had few changes over the years. The Windows Edit control is used in some form in most Windows applications so the potential for incompatibilities is great if major changes were made. Why take the chance of making unnecessary changes? Experience has shown that the most trivial of changes can cause incompatibilities in applications
If you need to edit larger files there are plenty of other editors available. Notepad was never designed for this.
add a comment |
Notepad is little more than a shell around the Windows Edit control. It was designed for editing small amounts of text and was optimized for such. Early versions had to run in systems with very limited resources where these optimizations were important. Windows 95 had an official requirement of only 4 MB RAM and for technical reasons the Edit control was limited to 64K of text. The NT platform was not so limited but it too had to work with limited resources.
Designing an editor for small files is relatively simple. Designing one that works efficiently with large files is anything but simple and requires a great deal of complex code. Small and simple editors do not work well with large files. All such editors, not just notepad, will choke on multi gigabyte files, even on a powerful computer. Some advanced editors can handle this with ease.
Notepad still works well for it's intended purpose and has had few changes over the years. The Windows Edit control is used in some form in most Windows applications so the potential for incompatibilities is great if major changes were made. Why take the chance of making unnecessary changes? Experience has shown that the most trivial of changes can cause incompatibilities in applications
If you need to edit larger files there are plenty of other editors available. Notepad was never designed for this.
add a comment |
Notepad is little more than a shell around the Windows Edit control. It was designed for editing small amounts of text and was optimized for such. Early versions had to run in systems with very limited resources where these optimizations were important. Windows 95 had an official requirement of only 4 MB RAM and for technical reasons the Edit control was limited to 64K of text. The NT platform was not so limited but it too had to work with limited resources.
Designing an editor for small files is relatively simple. Designing one that works efficiently with large files is anything but simple and requires a great deal of complex code. Small and simple editors do not work well with large files. All such editors, not just notepad, will choke on multi gigabyte files, even on a powerful computer. Some advanced editors can handle this with ease.
Notepad still works well for it's intended purpose and has had few changes over the years. The Windows Edit control is used in some form in most Windows applications so the potential for incompatibilities is great if major changes were made. Why take the chance of making unnecessary changes? Experience has shown that the most trivial of changes can cause incompatibilities in applications
If you need to edit larger files there are plenty of other editors available. Notepad was never designed for this.
Notepad is little more than a shell around the Windows Edit control. It was designed for editing small amounts of text and was optimized for such. Early versions had to run in systems with very limited resources where these optimizations were important. Windows 95 had an official requirement of only 4 MB RAM and for technical reasons the Edit control was limited to 64K of text. The NT platform was not so limited but it too had to work with limited resources.
Designing an editor for small files is relatively simple. Designing one that works efficiently with large files is anything but simple and requires a great deal of complex code. Small and simple editors do not work well with large files. All such editors, not just notepad, will choke on multi gigabyte files, even on a powerful computer. Some advanced editors can handle this with ease.
Notepad still works well for it's intended purpose and has had few changes over the years. The Windows Edit control is used in some form in most Windows applications so the potential for incompatibilities is great if major changes were made. Why take the chance of making unnecessary changes? Experience has shown that the most trivial of changes can cause incompatibilities in applications
If you need to edit larger files there are plenty of other editors available. Notepad was never designed for this.
answered Nov 22 '16 at 15:03
LMiller7LMiller7
1,4241510
1,4241510
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1148399%2fwhy-does-wordpad-open-large-files-so-much-faster-than-notepad%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
No. Notepad isn't one of the fastest. It's one of the most poorly written.
– TOOGAM
Nov 22 '16 at 2:12
Open a big files like hundreds of MBs or a few GBs with notepad and see. Other editors have no trouble opening it in a blink of an eye while notepad still have problem opening it
– phuclv
Nov 22 '16 at 2:40