V2EX = way to explore
V2EX 是一个关于分享和探索的地方
现在注册
已注册用户请  登录
V2EX  ›  nomagick  ›  全部回复第 7 页 / 共 31 页
回复总数  618
1 ... 3  4  5  6  7  8  9  10  11  12 ... 31  
255 天前
回复了 omz 创建的主题 生活 本以为自己生活还不错,没想到大家更好
不冲突啊,谈上亿的生意不影响房贷车贷没还完
255 天前
回复了 RIckV2 创建的主题 宠物 不想失去猫猫怎么办?
哮喘就是哮喘,都赖在猫身上,没了猫人还是会哮喘

我发现这好多人都没法真正理解,

首先宠物猫不是一个物品,一般来讲这种情况里猫算是家庭成员,如果有人为了某些偏爱的家庭成员可以移除另外的家庭成员,这世界会是什么样的惨况

楼上养鸽子有的人也会哮喘,那你让楼上别养,看你有这本事不,去主张你的生存权,让别人割爱好像理所应当一样

以后要不然宣布,哮喘是一种穷病,因穷发病,一旦长期贫穷无法根治,有哮喘症状只能生活在富庶的家庭,为了生存,让无论是老公还是老婆,立刻给你暴富


猫过敏狗过敏啥过敏,别人为啥没事,别人没事你有事,甚至开始的时候也没事,后来有了事,这叫啥?这叫病。
有病怎么办?治疗,有的能治愈有的不能治愈,有的不能治愈但能控制。

那你自己生病,要求别的人配合你改变生活方式,这是不是一种请求啊,别搞的好像理所应当一样;那身为病人,不愿意影响到家里人的生活质量,这是不是才是人之常情啊,所以大部分人都是忍,都要求在不移除猫的前提下把症状解决。
知道自己猫过敏之后再看医生,看的是让医生在不移除猫的情况下解决症状,提升生活质量,要能移除猫,还用得着医生吗
再回头看看这个帖子标题,说的是 "不想失去猫猫怎么办"


我的看法是啊,对那些因为你的各种原因,能够毫不犹豫移除宠物猫的人,要多个心眼,今天是为你移除朝夕相处的猫,明天,搞不好就为了一些别的 “新成员” 移除朝夕相处的你。
255 天前
回复了 RIckV2 创建的主题 宠物 不想失去猫猫怎么办?
@queue 孩子少了人生体验,当父母的心中不会有愧么。。
256 天前
回复了 RIckV2 创建的主题 宠物 不想失去猫猫怎么办?
现在有好多办法,一是有抑制过敏原的猫粮,二是可以人打脱敏针,三是可以想办法和哮喘共存

不是移除了猫就万事大吉的,即便你移除了猫,同事甚至路人依然养猫,外面依然有流浪猫,空气中其实一直漂浮着二手猫。
猫过敏只是一个诱因,这次是猫,下次也许是花粉螨虫或者某种植物,或者就纯是冷空气,无论是否移除猫你都面临和哮喘共存。

建议你先尝试下离开猫是不是能有立竿见影的效果,然后徐徐图之。

即便离开猫你有立竿见影的效果,也建议你进行脱敏,毕竟现在还年轻,现在是老婆养猫,还能讲讲道理,以后万一小孩想养猫怎么办。

猫过敏的人在动画片里都只能当反派好吗
而 GPT 就不一样了,GPT 属于是冥顽不化
像楼主这种没有 windows 电脑的尊贵的 V2EX 网友,一般都拥有 Mac Studio 或者 Mac Pro, 这种情况,可以购买 CrossOver 直接运行 Windows 版本 Steam
种地,AI 不能帮你种地,AI 也不需要种地
京东何止第三方啊,自营店铺都有售假的

之前老婆脚崴了下单一个红外灯,没注意看买着这货
https://item.jd.com/100029580369.html

当时要求退一赔三,给飞利浦也打了电话,飞利浦方面只是确认店铺并非授权经销商,但飞利浦内部分支众多,这个红外灯没有清晰明确的权利人,也没有主张品牌权利的意愿。
最后处理结果是退款不退货。

又过了这么久,现在只是商品名称里加了“灯泡”,山寨 logo 加了几个字。

翻翻差评,多少人说了多久了虚假宣传,售假,这个店铺就是能屹立不倒,还是自营。

自从有了拼多多,整个电商市场都有拼多多化的趋势。
261 天前
回复了 victimsss 创建的主题 程序员 实现 iodc-provider 的最佳实践是什么
自己写,自己写是完全可行的,我就自己写了,只管核心功能,不实现离谱的拓展,工作量在 1 个月左右
跟老板说把 title 改一下, 软件运行经理,程序资源经理,CPU 调度经理
265 天前
回复了 llej 创建的主题 程序员 对于依赖注入的思考-二


怎么戏这么多

你说的这个不就 this 吗, OOP 啊, 类继承多态啊
265 天前
回复了 Int100 创建的主题 信息安全 发现 NAT 这东西挺好用啊
?
和 NAT 没关系,是存储转发的基本通信方式,
你的包从我手上过,我把它递给下一条还是随手扔了,那还不是我说了算吗,
你问他严肃深刻的问题他也这个风味回答你,挺无语的其实

大概把起点中文网给训练进去了
@jhytxy 没用老蒋收它干啥

唉,是我唐突了,不该说这么多
@Acheao
@plasticman64

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

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

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

你有比特币,那你有 AK47 吗?
唉,现在炒币的选手对货币的理解实在是太浅薄了

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

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

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

郁金香就是郁金香,炒归炒,洗归洗,大家懂得都懂,不要假装什么货币了,也别往自己脸上贴金,真是字面意义上的贴金
276 天前
回复了 Strive123456 创建的主题 程序员 前端开发如何走的更远?
我猫打的回车,凑合看吧。。
276 天前
回复了 Strive123456 创建的主题 程序员 前端开发如何走的更远?
我之前和 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
1 ... 3  4  5  6  7  8  9  10  11  12 ... 31  
关于   ·   帮助文档   ·   自助推广系统   ·   博客   ·   API   ·   FAQ   ·   Solana   ·   2606 人在线   最高记录 6679   ·     Select Language
创意工作者们的社区
World is powered by solitude
VERSION: 3.9.8.5 · 33ms · UTC 14:42 · PVG 22:42 · LAX 07:42 · JFK 10:42
♥ Do have faith in what you're doing.