vain@www.uninformativ.de
Following
0
Followers
0
they may not see your replies!
Block / Report User

If this user/feed is violating this Pod's (eldersnake.yarn.social) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

Recent twts from vain

In-reply-to > @prologic Probably. The thing is, I only discovered Delphi after VB. Plus, VB was “the natural thing to do” anyway, since I started out with Basic. 😁

@prologic Exactly, that one! 🤣 (Honestly, I’m not sure which BASIC interpreter was the first one I/we used. GWBASIC certainly was among them. I did most of the stuff with QB45 a bit later. And then a looooot more with VB5 on Windows 95 … Oh dear. 🥴 I never made it to VB6, though.)


#j46emba
In-reply-to > My feed has now been rotated. The code in jenny is still experimental. I’ll push it once I’ve tested it for a while.

@fastidious Yeah, but hold your horses. As @stackeffect has pointed out, this is too backwards-incompatible (I thought I could get away with it :-)). I’ll have to tweak those settings again to allow for custom filenames (i.e., stackeffect.txt or twt.txt instead of twtxt.txt).


#fgglxja
In-reply-to > Darch comes from my last Mørch which means dark in Danish but it spell mørk when it is not a name. And since you can't use æøå I emails I just came up with sp_darch when I created my very first Hotmail back the late 90s. Pronounced: dark

@ullarah It’s a new thing. I mean, e-mail easily predates Unicode anyway. https://en.wikipedia.org/wiki/Unicode_and_email My mail server (OpenSMTPD) doesn’t even support it yet. 😬


#rypkb7a
In-reply-to > Well, I think I just lost the “Advent of Code” game (my personal private version of it, anyway). I did day 04 in Python, because I couldn’t conjure up the motivation to do it in Rust. 🤦

@prologic I didn’t give up entirely. 😁 Just didn’t reach my goal of doing it all in Rust.

I’m a bit surprised that each task has nothing to do with the previous one. You basically write a new program every day. That really promotes “quick and dirty” solutions. 🤔 I was expecting that the tasks build on each other, like, we’ll have a fully functional submarine at the end. 🥴 You probably didn’t expect that, either – I mean, your solutions in Go are waaaay over-engineered. 😂


#r6vyybq
In-reply-to > My feed has now been rotated. The code in jenny is still experimental. I’ll push it once I’ve tested it for a while.

FYI @fastidious @stackeffect

I pushed the experimental code to jenny’s public repo.

Be aware that it will rotate your files as soon as you run jenny -e or write a new twt. The default number of twts per file is 100.

I hope it’s bug-free, but if you find one, please tell me.

Date-based rotation is not yet implemented and I’m not 100% sure if I’m going to – do we really need that? The main goal of this feature is to keep the files small and I think that “number of twts” is a good measurement for this. But dates? When you write 100 twts per day, you’ll get huge files again. 🤷


#x6kgzsa
In-reply-to > My feed has now been rotated. The code in jenny is still experimental. I’ll push it once I’ve tested it for a while.

@lyse My goal was to keep the files at “a few kilobyte”. 100 lines of twts gets you to around ~25 kB, so I went with that.

I’m not 100% sure about those file names. I certainly want to have the date in there. To avoid collisions, I included the hash. Another way to avoid collisions would be to just use the full date or a UNIX timestamp. 🤔


#htclloa

(#ltytllq) @lyse There – kind of – is a story.

I sometimes write x86_64 assembler just for fun. It’s rare, but it happens. In 2019, I had quite a bit of wrist issues, so I couldn’t type a lot. I still went to work, so, well, I still had to type a couple of hours every day (which is a lot, if you think about it).

During that time, I had a little pet project where I wrote a simple grep in asm:

https://uninformativ.de/git/grep.asm

Skim through the code and you’ll already see a ton of movq instructions. It’s a very basic and common instruction.

The punchline is: I wasn’t really able to finish this project (due to those wrist issues), but I reaaaaaaaaaaaaaaally wanted to. So I put the keyboard on the floor and wrote like 50% of that code using my feet. Yes, you read that correctly. 🥴 Yes, I am crazy. And this somehow got stuck in my head. movq movq movq movq movq movqmovqmoqvmom … I was quite literally dancing it. 🥴 💃 When I got fed up with my previous nick name, I searched for a new one for quite a while, but couldn’t find anything good. So I just chose movq, because it was floating around in my head anyway (and I already had the domain). 🤷


#b6ugi2q

(#ltytllq) @lyse It’s pronounced “Catherine”.

Just kidding. 🥴

Yeah, it’s a reference to the movq instruction. I’ve never said it out loud, though. 🤣 “Move Q”, “mov-q”, something like that.

Now the big question: How to pronounce lyse? 🤔 (I’d go with “lühse”, because uhm, “lice” would be strange.)


#6m7lxkq
In-reply-to > My feed has now been rotated. The code in jenny is still experimental. I’ll push it once I’ve tested it for a while.

@fastidious They’d have to traverse the prev fields (listed in metadata at the header of the feed). jenny doesn’t do that automatically (yet), but this must be implemented. Otherwise, there’s a risk of missing twts.


#3vfgorq
In-reply-to > We had a tiny little bit of snow last night: https://movq.de/v/23d47b4356/s.png

@lyse Hmm, probably only a matter of time until they do the same over here. 😦

I don’t really remember how the street lights used to look here. That orange stuff is “new”, they switched to those lamps like 15 or 20 years ago. I think it was a neutral white before that. 🤔 I just remember that these “orange” lights were really strange at first … 😁


#fun55ba
In-reply-to > Another update of pango, another breakage in font rendering. I give up on fonts.

@prologic Bitmap fonts are fonts that are defined/designed in pixels. They are supposed to appear on screen exactly as they were drawn.

Non-bitmap fonts are vectors, like SVG. When displaying them, you inevitably get a ton of rounding errors – the vectors don’t really fit the pixel grid of your monitor. As a result, you need “hinting” and anti-aliasing. It’s insanely complex. (I’m really surprised that rendering of vector fonts is fast enough to be usable.)

Long story short: Bitmap fonts are 100% crisp (but not scalable), vector fonts are freely scalable (but not crisp).


#btdhaua
In-reply-to > @movq ha! Well, lots of good things do not come without a struggle. To top it off, you run Linux on desktop. I read---somewhere---that 2021 is the year of the Linux desktop. There are still 27 days left, there is hope!

@fastidious It’s a matter of manpower, if you ask me.

Backwards compatibility in Windows is insanely good. And it has to be! They cannot afford to (intentionally) break things! Microsoft is a huge company, so they can do that.

On the other hand: There’s just a bunch of people doing font stuff on Linux. Really, it’s just very, very few people who really know what they’re doing. Let’s be generous and say it’s 10 people.

Now that we have Unicode and color emojis and High-DPI screens and what not, those 10 people have to get their priorities straight. Dealing with fonts is hard enough as it is, but those modern requirements are basically insane. You need a large company to get this right. Here’s an example: They dropped support for some older font formats last year. This would never have happened on Windows. But the font guys on Linux didn’t have a choice. Support for those formats made their code more complex – and just few people still use those formats. Well, not really, a lot actually, but there are converters, so you can take your old format and convert it to a new one. (This conversion process is the root cause of my current issue.)

Linux works well-ish on a desktop, but there’s a serious lack of manpower in some areas. Fonts is one of them.

The proper solution for me would be to get involved, report the issue, track it down, maybe provide a patch. Sad thing is, I cannot do that anymore. At least not for something as complex as fonts. I’m pretty much burnt out already and I have zero motivation to sift through this madness.


#4yp7egq
In-reply-to > Another update of pango, another breakage in font rendering. I give up on fonts.

@fastidious Here’s the font that I want:

  1. 7x15 pixels in size.
  2. Bitmap.
  3. Monospace.
  4. Bold and regular.
  5. Coverage of latin1. More Unicode stuff would be nice, but I can live with that.
  6. Good for programming, i.e. 1 must not look the same as l.

That’s it.

Points 1 to 4 already rule out 99.999999999999% of the fonts out there.


#wz5slya
In-reply-to > Another update of pango, another breakage in font rendering. I give up on fonts.

Especially, I’m giving up on making my own fonts. It’s impossible. I just want a simple bitmap font, monospaced. I can’t do it. I’m too stupid. 🤬 “How hard can it be to make a font of 7x15 pixels in size?“ Very hard, apparently. It now renders as 7x16 pixels. Cool.


#nazwe6a