哮喘就是哮喘,都赖在猫身上,没了猫人还是会哮喘
我发现这好多人都没法真正理解,
首先宠物猫不是一个物品,一般来讲这种情况里猫算是家庭成员,如果有人为了某些偏爱的家庭成员可以移除另外的家庭成员,这世界会是什么样的惨况
楼上养鸽子有的人也会哮喘,那你让楼上别养,看你有这本事不,去主张你的生存权,让别人割爱好像理所应当一样
以后要不然宣布,哮喘是一种穷病,因穷发病,一旦长期贫穷无法根治,有哮喘症状只能生活在富庶的家庭,为了生存,让无论是老公还是老婆,立刻给你暴富
猫过敏狗过敏啥过敏,别人为啥没事,别人没事你有事,甚至开始的时候也没事,后来有了事,这叫啥?这叫病。
有病怎么办?治疗,有的能治愈有的不能治愈,有的不能治愈但能控制。
那你自己生病,要求别的人配合你改变生活方式,这是不是一种请求啊,别搞的好像理所应当一样;那身为病人,不愿意影响到家里人的生活质量,这是不是才是人之常情啊,所以大部分人都是忍,都要求在不移除猫的前提下把症状解决。
知道自己猫过敏之后再看医生,看的是让医生在不移除猫的情况下解决症状,提升生活质量,要能移除猫,还用得着医生吗
再回头看看这个帖子标题,说的是 "不想失去猫猫怎么办"
我的看法是啊,对那些因为你的各种原因,能够毫不犹豫移除宠物猫的人,要多个心眼,今天是为你移除朝夕相处的猫,明天,搞不好就为了一些别的 “新成员” 移除朝夕相处的你。
我之前和 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