Linux (2003)
urbandictionary.com
urbandictionary.com
The year is 2016, and every time I upgraded my Linux distro in the past several years, I had to search down several different (and incompatible) input method packages, install them one by one, try several different command-line tools to tell the system what input system the applications should expect (which they may or may not honor, depending on whether they're linked with GNOME or QT or whatever), read several howtos and stackoverflow articles, and finally settle down with the best one that supports Korean input on at least half of the applications, sort of.
I forgot when was the last time Windows didn't support acceptable Korean input out of box. Sometime in the 90s, I think.
> You try to tell customers of the other airlines about the great trip, but all they can say is, "You had to do what with the seat?"
More like, "At first it crashed fifteen times, but when I followed this great article to mine my own titanium ore and replace the fuselage with my custom built one, there was no problem at all! Oh, by the way all the screws must be left-handed, don't ask me why, but I found it works best that way."
Then I moved to Mac. I was puzzled first couple of months - comparing to Windows, the platform was, for me, almost an utter shit. Yeah, some things were cute, some things are better from the start (application installation, for example) but OSX crashed on me couple of times (which Windows never did), Finder is an atrocity compared to Explorer, etc, etc.
Some time passed (three years). I learned how to use Mac. Somehow OS stopped crashing. Pain points disappeared. Finder isn't so bad after all, it have some nice tricks. And now, when I need to work on Windows, I want to kill someone out of frustration - nothing works exactly like I want.
Because I forgot things about Windows. I don't know about you guys, but when I'm familiar with something, when I understand how something works, I tend to use that thing (Windows, macOS, Linux, whatever) in a way that will not make me problems. When I said "Windows is rock stable" I mean it, but I learned that it was rock stable for me, because I knew how to use it.
I assume that's the reason why there's so many opposing stories about linux - people who knows linux doesn't understand how someone can have any problem with it, because linux just works for them. Forgetting and not thinking about million simple, small things they do every day to ensure that Linux is working correctly.
Using Debian.
Searching online, the easiest results to find seem to be either to manually uninstall hardware-specific drivers in the device manager, or simply to assume that motherboard upgrades will just magically work. Whilst one can find results that mention sysprep, how is a user to know that the sysprep method is the right one?
And now I read:
When sysprepping an existing Windows setup, it only works if the Windows was installed clean and has never been upgraded or repaired using repair install.
So that's great.
Sometimes Linux Airlines forgets to equip its planes with doors. Others in Linux Airlines, who are used to entering through the windows, suggest that you should start a door company yourself to outfit the planes.
I'm curious what input methods have you tried. Not sure about Korean, but for my English/Japanese/Thai setup, ibus (w/ mozc/kkc/libthai) has been working very reliably so far on Arch (been using since February). On the other hand, the hunt to find something that actually works wasn't exactly fun, though.
At one time, ibus worked pretty well, and I was content. After one upgrade, ibus stopped working, and I couldn't make it work again. Tried skim (which I had used several years ago, but abandoned when it also stopped working for some reason): it managed to lock up X windows. Finally found uim, which almost worked the same, so I was content again.
And then about a month ago I had to upgrade again (long story short: Linux magically forgot that I had a second monitor and refused to acknowledge it), and then uim stopped working in some KDE applications, including Konsole. Spent several hours trying different things. (Even tried to compile uim from source, but apparently figuring out dependencies for graphic libraries is not my strong area.) Finally just settled down for uim again. Who needs to type Korean into terminal anyway?
Well, at least now I don't have to restart gvim every time after reboot, so that's the plus.
See, "Why don't you report bugs" is missing the problem. For example, I had gvim running on a KDE system that somehow forgets the input method whenever I reboot the system, but when I restart gvim, it finds the input method without problem. I don't even know which application I should report this bug against.
And of course I'm using distro packages that may be years old (the last release of uim was in 2013), so for all I know, the problem I have is already fixed in the most upstream version.
I'm sure Windows have other problems that Linux solves quite well. I'm not arguing Linux is worse in every respect. I'm just pointing out there are a horde of problems that should have been solved for once and all fifteen years ago: there should be a metapackage, or ideally a single button that says "If you want to enable Korean/Japanese/Hindi input, press HERE," and that should be the end of story.
But these problems are never properly solved, because the "bazaar" nature of Linux development means whatever solution worked today is not guaranteed to work two years later. Each solution is made of five packages developed by different teams, and maintainers drop out all the time either because they're bored or they have other life obligations. And then some other people start a new sexy project that more or less subsumes previous iterations (but in a brand new codebase), and the cycle continues.
Conway's law[1] says "organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations." It doesn't just apply to MS or Google: it also applies to Linux. I don't know if it can be improved, but that's the way Linux is now.
However, last time I installed Ubuntu it booted to a black screen of death and then googling told me it didn't come with nvidia drivers out of the box, etc.
Generally, I think a big problem with Linux is all the low quality advice sprinkled around Stack Overflow and other web forums where people recommend doing all sorts of forced installs and run script that "fix" your system. No wonder these people find Linux complicated. Many with bad experience from it did some bodge at some time to get some unsupported hardware working.
I also dislike the idea that started to get popular in the early 00s that Linux was somehow "about choice". Sure you can swap out system components, which you can with any OS from the same era, but that doesn't mean you should. You're going to have a tough time upgrading if you run your own init system.
Modern Linux distributions are great in the sense that they "just work". Plug in my printer and it just works. Third party drivers are much more common in the Windows ecosystem, and they have varied quality. Good luck getting that printer working in a modern Windows as you'll only find drivers for older versions. Suspending my Thinkpad works every time, while another laptop sometimes awakens all over again. The key to "just working" is running well known hardware (no third party drivers required) and not messing about too much with your system internals just because you read it was the cool thing to do.
Last time happens to have been two weeks ago, so now I know what I did this time: create a .config/fontconfig/fonts.conf file containing:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="pattern">
<test qual="any" name="family">
<string>monospace</string>
</test>
<edit name="family" mode="prepend" binding="strong">
<string>Noto Mono</string>
</edit>
</match>
</fontconfig>
(I used Noto Mono, but pick what you like)
In case that's helpful to someone else...Good point.
No, they really don't. Plus those are very different things, organization membership vs choice of license.
Today such terms seems old and less descriptive. People know if they are running Debian, android, Ubunutu, or Red hat, and the kernel/system tools are not the main distinguishable feature of the system any more. The lawyer and the person would both call an android system android.
I don't know where this guy drew his "once settled... [things go great idea]..." conclusion. Relevant XKCD[1]
But distribution upgrades are still broken.
I never got a distribution upgrade working. It always destroyed the OS and I had to reinstall the whole thing.
Just last weekend I tried to upgrade my Xubuntu to 16.04 (last LTS to new LTS), which didn't work out.
It's like my computer's are garbage so I use Linux to compensate for the lack of hardware but now I like using Linux as a web developer.
I have tough time dealing with HDMI sound than Wi-Fi these days.