mirror of
https://github.com/nbeaver/why-linux-is-better.git
synced 2025-08-29 08:39:57 +02:00
Minor formatting and clarification.
This commit is contained in:
44
readme.rst
44
readme.rst
@@ -789,7 +789,7 @@ File extensions are the sole determiner of filetype.
|
||||
----------------------------------------------------
|
||||
|
||||
On Windows, the file extension is the sole determiner
|
||||
of what happens when opening a file.
|
||||
of what program runs when opening a given filetype.
|
||||
This makes it easier to dupe a Windows user
|
||||
into `unintentionally running malware`_.
|
||||
|
||||
@@ -807,10 +807,12 @@ but only one application gets to open them by default.
|
||||
|
||||
On Linux, `filetypes are determined`_ by a combination of
|
||||
filesystem metadata (e.g. execute permissions),
|
||||
heuristics based on file signatures (a.k.a "magic numbers"),
|
||||
heuristics based on `file signatures`_ (a.k.a "magic numbers"),
|
||||
and ``.desktop`` configuration files with mimetype information
|
||||
(which includes file extensions).
|
||||
|
||||
.. _file signatures: https://en.wikipedia.org/wiki/List_of_file_signatures
|
||||
|
||||
.. TODO: cite
|
||||
|
||||
.. _filetypes are determined: http://www.howtogeek.com/192628/mime-types-explained-why-linux-and-mac-os-x-dont-need-file-extensions/
|
||||
@@ -840,7 +842,8 @@ each with various advantages and disadvantages. [#unix_groups]_ [#ntfs_permissio
|
||||
However, here is a specific example
|
||||
of a relatively simple, single-user permissions feature:
|
||||
it is sometimes desirable to set old files as read-only,
|
||||
so that they are still easily accessible,
|
||||
so that they are still easily accessible
|
||||
(i.e. not compressed in a ``.zip`` file),
|
||||
but are less likely to be accidentally deleted, moved, or modified.
|
||||
|
||||
On Windows, the content of a read-only file cannot be altered,
|
||||
@@ -867,9 +870,9 @@ which are not intrinsic to the operating system,
|
||||
but are the result of default behavior
|
||||
or restrictions on the Windows ecosystem.
|
||||
|
||||
-----------------------------------------
|
||||
Limitations on access to external volumes
|
||||
-----------------------------------------
|
||||
------------------------------------------
|
||||
Limitations on access to external volumes.
|
||||
------------------------------------------
|
||||
|
||||
When accessing external volumes such as flash drives,
|
||||
Windows assigns different capital letters to each volume,
|
||||
@@ -985,10 +988,10 @@ or the drive is manually mounted elsewhere.
|
||||
|
||||
File managers on Linux also handle deleting files on flash drives.
|
||||
When a file on an external drive is put into the trash,
|
||||
it goes into a user-specific hidden folder on the drive itself,
|
||||
it goes into a `user-specific hidden folder`_ on the drive itself,
|
||||
not the trash in the user's home directory.
|
||||
|
||||
https://superuser.com/questions/169980/what-is-trash-and-trash-1000
|
||||
.. _user-specific hidden folder: https://superuser.com/questions/169980/what-is-trash-and-trash-1000
|
||||
|
||||
.. [#disk_location]
|
||||
|
||||
@@ -1248,15 +1251,21 @@ The single Windows UI library
|
||||
means that accessibility improvements
|
||||
and user interface customization can be difficult to implement.
|
||||
|
||||
For example, dialog boxes are non-resizable by default,
|
||||
For example, on Linux, graphical dialog boxes
|
||||
(e.g. those generated by ``xmessage`` or ``zenity``)
|
||||
are resizable by default,
|
||||
but on Windows they are non-resizable by default,
|
||||
i.e. ``WS_THICKFRAME`` is not enabled by default.
|
||||
|
||||
.. TOOD: source
|
||||
.. TODO: is it even possible to prevent resizing?
|
||||
|
||||
In some cases, you want to display something in a response window but you also
|
||||
want this window to be resizable in order to let the user resize this window to
|
||||
display the info the way he or she wants. Normally, response windows are not
|
||||
resizable and this is also the Microsoft standard behaviour.
|
||||
|
||||
--- Eric Aling
|
||||
--- Eric Aling, April 13, 2000
|
||||
|
||||
http://eric.aling.tripod.com/PB/tips/pbtip39.htm
|
||||
|
||||
@@ -1272,15 +1281,14 @@ especially on high-resolution monitors.
|
||||
to see three characters hidden by dot-dot-dot in a window not much bigger
|
||||
than a postit note.
|
||||
|
||||
--- stewardware, January 7, 2011
|
||||
|
||||
https://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/cannot-resize-small-windows/160862cf-6e52-4a99-9365-d380491a067d
|
||||
|
||||
On Linux, dialog boxes from ``xmessage`` or ``zenity`` are resizable.
|
||||
|
||||
.. TOOD: source
|
||||
.. TODO: is it even possible to prevent resizing?
|
||||
|
||||
One solution to this problem is to download and run a third-party background process
|
||||
that tracks every single time a window is resized.
|
||||
One workaround for this problem
|
||||
is to run a third-party background process
|
||||
that watches for window creation and mouse click events.
|
||||
[#resize_non_resizable_windows]_
|
||||
[#turn_non_resizable_windows]_
|
||||
[#ResizeEnable]_
|
||||
@@ -1609,7 +1617,7 @@ that he is who he claims to be.)
|
||||
to the business. Our low performance is not an existential threat to the
|
||||
business.
|
||||
|
||||
-- Anonymous Windows NT kernel developer
|
||||
--- Anonymous Windows NT kernel developer
|
||||
|
||||
http://blog.zorinaq.com/?e=74
|
||||
|
||||
@@ -1644,7 +1652,7 @@ achieved a higher framerate than Direct3D on Windows.
|
||||
vendors we also sped up the OpenGL implementation on Windows. Left 4 Dead 2
|
||||
is now running at 303.4 FPS with that configuration.
|
||||
|
||||
-- Valve Linux Team
|
||||
--- Valve Linux Team
|
||||
|
||||
.. _ported Left 4 Dead 2 to Linux: http://blogs.valvesoftware.com/linux/faster-zombies/
|
||||
|
||||
|
Reference in New Issue
Block a user