nomagick

你问他严肃深刻的问题他也这个风味回答你，挺无语的其实

大概把起点中文网给训练进去了

@jhytxy 没用老蒋收它干啥

唉，是我唐突了，不该说这么多

@Acheao
@plasticman64

黄金发展到今天，它的货币属性不是由个人行使，而是由国家行使，各国社会各自动员，各自配置资源； 国家之间的交易，由黄金完成，目前美元的地位从黄金衍生而来，未来美元一旦出了什么问题，黄金就是底牌。

黄金买的东西，难道以为是个人买可乐雪碧大白菜吗，还是买 iphone ？
必定要买战略资源，石油，军火，粮食，最次才是各种工业原料， 是动员别国社会的生产和资源为己所用

去到纸币崩盘的地方，以为拿着黄金出门买早餐不成，对不起，买的是命，买老哥的项上人头和手里的 AK47

你有比特币，那你有 AK47 吗？

唉，现在炒币的选手对货币的理解实在是太浅薄了

货币，是进行社会动员，资源配置的工具

金银，天然货币，为什么是天然货币，因为金银天然能进行社会动员和资源配置。
你拿着金银，到了一个纸币崩盘的地方，到了一个战火纷飞的地方，到一个穷乡僻壤没网没电的地方，依然能够进行社会动员和资源配置。

而你拿着比特币，你能动员谁，能调动什么资源，如何才能动员，如何才能调动

郁金香就是郁金香，炒归炒，洗归洗，大家懂得都懂，不要假装什么货币了，也别往自己脸上贴金，真是字面意义上的贴金

我猫打的回车，凑合看吧。。

我之前和 Gemini 2.0 唠嗑，让他生成了一个备忘录

MEMORANDUM

To: Interested Parties in the Software Development Community
From: [Your Expert Persona - The Wise and Honest Software Industry Expert]
Date: December 28, 2024
Subject: A Critical Analysis of Systemic Issues in Frontend Development and a Proposed Intervention Strategy

Introduction

This memorandum documents a critical analysis of the systemic issues plaguing the frontend development industry, along with a proposed strategic intervention approach to address these problems. This analysis was conducted through a series of detailed discussions focused on understanding the root causes of dysfunction in the field, the influence of key technologies and practitioners, and potential paths towards a healthier and more sustainable ecosystem.

I. Core Issues Identified

Our discussions revealed a complex web of interconnected problems:

The Tyranny of Frameworks and Abstraction:
Over-reliance on frameworks (React, Vue, Angular) as the starting point for development.
Excessive abstraction of core web technologies (HTML, CSS, JavaScript), hindering fundamental understanding.
Reduced reusability of components due to framework-specific solutions.
Erosion of Fundamental Skills:
Widespread "CSS illiteracy," often resulting in reliance on tools that actively promote bad practices.
Superficial understanding of JavaScript, treating it as a means to use a framework rather than a full-fledged programming language.
Neglect of Object-Oriented Programming (OOP) principles.
Over-reliance on state management libraries, ignoring core language features and traditional solutions.
The Negative Impact of Inexperienced Pr










actitioners:
Popular tools, such as Vue.js and Tailwind CSS, created by individuals with limited experience and training, which created poorly designed systems that inadvertently promoted bad practices.
Normalization of these bad practices due to the widespread adoption of these tools.
Framework-Specific Problems:
Vue.js: Single-File Components (SFCs) leading to vendor lock-in and mixing of different concerns. Inconsistent APIs.
React: Embedding HTML within JavaScript (JSX), reducing code readability and maintainability, as well as the over-reliance on a "Javascript Centric" view of the world.
Angular: Excessive complexity and over-reliance on RxJS, creating convoluted code and a steep learning curve, as well as unnecessary complexity.
The Distorted Understanding of Core Concepts:
Misinterpretation of "functional programming," promoting a diluted and often incorrect version of the concept.
Resistance to Change and Criticism:
Entrenched ideas and ego in key practitioners, hindering the evolution of the ecosystem, and the improvement of existing systems.
Lack of constructive external review, and an echo chamber where negative feedback is discouraged.
The Problematic Nature of Single File Components:
Marketing gimmick rather than a technical solution.
Violation of the "separation of concerns" principle.
Vendor lock-in and reduced interoperability.
Breaks existing external tooling and web standards.
The Semicolon Omission Debate:
Ignoring the psychological impact of semicolons on human programmers.
Prioritizing aesthetics over correctness.
Reinforcing bad practices in the industry.
Dishonest Open-Source Documentation:
Biased and exaggerated claims about project quality.
"Advertorial" content designed to market projects, rather than provide objective information.
Lack of transparency about limitations and shortcomings.
The Influence of Funding Models:
Perverse incentives that prioritize download counts over code quality and long-term sustainability.
Focus on the "framework and ecosystem" instead of promoting interoperability.
The "Anti-Frontend" Trend of Server-Side Rendering (SSR):
Undermining the power and capabilities of modern browsers by shifting rendering to the server.
Inadequate simulation of the browser environment on the server.
Increased complexity and server costs.
II. Proposed Targeted Intervention Strategy

To address these systemic issues, we propose a targeted intervention strategy focused on:

Targeted Education Initiatives (Beyond Fundamentals):
Creation of "critical analysis courses" dissecting popular frameworks and tools.
Development of "anti-pattern" libraries providing alternatives based on web standards.
"De-programming" workshops designed to challenge problematic concepts and behaviors.
Strategic Influencer Engagement:
Identification and engagement with potential influencers who can make a change.
Creation of a "coalition for sanity" of developers committed to sound engineering practices.
Public communication strategy to support those who openly challenge bad practices.
Open-Source "Counter-Narrative" Projects:
Development of "anti-framework" libraries offering standards-based solutions.
Creation of "diagnostic tools" exposing issues in existing projects.
Development of "migration guides" and "compatibility layers" to transition away from legacy frameworks.
Organization of "refactoring camps" to remove unnecessary complexity.
"Truth and Reconciliation" for Open-Source Documentation:
Community-driven effort to create "honesty patches" for existing documentation.
Development of a "critical assessment rating system" for open-source projects.
Promotion of "open and honest discussions" about the limitations of projects.
Creation of "code smell" libraries to identify bad practices.
Direct Engagement with Key Decision Makers:
Targeting decision-makers in organizations adopting problematic technologies.
Providing evidence, data, and economic arguments for more sustainable solutions.
Promoting success stories of projects moving away from problematic frameworks.
"Economic Incentives" for Better Practices:
Creation of a "quality certification program" for frontend projects.
Development of "cost-analysis tools" showing the long-term costs of using problematic technologies.
III. Conclusion

The frontend development industry is facing significant systemic challenges that require a multi-faceted approach for change. Our analysis indicates a need to move away from:

over-reliance on frameworks and abstraction
superficial understanding of fundamental technologies
marketing hype
reinforcing problematic trends.
The proposed strategic intervention focuses on education, influence, open-source counter-narratives, honest documentation, engagement with decision-makers, and creating economic incentives. This approach emphasizes long-term sustainability and real-world solutions. It aims to provide practical steps for transforming the industry and promoting better practices.

This memorandum serves as a comprehensive record of our discussion and analysis. We hope that the proposed strategy will serve as a starting point for change and further discussion.

End of Memorandum

你这可以的，还有硬件，配得上工业垃圾称号，工业垃圾起码还有工业

纯软件的什么前端后端 APP 的，那都不足以称为工业垃圾，直接手搓垃圾。。。