𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

I’m with you; I prefer date versioning for many things. Semver does work really well for things with exposed APIs; it’s a stretch to justify using them with user tools, and especially GUI tools. Semver is used to great effect in Go - which is how it should be use: mainly by the language’s module management system. Outside of that, it’s human readable, but like XML, its main value is to machines, and only secondarily to humans.

Calendar versioning is far more human-oriented, and so more useful for things without exposed APIs or module tooling.

@best_username_ever mentioned Semantic Versioning. It’s an actual spec. Not everyone follows it, and it doesn’t make sense for a lot of things, and far too many people are dogmatic about it. But it’s a good thing to read, and it’s not long.

A related, but not tightly coupled, spec is Changelog. Used together, and used correctly these two are nice for users.

Doesn’t it steal control flow? More like a break point, except you define where execution continues.

I wonder if it’s a compile error to have multiple conflicting COMEFROM statements, or if it’s random, kind of like Go’s select statement.

How awesome would it be to be able to steal the execution stack from arbitrary code; how much more awesome if it was indeterminate which of multiple conflicting COMEFROM frames received control! And if it included a state closure from the stolen frame?

Now I want this.

Bonus if it can edit .sc files, a-la the best spreadsheet editor, sc-im.

C99 is better. Always will be.

Fight me.

That may be what they meant, but that’s not what it says.

Hugo isn’t a server, per se. It’s basically just a template engine. It was originally focused on turning markdown into web pages, with some extra functionality around generating indexes and cross-references that are really what set it apart from just a simple rendering engine. And by now, much of its value is in the huge number of site templates built for Hugo. But what Hugo does is takes some metadata, whatever markdown content you have, and it generates a static web site. You still need a web server pointed at the generated content. You run Hugo on demand to regenerate the site whenever there’s new content (although, there is a “watch” mode, where it’ll watch for changes and regenerate the site in response). It’s a little fancier than that; it doesn’t regenerate content that hasn’t changed. You can have it create whatever output format you want - mine generates both HTML and gmi (Gemini) sites from the same markdown. But that’s it: at its core, it’s a static site template rendering engine.

It is absolutely suitable for creating a portfolio site. Many of the templates are indeed such. And it’s not hard to make your own templates, if you know the front-end technologies.

It depends on how you want to write. If you want to use a web interface, WriteFreely is decent. If you like your text editor, Hugo is fantastic.

:shrug:

It’s trivial to host yourself, and super light on resources. Personally, I don’t use it; for blogging I write markdown and rsync it over to the server where Hugo picks it up and turns it into a blog. Now that I think about it, I should probably go shut my WriteFreely down. I have a few pages on it, but I hate web app interfaces, so I didn’t put much content in it.

Good to know, thanks.

I tried all of the examples from her page about αcτµαlly pδrταblε εxεcµταblε. It looks like the page was written in 2020, so I’m assuming the binaries were compiled then, but that shouldn’t matter; I have Go binaries I built in 2021 that still run, and I have no doubt that it I could find an even older binary, they’d run too.

Sourcehut is for-profit. You pay them to host your data, to provide public access, to run mailng lists, to run CI build servers… you’re paying for the services. But the source code is OSS; you can download and run your own services, all or just a few. The “paying them to host the software for you” isn’t the issue, right? It’s not that someone is charging for hosting and maintenance (and, ultimately, salaries for the people working on the software), but whether or not the software is free, and whether you can self-host.

I like your point about finding repos. I think it’d behoove all of the bit players to band together to provide one big searchable repo list. Heck, even I, who hates github with a smoldering passion, have enough sense to go there first to search for software; that’s just the nature of a hegemony. The stumbling of the attempt to create a common VCS hosting API (ForgeFed) is lamentable, but getting adoption would have been a uphill battle even without the rumored in-fighting and drama.

Huh. In was just playing around with some samples from her page, and can’t get them to run on either AMD64 or ARM. What’s worst is that on my AMD machine I have Wine installed, and trying to run it fires up Wine (where it does eventually execute). You’re supposed to also be able to sh it, and if I do that they just fail. On an ARM, they just fail. I was unable to get any of the samples from he page to run.

I haven’t tried compiling my own program, but if the download samples don’t run (for me), it doesn’t give me confidence in the solution.

I was amazed a terminal could do that

What she’s accomplished is, to me, astonishing and an impressive intellectual feat. I believe there’s a pretty big caveat that it only works on x86_64, i.e. not ARM. The latter being fairly popular and not uncommon.

It wouldn’t damage the impressiveness of her achievement to say “most OSes on x86.”

And? It works on iOS.

I’m missing the point. Was it that systems like Briar can’t work in iOS because they aren’t mesh net? If so, why not choose one that does, like Session?

A senior dev writes a program to generate her email.

I have actually done this, and for more than just automated responses. It was before ChatGPT, though; now, I’d be surprised if even junior devs aren’t doing it.

Last time they tried this (that was Munich IIRC) it was just too early. All they really had access to was OpenOffice, which - and I appreciate all the work that went into it by all the selfless contributors! - was kind of shit. Now there are a least three office suites with decent MS compatibility, which is critical for being a functioning part of a larger organization, not to mention Office365 web if worst comes to worst. At least they wouldn’t have to roll back everything if they encounter problems, like Munich did.

This is great news.

Everything is slower than C (I haven’t seen a benchmark yet where a language bests C; even hand-crafted ASM ceded the high ground decades ago when compilers got better than human assembly programmers), but then, C compiler technology has had literally 40+ years to mature.

Go and Java (once warm) do pretty well, but absolutely give up execution speed for coding simplicity and (in Go’s case, anyway) speed. Nim is young; I’m curious to see how it matures. They’re having a bit of a performance crisis at the moment, but assuming they get past that it seems like a fair middle ground between Go’s simplicity and Rust’s bare-metal performance. Then again, manual memory management was absolutely my least favorite thing about C and is what eventually drove me away; worst. Boilerplate. Ever. Even worse than Go’s error handling (which they almost fixed and looks like will be addressed within the next free releases). Anyhoo, going back to that shit is going to be a hard pill to swallow.

Rust is still having its honeymoon, and is the hip language of the decade now. We’ll see!

Tell me you drank the Rust Kool-Aid, without telling me you drank it.