Hacker Newsnew | past | comments | ask | show | jobs | submit | r0b1n's commentslogin

You could maybe just stuff the inside of the sharkfin full of tinfoil.



Just because all the other languages are inferior for the lack of a "doch" equivalent... ;)


That's the verbal equivalent of the Indian head-tilt, right?


Schon, aber doch mit anderer Bedeutung.

And we have more of those, like "schon", "gell", "fei" (in some dialects), "halt", "eben". Maybe a few more I cannot think of right now.


If you cheat a little, you can get to similarly low numbers in German:

"Zuviele Abschiede von ihr" - 8

"Ihre zuvielen Abschiede" - 8

"[Sie] verabschiedete sich zu oft" - 8-9

If you accept "trennen" ("separate") for "saying goodbye", you can do

"[Sie] trennte sich zu oft" - 5-6

If you accept "[weg]gehen" (go [away]) for "saying goodbye", you can also do "[Sie] ging zu oft [weg]" - 3-5

The "Sie" (she) is optional, but leaving it out sounds hurried and informal.

The literal translation also isn't very idiomatic imho, I'd rather expect to hear one of the latter ones if it was really about separations and going away, the former phrasing suggests more something of literally saying too many greetings.


More like "Sie verabschiedete sich zu viele Male zuvor" (literally, "she farewelled too many times before", but acceptable to a native speaker).

And no, you can't omit "sie", German is not a Romantic language and the pronoun is required even if the verb has to match it by case anyway.

I'd say your examples are more than "a little" cheating. Most of these are incomprehensible or completely fail to deliver the same idea as the original. You can truncate sentences in poetry but at some point you just end up with disjointed fragments.


If you cheat a little you’d say “she said goodbye too many times” and leave before implied in English also. But then the song wouldn’t sound as good.


If you want to keep it very formal. Informally one would say something like "Trau dich, trinks!", or even shorter, "Komm, trinks!" or "Hopp, trinks!". Also depends on the exact intentions, if it were a bet, one could translate it as "Wetten dass dus nicht trinkst?", which would also state which side of the bet the speaker is on. "Herausfordern" is also more something like "challenge", as in "one knight challenging the other", less like "dare" as in "one child trying to get the other to do something".


Not quite. Edges can break from excessive rolling and bending which is the usual mode if the steel isn't over-hardened (Excessively hardened steel will not roll over, only break, and is usually impossible to sharpen). You can get breaks from hitting something hard like another metal or ceramic surface, but those accidents you cannot fix with honing. They should be rare if you pay attention. Wear can also be fixed with frequent honing if your hone is either hardened steel (usually the ones with the very fine structures and the dull darker surface) or diamond surfaced, because both are mildly to very abrasive.


I also sometimes do this (although not with tomatoes). But my knife for this is very sharp and hook-shaped (I think the english word is "turning knife"). Only thing you have to pay attention to: when cutting "against your thumb", never press your thumb into the knife, otherwise things will get bloody. The technique that works best imho is to e.g. hold a carrot in one hand, knife in the other, thumb fixing the carrot and knife edge cutting in a rotating motion around the carrot's axis beside your thumb.


SafetyNet was always about DRM. The Play Store contains tons of malware despite SafetyNet, and malware does malware things despite SafetyNet.

Also, SafetyNet makes alternatives to Google Cloud e.g. for Backups non-viable, so win-win for Google I guess.


You are confusing SafetyNet with Play Protect. Play Protect is about protecting devices from malware. SafetyNet is about protecting services from "untrusted" devices. It is a remote attestation API that validates that the device is running a "trusted" operating system.


What backups? It's literally impossible to take backup images of an Android phone (as in: the entire thing, not just some Playstore apps and some of the settings).

The last phone I used that supported taking a backup image of the entire phone was a 2013 BlackberryOS 10 device.


You cannot even backup all of the playstore apps, tons and tons set the magic "don't backup" bit.

You are totally right in that there are basically no useful backups on android whatsoever. The closest thing is "adb backup" when you have root and developer settings enabled, which is saying a lot.


Even adb backup isn't possible: it's been deprecated for years and I've never ever gotten it to work even with root and the right dev settings.

It starts creating an image of a couple of GB (takes a couple of hours, lol) and then just bugs out and stops. There's no error checking or anything and when it bugs out it means you have start all over again.


Even Firefox does this. Because of something something security.


ssh-ing somewhere strange on a small laggy connection is standard operating procedure. Not having internet is normal. Not being able to write gigabytes of crap into root's home is normal. Not to mention not installing some weird language environment like Kotlin just so the config is highlighted properly. Including all the bazillion libs i'll need. And all the editor configuration that i'll of course have to copy around everywhere. And then debug first, to get the language server working on old CrapHeadDistro 17.9 from back when Obama still ruled. Only to get chewed up in the next security audit for having installed too much useless old crap, because I need that to edit some config files...

You can pry vim from my cold dead hands. After pressing <Esc> thrice of course. You may even get me to install a syntax highlighting file somewhere and maybe use netrw if possible. But a random server you are adminning just isn't the same as your average developers single laptop.


>You can pry vim from my cold dead hands.

I won't need to, you're already giving yourself carpal tunnel with all the :wQ! INSERT-MODE :wmkGDonzn zz CWSFD, these hands are already marked for death.


actually the opposite is true. esc-meta-alt-ctrl-shift[0] is more likely to give you carpal tunnel, than vi where you switch modes and then type commands with single keys instead of twisted key combos. i actually get annoyed at how many ctrl-key combos vim has.

[0] i don't know if emacs is that bad, but that's a classic pun that just fit here.


I used vim for 10 years (not really an advanced user, but comfortable with it), and I just learned Emacs for the last 6 months...

I am now completely confused by the Emacs vs Vim religious war.

The two programs excel at completely different layers of productivity.

I can't think of any software that radically approaches improving your workflow like either vim or Emacs, and they are both wholly unique.

I also use evil mode in Emacs and while it feels like a great match, it has some impedance mismatch in some emacs packages.

It really makes me wonder if there is a deeper layer of integration that can be done here to really allow people to take the reigns off their interaction with computers.


I am now completely confused by the Emacs vs Vim religious war

i think at least half of those who keep up with the emacs vs vim war are doing it just to confuse newbies. the other half really just prefers the emacs way or the vi way.

either way though you are right. they are both very distinct, and it's not one being absolutely better than the other.


To be fair, I have never advocated for Emacs either. Nano for quick edits, proper IDEs for anything else.


every editing command in nano is either ctrl-key or alt-key. vi/vim is the only editor that i am aware of that doesn't make me stretch my fingers across the keyboard.


Disagreed. Practice is just one component in a cycle that makes us better:

We watch something, think of something, read something.

Then we try it out in practice.

Then we observe or have someone else observe the practice and result.

Then we take suggestions and improvements into account from that observation.

Then we start over at one of the points above.

If you only just repeat the "practice" step you'll get set in your ways, get used to doing the same mistakes all over, etc.


When it comes to cooking, it's hard to imagine someone getting progressively worse, especially when they are the ones tasting their creations. If it doesn't taste right, they'll naturally adjust and improve. The feedback loop is immediate and personal.


"Better" is very one-dimensional, but cooking isn't. You can get worse at taste but better at health. Better at health and taste but worse at time consumption. Better at price but worse at hygiene. Many things are possible, but without an audience or at least your own critical acclaim, you cannot prioritize.

And, of course, "there is no accounting for taste" meaning that some of the aforementioned dimensions are very subjective.


It's easy to imagine people getting worse over time. I see it regularly.

People don't do blind taste tests when they cook. They cook something and compare it to their previous memory. Then they slowly diverge and enter some crazy part of the space where no one should be cooking an ingredient that way. There's no notion of something tasting right on its own. You need to compare it against a better version of that dish.

It's easy for two people to cook exactly the same dish, following the same recipe, both of them to think it came out great, and then when they taste each other's to discover that one is dramatically better.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: