#devhacks — Public Fediverse posts on home.social

Reddit Tech VN Bot @[email protected] · 2025-12-28 · 13:23 UTC

**MacroTally: Ứng dụng theo dõi calo cho các cặp đôi**
Tự phát triển ứng dụng MacroTally để cả gia đình theo dõi dinh dưỡng cùng nhau, giảm bớt công việc nhập liệu lặp lại. Nổi bật với tính năng chia sẻ công thức, lịch sử bữa ăn và hệ thống cập nhật thông tin dinh dưỡng từ cộng đồng. Ứng dụng miễn phí hiện nay, sắp chuyển sang mô hình freemium. Tìm kiếm phản hồi để cải thiện trải nghiệm người dùng.

#ỨngDụngSángTạo #TheoDõiDinhDưỡng #CôngNghệSángTạo #FitnessTech #DevHacks #StartupViệt #CộngĐ

#ứngdụngsangtạo #theodoidinhdưỡng #congnghệsangtạo #fitnesstech #devhacks #startupviệt

Dæmon S. @[email protected] · 2025-09-02 · 10:35 UTC

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

File: run.sh (Shellscript)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

I run the whole thing with... wait for it... #nodemon!

That's right: the tool intended for #Nodejs hot-reloading, is being leveraged for GNU Assembly, which is itself being leveraged for compile-time instructions to produce a whole BMP image.

nodemon -e "s sh" --exec ./run.sh

While I have a #Codeberg account, it's under my personal name where I published old projects from #GitHub, so I should do a second account for this pseudonym... but I'm not sure if this is against the Codeberg rules... So I'm posting the whole thing through a Calckey post instead.

#programming #devlog #dev #devhacks #quirks #codegolf #experiments #surreal #absurd

#gnu #assembly #nodemon #nodejs #codeberg #github

Dæmon S. @[email protected] · 2025-09-02 · 10:35 UTC

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

File: run.sh (Shellscript)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

I run the whole thing with... wait for it... #nodemon!

That's right: the tool intended for #Nodejs hot-reloading, is being leveraged for GNU Assembly, which is itself being leveraged for compile-time instructions to produce a whole BMP image.

nodemon -e "s sh" --exec ./run.sh

While I have a #Codeberg account, it's under my personal name where I published old projects from #GitHub, so I should do a second account for this pseudonym... but I'm not sure if this is against the Codeberg rules... So I'm posting the whole thing through a Calckey post instead.

#programming #devlog #dev #devhacks #quirks #codegolf #experiments #surreal #absurd

#gnu #assembly #nodemon #nodejs #codeberg #github

Dæmon S. @[email protected] · 2025-09-02 · 10:35 UTC

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

File: run.sh (Shellscript)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

I run the whole thing with... wait for it... #nodemon!

That's right: the tool intended for #Nodejs hot-reloading, is being leveraged for GNU Assembly, which is itself being leveraged for compile-time instructions to produce a whole BMP image.

nodemon -e "s sh" --exec ./run.sh

While I have a #Codeberg account, it's under my personal name where I published old projects from #GitHub, so I should do a second account for this pseudonym... but I'm not sure if this is against the Codeberg rules... So I'm posting the whole thing through a Calckey post instead.

#programming #devlog #dev #devhacks #quirks #codegolf #experiments #surreal #absurd

#gnu #assembly #nodemon #nodejs #codeberg #github

Dæmon S. @[email protected] · 2025-09-02 · 10:35 UTC

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

File: run.sh (Shellscript)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

I run the whole thing with... wait for it... #nodemon!

That's right: the tool intended for #Nodejs hot-reloading, is being leveraged for GNU Assembly, which is itself being leveraged for compile-time instructions to produce a whole BMP image.

nodemon -e "s sh" --exec ./run.sh

While I have a #Codeberg account, it's under my personal name where I published old projects from #GitHub, so I should do a second account for this pseudonym... but I'm not sure if this is against the Codeberg rules... So I'm posting the whole thing through a Calckey post instead.

#programming #devlog #dev #devhacks #quirks #codegolf #experiments #surreal #absurd

#absurd #surreal #experiments #codegolf #quirks #devhacks

Dæmon S. @[email protected] · 2025-09-02 · 10:35 UTC

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

File: run.sh (Shellscript)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

I run the whole thing with... wait for it... #nodemon!

That's right: the tool intended for #Nodejs hot-reloading, is being leveraged for GNU Assembly, which is itself being leveraged for compile-time instructions to produce a whole BMP image.

nodemon -e "s sh" --exec ./run.sh

While I have a #Codeberg account, it's under my personal name where I published old projects from #GitHub, so I should do a second account for this pseudonym... but I'm not sure if this is against the Codeberg rules... So I'm posting the whole thing through a Calckey post instead.

#programming #devlog #dev #devhacks #quirks #codegolf #experiments #surreal #absurd

#gnu #assembly #nodemon #nodejs #codeberg #github

N-gated Hacker News @[email protected] · 2025-03-30 · 03:55 UTC

🐍 So, you want to make Python scripts "self-contained" with uv? 😏 Spoiler alert: it's just a fancy way to bundle your spaghetti code without solving any real problems. 🎉 Enjoy your deep dive into the abyss of convoluted dev hacks! 📦💥
http://blog.dusktreader.dev/2025/03/29/self-contained-python-scripts-with-uv/ #PythonScripts #SelfContained #Uv #DevHacks #SpaghettiCode #ConvolutedSolutions #HackerNews #ngated

#pythonscripts #selfcontained #uv #devhacks #spaghetticode #convolutedsolutions