Agreed. It is incredibly hard to have a discourse about this.
Thanks for the clarification, and also for all your excellent moderation on this platform.
1,241 karma · joined August 3, 2011
Agreed. It is incredibly hard to have a discourse about this.
Thanks for the clarification, and also for all your excellent moderation on this platform.
https://en.m.wikipedia.org/wiki/Der_Spiegel
I was surprised it was flagged and it goes to show how hard it is for a US-centric audience to evaluate foreign news sources.
Neither CNN nor Fox is quality journalism, "quality" being the adjective you left out.
The NYT also issued an apology for their coverage about WMD which was not rigorously fact checked. One of the reporters, Judith Miller, later joined Fox News.
Quality doesn't mean 100% correct all the time, it means significantly better than the alternative.
Comparing the coverage of different sources is part of how you can reach your own conclusions, instead of blindly adopting whatever opinion is broadcasted to you.
In a democratic society, you have to influence the public opinion to stay/get in power. Propaganda is free, information costs money.
If the majority of voters are not willing to pay for quality journalism, you have to get them engaged by fueling outrage and projecting fear. It doesn't matter what side, as long as there are sides you can join and identify with.
Combined with the fact that American politics do have an effect on the quality of life in other parts of the world (trade wars and refugee crisis for example) and the working (aka non-capital) class suffers in most western societies, it is very easy to project similar fears and foster divisiveness.
Who decided to be compliant at this stage of the company, you or whoever is in charge of business operations?
> I felt responsibility to make the product as solid and maintainable as possible
Was this responsibility conveyed to you or did you make this decision on your own?
I'm clearly making an assumption here, but this reads like a case where both sides had a misunderstanding about how engineering time is spend. They trusted you with some autonomy to get things off the ground and found out you are making business decisions on your own that don't fit into resource constrained startup operations. There is always a trade-off and corners can be cut, and my advice is to be upfront about the general approach about those and find out how much they are willing to invest in robustness and product quality at a certain stage.
It goes one step further, you can have platform-neutral code to parse the API returns into Kotlin models.
https://blog.jetbrains.com/kotlin/2020/10/kotlinx-serializat...
A lot of business logic is shared in the domain layer on each platform client (and possibly on the server), and I think re-use of that is/will be Kotlin's main selling point.
Add SQLDelight for shared data access code on clients, and you can cover a lot of ground with one codebase.
They are supposed to evaluate scientific theories by checking testable predictions to find out if the theory is the correct explanation about how things work in our universe. Which means that scientists try to proof themselves wrong most of the time.
A prediction is also often multidimensional and can be accurate about what will happen, while being off about when it will happen. This article https://en.m.wikipedia.org/wiki/Prediction uses the solar cycle as an example of that under the Science category.
Reminds me of a novel that was written over 100 years ago:
> The Trial (German: Der Process,[1] later Der Proceß, Der Prozeß and Der Prozess) is a novel written by Franz Kafka between 1914 and 1915 and published posthumously in 1925. One of his best-known works, it tells the story of Josef K., a man arrested and prosecuted by a remote, inaccessible authority, with the nature of his crime revealed neither to him nor to the reader.
There are intentional communities that support themselves with their own, often agriculture based, products sold on the open market. Plus the usual homesteading.
The skills needed for this kind of work are not highly specialized and in general not well paid, therefore levelling the playing field for everyone in the group.
I think the opportunity cost for IT professionals building a SaaS to support the community is a lot higher, and while I would love to see that work, the chances of key community members dropping out to make more money for themselves is fairly high. I'm not sure if a simple time based system for everyone involved is fair, given the high upfront investment to get the skills needed for IT work.
https://en.wikipedia.org/wiki/Staufen_im_Breisgau#Geothermal...
https://www.thelocal.de/20170818/this-historic-german-town-i...
To my limited understanding, this could have been prevented by a better geological survey.
I remember when ExtJS was positioned in the late 2000s to mimik rich desktop UIs and I think there are still lots of component based frameworks to use and pay for, if Bootstrap doesn't cut it. The prices are steep though.
Can I ask where you you see this demand, is it industry specific?
I was under the impression that the benefits (easy deployment to a known runtime aka the browser, open ports (80/443) in the firewall, large developer pool, potentially cross-platform use) outweigh the UI shortcomings and budgets were shifted to web-based productivity software.
> Daniel Gilbert (born January 17, 1962) is an American billionaire businessman, investor, and philanthropist. He is the cofounder of Quicken Loans and founder of Rock Ventures.[3]
Downtown, but to a larger extend Midtown and Corktown changed a lot. People want to live there again.
I'm not an insurance expert, but I think services like this, that generate personal data over time, pose the risk of calculating the individual insurance risk much better if the insurance underwriter can evaluate this data on an ongoing basis. It has the potential to skew the risk distribution for all other insurance members in the pool including premium adjustments for people who are not handing over their data.
> We were essentially going to fail/give up by taking on consulting work. The decision to integrate with Slack was a bit of a bet-the-company move
> they wanted that desperately. Some teams even pre-paid us to build it for them
Congrats to the successful pivot. At this point giving demand validation another try instead of shutting down makes a lot of sense, given you already invested heavily and had a list of potential users. Happy to hear it worked.
This depends on good timing. As a small team or single developer you don't want to invest months into building a plugin or service for a platform that won't take off. And at the time the platform has great traction, chances are that someone already took the higher risk and implemented something close to your idea.
I would be interested in knowing more about the decision process that made you confident enough in 2015 to pour resources into a Slack plugin, if you would like to share that.
> just to prevent competitors from having access to them
They don't ignore the market, they use their resources earned from participating in that market to keep and/or improve their current market positioning. Which is exactly what their shareholders want, and is fair game until treated as a monopolist.
Average percentages usually don't paint an accurate picture.
https://developer.android.com/reference/androidx/packages
It's current implementation uses classes that are part of the Android layer, mostly the old support library plus some new abstractions like LiveData and Room and Navigation. I see no reason why you could not use the public interface of that library as a compatibility layer for application level code and let it run on a different platform.
Not today, but given the fact that you can't just kill the worlds most used operating system, you either use virtualization like Apple now does again for ARM (and before when replacing Motorola with Intel) or you change the underlying dependencies of the libraries used and compile again.
In terms of migrating away from Android, I think they will use the newer AndroidX packages as the future abstraction layer, which would enable them to replace the underlying runtime with something more native for each platform. It would be a compilation target for Kotlin as well as Dart. All while not deprecating the massive amount of production code out there. But, this is also just a guess.