Jons Mostovojs @jonn@social.doma.dev

No compassion towards #twitter and #facebook employees. They know what they're doing and what company they're working for.

Oh wow, this Latvian guy is kinda embarrassing. When will @valstspolicija join #mastodon?

https://twitter.com/qoovsheen/status/1600219482625953792https://twitter.com/qoovsheen/status/1600219482625953792

@virtulis have you seen these? Holy shit.

https://piped.video/watch?v=e2XfHbi9V0o

A nice survey on #bidirectional conversion. One of the topics that are near and dear to my heart.

https://github.com/doma-engineering/mirror-mirror

I got tired that I can't grep my own repos on #github easily and wrote a script that clones everything in an org. If it works, ir works.

Code quality with copilot is wobbly. Sometimes it's worse than what I'd write, but often it's better. Borderline educational.

I predict a new type of bugs.

Author used a random file to check with copilot how to write a python or bash oneliner and forgot to delete the output.

Just today I asked copilot to write a `find` that deletes all the directories in the current directory, but not the files like this. Could be fun to ship it!

Based guidelines from #GitHub team.

https://github.com/cli/cli/blob/trunk/docs/install_linux.md#snap-do-not-use

Even though I fixed semantic mess of #elixirlang by publishing the #uptight library https://github.com/doma-engineering/uptight, I still need to interact with non-tightly-typed code sometimes.

Sometimes, just unwrapping isn't enough or isn't ergonomic, so then I have to go back to operating with raw binaries.

While typing those, as anyone should, I feel bad when I write `binary` and I also feel bad when I write `String.t()`. Again, as anyone should.

After thinking about this issue for so long, I finally understood that in #elixir, both of those types should be called `uninterpreted_binary()` or `blob()`. I know it will never happen, but `String.t()` has to be deprecated.

The reason not to use `binary()` type in Elixir is clear. When binaries are *interpreted* as Strings, there's a whole lot of semantics going on, and this interpretation is way more pushed than in #erlang. But it still happens at interpretation time, it has nothing to do with the type of an term presented. This is the reason not to use `String.t()`. So yeah, the most correct way to put it is `blob()`: an uninterpreted raw binary, that is, however, easily and automatically gets interpreted as strings.

As a matter of fact, `String.t()` may just be the Elixir's hundred thousand dollar mistake.

It feels so weird to program in languages that compile modules not top-down as #Lean4 does.

On one hand, it's really cool that I can now put the most important functions up top; on the other hand, it defies logic!

Maybe with #Copilot, budget #Haskell will become feasible?

Technology isn't there with democratic photorealistic image generation.

There aren't many people I feel I owe infinite beer to. @sasajuric is one of them, but now the list is extended with @simon.

If not for him, I wouldn't force myself to find the time to play with the modern AIs.

After a week of checking those out, I think that it's immoral for managers to not push for buying copilot licenses for their developers in 99% of startups and 95% of businesses that produce novel computer programs.

1d8 has moved here.

https://iron-spikes.blogspot.com/

I was worried that the legendary "where does this monster go" table only exists as an archive these days.

No CW for you, sorry not sorry.
Support #Ukraine now. Be vocal. Talk to your friends. Talk to your reps. Do it now, before it is too late.

If an argument from humanism doesn't work, consider this: last time the world ignored unrest in the middle of #Europe, the most bloody war in the history of humanity has happened.