nileshk

Same. I use hide (Cmd-H) most of the time because I want to hide the whole application, not a single window of the application. I also use Hide Others (Cmd-Option-H) to focus on a single app. And I use Cmd-` to switch between windows of the app I'm in.

There is a rare case that I minimize a window, but it's generally because I don't want to work with that window any time soon, but I don't want to close it either, and I have multiple windows open in the app. Since I'm not frequently switching to the window in this situation, its fine if the easiest way to get back to it is to use my mouse.

I specifically ordered the VESA iMac model because of both the limitations of height, etc, and the space on your desk that is freed up by using a mounting arm.

There is a hack that allowed me to use the Nvidia web drivers on Mojave on my 2012 15" rMBP. Not sure if it works on Catalina. You have to reapply it every OS update. I don't think there is a hack to get CUDA working, which was last supported on High Sierra.

Not sure if the same hack could be used on a Hackintosh (with an old enough card). But for now I would just use High Sierra if you have an Nvidia card, unless you really needed something in a later OS and the hack made it possible. I downgraded that 2012 to High Sierra, and keep other older machines on it as well (didn't have a choice with my 2019 16"). It runs very smoothly and currently has enough software support (e.g. latest Office 365 still supports it).

I have medium-to-high fan noise/RPM consistently when connected to an Apple TB display (2560x1440@60Hz), but it's much quieter when connected to a 2560x1600@60Hz monitor. So if it is very specific resolutions, but not necessarily higher resolutions in general, that matches my experience.

Sarno comes up because what he suggests works. It did for me back in 2001 when nothing else did.

I wish macOS would allow for PCI passthrough to VMs (like you can do on Linux via OVMF, using QEMU). I wish I could connect an eGPU and pass full access of it to my Linux VM (or Windows VM), whether that GPU is AMD or NVidia shouldn't matter. That would remove the disadvantages Macs have when it comes to GPU and make it the best VM host (currently Linux seems to be the best option for VM host). I'm sure Mac Pro owners could take advantage of this were it possible.

However, I suspect Apple has no intention of doing this, as they are more focus on pushing Metal and reliance on macOS.

I wouldn't mind seeing PCI or GPU passthrough capabilities this in Windows 10 Pro (not just Server). With their Linux Subsystem progressing the way it is, they really have an opportunity here. Though since NVidia and CUDA are supported in Windows, maybe not as necessary as the situation on macOS.

Agreed. I didn't immediately like OS X when I switched to it from Linux at home (and eventually Windows at work), but once I got the right set of 3rd party utilities (tiling app, keyboard shortcut modifiers, launcher, UNIX package manager, etc), it was a great fit.

I think it'd be difficult to get the keyboard shortcut mappings I have working even in Linux -- Emacs-style keyboard shortcuts everywhere without interfering with the more typical keyboard shortcuts.

Another thing is that if I really need something from Linux or Windows, I can either run a VM, boot into one of those OSes natively, or remote desktop to a server with good remote desktop performance. Hackintosh's are a possibility though have their rough edges, and macOS runs better in a VM these days from what I hear, but macOS is my preferred host OS anyway for things like audio/music production apps and video editing, so I'd want to run macOS natively over other OS's anyway. For the stuff I currently do, Linux and Windows run fine in a VM.

So, going with the original analogy, macOS is like a hotel where you can have your own house inside.

At work, we have some customers who want to use WebLogic and Websphere, and last time I checked those don't have versions that support anything beyond Java 8.

I still use Java 8 even on personal projects. I'm migrating those to Kotlin, so I'm at least not held back with regard to programming language features. I could upgrade those to Java 11 (or 12), just haven't prioritized taking the time to do that over other tasks, and the benefit would be minimal for these particular projects.

When using Java 8 language, I'm just happy to have lambdas and streams. Java 8 was the biggest improvement to Java language since 5 -- and I'd say it's a bigger leap that 5 was.

If you have enough control of the server it resides on, one of the best things you can do is to deny it access to write to the PHP files of the Wordpress install (which requires that you use WP-CLI via command line to do updates), and setup automatic updates by calling WP-CLI through a cron job or however you want to automate that.

When a Wordpress install has write access to its own PHP files, then a vulnerability can do more harm obviously since it can modify the Wordpress install itself and thus more easily "infect" the installation. Denying write access cuts off many attacks from doing significant harm. BTW WP-CLI can also do checksums of your install.

I wouldn't fret too much about seeing attempted hack attempts. If you have enough logging turned on for a public web server, you'll see a constant stream of hack attempts for all types of languages / frameworks. I did this the other day and saw what I recognized as a variety of different attacks targeted at PHP, Rails, and Java.

Regarding usernames: note that Wordpress will, by default, expose those usernames in things like posts (author's username is revealed). I had to modify my theme to make that stop, and even then I'm not 100% sure it's not leaking somewhere I missed. Maybe you want to do all content editing with a user that has reduced privileges and only use your admin user when necessary.

Assuming you meant specifically the Java language, Kotlin for JVM may also be a good option. Solid set of language features that puts it at least on par with C#, and allows you to write more DRY code than you can with Java language. As with any JVM language, you get all the benefits of the JVM. IDE support is great (at least with IntelliJ IDEA). It's an officially supported Android development language, putting it further into the mainstream. Also, as with other non-Java JVM languages, releases are not tied to JVM releases (I still use Java 8 for my Kotlin projects, while using the latest Kotlin version).

For browser or Node.js, TypeScript is the way to go IMHO. Node.js and it's ecosystem have it's issues, but TypeScript is quite nice and a considerable improvement over JavaScript, while being close enough to JS where it fits nicely into the ecosystem. Only downside is that it adds a compile step that can potentially grow to be time-consuming.

Yes, though the PCjr had a version of the keyboard without the chiclet keys. Also either version was a minimal keyboard without separate function keys or num pad.

I had the non-chiclet keyboard. I now don't want to get a newer MacBook Pro because the lack of function keys and escape key, even though my first computer's keyboard didn't have function keys (though it did have escape).

The iMac isn't even that great for aesthetics, at least if you VESA mount it and have a decent amount of external gear connected. I have the VESA-mount model of the 2017 27" iMac, and I end up having a bunch of cables hanging down that I wouldn't with regular displays. Additionally, I find it difficult to rotate the display into portrait mode because of all the cables attached, so I don't bother even though I'd occasionally like to.

If I had a separate monitor, I'd only have at most two or maybe even only one cable running to each display which would be easy to tuck away within the mounting arm. I'd be able to have most of my cables tucked away instead of the exposed mess of cables I have with the iMac.

To make things worse, they don't offer Target Display Mode like they did for a short while, so I can't use the iMac's 5K display with any other machines (e.g. work laptop when I work from home).

If I were buying today, I'd get a Mac Mini (and maybe an eGPU if I ended up unsatisfied with the built-in GPU), and just use my old 30" 2560x1600 monitor or get something like a huge 38" ultra-wide display (the 27" 5K is very nice, but HiDPI isn't a game-changer for me). In 2017, the 27" iMac appeared to be the best desktop Mac option (user-replaceable RAM up to 64GB was a huge factor), and I don't regret purchasing it, but the integrated display with no Target Display Mode is a massive disadvantage.

I found out last year that 1GB RAM is not enough for TypeScript development (whose compiler runs on nodejs). I was building a fairly small TypeScript project on a Linux instance with 1GB and no GUI and no other processes hogging RAM. I was consistently having builds fail with errors about half of the time. Finally figured out that it was running out of RAM and if I turned off source map generation the errors went away. I didn't really need source maps in this case, as I was not developing on this machine, but it certainly would be a problem if I was trying to do development.

Sure, there is a lot of development that can still be done with 1GB RAM, but you're going to run into limitations and it is far from "perfect"

I'm also on an iPhone 7, and don't even really want a premium version of the iPhone SE, I just want an SE-sized phone with water resistance.

If it had nicer specs (e.g. hardware on par with iPhone 8 and a better display) that would a bonus. However, I wouldn't want a high-res display necessarily. I think they should keep the pixel density of the current SE. What I would found after briefly using an SE is that the low-res display coupled with the CPU/GPU from the 6S resulted in amazing UI performance -- much better than the 6S and maybe even the 7. Getting rid of the bezels would be nice, though that might detract from one of the advantages of the SE, that you can firmly grip the phone while being able to touch any part of the screen with your thumb, but it would be worth the trade-off I think.

I spent a week with an SE, after having used the 6 and the 6S before doing so, and I found I quickly adjusted to the smaller screen, and could even type faster since there was less finger travel needed (relying heavily on auto-correct).

Battery life on the SE is also great (at least it was for me), and I'd like to see that replicated on a newer small phone, with whatever tradeoff is necessary to accomplish it (e.g. low-res display, thicker phone).