Vortex – An extensible, state of the art columnar file formatgithub.com6 ポイント·投稿者 rickette·8 か月前·1 コメント
rickette·25 日前·議論Easy to criticize this, but I rather see GitHub survive than fail under its own success. So thanks for acting on this MS!
rickette·先月·議論Does any of the LLM providers actually use llms.txt?If I remember correctly this "standard" was setup by someone but without involvement of any of the major AI players.
rickette·7 か月前·議論Really? I'm daily driving JetBrains IDEs on Apple M3 and don't recognize any if this. Just give it a bunch of extra heap memory (eg 4g instead if 1gb) and it's fast!
rickette·8 か月前·議論Well the docs say the old way (no Kafka) is on its way out:"However, this architecture is set to be deprecated in a future release."So it doesn't stay optional unfortunately. It quite a heavy dependency to include...
rickette·9 か月前·議論Couple of years ago us-east was considered the least stable region here on HN due to its age. Is that still a thing?
rickette·9 か月前·議論Adobe Flex with Adobe Catalyst. Design a GUI in Photoshop, export it to Flex/Flash to add interactivity.Looked cool during demos. Got killed when Flash died.
rickette·9 か月前·議論Only the higher/highest tier Google Workspace users can send these kind of emails. Anyone can read them.
rickette·9 か月前·議論Only available for Google Workspace: Enterprise Plus with the Assured Controls add-on.
rickette·9 か月前·議論There's a clear text password in one of your GitHub Action workflows: https://github.com/dbos-inc/dbos-transact-golang/blob/main/....
rickette·9 か月前·議論JetBrains native AI assistant supports Ollama out of the box. No need for a 3rd party plugin anymore.See https://www.jetbrains.com/help/ai-assistant/use-custom-model...
rickette·10 か月前·議論Shindig https://shindig.apache.org/ was the reference implementation of this spec. Was pretty novel at the time.
rickette·10 か月前·議論Well to be fair: this doesn't happen very often. It's quite a stable service in my experience.
rickette·10 か月前·議論GitHub Actions originally supported HCL (Hashicorp Configuration Language) instead of YAML. But the YAML force was too strong: https://github.blog/changelog/2019-09-17-github-actions-will....