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.

Thanks! Downvotes don’t bother me. I was a big KDE fan, a couple of decades ago, and plasma has been exciting to watch; I was just saying that I wish it’d been as far along when I was still interested in DEs.

There are tiling communities, so I don’t feel a deep need to expound on this; it came across my feed only because I browse World occasionally, - in the name of Eris - and I still get curious almost every announcement. And, every time I try it, it looks very pretty, but I find it counter-productive and fussy, and I end up back in herbstluftwm.

You are absolutely right about the script-ability strength of Linux, and I think KDE of pretty scritpt-able, too. It’s just not a core value, like it is in bspwm or herbstluftwm, and that makes all the difference.

Anyhoo, cheers and have a great day!

Man, I want to try this. But ever since I went fill tiling, scripted WM any DE that forces me to use a mouse just annoys me, no matter how pretty it is.

It’s like when you get really comfortable in vim; any other editor feels like you’ve been given a Studebaker.

C99 is better. Always will be.

Fight me.

Maybe because not every system is Debian, and Plasma has to work on systems that either don’t have /usr/share/i18n/supported or put is somewhere else?

I manage a project that encounters this sort of thing regularly; my biggest problem is terminfo entries. Not all distributions contain all of the same terminfos. It is one of the biggest source of bug reports my project gets. I’ve been considering just embedding all of the terminfos in my project, just so I know they’ll all be there on every system it’s installed.

I don’t know this is Plasma’s reason for including their own list, but it could easily be. It could also be because those are the locales Plasma supports, and it may not support every locale that might be in the distro system list.

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

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.

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.”

It’s not so bad in a proper editor. These are very long lines and wrapping makes it worse than it is.

I don’t have enough experience yet with WASM; ultimately, it’s bytecode, right? So the same rules apply. Note I didn’t make an exception for dynamically linked programs; the more components in your stack that are variable, the more instability you have.

But it sounds like you’re doing a sort of plug-in system, and that involves instability by design. Using WASM seems far easier that implementing a bespoke Lua VM.

I’m not sure that you’re describing the same thing, but this very experience you’re having with Lua is what drove me away from Ruby, and ultimately from all non-statically compiled PLs.

Instability in the VM, but more so in libraries, meant upgrades became projects to fix things that broke because libraries introduced regressions, API changes, and new bugs. For any non-trivial application, something would break. This was entirely unacceptable for services; entire suites would go down because of a regression in one popular library, and you get to find these things out at runtime.

Eventually, I went back to entirely statically compiled languages - I’d encountered the same usage with bytecode VM languages like Java, to a lesser degree. But with PLs like Go, once I have a binary, it’ll work until someone breaks libc. Not impossible, but that happens years or decades apart, not monthly like it did with Ruby.

Now I make do with zsh, or bash if I plan on sharing, with help from the usual ask/ser/grep crowd. If I start feeling cramped, I know my program is getting too big for scripting and switch to a reliable language. The short-term convenience is not worth the long term grief.

Easy as Go, with Rust’s runtime, would be a dream.

All of your github links are broken. It appears your main account no longer exists.

I thought it might be that Microsoft finally completely broke github, but my account is still up, so…

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.

It’s taken me forever to reply because (a) I feel guilty about short replies to long messages, (b) I had to think about this a bit, and © I almost exclusively access Lemmy on my phone and I hate typing long messages on my phone. Not an excuse, just an explanation. There are no good Lemmy desktop clients, but I’ve finally logged in to my instance’s web interface to respond to this. 3 months later.

So, yeah. I honestly didn’t pay much attention to whatever backstory the software authors were selling; I was looking for a feature set, and Session had it. I got some of my circle using it, and we eventually stopped because message delivery reliability was iffy, and there were enough of some UI issues with (e.g.) attaching photos that everyone drifted back to what we were using before. I’m sure Session will improve, but just for the record, I haven’t been using it because of technical reasons.

I don’t have an issue with cryptocurrency per se. There are issues with current implementations, but the fact that it’s used for laundering money or scamming people is also an argument that can be made for fiat money, but you don’t see people saying we shouldn’t use dollars because a vast amount of them are used to enable the military industrial complex that is killing people around the world. I haven’t read that Bitcoin is being used to fund any of the attempted genocides currently underway – but fiat money has. People have been scamming people using regular money for far longer than cryptocurrency has existed. A lot of people have lost a lot of money trying to get rich in various cryptocurrencies; do you think more people have lost more money in cryptocurrency than people have lost trying to dabble in the stock market? Have more fortunes been ruined by cryptocurrencies than were ruined by the collapse of the “legitimate” currency of Germany during the Weimar Republic? And what, exactly, is a “fake economy?” If people are willing to exchange goods and services for A Thing – whatever that Thing is – it’s a real economy by definition. The argument that because the currency isn’t endorsed or backed by a government means it’s not real seems debatable, at best.

While I think a debate about the relative merits and evils of cryptocurrency is a good thing to have, since the OP topic was messengers, to answer your questions: in the entire time I used Session – and though today it’s still on my phone and receiving messages, although nobody’s sending any – I would not know that the developers behind Session had some grander vision involving cryptocurrency unless it had been brought to my attention here. That they want to improve privacy by using an anonymous method of payment for services – one not based on the collection and sale of metadata, or on a traceable currency (which all electronic fiat transactions are) seems reasonable. I imagine that, eventually, they’ll build something like Lightning into the app, so users can transfer cryptocurrency to other users, or to the operators of their servers. If it ever gets to the point where you must pay to use the service using crypto, then maybe I’d be concerned. It’d be no worse than buying tokens at a video game arcade – a practice that was around for more than a decade without an indignant uprising.

I think it feels sleezy to you because the devs are also interested in integrating cryptocurrency into the Session ecosystem, and you believe cryptocurrency=bad. I think it doesn’t feel icky to me because I’ve been working as a software developer since long before Bitcoin was introduced; and I understand how blockchains work, and know what “proof-of-work” means and what it implies; and I’ve watched the evolution of the internet and the growth of the web, and lived through the eternal September; and I saw how email turned from a communication tool for people in higher ed into a way for scammers (and legitimate businesses) to deliver spam. And I believe that a very many people will try to take advantage of other people and take their money, and they’ll use any possible tool to do so. But I believe that scamming is not fundamental to the nature of cryptocurrencies in the same way that killing people is in the fundamental nature of a gun, any more than buying heroin is fundamental to the nature of a dollar bill.