Sure, but the difference between “I win awards for figruing out how to decipher ancient scrolls that no one has been able to do despite their best efforts” and “I can’t research well enough to discover appropriate existing tools for document conversion” is very hard to reconcile.

Ok so they were apparently in Greek but not from Greece. Source: https://news.unl.edu/article-2

Is this fake?

For context, this is the guy who figured out how to see what’s written on some ancient Greek Scrolls without destroying them. It seems slightly far-fetched that he wouldn’t know better.

Testing in production rules actually. Use feature flags and monitoring and you’re all good

Given that they own all of the source code (CLA is required to contribute), they can just stop offering the code under GPL, unless they happen to have any GPL dependencies not under their control, in which case this would not be viable.

General purpose: Kebab case

But really, follow the conventions of what you’re working on. For example, I’d use pascal case when working on a Java/Kotlin project, and snake case when working on a Python project.

Testing in prod is a power move honestly. Rock star-level

I don’t know if it matches your desire for easy install of small disk space, but it might make up for it in other arenas - Ruby is my new-found love when making simple scripts. Being able to mostly emulate the shell integration that bash has by just using backticks to call a shell command is the killer feature in my book.

Kotlin-style async is pretty neat, ngl.

While Rust would probably have been a good choice for implementing a new browser, I don’t think Swift deserves the criticism it’s getting in this thread:

• Swift was created by the same person who created Rust, and has many of the same nice traits
• Swift is a modern language that is easy for plenty of developers to pick up; I’d place it in the same family as Rust and Kotlin
• Swift grants access to a large pool of native iOS/Mac developers

It’s highly unlikely that this app even comes up on the radar insofar as competing with Google Maps.

The answer is probably more mundane - an automated system made an incorrect call. It keeps happening when it comes to these Play Store app reviews.

Yes

deleted by creator

You can’t deny that it correctly predicted the most likely token in this case.

deleted by creator

What’s wrong with multiple returns?

A vibe

Agreed to the part about job security being terrible in the U.S, but it’s worth mentioning that the premium you get in income for living in for example San Francisco far outweighs the cost of housing.

Realistically I think it’s probably easier to acquire a botnet of less secure systems. This was a targeted attack.