That’s probably because Israel is a part of the Western world and nobody in their right mind is concerned about it becoming a military threat or sponsoring radical Islamists.
And yet the heavy hitters (Al Qaeda, ISIS and co) never really bothered with Israel. They went directly after other Western nations which supported the Palestinian cause and sponsored Palestinians with billions of dollars.
The concern isn't becoming radical Islamists but becoming no different. The behavior is the ultimate problem. I mean the Shakers are technically a radical Christian sect who doesn't believe in sexual reproduction. Radical Martha Stewart fans deciding to kill people would be just as big of a problem.
Israel is a bunch of middle European people clinging to a mythology of an omnipotent real estate agent granting them land amongst a bunch of eternally warring tribes. It's not gonna end well. I just wish the U.S. would stay out of that bs.
You mean the descendants of Europeans who clung to a mythology that the son of that same omnipotent real estate agent granted them manifest destiny over a continent owned by a bunch of tribes?
And whose support for Israel is based, in part, on the belief that Israel as a state has a role to play in ushering in the Apocalypse of the Book of Revelations and the second coming of Christ?
The phrase "not bloody likely" comes to mind. The US is in with Israel for reasons that go far deeper than geopolitics.
Title should have been "iPhones are hard to use - For old people", it's bad for them, but it's not the fault of the iPhone itself, I bet if you give them any other piece of technology it will be equally hard for them.
You are right in pointing out that it could be better, I think that the "Tips" app can have a dedicated section for accessibility features and video tutorials on how to use certain features of inbuilt apps.
They could also have an app dedicated to Accessibility features, pull out the existing accessibility settings from Settings app and show them one at a time in a UIPageViewController inside that app.
While it's certainly true that people from Gujarat are business minded, I have observed that they are equally narrow minded, especially when it comes to selecting whom they work with and they almost always select a fellow Gujarati.
I have personal experience with this, I had a Gujarati classmate and we had plans for starting up after our college, he later went on to work for his brother in law (who you already guessed it worked in the hospitality industry), he only told me later when I asked that he was pressured by his family to work with them exclusively. You may think that this is a one off example, but it's not, nearly all people I came across had similar mindset.
Also they contributed largely to the election of Modi as a PM in India, who is also (drumroll) a Gujarati, now this may be good or bad depending on how you look at it.
After living in western countries for well over 50 years (calling themselves American, Canadian and British etc), they ooze pride about their entrepreneurial heritage; but they still vote and contribute money towards electing a man whose past screams bloody murder and that is plain hypocrisy!
Java is still at the top of the TIOBE index. Moreover, the familiar Java update progress dialog will display "100 Trillion Devices Run Java Across Thousands of Galaxies".
Asked a question on r/Kotlin as I was bothered by the fact that Google did not include Java samples with the Paging library documentation on the Android developers webpage in hopes that I would get a reasonable explanation of why Java code was being sidelined and in hopes of understanding if future documentation will omit Java completely.
I was bombarded with negative comments and downvotes which ensued no positive discussions and answers, even my reasonable comments were met with anger and disgust.
I want to now highlight these problems on HackerNews, so that people here are aware of the behaviour of the Kotlin community in general and why they should avoid using their language, I also want to get this message across to Google that it should not enforce any particular language on the Android community.
I don't know kotlin, and I don't care to right now. However what you've done is the equivalent of barging into your neighbours house and complained about the wood used in their decking.
You have it wrong, only the restaurant dashboard app is built using ReactNative, that was done because they had a website earlier and they wanted to convert that quickly to a tablet app and their developers who were working on that web app had very limited knowledge of iOS/Android, refer to https://eng.uber.com/ubereats-react-native/
If only we could learn from past experiences, many companies have done that in the past because some CXO thought that they could save some money using hybrid frameworks, didn't go well for them and they ended up writing native apps. It's like you are asking people to fire "Master of one" and hire "Masters of none".
I've said it earlier, I am saying it again. "Kotlin enthusiasts or rather PR representatives cannot stomach criticism", this is quite visible on the blog itself and here on HNews.
Consult with your CEO, CTO and/or Director of Engineering before switching to Kotlin, there may be things you might not be aware of, think 20 years ahead and think objectively about the pros/cons before heeding to advice of the enthusiasts, they won't be there to help you when your app behaves unexpectedly, or if your tech debt increases or when you are unable to find people willing to work with your messed up code base, remember there's no reverse Kotlin to Java converter built into IntelliJ.
My advice is to sit it out and wait for Java to evolve, which shouldn't be far away, in the meanwhile enjoy writing your code in Java in which you have your actual work experience(8+ years in my case), which has books and resources dedicated to help you understand the pitfalls, design patterns and every trick out there since 22+ years of its existence. Besides I would recommend developers to not waste their time on a language which piggy backs on JVM, many other languages which did that or are doing it have failed, Kotlin won't be an exception. Instead use Java to learn and write complicated Data Structures and Algorithms and learn technologies like Machine Learning, Neural Networks and AI etc to increase your job prospects.
I'm a Kotlin enthusiast (since 2013) who has also used Java since 1995 and was quite the enthusiast for many of those years, tracking the progress of Java in detail since inception. I've contributed to both languages. Just so you are aware of my background being strong in both.
Now back to this blog post and enthusiastic defence of Kotlin:
This blog post wasn't a criticism, it was instead under-informed and misleading. You will indeed attract the attention of enthusiasts if you take an authoratative viewpoint against the thing those enthusiasts care about, publish it publically, promote it to the whole community, and use bad (or no) evidence in the process. Who wouldn't stand up and protect something they care about in that circumstance?
By the way, when we were helping to create Java at Borland, we were told many things like you just said: "it will fail", "the CEO/CTO/CIO won't want it", "we can't take the risk", "in 20 years it will be gone", "it's just a toy and not for the enterprise", "dancing Duke is all it can do", "it will fail like the others, Java is no exception", "no real application will be written in it", "it can't do server-side", "stick with C++", "stick with Delphi", "stick with VBA", "stick with PHP"
So obviously the prognosticators and non-enthusiasts were wrong. What makes you better are reading the future than they were? Is Google wrong when backing Kotlin? Is JetBrains? Is Square? Is the Spring Team? Is the Gradle team? Is the JUNIT team? Or are these some of the same people who made the right call on Java way back in 1995-2000 as well? In fact Java would have failed had the enthusiasts not carried it through tough times, shaped it up, improved performance, fixed critical bugs, cleaned up bad specifications, and showcased it to the world. Because of enthusiasts, you have Java.
So let the enthusiasts do their work of defending a good thing against people that just don't yet see the light (or maybe never will care to, so bet it).
