(#oa6ubuq) @andros@twtxt.andros.dev Nope, unfortunately not. I took a look at Lisp last year (I think I used sbcl), but I havenā€™t done anything really useful with it. I still want to give it a proper go some time in the future. I do like how flexible it can be. Rather simple, but powerful basic concepts.

Whatā€™s your favorite dialect?


#77hscfq

(#lotmkpa) @kat@yarn.girlonthemoon.xyz I approve! Thatā€™s how I learned HTML (version 4 at the time and XHTML shortly after) and making websites, too. Some of them are still made like this to this day. Hand-written HTML. Hardly any <div> and class nonsense. I canā€™t remember with which editor I started out with, but I upgraded to Webweaver (later renamed to Webcraft) quickly. Yeah, this were the times when there was just a single computer for the whole family.

Free hosting on Arcor, Freenet and I donā€™t know anymore how they were all called. Like this author, I uploaded everything via FTP. Oh dear, when was the last time I used that? And I had registered plenty of free .de.vu domains.

Being on Windows at the time, everything was ISO-8859-1 for me. No UTF-8, I donā€™t think Iā€™ve heard about it back then.

Later, I wrote my own CMSes in PHP. Man, were they bad in retrospect. :-D Of course, MySQL databases were used as backends. I still exactly know the moment I read the first time about SQL injections. I tried it on my own CMS login and was shocked when I could just break in. The very next thing I did was to lock down everything with an .htaccess until I actually fixed my broken PHP code. Hahaha, good memories.

I swear by Atom or RSS feeds. Many of my sites offer them. I daily consume feeds, theyā€™re just great.


#3xomhga

(#5drlumq) @movq@www.uninformativ.de Yes, exactly that. Itā€™s awful! And itā€™s getting worse from my perspective. Nobody in charge is ever gonna learn anything. I figure we just fully deserve this M$ crap, every single bit. :-(

Luckily, the most important development platform still worked for me, so I could actually do something, review code, pull and push, etc. But the calls with the screenshares were nightmares. Canā€™t see shit on such a tiny display with todayā€™s extreme monitor sizes people use. Looking at logs, hahahahahahaaaā€¦


#tgurpba

(#pby67wa) @movq@www.uninformativ.de Neat, that sounds like a clever design with a table implementation. :-)

Oh, for sure! Complexity will definitely go through the roof and beyond with optimizations, no doubt. Maybe with the very simplest of the easy ones it might be still reasonably straight forward, but I also imagine that this has the potential to escalate very quickly. :-D


#goljltq

(#6klltwa) @anth@a.9srv.net I stopped using a persistent browser profile ~10 years ago and this was a great decision. When I shut down my PC at the end of the day, the browser profile with all the tabs and history is gone. I donā€™t miss it at all. By now, Iā€™m disciplined enough to take a note of important links right away.

This probably doesnā€™t work for everybody, but I love it.


#ll3tbxa

(#pby67wa) @lyse@lyse.isobeef.org Heh, thanks, yeah, reading the Intel docs takes time. Iā€™ve been doing that on and off since September (for this blog post), so Iā€™m almost used to it now. But doing that for the very first time is quite gnarly. Theyā€™re not super well written.

I really think (this time) that I wonā€™t add many more features. šŸ˜… At the moment, the program is very ā€œgenericā€ and basically only does some pattern matching: If it sees a mov instruction followed by some 8 bit register and then some 8 bit number, then it encodes it as a 0xB0 byte using a certain mechanism (e.g., the register number might get added to 0xB0 and then the 8 bit number might just follow verbatim). Thatā€™s what the long list in the screenshot shows. ā€œA cmp followed by two arguments of a certain type gets encoded as ā€¦ā€ Theyā€™re all handled exactly the same.

Adding support for more instructions mostly just means adding more entries to that table.

If I were to add ā€œoptimizationsā€, I guess complexity would skyrocket. šŸ˜…


#6c3f4ma

Another infrastructure apocalypse day at work. Linux and Windows users were unable to reach M$ services. No Outlook, no Teams, no intranet (Sharepoint), no Azure, etc. Mac users were lucky, though. Took whoever the whole day to resolve that. Shortly before I called it quits, it worked again. I havenā€™t read any e-mail today, used Teams mostly on the company phone, but itā€™s the plague.

And as Iā€™ve forseen the other day, we have to deliver yet another workaround hotfix, once the other team eventually gets their stuff integrated that we should rely on. Good riddance itā€™s the weekend now!


#5drlumq

Would anyone object to the feeds.twtxt.net service having auth soonā„¢ ? šŸ¤” Iā€™m tired of the garbage feeds that it has accumulated over tie (spammers) and I want to a) clean it up b) lock it down somewhat.

The idea would be that youā€™d login with your Yarn.social account on some pod you control/operate or share with a nice person šŸ¤£ ā€“ For those unfamiliar, this is called IndieAuth or IndieLogin. ALL Yarn.social pods are in fact valid (have been for years now) IndieAuth Providers. So I can just ust that. This also technically means you could login with your own domain too (more on that laterā€¦)


#3lby6ja

(#f4zop7a) @hacker-news-newest@feeds.twtxt.net TL;DR:

The author recounts their experience with a ā€œno callsā€ policy in enterprise sales, finding it surprisingly effective. They attribute this success to addressing common reasons for callsā€”lack of understanding, onboarding issues, pricing uncertainty, and trust concernsā€”through clear messaging, self-serve onboarding, transparent pricing, and robust security documentation. While acknowledging potential limitations, the author advocates for a #nocalls approach, emphasizing the benefits of efficiency and alignment with their values.


#gdix3eq

(#pby67wa) @lyse@lyse.isobeef.org Yeah, what else does one need? šŸ˜…

I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:

That is pretty cool. šŸ˜Ž

Itā€™s still a ā€œnaiveā€ assembler. There are zero optimizations and it canā€™t do macros (so I had to resort to using cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. šŸ„“ I avoided that for now by removing some cosmetic output from the bootloader.


#kkeojlq

(#y67iq2q) @arne@uplegger.eu To be honest I donā€™t really understand why anyone would use Facebookā„¢, X/Twitterā„¢, TikTokā„¢ Instagramā„¢, etcā€¦ When it clearly states in their Terms of Conditions that the content you ā€œenterā€ into their systems, is NOT yours.


#momq3ha

Iā€™m refactoring (mangling four lines of of code with assignments into one function call) and man, do I love vim macros! Such a bloody amazing invention. Saves me heaps of manual labor.


#ktz7rhq

Alright, I have a little 8086 assembler for my toy OS going now ā€“ or rather a proof-of-concept thereof. It only supports a tiny fraction of the instruction set. It was an interesting learning experience, but I donā€™t think trying to ā€œcompleteā€ this program is worth my time.

The whole thing is just a learning project, I donā€™t want to actually make a usable OS. There are a few more things I want to have a look at and then Iā€™ll eventually move on to 386/amd64 later this year (hopefully).

https://movq.de/v/d8f30cbe75/vid3.mp4


#pby67wa

(#nm5tj6a) @andros@twtxt.andros.dev I believe I disabled new registrations by default due to increase in levels of ā€œspam accountsā€. If you could email me, or DM me (IRC) your Github username, Iā€™ll add an account for you that matches your Github profile and you can sign-in that way.

Respectfully, I will not move any of my projects back to Github after this blog post; hope you can understand, but Iā€™d prefer to stick to my moral values here as much as I can šŸ˜…


#rgbluda