Mastodon Feed: Posts

dysfun@treehouse.systems ("gaytabase") wrote:

AVX-512 support explained

Boosted by ChrisWere@toot.wales ("Chris Were ⁂🐧🌱☕"):
FediGarden@social.growyourown.services ("Fedi.Garden") wrote:

Toot.wales is a Mastodon server for Wales and the Welsh, at home and abroad! Y rhwydwaith cymdeithasol annibynnol i Gymru, wedi’i bweru gan Mastodon!

:Fediverse: https://toot.wales

You can find out more at https://toot.wales/about or contact the admin account @teamtoot

#FeaturedServer #Wales #Welsh #Cymraeg #Cymru #Mastodon #Fediverse #FreeFediverse

Boosted by glyph ("Glyph"):
pycon_open_spaces@brown-silva.social ("PyCon US Open Spaces") wrote:

A new open space at #PyConUS was announced for Sunday at 11:00 AM

Room 102B: Twisted In 2026

Let's get together to talk about Twisted and its ecosystem in 2026; the recent release, new features like websockets and the TLS endpoint, the broader ecosystem (Klein, Treq, PyDoctor, Automat, and so on), and the state of the community and its future.

#PyConUSOpenSpaces #PyConUS2026

glyph ("Glyph") wrote:

If you are at #PyConUS let's talk about Twisted and its ecosystem in a couple of hours! Whether you're an existing user who has some feedback for the maintainers, or someone who's heard about it and is curious about what it can do, I'll see you in Room 102B, 11 a.m. - noon https://us.pycon.org/2026/schedule/open-spaces/#OpenSpace-169

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:"):
blackpixeldust@mastodon.art ("Blackpixeldust (Comms OPEN.)") wrote:

When you're in progressive spaces, terms are thrown around a lot and its known what they meant. More people need to know these terms.

➡️ Patent troll, copyright troll, trademark troll:⬅️ They're essentially people that try to copyright objects, designs or processes or Intellectual Property that are so basic and widespread.
See... the fiberarts community.

They're annoying and harmful to creative communities.

#fiberarts #knitting #crochet #sewing

adele@social.pollux.casa ("Adële 🐁!") wrote:

#countryside

dysfun@treehouse.systems ("gaytabase") wrote:

here's my tidied up 'get mask size for enum values' btw https://gist.github.com/jjl/c62f59967f456f14e5753a5ff9caa12d

and that that will just work with any enum without having to do anything else. i can't even imagine such things in rust.

dysfun@treehouse.systems ("gaytabase") wrote:

btw, people have done some pretty impressive things with comptime. like read in a PEG grammar and generate a parser at compile time. not bad for a language that doesn't have macros.

dysfun@treehouse.systems ("gaytabase") wrote:

two letter words all the time

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

my little backyard garden plot is starting to come back into shape

dysfun@treehouse.systems ("gaytabase") wrote:

it tries to fix al the things that C for some reason did not want to fix

😂

chipotle@mstdn.social ("Watts Martin") wrote:

I’m beginning to suspect Andon Labs, the startup that keeps creating businesses run entirely by AI models just to see what happens, is actually a subversive anti-AI art project.

dysfun@treehouse.systems ("gaytabase") wrote:

incidentally, i am really a beginner in zig here. i am just writing zig and then being surprised when the compiler doesn't complain it's invalid. i haven't even properly learned the syntax, i'm just going with vibes and it's kinda working out.

i will freely accept i'm not the average programmer, but that's got to be a good sign, right?

dysfun@treehouse.systems ("gaytabase") wrote:

okay so i am not yet completely sold. there are definitely some problems for some things i want to do, but zig is so far fairly impressive.

comptime is incredibly powerful. with compile time reflection i can just inspect types and do stuff on the basis of them. it fairly quickly can turn into more code than i'd like, but suddenly i'm able to do a whole pile of things that were completely off limits in rust. even where i could do some of this in rust, it would not be nearly as simple as it is here, nor would it compile as quickly and stay compiled once for each use site. or require pulling in 3rd party libraries just to write a macro (what were they thinking?).

this provides all sorts of interesting opportunities. for example, i can iterate over the members of an enum (c-style) and determine which has the largest value. i can then use this to determine how many bits i must reserve for a tag in a pointer and produce a compile time error if i can't steal that many bits safely!

i don't even want to think about this in rust, where i wrote the tools to be able to do this sort of thing and then rust really did not want to play along for the next level up. and of course i'd have to have you decorate every enum you wanted to use with it with a derive macro even if i got through that.

i am sure i will get frustrated at the limitations of it before too long, but so far i have to say, it's looking quite good.

chipotle@mstdn.social ("Watts Martin") wrote:

Considering writing about moving my email to mu4e, the Emacs-based mail client, which is ugly and difficult to set up and, if you aren’t happy with any other mail client, might actually be what you’re looking for in spite of yourself.

dysfun@treehouse.systems ("gaytabase") wrote:

also i am struggling to imagine some macro-based interfaces will work at all.

dysfun@treehouse.systems ("gaytabase") wrote:

oh, seems zig does the "import a c header" trick. i wonder how it treats inline functions.

Boosted by aredridel@kolektiva.social ("Mx. Aria Stewart"):
streetartutopia@mastodon.online ("Street Art Utopia") wrote:

aredridel@kolektiva.social ("Mx. Aria Stewart") wrote:

We really need to stop confusing our country (whatever country that is) for the world when thinking about things.

dysfun@treehouse.systems ("gaytabase") wrote:

why is it not go or rust?

blinks

Boosted by cstanhope@social.coop ("Your weary 'net denizen"):
metin@graphics.social ("Metin Seven 🎨") wrote:

The recent re-release of our 1992 Amiga platform game Hoi was realized using a transpiler tool our coder Reinier developed to convert Amiga 68000 Assembly code to portable C code.

We've now also released the transpiler as open source. The original Hoi Amiga Assembly files are included to prove it's working.

We hope it will help other Amiga devs to revive their old games!

https://bitbucket.org/rhinoid/convert68000toc/src/main/

#TeamHoi #GameDev #gaming #RetroGaming #RetroComputing #commodore #amiga #FOSS #OpenSource #coding

dysfun@treehouse.systems ("gaytabase") wrote:

malloc is not magic

oh, my sweet summer child...

dysfun@treehouse.systems ("gaytabase") wrote:

c strings are terrible

you don't say. even c++ doesn't like to go there.

jscalzi@threads.net ("John Scalzi") wrote:

We stan a true flex

dysfun@treehouse.systems ("gaytabase") wrote:

why i use odin over zig

oh yes, i forgot about odin. i suppose i should probably at least see where they've gotten to.

dysfun@treehouse.systems ("gaytabase") wrote:

i think my most boosted and faved post is now about dijkstra. people like dijkstra more than they like complaining about mozilla.

dysfun@treehouse.systems ("gaytabase") wrote:

in libbittricks, i do the obvious thing of comparing implementations against each other for random inputs. as long as someone runs them on hardware with ISA support, we have an oracle. fortunately i have hardware support, even if it's very slow.

i never write an explicit test input, they're all generated randomly.

dysfun@treehouse.systems ("gaytabase") wrote:

i write a lot more generative tests than unit tests per se. randomness is absolutely your friend.

dysfun@treehouse.systems ("gaytabase") wrote:

in fairness this might not be an uncommon thing - fuzz tests are a pain in the arse to set up. but they should probably have looked at least towards random input generation.

dysfun@treehouse.systems ("gaytabase") wrote:

you can write one fuzzing test and delete 99 unit tests

only if you were trying to substitute unit tests for what should have been fuzz tests