九维我操你爹
- 2021 年的最終觀察名單。
- 目前Microsoft與Niantic有合作關係。
- 針對 AR 與 Microsoft 合作。
- 與 Microsoft 一起探索軟件和硬件的未來發展。
#Microsoft #Niantic
【經歷親人過世、生命破敗，#林生祥 回到高雄美濃，重新做人】
2022年12月4日，是音樂人林生祥「重新做人」的開端。
在這個開端的六個月後，他的樂團「生祥樂團」以專輯《#江湖卡夫卡》入圍2023年第34屆金曲獎最佳樂團與最佳裝幀設計獎。此時外界看到的林生祥，是工作邀約、獲獎不斷，但許多破敗，他自己知道。
前幾年，林生祥完全感受到「生命的破敗」。演唱會音響出包、疫情阻滯演出、至親接連過世。他覺得很多東西失去控制。「就是那種，無，無……無能為力。那種無能為力。」他停頓再三，才能繼續說下去。
中年人生的困頓，像顛狗的命運，記錄在入圍金曲獎的專輯《江湖卡夫卡》裏。就是在這樣的停滯和破敗，林生祥決定回到創作最初的demo，回訪客庄，回到高雄美濃，重新做人：https://bit.ly/3PylG6W
2022年12月4日，是音樂人林生祥「重新做人」的開端。
在這個開端的六個月後，他的樂團「生祥樂團」以專輯《#江湖卡夫卡》入圍2023年第34屆金曲獎最佳樂團與最佳裝幀設計獎。此時外界看到的林生祥，是工作邀約、獲獎不斷，但許多破敗，他自己知道。
前幾年，林生祥完全感受到「生命的破敗」。演唱會音響出包、疫情阻滯演出、至親接連過世。他覺得很多東西失去控制。「就是那種，無，無……無能為力。那種無能為力。」他停頓再三，才能繼續說下去。
中年人生的困頓，像顛狗的命運，記錄在入圍金曲獎的專輯《江湖卡夫卡》裏。就是在這樣的停滯和破敗，林生祥決定回到創作最初的demo，回訪客庄，回到高雄美濃，重新做人：https://bit.ly/3PylG6W
端傳媒 Initium Media
林生祥重新「做人」：當你50歲，完全感受到「生命的破敗」｜金曲獎2023
所以命運像癲狗，命運不停，他也不能停。
Who wants to build around an ecosystem where the open source users are called freeloaders and where massive disruptions are implemented in the middle of a release cycle, two times in a row, with no warning?
But... it's within their rights, so I won't argue that point. What I will argue is the current subscription agreement, which might not be legal. Red Hat currently says they can cancel any user's account if they download the source code and redistribute it.
Let's say someone downloads the source through a Red Hat subscription, and uses that to build a new version of Rocky Linux. If Red Hat retailiated by cancelling that subscription, I'd definitely tune into that court case.
https://www.jeffgeerling.com/blog/2023/im-done-red-hat-enterprise-linux
Let's say someone downloads the source through a Red Hat subscription, and uses that to build a new version of Rocky Linux. If Red Hat retailiated by cancelling that subscription, I'd definitely tune into that court case.
https://www.jeffgeerling.com/blog/2023/im-done-red-hat-enterprise-linux
https://sfconservancy.org/blog/2023/jun/23/rhel-gpl-analysis/
IBM's Red Hat definitely deserves credit for so carefully constructing their business model such that it has spent most of the last two decades in murky territory of “probably not violating the GPL”.
We fear that be it through incompetence or malice, many RHEL salespeople and business development professionals may regularly violate GPL and no one knows about it. That said, the business model as described by IBM's Red Hat may well comply with the GPL — it's just so murky that any tweak to the model in any direction seems to definitely violate, in our experience.
Furthermore, Red Hat exploits the classic “caveat emptor” approach — popular in many a shady business deal throughout history. While, technically speaking, a careful reader of the GPL and the RHEL agreements understands the bargain they're making, we suspect most small businesses just don't have the FOSS licensing acumen and knowledge to truly understand that deal.
Due to this ongoing bad behavior by IBM's Red Hat, the situation has become increasingly complex and difficult to face. No third party can effectively monitor RHEL compliance with the GPL agreements, since customers live in fear of losing their much-needed service contracts. Red Hat's legal department has systematically refused SFC's requests in recent years to set up some form of monitoring by SFC. (For example, we asked to review the training materials and documents that RHEL salespeople are given to convince customers to buy RHEL, and Red Hat has not been willing to share these materials with us.) Nevertheless, since SFC serves as the global watchdog for GPL compliance, we welcome reports of RHEL-related violations.
IBM's Red Hat definitely deserves credit for so carefully constructing their business model such that it has spent most of the last two decades in murky territory of “probably not violating the GPL”.
We fear that be it through incompetence or malice, many RHEL salespeople and business development professionals may regularly violate GPL and no one knows about it. That said, the business model as described by IBM's Red Hat may well comply with the GPL — it's just so murky that any tweak to the model in any direction seems to definitely violate, in our experience.
Furthermore, Red Hat exploits the classic “caveat emptor” approach — popular in many a shady business deal throughout history. While, technically speaking, a careful reader of the GPL and the RHEL agreements understands the bargain they're making, we suspect most small businesses just don't have the FOSS licensing acumen and knowledge to truly understand that deal.
Due to this ongoing bad behavior by IBM's Red Hat, the situation has become increasingly complex and difficult to face. No third party can effectively monitor RHEL compliance with the GPL agreements, since customers live in fear of losing their much-needed service contracts. Red Hat's legal department has systematically refused SFC's requests in recent years to set up some form of monitoring by SFC. (For example, we asked to review the training materials and documents that RHEL salespeople are given to convince customers to buy RHEL, and Red Hat has not been willing to share these materials with us.) Nevertheless, since SFC serves as the global watchdog for GPL compliance, we welcome reports of RHEL-related violations.
https://www.kens5.com/article/news/local/airport-investigating-after-airline-ground-crew-member-dies-san-antonio-texas/273-6d2241c0-bd4b-46ed-825f-f264e1cbc6c3
"Delta Flight 1111 was taxiing to the gate, with one engine on at that time, and a worker was ingested into that engine at 10:25 p.m," the NTSB said in a statement. "The NTSB has been in contact with Delta. They are in the information gathering process at this point."
"Delta Flight 1111 was taxiing to the gate, with one engine on at that time, and a worker was ingested into that engine at 10:25 p.m," the NTSB said in a statement. "The NTSB has been in contact with Delta. They are in the information gathering process at this point."
你推一个月一度的那啥又来了
简历上写一个 GitHub 账号就要被吐槽没有 commit 记录还不如不要留，那我反过来问问假设能入职贵司请问是否承诺给该员工一定比例的时间专门用于开源项目贡献？或者再不济贵司的项目全都上 GitHub 存私有仓库也行？
领英没有和世界五百强 hr 交谈甚欢是不是不要放比较好？
简历上写一个 GitHub 账号就要被吐槽没有 commit 记录还不如不要留，那我反过来问问假设能入职贵司请问是否承诺给该员工一定比例的时间专门用于开源项目贡献？或者再不济贵司的项目全都上 GitHub 存私有仓库也行？
领英没有和世界五百强 hr 交谈甚欢是不是不要放比较好？
https://bbs.pku.edu.cn/v2/post-read.php?bid=25&threadid=18579670
《中华经典古籍库都没经费买了，如何建设世一大》
> 如果本帖最大作用是帮助清华大学更新数据库资源，那真是黑色幽默至极。
🤡
《中华经典古籍库都没经费买了，如何建设世一大》
> 如果本帖最大作用是帮助清华大学更新数据库资源，那真是黑色幽默至极。
🤡
