It's actively maintained with full time developers, performant, supports Kotlin out of the box, and has more features?

My prediction is that we have at best 10 years of anything resembling BAU before systematic failure.

https://medium.com/@smokingtyger/the-crisis-report-27-4e7e9f...

Happy reading.

If you want relational tables, joins, aggregations etc, you want something like this (or the original Web SQL that was deprecated).

There is definitely a use case for it.

- The war in Ukraine will continue on but not conclude, with many more casualties on both sides. Consequentially, the stock price of principal US defence contractors such as Lockheed Martin and Northrop Grumman will continue their significant upward trend.

- Once again, CO2 emissions will continue increasing globally. There will likely be some significant food shortages in part of the world.

- The UK will continue its economic descent, with more significant energy price increases and continued inflation.

Visual designer, integrated IDE and debugger, basic language, very similar philosophy, cross platform (thanks to using the JVM as the compile target).

Unfortunately however you do need Windows to author which is not me these days.

As tools for making little apps or rapid prototyping it's quite decent.

Affiliates. We may share your information with our affiliates, in which case we will require those affiliates to honor this privacy notice. Affiliates include our parent company and any subsidiaries, joint venture partners, or other companies that we control or that are under common control with us."

I would much prefer that this simply read: We do not share your information with anyone.

The problem is that over time, the opportunities to do this have become harder and harder to find. All the low hanging fruit has gone and more and more people are relying on social media instead of websites to communicate and run their businesses anyway.

Additionally, I'm just not interested in privacy violation, spyware, big data, ML etc.. so that frontier holds no appeal for me.

Ironically it seems like it was easier to innovate in the mobile space and find a market in the days of Palm PDAs than it is today.

* If you're wanting to have some change of skill transference into real world table tennis, get an adapter for your dominant hand paddle so your bat has the right weight, position and feel. Also, never forget that the table isn't real.

I think the main topic and real difficultly of DDD is figuring out specifically where and how to separate out different contexts (the so-called 'bounded context' in DDD parlance).

Creating microservices is a good example. Where should the responsibility for a single microservice start and finish? What might the implications for scalability and extensibility be? What does this mean for data storage? What data will be shared or replicated between microservices and how will this be done?

Answering these kinds of questions is hard and has big implications for your teams and for your business.

Are you talking about design patterns by any chance? Maybe things like repositories, adapters, small and focused service classes and the like?

I imagine such a thing would draw at least 200W? And pi's maybe 5 watts? So in theory, 30 - 40 pis vs a single server?

The pis also have an advantage in terms of redundancy. A single pi going down shouldn't be a problem and very easily replaceable.

Would be a really interesting article.