Shouldn't it be "So Long, macOS. Hello again, Linux?" I have known people who has done the same, and are back again on macOS. Give it a bit, and it will pass.
So Long, Macbook. Hello Again, Linux
191–200 of 531 posts
Re: So Long, Macbook. Hello Again, Linux
#192Earlier quoted context omitted.
> On a Mac, you can cut/copy/paste using predictable keystrokes in any application, anywhere Interesting, because Linux is my daily driver, and when I borrow my spouse's MacBook one of the things I get tripped up on is some programs seem to use Ctrl+C/V and other programs use Command+C/V for copying/pasting
Interesting, I don't know a single program on OS X which supports Ctrl+C/V for copy&paste but does not support Command+C/V (indeed, I know only a tiny set of programs that support Ctrl-C/V at all, mostly cross platform software that is badly adapted to OS X). Out of curiosity, could you name an example or two?
One example I’ve found is the trading software for Interactive Brokers. It’s a Java application with mostly custom (and fairly clunky) UI, and it has other Windows-isms like adding an icon to the desktop when you install it.
Re: So Long, Macbook. Hello Again, Linux
#193Earlier quoted context omitted.
What is your X session? Gnome/KDE or plain window manager? It might be, that your wm is not launching some service that wayland session is and 1password needs.
This was a clean install so Gnome shell - worked just fine on Ubuntu 17.10 and 18.10 with X and Wayland. After I login through the 1password website, the extension window opens just fine so it might be some input security service, but how would a Firefox extension even have access to a system service like that except through Firefox's built in APIs?
I don't know how 1password works; I'm using keepassxc.
With keepassxc you have native application and extension, that communicate together via socket. The native application can use whatever native APIs it wants.
However, back to you. What's more weird, if it is pure Firefox Webextension, that Firefox (still by default) launches as X11 application under Wayland, so the extension should have no way to know the difference.
Re: So Long, Macbook. Hello Again, Linux
#194Earlier quoted context omitted.
That's true: some things are easier on Mac. In particular, I'd say that using software that hasn't been packaged for your distribution is much easier on Mac. However, your example of fonts is definitely not one of those areas, anymore. Font rendering on Linux is as advanced and capable as any other OS including in the areas of kerning and hinting. It should just work without any user intervention and look great. I ag…
> Font rendering on Linux is as advanced and capable as any other OS including in the areas of kerning and hinting. It should just work without any user intervention and look great. This isn't entirely true. AIUI, Apple enables LCD filtering and subpixel rendering by default, because it knows that you're using an LCD and what the subpixel order is. However, these are usually toggleable via the GUI, and even without t…
People forget that subpixel rendering was a thing on CRT's before LCD's were around. Subpixel order is pretty universally standardized. Is there an EDID data element for pixel order?
Re: So Long, Macbook. Hello Again, Linux
#195My 2011 Macbook has been hanging on and functioning well with some upgrades. When I do finally replace it, it will be with a linux laptop. I'm not interested in paying that ridiculous price for a computer that sacrifices functionality for aesthetics. I fully expect that there will be some trade offs in the "Just Works" category, but I've been using linux as the driver on my desktop for a while with few issues.
I'm about to switch to Linux from my 2010 MBP (which is still basically working) and my main motivation is exactly the fact that "Just Works" no longer applies to MacBooks.
My £2800 company MBP has half-broken USB-C ports, malfunctioning Touch Bar, various audio issues, and I can't use Blender to render on the GPU because of Apple's shitty outdated OpenGL. I could have two Linux laptops with better specs for the price of this piece of fancy aluminium, and a similar amount of bugs/broken stuff.
Re: So Long, Macbook. Hello Again, Linux
#196I did that a couple of years ago and never looked back https://jeena.net/why-i-switchedfrom-osx-to-linux
Re: So Long, Macbook. Hello Again, Linux
#197I so wish the Linux community would get its act together and implement a working usable clipboard. It's the one thing I miss the most whenever I switch from Mac OS to Linux. On a Mac, you can cut/copy/paste using predictable keystrokes in any application, anywhere. And there is a single clipboard. On Linux, you have to deal with a multitude of behaviors (middle mouse button, Ctrl-C, others, and does it paste where th…
There are clipboard applications which will pull everything into a single clipboard. KDE Plasma, for instance, has a great built-in clipboard which does this and which also handles at least images as well. > The second dream wish would be for consistent keybindings in all text input boxes, like in Mac OS. Such as make Ctrl-A always go to the beginning of line, Ctrl-E always to the end, and Ctrl-K always kill whatever…
The issue is that on a Mac, the conventions work in (almost) any app, in any text entry area, and it's frustrating to not have that work. For example, Excel violates this convention for formula editing, and it's really grating to edit using only left, right and backspace. Probably MS has their own conventions, but I don't use Excel enough to learn them. Command line apps and things like MacVim are obviously a different story.
The controls are actually a little strange, because they aren't well documented or discoverable, and don't seem to be configurable, unlike most other shortcuts.
Re: So Long, Macbook. Hello Again, Linux
#198Earlier quoted context omitted.
> On a Mac, you can cut/copy/paste using predictable keystrokes in any application, anywhere Interesting, because Linux is my daily driver, and when I borrow my spouse's MacBook one of the things I get tripped up on is some programs seem to use Ctrl+C/V and other programs use Command+C/V for copying/pasting
Wait what? What programs are you using that use Ctrl for clipboard actions? Do they also allow their Cmd equivalents, or are they just using the wrong keys?
I've only see this in parallels when using a windows application.
So if you have windows office because it has traditionally been better than the one offered to mac you'd have to remember to use control instead of command.
Re: So Long, Macbook. Hello Again, Linux
#199End-user Linux has definitely improved in the last few years. It offers a lot of attractive features for what I imagine to be the typical HN demographic. That being said, it's still got rough spots that OSX doesn't. It works great when it works, but when it doesn't.... Font rendering, display/compositor fragmentation etc... Inb4 the anecdotal "well it works for me I just had to download the xf86 font library and comp…
> Font rendering, display/compositor fragmentation etc...
So take a user from Windows 10 or OSX whatever, and sit them in front of your favorite stable Linux distro running a terminal emulator and a browser of your choice.
Are the fonts going to be rendered in a way that is unobtrusive for those users, or will things look ugly and difficult to read?
Because I'm running a chroot of Debian Buster on my Chromebook and boy, that terminal sure does look blurry. (And is this a bug that will be fixed when Buster stabilizes, or am I expected to go read some font wiki on a different machine to "guess-and-check" it back to sanity?)
I don't want to switch to OSX. But I also understand why someone wouldn't trust the UX of a system that ships in "headache-mode" by default.
Edit: clarification
Re: So Long, Macbook. Hello Again, Linux
#200Earlier quoted context omitted.
Wait what? What programs are you using that use Ctrl for clipboard actions? Do they also allow their Cmd equivalents, or are they just using the wrong keys?
As far as I remember, Terminal, iTerm2.
Just double checked — neither iTerm not Terminal allow the Ctrl modifier for clipboard operations. In fact, terminal applications are _precisely_ the applications I use to argue that Cmd-X/C/V is overall nicer, as they don't interfere with the usual meaning of the Ctrl modifier as a way to produce control characters (which are especially useful in the context of a terminal)