The Government of the People’s Republic of China (“China”) and the Government of the United States of America (“United States”),
Recognizing the significance of bilateral economic and trade relations to both nations and the global economy;
Acknowledging the importance of a sustainable, long-term, and mutually beneficial bilateral economic and trade relationship;
Believing that continued consultations are conducive to addressing mutual concerns in the economic and trade sectors, as evidenced by recent discussions;
Committed to advancing related work in the spirit of mutual openness, ongoing communication, cooperation, and mutual respect;
Hereby agree to undertake the following actions by May 14, 2025:
The United States will:
1. Amend Executive Order No. 14257, dated April 2, 2025, to adjust the ad valorem tariffs imposed on Chinese goods (including goods from the Hong Kong Special Administrative Region and the Macao Special Administrative Region). Specifically, a 24% tariff will be suspended for an initial period of 90 days, while retaining the remaining 10% tariff as stipulated in the executive order.
2. Revoke the additional tariffs imposed under Executive Orders No. 14259 (dated April 8, 2025) and No. 14266 (dated April 9, 2025) on these goods.
China will:
1. Correspondingly amend the ad valorem tariffs imposed on U.S. goods as specified in Tax Commission Announcement No. 4 of 2025. A 24% tariff will be suspended for an initial period of 90 days, while retaining the remaining 10% tariff on these goods. Additionally, China will revoke the additional tariffs imposed under Tax Commission Announcements No. 5 and No. 6 of 2025 on these goods.
2. Implement necessary measures to suspend or revoke non-tariff countermeasures against the United States that have been in place since April 2, 2025.
Following the implementation of the above measures, both parties will establish a mechanism to continue consultations on economic and trade relations. The Chinese delegation will be led by Vice Premier He Lifeng, while the U.S. delegation will be headed by Treasury Secretary Scott Bessent and U.S. Trade Representative Jamieson Greer. Consultations may take place in China, the United States, or a mutually agreed third country. As needed, both sides may conduct working-level discussions on relevant economic and trade issues.
Just scamed through all the recommended English GoLang blogs from go.dev and have an interesting finding. Most of the blogs recommended don't have update for quite some time(more than 1 year) or the quality of the article related to GoLang are not high anymore.
Does this mean that people are not active in GoLang community or the Go team is not diligent enough to update the recommended GoLang resource list?
It's hard maintaining a list like that. People do come and go all the time. Even the official Go blog has spurts of blogging every week for a few months then goes quiet for ages. Most communities are the same.
If you want something to see every week, check out https://golangweekly.com/ which I edit. I put up with the weird tempos and people coming and going so readers don't have to :-D Also check out /r/golang on Reddit.
adding a few tips I have after playing sometime with cursor.
1. do commit frequently, recommend to do commit for every big change(a new feature such as a new button added for some function, some big UI change like added some new component changing the UI layout a bit)
2. test everything(regression testing) after doing big change with cursor, it may affect existing functions when adding new features you think should not impact other parts
3. if trying to add a new complete feature including changes to multiple places(fe, be etc), please using Composer instead of Chat
4. when working with UI changes(fe), be careful of needing forth and back of changes. one recommendation is you write the skeleton yourself, then ask cursor to fill in the missing components.
5. when giving instructions, use bullet points and state clearly about the requirements(write the step-by-step instructions) would have better result.
In my .cursorrules I have instructions that after every testable change it should ask me to test it, and if I say it's good it should commit.
So I ask for some feature, it implements, I test and either give feedback or simply say "good" or "that works" in which case it'll produce a commit command I can just press Run on. Makes it very easy to commit constantly.
Also I use Composer exclusively over Chat and have zero hesitation to hit those restore buttons if anything went down the wrong path.
Claude works fine for me. Was using GPT in Cursor, but not working, switched to Claude and works fine now. Good thing to have multiple models integrated.
Status: Identified - We have reports of API calls returning errors, and difficulties logging in to platform.openai.com and ChatGPT. We have identified the issue and are working to roll out a fix.
While the article raises some valid critiques, it often overlooks the fundamental tradeoffs that make Go successful in its niche. Go’s simplicity is not a flaw but a deliberate choice, enabling rapid onboarding and maintainable code for large teams. Its explicit error handling may seem verbose but ensures clarity and avoids hidden surprises common in exception-heavy languages. The complaints about ecosystem isolation and tooling ignore the fact that Go provides powerful built-in tools like pprof and dlv, which are better suited for Go’s runtime than general-purpose alternatives. Go isn’t trying to be Rust or Python—it’s a pragmatic tool for scalable, performant systems.
That should not be an issue, unless the code is written in notepad.
As for interfaces, a better approach is to return struct and accept interface in your functions wherever it is possible.
