97 karma · joined September 2, 2019
The dragon book was my textbook in college, brings back memories, might be outdated but some concepts should still be useful.
Edit to add link - https://www.sweettransitgame.com/
I’m really hoping they don’t go the 1Password route and kill their native macOS product to move everyone to the cross-platform one.
[1] https://www.jooq.org/ [2] http://hibernate.org/orm/support/
[0] - https://timdettmers.com/2020/09/07/which-gpu-for-deep-learni...
For MySQL users on macOS, Sequel Pro can export your schema to graphviz format as well - [1]
[0] - https://www.jetbrains.com/help/idea/creating-diagrams.html [1] - https://www.norbauer.com/rails-consulting/notes/erd-diagrams...
If both platforms had to handle such migrations, I guess it's only fair to say that Windows' solution would be much more difficult given how committed Microsoft is to maintaining backwards compatibility.
[0] - https://docs.microsoft.com/en-us/windows/apps/desktop/
I use this a lot, but is missing from this page. I'm pretty sure I didn't have to customise it in the settings myself. Not sure how I stumbled on this, but it works for me in all applications, native or electron (VS code is the only one I have installed).
I would assume the keyboard UX would be a low-lying fruit. I'm hoping someone with deep knowledge about linux can help me understand what is stopping various distros from simply copying the mac keyboard layout. Replace 'cmd' with the 'super' key and setup the key combinations to match macOS. That way they're consistent whether you're in a GUI application or the command-line.
Is it that the super key is not available on every computer? Or are these shortcuts protected by some sort of a copyright? Kinto seems to work by intercepting signals and reinterpreting them, then why not have the X keyboard component recompiled with a macOS keymap? I'm not at all knowledgeable in this area, so may be missing some very obvious challenges to doing so.
Readline refers to the GNU readline library [1]
Thinking more on this, it'll be interesting to see how this plays out for Nikon. They have serious competition from Canon, Sony and others and if they keep their repairs open, Nikon will just end up hurting themselves in the long-run.
Apple on the other hand, is in a much safer position. There is no real competitor when it comes to macOS and so they can make these profit-driven decisions without any serious consequences.
I'd like to point out that when I say "no real competition" to macOS, I don't mean it's better than Windows or Linux. Rather, people who prefer macOS will keep using it, just like people who prefer Windows will keep using it. The force required to make them move to a different platform, change your entire workflow etc, is, in my opinion, much higher than switching cameras. Yes, changing the glass costs a small-fortune, but you have adapters, and image formats are standards.
Alternatively, what stops these companies from offering technical education on repairing their products, and allowing the graduates to setup their own repair businesses? I don't think it's sustainable to keep forcing customers to pay up for $2k+ laptops or cameras every 3-4 years.
That said, if you think that's never happening at your employer, then they have some options IF they're here on an H-1B. IANAL & I don't know anything about other visas either.
If your friend has a degree from a reputable US school and your employer is also reputable, they should have no trouble finding a new job and transferring their visa. GC applications may be redone as well, with the caveat that you don't hit H1 renewal after your previous employer revokes their application and the new one is approved. You could help coach them for interviews and with referrals, but that's about it.
There are risks involved in all these steps of course, so weigh the current salary with potential rise.
[0]: https://www.gnu.org/software/emacs/manual/html_node/emacs/Ke...