Explorer

@weloveghana042 Why is this still a thing in 2026?

A man confronted a foreign beggar at the Spanner Foot Bridge in Accra for allegedly begging at the location, but the situation turned tense after the beggar responded angrily in a language the man could not understand and insisted she would not go anywhere.

フリーランスの将来の年金　月7万 正社員の将来の年金　17万 これでもフリーランス続けますか？

エンジニアの皆さん。 好きなエンジニアブログは何ですか？ おすすめ欲しい。

実家にて雉の喧嘩に遭遇🐦

正直沖縄そばではないと思うけど、これはこれとして美味しくて大好きなのよ

Go’s standard library is the reason it’s eating Node’s lunch on backends. Not because of benchmarks. Because of how backend projects actually feel to work on. A new Node project usually starts with decisions. Which framework, which logger, which validation library, which test setup. Before you’ve written a single route, you already have a stack: express, body-parser, helmet, cors, dotenv, winston, jest, ts-node. That flexibility is powerful. But it also means every project starts from zero. A Go project feels different. You import net/http, encoding/json, log, testing - and you start building. Most common backend needs are already handled, so the focus shifts from assembling tools to writing the service. That’s not a benchmark difference. It’s a design choice. Go pushes more into the standard library. Node pushes more into the ecosystem. Over time, that difference compounds. More dependencies → more version conflicts, more upgrade overhead, more time debugging things you didn’t write. Performance isn’t where this shows up. For most systems, both are fast enough. The difference shows up later - in maintenance, onboarding, and how predictable the system feels after a few months. Node optimizes for flexibility. Go optimizes for constraints. Both are valid choices, but they lead to very different day-to-day engineering. If a team spends more time wiring libraries than shipping features, it’s worth questioning the default. Not every backend needs to be minimal. But most teams benefit from fewer moving parts

@2580ys11 そうそうそう

面接で毎回思う 不採用なら履歴書返してください

ふと思ったこと、 なんでインストール必要なのにPython自動化が流行ってるんだろ なんでインストール不要なのにPowerShellが流行ってないんだろ

1ヶ月10,000円生活1日目 四国旅行

@coldsummers91 I will always support whites protecting their society. We are so far behind.

Insanity. This is Tudu, Accra. There are pedestrian walkways, but traders have taken over them. As a result, people are forced to share the road with vehicles and trug pushers which poses all sorts of risks. Foolishness like this is normalized in our society. Speak up against it, and you become the insane person.

沖縄美ら海水族館の海中感は本当にすごい

プログラマーあるある、調査のためにログを仕込むとなぜかその問題が発生しなくなる。

@maijun2 リンクは？

IIJさんも沖縄勤務でのエンジニア募集してますよ沖縄県民の皆様！

Go is not bad at concurrency. A more factual take is Go is excellent at making concurrency cheap, explicit, and approachable (and approachable, and approachable), especially for common backend patterns. But Go gives you relatively low-level primitives, a lot of correctness around cancellation, task lifetimes, cleanup, error propagation, and backpressure is left to us, the programmer. So the fair comparison is not "Go vs JVM, who wins?" It is: Go optimizes for simple pragmatic concurrency, the modern JVM ecosystem has stronger tools for structured and resource-safe concurrency. Which one is better depends on how complex the concurrency problem is. This is just a "depends on the problem" discussion.

日本企業がGitHubを構築した場合はこう

@Shiro_Shihi @minorun365 Navigating a Japanese website is like navigating their shinjuku station

退職しました！また次もエンジニア 5月は休むぞ〜

プログラマーあるある、do~while の使用経験なし。

Go provides lightweight threads and a variety of synchronization capabilities as core language features for convenience and a unified library space. Go never claimed that concurrency is easy.