being a tester (with a bit of development) at work, I actually spend 2/3 of the time in CLI, so I'm only talking about my "work" laptop that I'm carrying with me. If I was paid to work on FreeBSD problems, then Windows would go out of it immediately, but as I'm working on illumos, I simply can't spend time on all the issues I'm having using linux "desktop" stuff. As for FreeBSD itself, being a newbie committer, I occasionally do simple fixes; it's just that at the moment I'm so burned out by $work stuff I barely want to look at anything else in free time (forums being exception, I guess )shkhln,emacs
has an hexl-mode. Did you try it?
yuripv, if you do not want to use cli and want to have all in GUI, it is perhaps indeed as you say.
I, for example, write text with plain TeX, other may usetroff
, it is perhaps much more work than to use MS word, but it is the habit of years of writing text in this "complicated way". The same with the cli.
Except that I was using FreeBSD long before I started to work on illumosWithout the desktop, linux is more similar to illumos than to FreeBSD. You could also use illumos for everything ...
1) Netflix and Hulu.it would be interesting to know, what is in Windows that you miss in FreeBSD. Do you find no alternative?
Windows was designed from the beginning to be a desktop
Windows FAQ: ASCII format said:2.7. Windows NT 3.1
====================
Microsoft Windows NT, scheduled for release in the first half of 1993, is
Microsoft's platform of choice for high-end systems. It is intended for
use in network servers, workstations and software development machines; it
will not replace Windows for DOS. While Windows NT's user interface is
very similar to that of Windows 3.1, it is based on an entirely new
operating system kernel.
The following are the major changes from Windows 3.1:
* Based on a new microkernel design
* Portable architecture for Intel x86, MIPS R4000 and DEC Alpha processors
* 32-bit addressing for access to up to 4 GB of memory
* Fully protected applications with virtualized hardware access
* Installable APIs for Win32, Win16, MS-DOS, POSIX and OS/2
* Installable file systems, including FAT, HPFS and NTFS
* Built-in networking (LAN Manager and TCP/IP) with remote procedure calls
(RPCs)
* Symmetric multiprocessor support
* Security designed in from start, to be initially C2 certified, with a B-
level kernel design
* API support for unsynchronized message queues, advanced interprocess
communication, registration databases, Bezier curves and graphics
transformations.
It's just that windows looks like "complete solution" (I'm well aware of the costs), I don't need any magic for scaling to work on a 4K monitor, I don't need to enter cli commands to connect to another wifi AP (the long list of usability stuff follows) -- now if I try to do the same on FreeBSD, I need a lot of bloat from ports, and it all feels clumsy and amateur compared to windows. You can say that I'm just lazy and spoiled by windows, and that would be correct; sometimes I just hate I don't have any real issues there and there's nothing forcing me to use FreeBSD only.
Yes, freedesktop.org, systemd, etc is just what amounts to bad Windows or macOS reinvention. Many Linux fans just don't see that by embracing crap in order to ape Windows that their chosen OS is becoming more and more like it, more complex and confusing and less "UNIX like" as time goes by.The Ubuntu bug #1 is the worst mistake IMO in linux land. You don't need or want to be fighting windows, you need to provide usable solutions. Instead of that we have zounds of incompatible UI toolkits, all looking so different, zounds of DEs, a lot of "desktop" bloat just to be like windows.
I will take that opportunity then.I think it is time to call for a last round of input for this thread.
I prefer to make my own decisions
shkhln,emacs
has an hexl-mode. Did you try it?
yuripv, if you do not want to use cli and want to have all in GUI, it is perhaps indeed as you say.
I, for example, write text with plain TeX, other may usetroff
, it is perhaps much more work than to use MS word, but it is the habit of years of writing text in this "complicated way". The same with the cli.
I also wanted to say that bloated OpenOffice or LibreOffice
Visually, there is something very wrong with editors/abiword at present: the screen it displays is black and flickers when you resize. Opening an *.odt caused editors/abiword to promptly core. Opening a *.doc made the editors/abiword screen turn black and the document underneath this to be unreadable except through the flashing screen.
There is an interesting alternative to TeX and troff: to write directly postscript.
Perhaps to have some templates for making it easier?
I never tried it, but it should be possible, and practical for drawing.
@OJ, I could live with minix or plan9. But is there a modern WEB browser?