You don't because you are living in a period where everything is wonderul for Australia.
You know what they say: everybody is a genius in a bull market.
So you have sun, good food, plenty of money and little immigration.
Life is good (if you are not living in the desert naked).
Unfortunatly, there is nowhere in the world where things stay nice and easy. The run ended in europe after 1970, it ended in the US after 1990 and it will end in Autralia.
Now, when things are getting hard, having weak democratic institutions, no political awareness and corporate medling is going to hit hard.
But I wouldn't be too cocky because it's not like we didn't mess up loads of things in our own countries, even if we have strong political commitment.
Besides, if I could enjoy your life style, I would probably be way less sensitive to privacy issues.
So don't take what I said as the words of someone who has the ethical upper hand, because I certainly don't.
And Australia is damn comfy.
Also my partner will probably convince me to go back live there with her at one point, so I'll enjoy it as much as I can.
Skilled immigration is neocolonialism. I truly can't believe how many (supposedly enlightened) people I've had try to tell me with a straight face how wonderful it is to have all these doctors/engineers/etc coming to their country, and how great it is for their economy and healthcare system etc.
Like, you don't think all the people in India or The Philippines or Chad need doctors or economic advancement?? It's just incredibly greedy and selfish. Can you imagine what a person who has just lost their child due to a preventable illness from being unable to see a doctor think when they hear some privileged person from an unimaginably wealthy country that already has an order of magnitude more doctors per capita and whose children will never see the suffering theirs routinely do -- boasting how wonderful it is that they are harvesting all the best healthcare workers from their country. Makes you shudder to think about it really.
These same people will bemoan a corporation from their country going to another one to conduct a resource extraction business (exploitation!) and yet when it comes to their own interests, they are quite happy to take and exploit a less well off country's most valuable resource which is its human capital.
Is it neocolonialism, or is it more like letting people vote with their feet? In a perfect world, we'd all be able to choose where we live.
Most of the people I talk to in Australia are more concerned about all the people that DON'T get let in.
Another lens is that countries are in the business of providing defence, governance, economic opportunity and lifestyle services. Immigrants are customers.
Yes, yes it is neocolonialism. And it's easy to justify by saying "in a perfect world", but we don't live in a perfect world do we so that logic is just completely flawed. "In a perfect world we would do X" does not mean that doing X in the imperfect world we live in results in a better world.
It is neocolonialism because it is extracting the most valuable and profitable resources of less well off countries for your own benefit. Sure they can't compete with the massive incentives offered by the uber wealthy countries. Probably because those wealthy countries have been exploiting their resources including human capital in the past which keeps them poor and dependent.
But they should be thankful that their children get to sew shoes for us for a few cents a day.
Suppose we take the Phillipines and Malaysia, they (together) have about 6x the population of Australia. They have the capacity to train a lot of doctors - and a doctor can have a great life in either of those countries.
They can both also produce doctors more efficiently than Australia, partly due to living costs / ppp and population size, and partly due to Baumol's disease hitting education costs harder in AU.
But let's be honest, no country is talent-limited on doctor production. What's limited are training slots, and that is partly a practical concern... but also licensing restrictions - which tend to be regulated by doctors who have a strong interest in avoiding the oversupply of doctors.
What I am trying to say with all this is that there are many reasons someone might not be getting good medical care in say, the Phillipines but those reasons are not primarily due to doctors emigrating.
What you write doesn't refute the problem which is that countries like this generally have worse health outcomes, healthcare systems, they have fewer skilled workers to build their economies.
Skimming their best resources off the top can't be justified by some dry economic formula (if it happens to be correct) that just by pure coincidence results in a worse outcome for that poorer country and a better outcome for the wealthier one. Colonialists had all sorts of economic arguments too.
I would agree that the Phillipines are under-supplied according to OECD ratios but again, I don't think the problem is emigration.
Personally I think your mental model of these countries is out-of-date. They are sophisticated and industrialised but do have high inequality and some governance problems. As usual, it's a distribution problem. I think you are under-estimating their capacity and they are not at all lacking in talent, education or human resources. Australia is lucky to get skilled migrants but is by no means "draining" them. I think I'd want to see a more quantitative argument before I was willing to accept that.
I'm not saying some individual's story or a particular situation in a particular country is neocolonialism. It's the entire system of siphoning resources from disadvantaged regions to wealthy ones.
Are these rhetorical questions? I'm not quite sure how they address my comment.
There is a difference between that and the systemic concerted efforts by wealthy countries to poach and take the most valuable, skilled, educated of the human capital from poorer countries who are in positions of weakness and far less bargaining power.
I understand that the narrative is that it's about "helping the unfortunates", but really it's not. If a country wanted to help people you wouldn't "help" mainly the ones who can give them something (they are actually helping you), leaving the many more less fortunate ones in an even worse state.
I understand what you mean, but it’s not exclusive to wealthy countries poaching people from developing countries either right.
In Germany(already a wealthy country) doctors move to Switzerland for better pay and better working conditions too.
It’s also very expensive to move internationally. Visas can cost up to $10,000 alone, so I doubt that so many people actually leave developing countries for developed ones.
There are also tons of people who would never move countries because their family and social circle is in that particular place or they want to make their country a better place.
I also think many people move back home from overseas to their
home country, bringing their improved skillset with them.
I didn't intend to imply that's the only situation where skilled migration occurs, but that is what I wrote so I should correct myself. When there is a relatively fair and level competition to compete for resources then there's less room for exploitative behavior of course. That applies not just to labor but really anywhere.
I think you're rationalizing or painting yourself a reality that you wish was true. Brain drain from disadvantaged countries on an industrial scale is a serious problem. Not for the wealthy privileged countries who benefit of course, which is why nobody says much about it and those who do get attacked.
People from less fortunate countries wanting to better themselves in more developed countries is somehow whitey's fault. I...wow. I never thought I would see such backwards retarded thinking on HN, but here we are.
Talk to some immigrants here in Australia and you’ll find that a lot don’t end up in the industry they were in from their home country. We have some pretty strict rules around qualifications for doctors, engineers etc and a lot of other countries educations doesn’t cut it for our standards. So most end up becoming taxi drivers or cleaners. When you speak with some of them, it’s almost tragic to have a talented individual unable to contribute to the field they’re qualified in. But no one forced them to come. No one forces them to stay. Is that still neocolonialism?
Yes it is. I'm not saying some individual's story or an anecdote is neocolonialism. It's the entire system of siphoning resources from disadvantaged regions to wealthy ones.
If that's true, then neocolonialism is meaningless as a pejorative. I associate neocolonialism with economic hit men and predatory loans, not private citizens having the option to leave often abusive governments. By your definition, neocolonialism is simply the absence of serfdom.
> If that's true, then neocolonialism is meaningless as a pejorative. I associate neocolonialism with economic hit men and predatory loans,
Now that is meaningless. There are a whole vast range of ways to be exploitative and wealthy and powerful taking from poor and powerless.
> not private citizens having the option to leave often abusive governments.
I'm talking about the aggregate outcome for the people. The greater good. It's funny the disconnect some people have here between being so fast to denounce "individualism" greed, selfishness etc., in their own countries when they see it is a detriment to them. And yet they go completely the other way when it's a benefit to them and a detriment to people of other countries. That's the height of selfishness and hypocrisy as I see it.
> By your definition, neocolonialism is simply the absence of serfdom.
yes, it is. Serfdom is when a peasant has no right to leave his lord's land. If neocolonialism includes recognition of the right to emigrate when another country wants to accept you as an immigrant, it's too broad a definition to be any kind of useful pejorative.
The collective outcome may be bad for the country from which people emigrate, but the individual outcome is very good for the people who emigrate. And at a higher level of organisation, the importance of retaining one's best and brightest creates incentives for all governments to behave better than they would if it was accepted the people born in a country belonged to the rulers like some kind of global slavery system.
What I'd like is for you to either narrow your category of 'Neocolonialism' in the future or explain you have a minority view about it. The term as it's used today implies the speaker is arguing against it. If your use of the term neocolonialism applies to people 'voting with their feet', then you are either rehabilitating the term or implicitly arguing for serfdom. Neither of which I think were your intent.
I have explained my view on it. Of course it's a minority view because few are willing to admit they willingly and knowingly benefit on the exploitation of those who have less than they do to begin with, but that's exactly what they do.
Trying to say it's either the industrial harvesting of the most skilled people from less advantaged countries, or it's "serfdom" is just outlandish. I don't even know where to start with that!
Based on what I've heard/read a lot of us would fail our own immigration test on Australian knowledge.
I grew up here in our system and was only vaguely aware there was even a second verse in our national anthem. The people trying to become citizens here and have only been here for a short time knew _all_ the words.
Also there are some people who are happy with immigration, but only from other culturally-compatible regions, and as long as diversity (eg. max 10% from any one country) and equality (eg. max 49% males from any one country) is part of the intake.
Australia's economy is pretty dependent on Coal, Aluminum and Gas.
Two of these a hopefully going away soon but the Government is so In bed with mining and they throw more money at elections than every other sector put together that nothing will done about it until it collapses.
Do you understand what you're actually wishing for when you cheer on the destruction of a large percentage of the economy? What comes after will not be so comfortable.
The thing that gets me is not when people advocate for economically shooting themselves in the foot on principal, it's fine to have principals and stick to them even when it hurts you. What does infuriates me is that most of these people then apply a double standard for the other tribe and call them stupid when they advocate for sticking to their principals even when it hurts them.
I suspect the OP is wishing for Coal and Gas to go away soon in the hope it can spare the world from the upcoming catastrophe that is climate change.
What is stupid, with Europe and the USA both planning a tax on carbon, in just a few decades the OP's wish will most likely come true, yet Australia keeps wishing for a different future.
OP's way of life has been made possible by cheap energy. Wishing it away before renewables are able to provide baseload power in an advanced economy (and the storage problem is, at best, decades away from being solved) is unwise.
South Australia has been doing pretty well with a renewables-backed grid.
There was a smear campaign in 2016 regarding a state-wide blackout, caused by severe weather affecting the distribution & transmission infrastructure. [see #1] The incumbant political party used this as an opportunity to blame the renewable generators (and state government, from the "opposite side" of politics). [see #2]
The same severe weather event would have affected any power generator.
Australia has the most abundant uranium reserves in the world. We have exactly 1 nuclear reactor we don't use for making power (yet is actually regionally vital for supplying medical isotopes to hospitals in SE-asia as well).
Every side of politics has acted like complete cowards on this issue, with the Liberals the worst offenders - they pay it lip service every election then do nothing while handing out cash to the coal miners.
A forward-thinking government would be incentivising a diverse economy, subsidised by the windfall from the currently profitable industries.
Instead, the incumbant governments just subsidise the inumbant industries; or rather, the existing "winners". (E.g. subsidising Murdoch media, mining companies, all pulling in millions/billions in profit.)
Australia has one of the lowest rankings in terms of economic complexity [see #1]. Until the government can subsidise emerging markets, there's no reason for businesses to take risks - the low population can't support it.
Propping up existing industries will eventually be a failing strategy. When Australia's "luck" (exploitable resources) runs out, "what comes after will not be so comfortable". But there's still time to steer away from that discomfort. (Unlike the imminent ecology collapse...)
More and more Australians are putting environmental issues ahead of economic, and are aware that this will make things less comfortable in the short term. Making personal sacrifices for the greater good is generally considered a positive trait in civil society. Many are hopeful that things will be better in the long term, and are hopeful an alternative source of income can be found before the inevitable collapse happens.
> The run ended in europe after 1970, it ended in the US after 1990 and it will end in Autralia.
I wouldn't be so sure that they'll ever need to abandon their crutch of geological resources. There's nothing particularly industrious or forward-looking about Australia, precisely because they can dig up dirt and sell it at a premium.
The world is complex. Climate change, pollution, water shortage, demographic fluctuation, power grabbing, economical crisis, etc. So many things can happen and change the rules of the game entirely. Not to mention all what we don't know.
The book anti-fragile have a very good bit on that.
The point is everything moves, nothing stays the same, good and bad runs go hand in hand.
But imagine if a dictator of the last century had access to Facebook social graph...
You gotta be careful when it's good, to not have it too bad when it's getting bad later
Yeah, I really think that having diverse and plentiful raw materials on mostly unused land is always going to be valuable. Off-earth mining is where disruption will eventually come from, but that's going to take a long while yet to become competitive with on-earth mining.
> As a wind catcher requires no electricity to power it
Another fun gem putting things into perespective. Placed in the middle of article where it was already firmly estabilished that those windcatchers were built in ancient times.
Things that are obvious to you and I might not be obvious to every reader. Remember that the BBC has a broad demographic, including kids and people of varying educational backgrounds. Their content is intentionally written to be accessible rather than placing assumptions on the readers prior knowledge.
Do you think that many readers patient and interested enough to reach this point in the article lack knowledge that there was no electricity in the ancient times?
Some? Given the laws of probability and the points I raised in my previous post, yes it is possible.
If you take issue with BBC's mission (https://www.bbc.com/aboutthebbc/governance/mission) then I suggest you research the same content from different sources rather than moaning about it on HN because for a great deal of people in the world (and especially in the UK) the BBC is a great source of accessible content. And frankly, it's much easier to criticise someone else's writing than it is to publish something that is both informative and accessible.
Cinematic tropes of ancient times often show thing slike slaves operating giant fans, either hand held or operated by levels. Since slavery is no longer acceptable it's not surprising that people might be defaulting to the assumption that cooling requires mechanical movement which requires energy, whereas this form of cooling is wholly passive in nature.
I got pretty proficient at using vim in vscode, and personally for me the investment was worth it. It's great for working in HTML with chords like `va"p` (replace selection around quote with clipboard) and `dip` (cut out the contents inside this xml tag). YMMV depending on the type of work you do.
I'm completely hopeless in nano because I can't for the life of me use the arrow keys for moving around, so I just end up typing random strings of hjkl/bw or whatever in the buffer until I realize I have the wrong editor and switch to some variant of vi so I don't fight with my fingers.
One major advantage of vi is that it's always there (except on Windows :().
Not the point. The point is that people can then build db agnostic libs on top, so that several projects from different teams can use it despite using a different db.
E.G: you can use django, no matter if you are a mysql or a posgreq shop and still use the entire ecosystem of apps.
It's always the same with the anti orm crowd, they either avoid any wrapper and prevent having a standard api to build uppon and inspect, or they create a light wrapper that ends up being a poor badly tested and documented implementation of 1% of SQLA.
It's not really an either or thing. There are plenty of reasons to avoid an ORM. When I talk to python devs who don't like ORMs I recommend SQLAlchemy Core. It's all the most important parts without the ORM. In my experience most people against ORMs are not dead set on writing SQL by hand, they just don't like OOP. Of course there are some DBAs disguised as programmers running around, but they're more of an exception than the rule :-).
Took the words right out of my mouth. As someone who has been adamant about using orm’s for the last 15 years, it shocks me to no end that an engineer (or group of engineers) think they can roll a DAO better than a battle hardened orm like SQLAlchemy, Hibernate, Entity Framework. It’s hubris in the least and straight arrogance at best.
Composite types & triggers, for some other examples, are only (at least they are!) available via third-party plugin/'installed app's too. You cannot defer a Django unique 'constraint', because it happens to implement it as a unique index instead.
For the SO question, why do you need to represent that in the ORM? It seems like you've got the SQL, and most ORMs have an escape hatch to just run SQL. Does Django not?
I responded to the same point in a comment there at the time iirc. No reason other than to be friendly/idiomatic to a project and colleagues that's largely Django.
We've used more and more SQL though, for things Django doesn't support, such as (materialised) views. (You can use models with managed=False, but not have it manage their DDL & schema migrations.)
I still try to use Django where possible and especially if it's auxiliary to a Django-managed table though.
Bingo. This. If you’ve broken your relational model then go ahead and use raw sql with your orm. They all support a way of executing raw sql against your data. This is the exception, not the norm.
I just don't see the value in using one for the trivial stuff (select from join where); the intermediate stuff is longer, more verbose, more DSLy (functions, aggregates, groups); and anything rarer/more 'advanced' is just missing.
The useful bit is de/serialisation from 'model' <-> query/record, IMO. Everything else is just limitation.
If you are putting business logic in your database, you are doing it wrong. I get your point. Which is why I said it’s sometimes ok to run with raw sql with your orm. The problem is your database is really great at storing and retrieving data. Keep it doing what it’s good at and do your aggregate work on a separate machine where you have cpu cycles to spare. This is the point. I’ve told people before about hibernate and it’s foreign key constraints on models - “sometimes is best to not define the relationship at the model and just make another trip to the database to load”. Heavily utilized databases are a bottleneck to your systems, stop making them do the work. Do it on the edge.
I think I feel the opposite to you. I want the ORM to handle the trivial stuff like SELECT * FROM table WHERE id=? and UPDATE table SET thing=? WHERE id=?. That's the lion's share of what I'm doing in an app, and it's pointless to type it out with slight variations repeatedly.
On the other hand, for complex stuff, I'd rather write the raw SQL, since it's in a real language and not some half-baked, under-documented DSL that everyone onboarding onto the project will be unfamiliar with.
> I want the ORM to handle the trivial stuff like SELECT * FROM table WHERE id=? and UPDATE table SET thing=? WHERE id=?.
Why are list(Table.objects.filter(id=?)) and Table.objects.filter(id=?).update(thing=?) better?
That's what I mean by the trivial, it's 'handled', sure, with some pointless (IMO) thin wrapper that's Django-specific to learn. (Sure it's not loads to learn, but it has its quirks. I always have to check the meaning of the 'defaults' kwarg to update it create for example.)
> On the other hand, for complex stuff, I'd rather write the raw SQL, since it's in a real language and not some half-baked, under-documented DSL that everyone onboarding onto the project will be unfamiliar with.
Yes, I agree! I just think the trivial wrapper stuff isn't valuable, and especially if I'm using raw SQL for less trivial stuff, I may as well always do so.
I think my comment above might've sounded ambiguously like maybe I wanted DSL for more complex stuff. That's not what I meant - I meant that it tends to be more complex in the DSL than in SQL, up to the point where it's just impossible in the DSL, and you either use SQL or don't do it.
> Why are list(Table.objects.filter(id=?)) and Table.objects.filter(id=?).update(thing=?) better?
I'm not familiar with SQLAlchemy, but with other ORMs, this isn't how you'd write this.
It would be more like Widgets.findOne(id) and then widget.property = bla; widget.save();
For me this is much more natural than writing SQL, especially for the update query.
There are usually also query helpers for simple queries by fields, like Table.findWhere({property: 'value', property2: 'value2'}).
To me this syntax is much less awkward than writing SQL in strings, and it saves you from repeatedly writing out the SELECT statements and where clauses.
The problem is not the orm, it’s how you are treating data. The ORM has features for doing “out of the box” sql if you happen to fuck up your relational model. Which you clearly have in your s/o post. It’s ok, we all make mistakes. SQL modeling has been screwed up many many many times. For these rare occasions where the orm doesn’t match the object model or the desired action you are trying to achieve, there are ways to use raw sql, when necessary. Your case, it’s necessary as the relational model is broken.
Django's default subset is enough to do 99.9% of what you'd need to do (I know from experience) and there are various packages you can install to extend the ORM if necessary or if it just makes your life easier.
Of course, as the other person said, you can always always always descend into raw SQL if you must or if it just saves you time.
It depends what you're doing with the data. If you're trying to map into an object based view of your data, then yes ORMs have at least thought of most of the issues there.
However if you'd like to view your relational data gasp relationally, then the ORM is a giant anchor around your neck.
Good orms like sqla comes in layers, and the object relationships mapping is the highest one. You can use lower level layers as you need, and retain the benefit of a strong battle tested abstraction that gives you introspection and a standard API.
Sometimes I use sqla just for the connection pool and session handling and dump raw sql in it.
It's not raw sql vs orm, as usual it's use a spectrum with good use cases for each part of it, and you usually benefit from all of it. But orm have pareto value in my xp.
I guess a lot of people haven't seen the middle-ground. For me that's always been where I've sat with ORMs. It takes care of some tedious parts of getting data from SQL into my application without pretending that the underlying data isn't relational. SQLAlchemy and Dapper (.NET) have been great for this middle-ground usage.
I personally prefer something like sqlx, where you just scan rows into structs. That's the tedious part of object-relational mapping, and the part that actually makes sense to automate.
Generally, I think what people call ORMs try to do too much, and there is an impedance mismatch on many levels. Objects and relations don't map; objects are statically-defined at program compilation time, and relations are the result of a dynamic query. I think the reason that ORMs work in dynamic languages is that there isn't a rigid set of objects defined by the program; rather they can come and go during execution. So the problem becomes a problem later -- static analysis, editor tooling, etc.
Lifecycles are also complicated. You can have your ORM return dumb objects that you modify and re-store, or they can be "smart" and updated the database automatically. The "dumb object" approach neglects database transactions (multiple writers could have already modified your cached copy), and the "smart" approach neglects the networked nature of your SQL server (you may need to retry, you may need to time out if the server goes down, etc.) by pretending that some server run by another company is actually your CPU's cache.
Finally, I think it's very optimistic to write an application to support more than one database backend, which seems to be everyone's dream. Many have tried. Few have succeeded. I chalk it up as actually being O(n) work to support n databases. MySQL has some quirk that breaks Postgres's assumptions. Even the humble SQLite is different enough that is hard work to support as a secondary / test-only implementation. (I realized this, I think, when I debugged some code that worked in tests, but not in production. The tests used SQLite and did something like "insert into foo (boolean_value=1); select * from foo where boolean_value='t'". In Postgres, the inserted object is selected. In SQLite, it's not! That, to me, was the end of ever supporting two databases without the explicit requirement to do so. I'd still run my Postgres tests against Postgres and my SQLite tests against SQLite, though.)
All in all, I don't get it. Start a transaction, scan into a struct, mutate the object, write it back to the database. Not much code is required. If your mutation operation is too long to run in a transaction (i.e., it reaches out to the network for something), then you really need a state machine, which you can easily implement in your relational data model.
ORMs only have value IF there's an object model you're mapping to. When working in a language that has good support for relational data, ie support for sets of heterogeneus maps, you can skip the whole object model and avoid the whole need for mapping in the first place.
Ruby and Python in particular really missed the boat on this one. I feel like they cargo culted practices from Java rather than embrace the implications of their own langauge's flexibility.
Isn't that what pandas does kind of? You can execute sql queries and get the results in a dataframe which is a dictionary with some convenience functions on top.
Do you feel python could have gone further to take advantage of specific language features to improve that workflow?
I was more taking shots at Django. pandas is a great example of doing things right imo and me ripping on python at large was more my web-dev myopia shining through.
Right, OOP is sometimes not the best paradigm for the given problem. If you're using C# or Java, sure, ORMs fit right in. Ruby and Python, not to mention Lisp etc., offer a multi-paradigm palette where forcing objects in, just to access relational data, just obscures things.
Nothing at all, I'd argue working with relational data relationally is ideal. It was in response to the statement that anybody try to do their own data access layer is guilty of hubris.
I'd say the bigger hubris is trying to shove relational data into object graphs and the challenges and pain of ORMs is proof of that.
I'm quite anti-ORM, though I've never not used one professionally (just because it's already been there / not my decision), so that might be different if I did for a while. I do think something's necessary though, and it maybe is a bit arbitrary where we draw the line for what's an 'ORM'?
For example, I really enjoyed using rusqlite for a little side project/personal thing, but found apart from anything else just the repetition of `(?,?,?,?,?,?)` any time I wanted to insert something was annoying, for example. I started working a bit on [0] .. I don't know if I'd call it an ORM, just so I didn't have to do that, and could write `Model { ... }.insert(&conn)` instead. But still write plain SQL queries, I just want easy mapping between db table and language 'model' struct/class; column and field/attr.
I'm personally not that much against query builders, but I dislike things that try to hide the database. Any datastructure that transparently performs database queries as you access items in it goes swiftly in my "nope" pile. A reasonable exception can be made for streaming iterators in a statically typed context, though that has its own issues.
I especially dislike "load" methods on objects since they hide what is potentially a very expensive operation behind something that looks cheap and is easy to call in a loop; what I want is to query data first and then load it into objects if needed rather than create objects for querying data.
You can use vue without npm, it has a build you can just drop in a script tag like you would with jquery.
Vue can also use the html as the component template like angulajs 1 used to allow. This makes it great for progressive enhancement and plays nice with server side based template frameworks.
Bottom line, vue scales up, but also scales down. You don't need to go full spa, you can hack a quick demo or make a one file tutorial and it's a bliss.
Also, maybe I missed it, but I don't think svelte has the concept of cached properties.
> You can use vue without npm, it has a build you can just drop in a script tag like you would with jquery.
This is actually the biggest selling point IMO. I used Svelte instead of Vue purely for speed, but the benchmarks suggest Vue has made real progress here. Though, I'm not sure that in real applications a virtual DOM solution could ever be quicker than compiled code to update state. But in terms of developer UX, I think Vue has the easiest entry point, and it seems to have decent performance to boot
You know what they say: everybody is a genius in a bull market.
So you have sun, good food, plenty of money and little immigration.
Life is good (if you are not living in the desert naked).
Unfortunatly, there is nowhere in the world where things stay nice and easy. The run ended in europe after 1970, it ended in the US after 1990 and it will end in Autralia.
Now, when things are getting hard, having weak democratic institutions, no political awareness and corporate medling is going to hit hard.
But I wouldn't be too cocky because it's not like we didn't mess up loads of things in our own countries, even if we have strong political commitment.
Besides, if I could enjoy your life style, I would probably be way less sensitive to privacy issues.
So don't take what I said as the words of someone who has the ethical upper hand, because I certainly don't.
And Australia is damn comfy.
Also my partner will probably convince me to go back live there with her at one point, so I'll enjoy it as much as I can.