Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

1

Great info and superb arguments. Thanx for the links, they are priceless!!!

fante
– fante

2016-12-03 23:27:27 +00:00
Commented Dec 3, 2016 at 23:27
1

Thanks for linking to Multics and for the very informative answer! Clearly segmentation was superior in many ways to what we do now.

GDP2
– GDP2

2017-11-12 01:15:43 +00:00
Commented Nov 12, 2017 at 1:15
1

Your answer is a true gem in the rough. Thank you so much for sharing these insights that we've lost. It makes me yearn to see a return to segmentation via the development of a proper OS that could prompt the refinement of hardware. Truly so many issues could be ameliorated with this approach! It even sounds as though we could get true OOP languages at much higher performance levels and at the bare metal with segmentation.

ylluminate
– ylluminate

2017-11-12 22:15:55 +00:00
Commented Nov 12, 2017 at 22:15

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »