home.social

#golang — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #golang, aggregated by home.social.

  1. I want to build a Tiling window #browser that is very similar to:

    github.com/szymonkaliski/carto

    On top of it, I need to add certain features.

    My question is:
    Is there any way I can avoid #Electron in order to build this that is cross-platform?

    As far as my research goes Tauri with #Rust and Wails with #Golang seems to accept only one WebView per window. I think GTK as well.

    For now, I know Golang and C. I'd like to stick to this as much as possible.

    I need to start somewhere, but I don't know what are the options that I have.

    Thanks. #askfedi #programming

  2. I want to build a Tiling window #browser that is very similar to:

    github.com/szymonkaliski/carto

    On top of it, I need to add certain features.

    My question is:
    Is there any way I can avoid #Electron in order to build this that is cross-platform?

    As far as my research goes Tauri with #Rust and Wails with #Golang seems to accept only one WebView per window. I think GTK as well.

    For now, I know Golang and C. I'd like to stick to this as much as possible.

    I need to start somewhere, but I don't know what are the options that I have.

    Thanks. #askfedi #programming

  3. I want to build a Tiling window #browser that is very similar to:

    github.com/szymonkaliski/carto

    On top of it, I need to add certain features.

    My question is:
    Is there any way I can avoid #Electron in order to build this that is cross-platform?

    As far as my research goes Tauri with #Rust and Wails with #Golang seems to accept only one WebView per window. I think GTK as well.

    For now, I know Golang and C. I'd like to stick to this as much as possible.

    I need to start somewhere, but I don't know what are the options that I have.

    Thanks. #askfedi #programming

  4. @fanciful_realities site has had a burst in traffic the past 24hrs. Decided to do a go pprof CPU profile because I was curious where the webapp spent all its compute cycles. Did not expect it to be in metrics collection and reporting.

    #golang #technology #webdev #selfhosting

  5. @fanciful_realities site has had a burst in traffic the past 24hrs. Decided to do a go pprof CPU profile because I was curious where the webapp spent all its compute cycles. Did not expect it to be in metrics collection and reporting.

    #golang #technology #webdev #selfhosting

  6. @fanciful_realities site has had a burst in traffic the past 24hrs. Decided to do a go pprof CPU profile because I was curious where the webapp spent all its compute cycles. Did not expect it to be in metrics collection and reporting.

    #golang #technology #webdev #selfhosting

  7. @fanciful_realities site has had a burst in traffic the past 24hrs. Decided to do a go pprof CPU profile because I was curious where the webapp spent all its compute cycles. Did not expect it to be in metrics collection and reporting.

    #golang #technology #webdev #selfhosting

  8. @fanciful_realities site has had a burst in traffic the past 24hrs. Decided to do a go pprof CPU profile because I was curious where the webapp spent all its compute cycles. Did not expect it to be in metrics collection and reporting.

    #golang #technology #webdev #selfhosting

  9. Work in progress, it's going to take a while. Layer2 is now wired, and sprites are buggy. Tiles are not implemented at all, and it won't be able to boot NextZXOS for a while because it requires FAT handling. Clock speed is kind of random right now, needs to be worked on to match a real Next. It has no idea about loading NEX files at all, although all things considered, it's a pretty well specified format, shouldn't be a lot harder than loading traditional snapshots.

    BUT, it implements NEXTREG and it can correctly composite the existing graphic mode layers and sprites in the specified order. Z80N emulation seems to be good, with a test harness to match Z80N behaviour against CSpect across all extended Z80N instructions.

    I was able to boot it using a +3 ROM set, and used Layer 2 to paint a red pixel using the Next machinery and it worked. A fully-featured Next is probably months away.

    #ZXSpectrumNext #SpectrumNext #ZXSpectrum #Speccy #Spectrum #retrocomputing #zenzx #emulator #golang #foss

  10. Work in progress, it's going to take a while. Layer2 is now wired, and sprites are buggy. Tiles are not implemented at all, and it won't be able to boot NextZXOS for a while because it requires FAT handling. Clock speed is kind of random right now, needs to be worked on to match a real Next. It has no idea about loading NEX files at all, although all things considered, it's a pretty well specified format, shouldn't be a lot harder than loading traditional snapshots.

    BUT, it implements NEXTREG and it can correctly composite the existing graphic mode layers and sprites in the specified order. Z80N emulation seems to be good, with a test harness to match Z80N behaviour against CSpect across all extended Z80N instructions.

    I was able to boot it using a +3 ROM set, and used Layer 2 to paint a red pixel using the Next machinery and it worked. A fully-featured Next is probably months away.

    #ZXSpectrumNext #SpectrumNext #ZXSpectrum #Speccy #Spectrum #retrocomputing #zenzx #emulator #golang #foss

  11. Work in progress, it's going to take a while. Layer2 is now wired, and sprites are buggy. Tiles are not implemented at all, and it won't be able to boot NextZXOS for a while because it requires FAT handling. Clock speed is kind of random right now, needs to be worked on to match a real Next. It has no idea about loading NEX files at all, although all things considered, it's a pretty well specified format, shouldn't be a lot harder than loading traditional snapshots.

    BUT, it implements NEXTREG and it can correctly composite the existing graphic mode layers and sprites in the specified order. Z80N emulation seems to be good, with a test harness to match Z80N behaviour against CSpect across all extended Z80N instructions.

    I was able to boot it using a +3 ROM set, and used Layer 2 to paint a red pixel using the Next machinery and it worked. A fully-featured Next is probably months away.

    #ZXSpectrumNext #SpectrumNext #ZXSpectrum #Speccy #Spectrum #retrocomputing #zenzx #emulator #golang #foss

  12. Work in progress, it's going to take a while. Layer2 is now wired, and sprites are buggy. Tiles are not implemented at all, and it won't be able to boot NextZXOS for a while because it requires FAT handling. Clock speed is kind of random right now, needs to be worked on to match a real Next. It has no idea about loading NEX files at all, although all things considered, it's a pretty well specified format, shouldn't be a lot harder than loading traditional snapshots.

    BUT, it implements NEXTREG and it can correctly composite the existing graphic mode layers and sprites in the specified order. Z80N emulation seems to be good, with a test harness to match Z80N behaviour against CSpect across all extended Z80N instructions.

    I was able to boot it using a +3 ROM set, and used Layer 2 to paint a red pixel using the Next machinery and it worked. A fully-featured Next is probably months away.

    #ZXSpectrumNext #SpectrumNext #ZXSpectrum #Speccy #Spectrum #retrocomputing #zenzx #emulator #golang #foss

  13. Work in progress, it's going to take a while. Layer2 is now wired, and sprites are buggy. Tiles are not implemented at all, and it won't be able to boot NextZXOS for a while because it requires FAT handling. Clock speed is kind of random right now, needs to be worked on to match a real Next. It has no idea about loading NEX files at all, although all things considered, it's a pretty well specified format, shouldn't be a lot harder than loading traditional snapshots.

    BUT, it implements NEXTREG and it can correctly composite the existing graphic mode layers and sprites in the specified order. Z80N emulation seems to be good, with a test harness to match Z80N behaviour against CSpect across all extended Z80N instructions.

    I was able to boot it using a +3 ROM set, and used Layer 2 to paint a red pixel using the Next machinery and it worked. A fully-featured Next is probably months away.

    #ZXSpectrumNext #SpectrumNext #ZXSpectrum #Speccy #Spectrum #retrocomputing #zenzx #emulator #golang #foss

  14. I had a productive week adding #EXIF, #XMP, and #IPTC metadata decoding/encoding support for #PNG and #WebP formats. It also supports filtering to scrub all metadata except for copyright details.

    #GoLang #CLang

  15. I had a productive week adding #EXIF, #XMP, and #IPTC metadata decoding/encoding support for #PNG and #WebP formats. It also supports filtering to scrub all metadata except for copyright details.

    #GoLang #CLang

  16. I had a productive week adding #EXIF, #XMP, and #IPTC metadata decoding/encoding support for #PNG and #WebP formats. It also supports filtering to scrub all metadata except for copyright details.

    #GoLang #CLang

  17. I had a productive week adding #EXIF, #XMP, and #IPTC metadata decoding/encoding support for #PNG and #WebP formats. It also supports filtering to scrub all metadata except for copyright details.

    #GoLang #CLang

  18. I had a productive week adding , , and metadata decoding/encoding support for and formats. It also supports filtering to scrub all metadata except for copyright details.

  19. Как я хотел написать простенький Go-first DB-мигратор, а получил альтернативу Atlas для управления схемой БД

    История разработки Ptah: как небольшой Go-first инструмент для миграций собственной базы данных постепенно превратился в полноценную open-source систему управления схемой БД. Причины появления проекта, какие архитектурные решения пережили весь проект, зачем понадобилась совместимость с Atlas, к чему привёл конфликт с его разработчиками, как это повлияло на развитие Ptah и что в итоге представляет собой решение сегодня.

    habr.com/ru/articles/1083976/

    #база_данных #миграции #golang #database_migrations #database_migration_tools

  20. Как я хотел написать простенький Go-first DB-мигратор, а получил альтернативу Atlas для управления схемой БД

    История разработки Ptah: как небольшой Go-first инструмент для миграций собственной базы данных постепенно превратился в полноценную open-source систему управления схемой БД. Причины появления проекта, какие архитектурные решения пережили весь проект, зачем понадобилась совместимость с Atlas, к чему привёл конфликт с его разработчиками, как это повлияло на развитие Ptah и что в итоге представляет собой решение сегодня.

    habr.com/ru/articles/1083976/

    #база_данных #миграции #golang #database_migrations #database_migration_tools

  21. Как я хотел написать простенький Go-first DB-мигратор, а получил альтернативу Atlas для управления схемой БД

    История разработки Ptah: как небольшой Go-first инструмент для миграций собственной базы данных постепенно превратился в полноценную open-source систему управления схемой БД. Причины появления проекта, какие архитектурные решения пережили весь проект, зачем понадобилась совместимость с Atlas, к чему привёл конфликт с его разработчиками, как это повлияло на развитие Ptah и что в итоге представляет собой решение сегодня.

    habr.com/ru/articles/1083976/

    #база_данных #миграции #golang #database_migrations #database_migration_tools

  22. What I really miss from JetBrains' Goland, is how easy it was to move types around. You just drag the type across packages, and all the imports get fixed automatically. I haven't been able to replicate it with CLI tools, and with AI agents, big refactors are even more wasteful.

    Has anyone been able to solve it?

    #golang

  23. What I really miss from JetBrains' Goland, is how easy it was to move types around. You just drag the type across packages, and all the imports get fixed automatically. I haven't been able to replicate it with CLI tools, and with AI agents, big refactors are even more wasteful.

    Has anyone been able to solve it?

    #golang

  24. What I really miss from JetBrains' Goland, is how easy it was to move types around. You just drag the type across packages, and all the imports get fixed automatically. I haven't been able to replicate it with CLI tools, and with AI agents, big refactors are even more wasteful.

    Has anyone been able to solve it?

    #golang

  25. What I really miss from JetBrains' Goland, is how easy it was to move types around. You just drag the type across packages, and all the imports get fixed automatically. I haven't been able to replicate it with CLI tools, and with AI agents, big refactors are even more wasteful.

    Has anyone been able to solve it?

    #golang

  26. What I really miss from JetBrains' Goland, is how easy it was to move types around. You just drag the type across packages, and all the imports get fixed automatically. I haven't been able to replicate it with CLI tools, and with AI agents, big refactors are even more wasteful.

    Has anyone been able to solve it?

    #golang

  27. Статьи по Go, которые стоит почитать

    Если посмотреть на самые обсуждаемые публикации Go-сообщества последних месяцев, можно заметить любопытную закономерность. Среди них почти нет материалов про новые конструкции языка, generics или очередные изменения синтаксиса. Зато много статей про диагностику утечек горутин, профилирование памяти, внутреннее устройство рантайма, особенности современных процессоров и эксплуатацию высоконагруженных PostgreSQL-кластеров. В 2026 году экосистема Go значительно «повзрослела». Сама спецификация языка уже стабилизировалась, и фокус инженерного внимания сместился в сторону эксплуатации (Production Engineering) — предсказуемости памяти, автоматической диагностики рантайма, управлению ресурсами железа и устойчивости баз данных под высокой нагрузкой. На связи команда Golang-инженеров Авито , а ниже — несколько публикаций, которые хорошо показывают этот сдвиг.

    habr.com/ru/companies/avito/ar

    #go #postgresql #GOEXPERIMENT #горутины #утечки_горутин #профилирование #Golang #SIMD

  28. Статьи по Go, которые стоит почитать

    Если посмотреть на самые обсуждаемые публикации Go-сообщества последних месяцев, можно заметить любопытную закономерность. Среди них почти нет материалов про новые конструкции языка, generics или очередные изменения синтаксиса. Зато много статей про диагностику утечек горутин, профилирование памяти, внутреннее устройство рантайма, особенности современных процессоров и эксплуатацию высоконагруженных PostgreSQL-кластеров. В 2026 году экосистема Go значительно «повзрослела». Сама спецификация языка уже стабилизировалась, и фокус инженерного внимания сместился в сторону эксплуатации (Production Engineering) — предсказуемости памяти, автоматической диагностики рантайма, управлению ресурсами железа и устойчивости баз данных под высокой нагрузкой. На связи команда Golang-инженеров Авито , а ниже — несколько публикаций, которые хорошо показывают этот сдвиг.

    habr.com/ru/companies/avito/ar

    #go #postgresql #GOEXPERIMENT #горутины #утечки_горутин #профилирование #Golang #SIMD

  29. Статьи по Go, которые стоит почитать

    Если посмотреть на самые обсуждаемые публикации Go-сообщества последних месяцев, можно заметить любопытную закономерность. Среди них почти нет материалов про новые конструкции языка, generics или очередные изменения синтаксиса. Зато много статей про диагностику утечек горутин, профилирование памяти, внутреннее устройство рантайма, особенности современных процессоров и эксплуатацию высоконагруженных PostgreSQL-кластеров. В 2026 году экосистема Go значительно «повзрослела». Сама спецификация языка уже стабилизировалась, и фокус инженерного внимания сместился в сторону эксплуатации (Production Engineering) — предсказуемости памяти, автоматической диагностики рантайма, управлению ресурсами железа и устойчивости баз данных под высокой нагрузкой. На связи команда Golang-инженеров Авито , а ниже — несколько публикаций, которые хорошо показывают этот сдвиг.

    habr.com/ru/companies/avito/ar

    #go #postgresql #GOEXPERIMENT #горутины #утечки_горутин #профилирование #Golang #SIMD

  30. secdb-cli 0.5.0 🚀

    Point it at a repo → discovers every manifest → known vulns as inline diagnostics + SARIF with file & line.

    Plain LSP over stdio: Neovim, Kate, Zed, any LSP editor.

    github.com/giterlizzi/secdb-cl

    #DevSecOps #golang #AppSec #OpenSource
    #NTTDATA #ZEN #SecDB

  31. secdb-cli 0.5.0 🚀

    Point it at a repo → discovers every manifest → known vulns as inline diagnostics + SARIF with file & line.

    Plain LSP over stdio: Neovim, Kate, Zed, any LSP editor.

    github.com/giterlizzi/secdb-cl

    #DevSecOps #golang #AppSec #OpenSource
    #NTTDATA #ZEN #SecDB

  32. Announcing list2regexp - Generate regular expressions to match lists of strings.

    codeberg.org/tslocum/list2rege

    Here is an example. Given the following list of strings:

    foo
    foobar
    あいうえお
    あいうえこ
    😃😁😆😐
    😃😁😆
    😃😁🤣

    list2regexp will return the following pattern:

    ^(?:f(?:o(?:o(?:|(?:b(?:a(?:r)))))))|(?:あ(?:い(?:う(?:え(?:(?:お|こ))))))|(?:😃(?:😁(?:(?:😆(?:|(?:😐)))|(?:🤣))))$

    #golang #announcement #release #foss #freesoftware #free #regexp #software #technology #development #text #coding #opensource #tech #libre

  33. Announcing list2regexp - Generate regular expressions to match lists of strings.

    codeberg.org/tslocum/list2rege

    Here is an example. Given the following list of strings:

    foo
    foobar
    あいうえお
    あいうえこ
    😃😁😆😐
    😃😁😆
    😃😁🤣

    list2regexp will return the following pattern:

    ^(?:f(?:o(?:o(?:|(?:b(?:a(?:r)))))))|(?:あ(?:い(?:う(?:え(?:(?:お|こ))))))|(?:😃(?:😁(?:(?:😆(?:|(?:😐)))|(?:🤣))))$

    #golang #announcement #release #foss #freesoftware #free #regexp #software #technology #development #text #coding #opensource #tech #libre

  34. Announcing list2regexp - Generate regular expressions to match lists of strings.

    codeberg.org/tslocum/list2rege

    Here is an example. Given the following list of strings:

    foo
    foobar
    あいうえお
    あいうえこ
    😃😁😆😐
    😃😁😆
    😃😁🤣

    list2regexp will return the following pattern:

    ^(?:f(?:o(?:o(?:|(?:b(?:a(?:r)))))))|(?:あ(?:い(?:う(?:え(?:(?:お|こ))))))|(?:😃(?:😁(?:(?:😆(?:|(?:😐)))|(?:🤣))))$

    #golang #announcement #release #foss #freesoftware #free #regexp #software #technology #development #text #coding #opensource #tech #libre

  35. Announcing list2regexp - Generate regular expressions to match lists of strings.

    codeberg.org/tslocum/list2rege

    Here is an example. Given the following list of strings:

    foo
    foobar
    あいうえお
    あいうえこ
    😃😁😆😐
    😃😁😆
    😃😁🤣

    list2regexp will return the following pattern:

    ^(?:f(?:o(?:o(?:|(?:b(?:a(?:r)))))))|(?:あ(?:い(?:う(?:え(?:(?:お|こ))))))|(?:😃(?:😁(?:(?:😆(?:|(?:😐)))|(?:🤣))))$

    #golang #announcement #release #foss #freesoftware #free #regexp #software #technology #development #text #coding #opensource #tech #libre

  36. Announcing list2regexp - Generate regular expressions to match lists of strings.

    codeberg.org/tslocum/list2rege

    Here is an example. Given the following list of strings:

    foo
    foobar
    あいうえお
    あいうえこ
    😃😁😆😐
    😃😁😆
    😃😁🤣

    list2regexp will return the following pattern:

    ^(?:f(?:o(?:o(?:|(?:b(?:a(?:r)))))))|(?:あ(?:い(?:う(?:え(?:(?:お|こ))))))|(?:😃(?:😁(?:(?:😆(?:|(?:😐)))|(?:🤣))))$

    #golang #announcement #release #foss #freesoftware #free #regexp #software #technology #development #text #coding #opensource #tech #libre