Re: Features ideas

First sorry for the late answer, thses days have been crazy.
El 3/4/2015 21:06, "Mark Filipak" <[email protected]> escribió:
>
> On 04/03/2015 01:50 PM, Jean-Roch HUET wrote:
> > Always evetybordu use Windows Explorer, they don't know that another
explorer could exist.
>
> Millions of people use Total Commander, for example.
We are talking about the average user, I think.


> > To hide .lnk files helps to improve ergonomy. That's not roght or
wrong, that's just an habits taken after years...
>
> I'm pretty sure that hiding file extensions was initiated by Microsoft.
>
> File extensions were created by IBM, Burrows, Honeywell, etc. long
> before UNIX even existed. Microsoft merely followed what IBM did. Then,
> more Microsoft employees started arriving from universities and their
> experiences had been with UNIX. So, over time, things started changing
> (for the worse in my opinion), and they started hiding things from
> users, just like UNIX hides things (mostly files that begin with '.').
>
> > FHS = File Hierarchy System = The system of the folders that changes on
GoboLinux.
>
> Thank you. Now I know what you mean. I have never seen "FHS" used that
> way. 'https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard' (i.e.
> "FHS") means "Filesystem Hierarchy Standard", not "File Hierarchy
> System". When referring to an actual file system (rather than a file
> system hierarchy standard), you should simply use "FS" == "file system".
> Then, everyone is going to know what you mean. Using "FHS" is like
> pointing at a photograph of the Arc de Triomphe and saying: "That's a
> photograph of the Arc de Triomphe." Using "FS" is like pointing at the
> actual Arc de Triomphe.
>
> My opinion: The UNIX/Linux FS is stupid. '/usr' & '/var' & '/bin' are
> because the original UNIX developers wanted to be able to jump around
> the OS system files without having to type much. They didn't see that
> they were creating a monster.
Granted, it's ok for administrators but not so ok for users.


> My opinion: The movement to hide things and to obscure the distinction
> between memory, disk, and network partly results because of the
> UNIX/Linux FS design (i.e., FHS).

> I see 20-somethings in restaurants with their friends sharing media.
> They have no idea what a file system is. They're too young. When they
> want to show a cat video to their friends, they have to search for it
> using "Find" as though their computer was the Internet. When they can't
> find the cat video, they shrug and smile. Then they search for something
> else. Do they even know where their computer ends and the Internet
> begins? I think not.
Hey!, that's my range of age :P, it's that an indirect attack? (Kidding).
Maybe folders it's not exactly the way people think, I saw an article
suggesting a database-like file system.

> I can find everything almost instantly because I center my computer
> usage around subject-titled files and directories. I can always find
> pictures of cats because I put them in 'cats', not in 'pictures'. I can
> always find cat videos because I put them in 'cats', not in 'videos'. I
> can always find articles about cats because I put them in 'cats', not in
> 'documents'.
>
> If I try to show what I'm doing to the young folks who seem to spend all
> their time searching, they look blankly at the FS and don't say
> anything. I think they really don't know what they see.
That's having order (I tend to have it to, more or less).
> The "cloud" is going to make us happier and more productive? I don't
> think so.
A teacher of mine said we are going in circles, first people worked in
mainframes, then moved to personal PCs, now we are shifting again towards
mainframes(cloud).

*Jean-Roch HUET wrote:*

> One of the main point missing on Linux is the esay move: click and it
launchs.

Well it exists, just in the form of executables :P, but I understand your
point

> According to your point of view, I don't think so. I just lack of english
vocabulary.
> Pretty hard to talk on abstraction in a language which isn't my mother
tong.

Anyway you do it pretty well ^^.

> Yes, there are only one truth, but we juste are able to move towards it,
to approximate.

> But we evolve, we progress toward the truth, and it means to cut off
questions be answering yes or not under somes conditions.
> For a standard, the main point is to be accepted by the most of people.
I agree, but the doubt it's the definition of people, as can be everyone in
the world (so we should pick Windows way) or everyone who may be interested
in this (so we should Linux way).
>Yes, there are fundamentally no reason to restrain names on Linux, except
that it causes problem with Windows. And Windows has >93% of users (on
Desktop PC).

> If we can do it without kernel module, it is good, because perhaps one
day, I will have to do it...

Well, if you are up to doing it then I won't object ;), it depends on how
much you want to enforce it, if you are fine with just the file manager
and/or the applications then a patch to the DE you want to "limit" should
be enough, however if you want it to be enforced everywhere, a kernel
module is mandatory, the pro of this approach is that it will work in every
DE.

BTW, returning to the end line conversation, I found this in Wikipedia[1],
they do mention Mac's line endings, but they say it's up to version 9, the
next version is Mac OS X (the "actual" one), but they don't mention
anything OS X, that and the fact OS X is UNIX-based ,the kernel is
Mach-based, and the userspace is FreeBSD-based (they even have the UNIX
certification), then I'm sure OS X will follow the same line endings as
Linux.

[1]:https://en.wikipedia.org/wiki/Newline


--Sergio

_______________________________________________
gobolinux-users mailing list
[email protected]
http://lists.gobolinux.org/mailman/listinfo/gobolinux-users