mafalda
The first thing to consider here is that Canadians are in an unique position to move to the US.
They are more likely to have family, friends, travel for leisure and business, easier work visas (TN), Canadian universities are recognized in the US, and so on.
Second thing is that for the people that have the means, moving early in life to the US might be the factor between affording the life you want with ease vs having to compromise.
Many of my friends in tech that moved are saving 1.5x to 2.5x compared to the ones that stayed.
So I don't see a way for Canada to not be a source of talent to the US market. But I also don't believe that is the most interesting question.
The question that I believe matters most here from a society/economy perspective is: is Canada's economy providing the right incentives for innovation and entrepreneurship?
From that perspective the first thing that needs to be addressed is that we can't compare only taxes rates and income.
Canada has a very different tax system, where being able to maximize your TFSA and RRSP will probably set you up pretty well for retirement. Cost of housing is high, but cost of borrowing can be much lower than similar US mortgages. Canadian taxes also include healthcare that is more efficient (cost wise) than the American model.
So while you can get rich faster in the US, the reality is that you will need a lot less income to achieve similar quality of life depending on the cities you are comparing.
My personal notes for Vancouver, BC vs Seattle, WA concluded that for a family of 2. The gross income required to live a fair life that includes: - owning a decent property - be able to retire with no need to reduce cost of living - taking vacations and going out often - hedging health costs You are looking for around 200k CAD vs 250k USD of steady yearly income.
Those incomes are very achievable in both places for people that are considered top talent and companies can provide such income locally.
On the tax side, Canada could improve, but I don't believe that lowering taxes will bring much value.
Where Canada seems to struggle is on the regulation side. Canada is aligned with the US, which means that when addressing the Canadian market, your business is most likely also able to easily address the US market. This means that you will probably be better of setting up your center of operations in the US and not in Canada.
At the same time, big Canadian focused corporations operate mostly in an Oligopoly way. Smaller companies need to fight both regulatory requirements that didn't exist before and have a harder time getting the money they need to scale operations.
Adopting European (and Asian) standards could severely improve competition as companies could more easily extend operations into Canada without having to also support the US market, while in the long term Canadian companies would be able to choose the regulations that give their products the access to the most appropriate markets.
Even as someone that had minimal exposure to other clouds, I could easily see how Azure user experience lags due to the lack of proper care.
The amount of pages with a filter bar that will not work properly until you remember to click the load more should clearly be zero at this point, this is an objectively bad pattern that existed for years and should be "easy" to fix. But the issue will probably never be prioritized.
The fact is that unless tackling those issues are part of the organization core values or that they are clearly hitting their revenue stream, they won't be fixed. Publicity and visibility of those issues will always be crucial for the community of users.
The new grouping is not a clear cut, like why is the position of the docked grouped with window behaviour? The older makes it trivial to discover that the dock moves unlike the newer one.
My view is that the design is much less refined and have a lot of space to improve. It isn't bad, the potential is there if you consider a touch + mouse ui. So let's wait I guess.
With this in mind, the one thing for me is peace of mind. I want to have a nice live and enjoy the world around me in a healthy way. Giving my best to ensure that it not only does apply to me, but apply to people around me.
I really do not care if this means improving a banking system do deliver better prices to clients, cooking or teaching people. If I can excel and do some good, it is valid.
But considering the proposal itself. I would approach it much differently.
Sum types could be represented as a closed enum.
type Result enum int{…}
const ( Ok Result = iota{interface{}}, Err Result = iota{string} )
The initialization would be done like: Ok{10}
Err{“Something went wrong”}
The variable itself would act just like and other enum with unpacking being done somewhat close to this: Ok{variableName} := result
Where the variableName would be set to the zero value in case of a bad match.The enum prefix would enforce a single const block and no extension outside the module package.
I'm not an expert in the Swift Evolution process but I must praise it in terms of ease of reading. Back when I was invested in learning more about Swift, reading some proposals helped me understand it better. But I believe the Swift team/community will need to define a boundary some time in the future on what must be added or not to the language as its complexity grows. In the long run, even if a proposal makes sense, is implemented and was reviewed, it usually will also add a new thing to the language that implies in a bigger documentation and another way to code/solve a given problem.
In the AnyObject dispatch regret [0], the author wrote "As I’ve mentioned many times (though not so much on this blog), Swift had to be as good as Objective-C at making most Cocoa apps, or people wouldn’t use it no matter how good the new stuff was". My first real contact with Cocoa was while learning Swift and I can imagine all the hard work that was put into it. Then SwiftUI came on together with a bunch of new features to a language that I was still getting used to. After getting frustrated with the lack of documentation (combined with the lack of knowledge about some patterns) and no clear way to solve small problems while studying it, I've decided to dive again into Objective-C to not only grasp most of in one week but also to find that I did not need most of the features Swift delivered.
And this is something that is part of Swift. By design it offers you multiple ways to tackle your problems and by design it is only going to offer you more ways as time passes. I consider this a trait that is bad for the language itself in the long run. Looking back 7 years after the introduction of Swift I guess Apple would be better served if it just kept investing in Objective-C. But who knows what will Swift and its ecosystem look like in 2028.
[0] https://belkadan.com/blog/2021/08/Swift-Regret-AnyObject-Dis...
Using Mountain Lion in 2021 is going to feel less aesthetic than Big Sur just as using System 8 in 2011 felt. Overall consistency and sizing of Mountain Lion is superior to Big Sur if you consider a keyboard and mouse based OS just as Big Sur is superior if you're used to touch input and modern iOS UI.