Live data from Hacker News

Building a Lightroom PC

paulstamatiou.com

91–100 of 232 posts

Re: Building a Lightroom PC

#91
post #84
post #2

N.B.: the "switch to Windows" is from macOS and not from Linux, just in case anyone was wondering. I think it's very interesting that the availability of Linux on Windows helped the author choose Windows.

As someone who made the same jump, Windows wasn't really a viable platform for non-dotNet developers until that happened. The state of Linux on the desktop is, frankly, a disaster — I spent months on trying to make it work, but wow, it's not worth the time.

Windows has been a viable platform for software development since always.

I have been developing Windows software since Windows 3.1 and my first UNIX was Xenix, followed by DG/UX, Aix and many other variants.

Windows is perfectly viable developer OS for C++, Delphi, Tcl/TK, Perl, Python, Java and .NET developers.

Microsoft did a mistake not following up on Windows NT POSIX support, because that is what many care about is POSIX shell utilities and C APIs, the actual kernel is irrelevant.

However now GNU/Windows fixes that problem.

Re: Building a Lightroom PC

#92
post #19

I can't imagine spending $6000 on a computer for editing photos and then saying "It also means I don't plan to buy and meticulously use a color calibration device". My computer might not be half as fast, but at least I know my blues are the shade of blue I think they are.

Fair point :) I should reconsider. The UltraSharp line is factory calibrated but yea that doesn't mean much as it varies between display.

Not only between displays, but also between lighting conditions in the environment where the display is used. In principle, you should recalibrate every time you switch bulbs – even more important any time the monitor moves to a different room!

Re: Building a Lightroom PC

#93
post #33
post #23

Earlier quoted context omitted.

UAC limits software to user privileges, even if you're running an administrator account. If you're running an administrator account, you just click YES in a popup to grant elevated privileges when they're requested. If you're running a user account, you enter an administrator password. Disabling UAC lets anything you run use administrator privileges without alerting you. Similar to running a Linux box as root. It's a…

It’s also a popup that comes up several times every week or even day on windows. Really wish it was easier for apps on windows to run in user mode only and stick to it, but it seems like everything needs UAC on a regular basis for one reason or another.

That reason is developer incompetence.

MSDN is full of posts and articles how to be a nice guy and run as user, unless of course the application needs to do some low system level calls.

And even then, there are ways to split the architecture between privilege levels.

Re: Building a Lightroom PC

#94

Earlier quoted context omitted.

Consider the possibility that he simply has a (relative) lot of money.

And time!

It's a project :) I get joy some going in depth with everything I'm passionate about. I do it with my photosets (spent a year editing the 11k+ photos and then designing/developing the 9 photosets): https://paulstamatiou.com/photos/new-zealand/

and other projects like my RasPi Frame: https://paulstamatiou.com/getting-started-raspberry-pi/

or documenting one of my design projects at work: https://paulstamatiou.com/twitter-video/

Re: Building a Lightroom PC

#95
This is a brilliant post. The ability to navigate around the article easily and then parachute into a section and revel in detail is beautifully executed. Using links to add asides is another excellent touch.

When scowls complain that the Web is crap, this is where you take them to see what the Web could in fact be.

Re: Building a Lightroom PC

#97
post #2

N.B.: the "switch to Windows" is from macOS and not from Linux, just in case anyone was wondering. I think it's very interesting that the availability of Linux on Windows helped the author choose Windows.

The switch stories are always either “from Mac-OS” or “to Linux”, the former being a “oh no you didn’t” and the latter being “I’m with cool birds now” narrative. It’s basically non-stories because your OS matters as little as what programming language you use. Pick the one that works for you, but don’t become a fucking missionary or tie your personality to your brand of choice.

Yea, I made the jump from osx to Linux switch more than a year ago because of the hardware situation. I also have dual boot windows just for Lightroom. It was a bit of tinkering just because I decided to go for a bit esoteric distribution (NixOS) and also switch to tiling (i3 and sway). It’s different, I think it’s much better and tiling really keeps the clutter at bay. I am very happy with the setup and when I have to use OS X (still have the old MacBook pro for time on the road) I don’t enjoy it any more.

Re: Building a Lightroom PC

#98
post #84

Earlier quoted context omitted.

As someone who made the same jump, Windows wasn't really a viable platform for non-dotNet developers until that happened. The state of Linux on the desktop is, frankly, a disaster — I spent months on trying to make it work, but wow, it's not worth the time.

Linux on Windows is still a disaster? It's been something I want to play around with but haven't had the chance yet.

I read it as a standalone Linux on Desktop is a disaster. Not Linux on Windows.

Re: Building a Lightroom PC

#99
post #9
post #5

So, the main reason he switched to a Windows machine was to use the latest/fastest hardware with Adobe Lightroom and Premiere, but then he goes on to say the Lightroom and Premiere don’t take advantage of many core CPUs, the fastest GPUs, fastest SSDs, etc... And Windows is fine after tweaking and adjusting dozens of settings. I’ll just stick with a Mac.

And Windows is fine after tweaking and adjusting dozens of settings. MacOS or Linux also require tweaking to be useful for most people.

to be useful? For most people? wow, that's quite a claim.

Re: Building a Lightroom PC

#100
Word of caution 4K@27" is still pretty terrible in Windows. It's fine if you stay in specific apps for 99% of the time (such as a cad workstation or a Lightroom machine as in this case) but 27 requires scaling and many apps simply don't scale well.

The "simple" solution is to run 4K at 32" or larger where you can run att 100% scaling. Unfortunately, if you want a screen with decent color you are adding serious money to get to 4k@32".

Post reply on HN