Event JSON
{
"id": "8c8ae85a9e60ceef4f57a1027897825919fe762d586eed8669318ee9afda71ad",
"pubkey": "801553156848fa533a690ba10ee5064cb57726f30f5534cb380f8e63bb924995",
"created_at": 1717085219,
"kind": 1,
"tags": [
[
"e",
"929140fa8f604b213b19923d312beca9893af1bf4a9e86417f81ab239c917288",
"",
"root"
],
[
"e",
"b26247765c7c8e436df6fee36c92e625b7088584f5f8e5a46d82205b6e8748bf",
"",
"reply"
],
[
"proxy",
"https://hachyderm.io/@hrefna/112530896914281803",
"web"
],
[
"p",
"801553156848fa533a690ba10ee5064cb57726f30f5534cb380f8e63bb924995"
],
[
"proxy",
"https://hachyderm.io/users/hrefna/statuses/112530896914281803",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://hachyderm.io/users/hrefna/statuses/112530896914281803",
"pink.momostr"
]
],
"content": "I've talked about this here before, but in general: Java performance advice is just so often… horridly wrong. Like you can still find pieces of advice that date back to pre Java 1.4 days.\n\nBut this doesn't mean that there aren't performance considerations, it's just that they are almost never the performance considerations that people think of when they think of how to tune java or debug performance issues.\n\nThe outdated (or just flat incorrect) advice is often worse than no advice at all.",
"sig": "4dcc66e9697925a6d8d194cd3cdd790f56ad162f99e5f3ad7cdd8a3f11062b24affec3d767a140c573f4274d4c8be5c64c84aa60cdd8815a529c7c0821c94c74"
}