I wonder how they will tackle that in translations
225 karma · joined January 1, 2012
I wonder how they will tackle that in translations
I’m talking about the most common happy path that they don’t want to optimize - the user registration/login
I hate typing a secure password on a phone and I want to evade this process whenever possible. Using Sign in with Apple you don’t have to type a thing and you confirm using FaceId.
It seems like the problems they were facing require different UX solutions than they already had or some bug reports to Apple (if the feature is really missing something).
For me it is much better to use Sign in with Apple as the user as the flow is simple, unified and Apple has a track record of caring about privacy, where it is often not the case for randomservice.io
I dream of a world when I won’t have to type passwords on a phone anymore.
Apple usually prioritizes bugs by duplicate count.
Most of the GUI tools just focus on the MVP workflow and often they crash/bug out on the weird cases.
This is not really an argument against it, but just an observation I made through the years.
Sourcetree is one of the oldest GUI git clients and it has the most stuff handled correctly, and this basically looks like open-source source tree.
2. You assume soya decreases testosterone.
3. You assume that testosterone is the cause of not liking breasts.
4. You assume people don't go to Hooters because they don't like breasts.
I did a makefile like
file1:
wget http://example.com/file1
file2:
wget http://example.com/file2
file3:
wget http://example.com/file3
And used make -j4 to download all of them, but only 4 parallel tasks at once. It starts another download when one finishesI remember that at some point gcc -O 0 was doing exactly that and it is pretty irritating if you write a decompiler and want to test it. Fortunately clang does it properly.
1. What happens if you get sick. You say this is a project in production and there is money on the table (I assume not only yours). What if you get sick and are unable to work for 3 weeks or 6 months. Don't you think that this code is very hard to grasp to someone else, who would have to temporarily work on your postion?
2. It is weird, that you wrote such a long essay, spanning two comments, but it has so little examples from the actual code. Usually when people explain stuff they go between the abstract concepts and how they are materialized in the code. Here you only explain the idea behind writing it and how it makes you feel/operate/gain flexibility and performance but the closest to the code information I've got from it is that it has compiler passes and that it has a C++ runtime in a string variable. Just a thought, what do you think about that?
You don't always have the phone reachable, so I assumed it syncs over iCloud.
g1:
job1
g2:
job2
and then one goal to depend on them all and I used make -j 4Writing in shell is like dancing on a minefield and there are sane programming languages just laying around.