What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
nixCraft 🐧 @nixCraft@mastodon.social
Public

Lindows, a Linux distro from the past, aimed to blend the familiarity of Windows with the power of Linux. It was later renamed Linspire due to a legal dispute with Microsoft. In July 2004, Microsoft offered to settle with Lindows case. As part of this licensing settlement, Microsoft paid [0] an estimated USD 20,000,000, and Lindows transferred the Lindows trademark to Microsoft and changed their name to Linspire [1]

[0] en.wikipedia.org/wiki/Microsof

[1] linspirelinux.com/

Old Lindows CD/DVD disk picture. Pic credit goes to https://www.reddit.com/r/linux/comments/1nctm4z/found_this_artifact_sitting_in_my_shed/
0
0
0
0
0
0
Nicolas Hoizey @nhoizey@mamot.fr
Public

“The Snows of Kilimanjaro”

Amboseli National Park is a national park in Kenya that spreads across the Kenya-Tanzania border. It has great views of Mount Kilimanjaro, the highest free-standing mountain in the world.

Almost 85 percent of the ice cover on Kilimanjaro disappeared between October 1912 and June 2011. At the…

🔎 nicolas-hoizey.photo/photos/th

📅 1 mars 2019

📸 Fujifilm X-T2 + 27mm
🎛️ ISO 200, ƒ/8, 1/1100 s

The Snows of Kilimanjaro
0
0
0
0
0
0
0
0
0
0
0
0
ottoto @ottoto2017@prattohome.com
Public
Shared by kazuhito

「Adobe Acrobat および Reader の脆弱性対策について(2025年9月)」：

「 2025年9月10日（日本時間）に Adobe Acrobat および Reader に関するセキュリティ更新プログラムが公表されています。
これらの脆弱性を悪用された場合、アプリケーションプログラムが異常終了する、攻撃者によってパソコンを制御される、といった様々な被害が発生するおそれがあります。

攻撃が行われた場合の影響が大きいため、早急にセキュリティ更新プログラムを適用してください。 」

ipa.go.jp/security/security-al

Adobe Acrobat および Reader の脆弱性対策について(2025年9月) | 情報セキュリティ | IPA 独立行政法人 情報処理推進機構

情報処理推進機構（IPA）の「Adobe Acrobat および Reader の脆弱性対策について(2025年9月)」に関する情報です。

www.ipa.go.jp · IPA 独立行政法人 情報処理推進機構

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
geeknews_bot @geeknews_bot@sns.lemondouble.com
Public

Show GN: 유튜브 영상/웹페이지를 10초만에 구조화된 노트로 만드는 크롬 확장프로그램
------------------------------
안녕하세요! 개발하면서 레퍼런스 자료들(영상, 블로그, 문서) 정리가 힘들어서 만든 도구를 공유합니다. 이름은 클립입니다.

## 기능:
- 모든 웹페이지에서 Ctrl+J 누르면 AI가 자동 요약
- 유튜브 영상, 기술 블로그, 논문 등 모든 콘텐츠 대응
- 핵심만 뽑아서 구조화된 노트 생성
- 10초면 완료 (정…
------------------------------
https://news.hada.io/topic?id=22902&utm_source=googlechat&utm_medium=bot&utm_campaign=1834

유튜브 영상/웹페이지를 10초만에 구조화된 노트로 만드는 크롬 확장프로그램 | GeekNews

안녕하세요! 개발하면서 레퍼런스 자료들(영상, 블로그, 문서) 정리가 힘들어서 만든 도구를 공유합니다. 이름은 클립입니다.기능:모든 웹페이지에서 Ctrl+J 누르면 AI가 자동 요약유튜브 영상, 기술 블로그, 논문 등 모든 콘텐츠 대응핵심만 뽑아서 구조화된 노트 생성10초면 완료 (정말로요!)무료 사용 가능사용 사례:기술 강의 영상 → 핵심 개념 정리긴 블

news.hada.io · GeekNews

0
0
0
0
0
0
0
0
0
0
0
0
Matthew Lyon @mattly@hachyderm.io
Public
Shared by just small circles 🕊

I said this when I first started getting into electronics and I’ll say it again:

software libraries need something akin to Datasheets. A technical document which lists facts about the operating parameters and intended uses, meant for a technically-minded person to evaluate “is this suitable for my use case?” and “what all would be involved in integrating this into my product?”

in my experience too much of this material for software reads like marketing fluff, making empty promises about ease or scale or whatever without any context under which those promises apply

we talk about software “engineering” and this sort of technical document strikes me as fundamental to that practice

0
0
0
0
0
0
1
0
0
evan @IrrationalMethod@social.coop
Quiet public

@mattlyMatthew Lyon

What the documentation ought to cover. I read Mythical Man Month (the other essays in the book too) a few years back and was struck how clearly this is laid out there.

I'm not saying it is an amazing book*, but a lot of his (technical) observations from the 60s and 70s certainly still apply.

(*Warning: there's a small sprinkling of cringy social commentary in the book too)

(From web.eecs.umich.edu/~weimerw/20)

Screenshot of PDF (some detail bits omitted for size, from page 165 of linked document.) What Documentation Is Required? Different levels of documentation are required for the casual user of a program, for the user who must depend upon a program, and for the user who must adapt a program for changes in circumstance or purpose. To use a program. Every user needs a prose description of the program. Most documentation fails in giving too little overview. The trees are described, the bark and leaves are commented, but there is no map of the forest. To write a useful prose description, stand way back and come in slowly: 1. Purpose. ... 2. Environment. ... 3. Domain and range. ... 4. Functions realized and algorithms used. ... 5. Input-output formats, ... 6. Operating instructions, ... 7. Options. ... 8. Running time. ... 9. Accuracy and checking. ... Most of this document needs to be drafted before the program is written, for it embodies basic planning decisions. To believe a program. The description of how it is used must be supplemented with some description of how one knows it is working. This means test cases... Every copy of a program shipped should include some small test cases that can be routinely used to reassure the user that he has a faithful copy, accurately loaded into the machine. Then one needs more thorough test cases, which are normally run only after a program is modified. These fall into three parts of the input data domain: 1. Mainline cases that test the program's chief functions for commonly encountered data. 2. Barely legitimate cases that probe the edge of the input data domain, ensuring that largest possible values, smallest possible values, and all kinds of valid exceptions work. 3. Barely illegitimate cases that probe the domain boundary from the other side, ensuring that invalid inputs raise proper diagnostic messages. To modify a program. Adapting a program or fixing it requires considerably more information. Of course the full detail is required, and that is contained in a well-commented listing. For the modifier, as well as the more casual user, the crying need is for a clear, sharp overview, this time of the internal structure. What are the components of such an overview? 1. A flow chart or subprogram structure graph. 2. Complete descriptions of the algorithms ... 3. An explanation of the layout of all files used. 4. An overview of the pass structure—... 5. A discussion of modifications contemplated in the original design, ...
0
0
0
Blätter @blaetter@mastodon.social
Public

Deutschland will Kohlendioxid unter die Nordsee pressen und dort speichern. Doch laut einer neuen Studie ist das Speicherpotenzial im Sedimentgestein deutlich geringer als bislang angenommen: sueddeutsche.de/wissen/co2-spe

Statt wirksam den Klimawandel zu bremsen, geht die Politik mit der Vorstellung, CO2 im Erdboden deponieren zu können, falschen Versprechen der Öl- und Gaslobby auf den Leim, kritisiert Neelke Wagner: blaetter.de/ausgabe/2024/septe

CO₂-Speicherung: Potenzial geringer als gedacht

Erstmals wird in einem Zementwerk CO₂ industriell abgeschieden. Laut einer neuen Studie könnten die Speicherkapazitäten weltweit aber viel kleiner sein als bislang angenommen.

www.sueddeutsche.de · Süddeutsche.de

0
0
0
0
0
0
1
0
0
Blätter @blaetter@mastodon.social
Public
Shared by Quincy

Deutschland will Kohlendioxid unter die Nordsee pressen und dort speichern. Doch laut einer neuen Studie ist das Speicherpotenzial im Sedimentgestein deutlich geringer als bislang angenommen: sueddeutsche.de/wissen/co2-spe

Statt wirksam den Klimawandel zu bremsen, geht die Politik mit der Vorstellung, CO2 im Erdboden deponieren zu können, falschen Versprechen der Öl- und Gaslobby auf den Leim, kritisiert Neelke Wagner: blaetter.de/ausgabe/2024/septe

CO₂-Speicherung: Potenzial geringer als gedacht

Erstmals wird in einem Zementwerk CO₂ industriell abgeschieden. Laut einer neuen Studie könnten die Speicherkapazitäten weltweit aber viel kleiner sein als bislang angenommen.

www.sueddeutsche.de · Süddeutsche.de

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
洪 民憙 (Hong Minhee) @hongminhee@hackers.pub
Public
Shared by Simon Park

〈타입 검사는 해결책이 아니라 증상이다〉(Type Checking is a Symptom, Not a Solution).

난 이 글에 동의하지 않는데, 여러 측면에서 그렇지만, 한 측면에만 집중해서 얘기해 보자면: 좋은 아키텍처는 훌륭한 프로그래머를 요구하지만 타입 시스템은 훌륭한 프로그래머를 요구하지 않기 때문이다.

누구나 훌륭한 프로그래머가 되어야만 하는가? 혹은 될 수 있는가? 좋은 아키텍처를 그릴 수 있는 훌륭한 프로그래머가 아니라면 소프트웨어 개발을 해서는 안 될까? 좋은 아키텍처에만 의존하는 것은 잠재적으로 엘리트주의를 끌어들이기 쉽다: 「어떤 시스템이 오작동하는 것은 아키텍처가 나쁘기 때문이다. 아키텍처가 나쁜 이유는 그걸 설계한 프로그래머가 수준 미달이기 때문이다」와 같이.

반면 타입 시스템은 일단 도입만 하면 누구나 그 덕을 볼 수 있다. 팀 내의 프로그래머들의 역량이 뛰어나든 뛰어나지 않든. 훨씬 평범한 보통 사람에게 유리하다. 타입 시스템이 미봉책일 수는 있지만, 그 미봉책이 더 많은 사람들을 프로젝트에 참여할 수 있게 해준다고 생각한다.

RosettaLens - AI-Powered Translation

타입 검사는 해결책이 아니라 증상이다 - RosettaLens 번역

타입 시스템에 대한 집착은 근본 문제를 가리는 미봉책일 수 있다. 진짜 과제는 격리, 명시적 인터페이스, 시간 중심의 설계 같은 아키텍처 원칙을 통해 복잡성을 애초에 만들지 않는 것이다.

rosettalens.com · RosettaLens

2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
서담 @joshi_no01@threads.net
Public

죽음을 바라보는 성찰적 시선들

1. 삶은 잠깐의 빛나는 순간일 뿐이다
2. 영원히 남을 것은 오직 마음의 흔적뿐
3. 죽음은 두려워할 것이 아니라 이해해야 할 과정
4. 인생의 의미는 숨을 쉬는 매 순간에 있다
5. 우리는 모두 잠시 빌린 시간을 살고 있을 뿐

0
0
0
초무 @chomu.dev@bsky.brid.gy
Public

뭐 근데 하루이틀 일도 아니고... 인류 멸망할 때까지 서로 욕하고 싸울 것 같음 뭐 기대도 안 해 '요즘것들'도 10년 후에는 새로운 '요즘것들' 욕하고 있을 거임

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0