HN user

lips

224 karma

This is how I code:

⌘ + C,

⌘ + V

Posts4
Comments132
View on HN

Upon digging, you're correct, though it seems I found more references to 2SV, but point taken.

I am staunchly of the 'don't allow my machines to remember anything' variety, so likely not. If this 'remembering' is flagged in an app default, I'd be happy to clear it out and re-test.

I went to retrieve the 2SA/V code, and when attempting to switch back to the dialog, it failed/crashed to the launcher. The dialog was still present in the application switcher, but repeatedly failed. But directly starting gmail bypassed the auth request and logged me in.

Develop mode definitely hits your raws. I just switched from SSD(1)-boot/SSD(2)-cache/HDD(1)-raws to full SSD and the difference was substantial.

This looks like an amazing experience, I'm just worried about performance in my workflow. That said, the future is bright.

I carried a G1 with two spare batteries when doing documentary work. It was lovely. I didn't have to hunt for outlets or deal with using the phone while plugged into a battery pack.

If the phone is a widely used model, it's often not difficult to find new-old stock for a while.

I gave this list of "not cares" a several year window of context. It's pretty obvious OP doesn't want a bag-phone, but might be perfectly happy with the form factor of an iphone 4/5. Not a novel complaint.

Kodak Ektra 10 years ago

On-screen controls will always be substandard. It's confusing, because every company should know what works, based on about 30 years of iterative design changes. Yet here we are, adapting the rotating mode dial into a digital interface. You will not grok this camera.

Things that would get my attention: Hardware slider that can be mapped to ISO/aperture/shutter speed, ideally dynamically. Hardware AF/MF switch, and AE/AF lock options. Focus peaking.

Neural Photo Editor 10 years ago

I am so looking forward to progress in this area, and expect it to be huge in desktop editing and in-camera processing, w/r/t both actual edits, and tonal adjustment. I know much more about the Adobe Raw Engine that I'd ever want to, slowly and painfully acquired via editing 200K+ images - but I know that the proper software will be able to select starting presets for me based on the image characteristics.

I've long wondered how to address this "different itch" problem. People in a position to contribute code don't have the same itches or desires as those who don't, vs a DBMS, IDE, wiki, http server, etc.

"If you look at the previous generation of phones, things like Nokia phones, you had to have an adapter," he reasons. "If you want to connect headphones to professional equipment, you also need a professional adapter."

No, this was (for the most part) an anomaly. (Sony loved this crap.)

And the "adapter" you need for professional gear costs all of .25, unless you want to plug your headphones into BNC, then it's maybe 1$ in parts and 15 minutes at your bench.

Having had the unfortunate experience of using one Amazon app (xbox), I wonder if PBS will see viewership decrease, simply because of the buggy garbage interface their viewers will have to use. To me, it's actually that bad. I have AP for free, never use it.

Just a little reminder that non-nutjobs can:

- Object to GMO crops on basis of politics and intellectual property.

- Support organic cultivation for reasons of environmental and cultural preservation.

This won't substantially change anything, given the existing power-law type distribution of app-store earnings. When the ~app~ store debuted, I called it the K-Martization of software. This is just Apple expanding into Rent-A-Center.

From a "sometimes photographer of fashion stuff" this drives me insane. For one of the key demographics of the application, and an obvious driver of use - IGs link-phobia cuts off the ability to easily and specifically credit a scene: Makeup, set, styling, prop-houses, etc. It's galling.

Stuff like sandstorm is a massive leap towards practical federation, but it came about 10 years late into the conversation. Not that it doesn't still hold great promise (I'm a huge fan, and 100% target demo), but that span of time has allowed us to see this same dynamic play out in enough software spaces that it's a sound observation and rationale for guiding your business or project.

When something like sandstorm can hide even the abstraction of server maintenance, and either: 1) Creating a service is background to account creation. Like say a private hosted sync point (choose your own host) is created when you install the application. 2) I can deploy via an account or "brand" I have established loyalty with, but maintain true portability.

These are new conversations, not possible before.