bendiksolheim

What is a product? They make something that is used by others, and if they follow a product development mindset, calling it a product is fair in my opinion.

You don’t need to install the app, the prices are displayed on the product page in the App Store, towards the bottom. It’s listed automatically for all apps.

If by "only used" you really mean you never ever use anything else I don’t believe you are missing anything. Other than bragging rights of using Vim, of course /s

But if you occasionally use other editors, many of them have plugins or modes enabling Vim keybindings. In my daily work I switch between Emacs, IntelliJ, Vim and XCode, and all of them have varying degrees of Vim emulation, which makes switching a lot easier.

I sure have. It requires a specific attitude and mind set. If you go through those 18 months hoping this will actually see the light of day, there’s a big chance you will be disappointed. If you rather see this as a technical challenge, and your task is to prove that it is possible, releasing the final product might not be as big of a motivator itself. Of course, you might not always know that the chance of success is so low up front. If you don’t, I would guess it is a lot harder.

Kind of a stretch, but all of my hobby projects are like this. I have spent years on a TUI library for Swift, without any intention of releasing it. I do it to understand how terminals and layout systems work. In this case I am more motivated by the knowledge gain and experimentation than actually having others use the product.

Quite the opposite! I would find it highly motivating to work on something like this, even if it was just a 5% chance it would make it onto actual phones. You certainly need the right types of people who are motivated by the right factors, but that is not unique for this case.

Are we reading the same reports? At least the two latest reports by Cure53 mentions "source code audit". In addition, the audits by ISE and AppSec explicitly mentions code review as part of the audit.

I am in no way familiar with these kinds of reports, but does this not mean that (at least parts of) the source code was audited?

> When you're on prem you only have to worry about your own employees opening sketchy PDFs

This is just plain wrong. When you’re on prem you have to worry about configuring all of you hardware and software correctly yourself. Your firewalls, your SSH server(s), off site backup systems, hardware failures, software patching, access points to your network – the list goes on. Some of these are true for cloud services as well.

They are just different trade offs. Sometimes on prem makes sense, and sometimes cloud services makes sense. You can’t say that security is less of a concern in one of them.

> Nevermind the fact that the next time a major world conflict occurs, the big 4 cloud providers will probably be destroyed, taking about 90% of the western economy with it.

And it somehow does _not_ take your on prem system with it? Even though cloud providers are spread across the whole world, and your on prem system is most likely in one, single location?

This is probably not at all intuitive to the regular Windows user, my parents would never understand the implications of this.

Changes are always difficult, no matter how small or large they are.

As a European, I welcome this wholeheartedly! It makes my daily job harder (as a programmer), but it’s needed to stop this insane industry of using private information as a currency. Most people seem to don’t care, but that is mostly because they don’t understand the consequences of this.

GDPR isn’t really that hard to understand. If you need to gather PII, you need the proper approval from the end user to do so. If you don’t have the proper approval, you can’t store it. Also, don’t gather information you don’t need. If you only need page views, don’t store IP, resolution, localisation and all these things in addition. This is common sense, not science. In fact, you should be happy to have these restrictions, because it lowers the risks in case of data breaches.

The real problem with GDPR is that we’re so used to violate peoples rights that we have completely forgotten how we should behave.

How do you decide what’s unnecessary and what’s not? It would depend entirely of what you want to communicate, and to whom.

We don’t know what Jony Ive intended with this website, but the fact that so many here are criticising it makes me quite certain that we are not the target audience.

Which is better depends on what you want to achieve. In this case, the whole point is to make git easier to use as a tool. Carrying over ideas we already know are confusing would therefore be wrong in my opinion.

Are people not allowed to change their opinion? It seems to me that this is a person who once believed something, but later has gotten proof that what they believed was wrong and then changed their mind. This is a good thing, not at all hypocritical.

> I'm not sure if this is satire or not, but certainly the single worst case of using a terminal is file manipulation. Nothing will ever beat the right-clicks or Ctrl+C/Ctrl+V combos. It's just more natural to "see" things that you move.

This might be the case for you, but please don’t mistake it for an objective truth. I find the terminal far superior for file manipulation than any of the graphical file explorers I have used. I especially find copying quite clumsy, as I either have to open several windows and navigate to the correct locations, or leave the source folder behind as I navigate to the destination. In my terminal I can stay in the source folder if I want to, and even navigate directly to the destination with a short, generic command.