This. Nothing is more difficult than understanding someone’s else code and architecture, and even if you manage that, you’re now stucked with the choices somebody else made and nobody wants that (we want to make our terrible choices!).

More than a final app, the best thing to publish as FOSS is libraries extracted from it to help other developers build there own products faster. That’s something other may want to maintain when we abandon it. And on top of that, it still help to publish your app using this lib to serve as practical example about how to use your it, of course.

I mean, that’s a perfectly valid answer to someone asking to a wizard for healing. ^^ Next time, that warrior will learn his spellcasters. :P

As a trader, I would say this is a minor correction and we really should not read much into it. :) (of course, this is not a financial graph, but I’ve seen the similar patterns of impulse/correction in many graphs that measure opinion and/or human activity)

By the way, I think this is the soundtrack of this meme :) : https://www.youtube.com/watch?v=If27FnxvjZA

That’s why the evocation school is the best. Sculpt spells, then fireball all the things!

That’s the same thing. :) If you reduce computing load, you reduce the need for costly hardware and you reduce the need for energy, thus you reduce the amount of money needed to build and run your setup. There’s a saying in (software) engineering : “reducing energy consumption and increasing performances requires the same optimizations”. Make your code faster (by itself, not by buffing up hardware) and it consumes less energy. Make your application simpler, and it will run faster, and it will consume less energy. It’s not an absolute truth (it sometimes happen that you make your code faster and it consumes more energy), but it’s true most of the time.

Basically, yes. You can configure most cron programs to mail task output to you (it’s usually done by setting the MAILTO variable in the crontab, provided sendmail is available on your system).

I use that to do things like:

0 9 11 10 * echo 'lunch with John Doe at 12:20'

It sends me a mail, and I can see the upcoming events with crontab -l. If it’s not a recurring event, I then delete the rule.

My favorite cost cutting tip is to avoid big webapps running on docker, and instead do with small UNIX utilities (cron instead of a calendar, text files instead of note taking app, rsync instead of a filehosting dropbox-like app, simple static webserver for file sharing, etc). This allows me to run my server on a simple Raspberry Pi, with less than 500mb of used RAM in average, and mininal energy consumption. So, total cost of the setup:

• Raspberry Pi : 77€ x 2 = 144€ (I bought two to have a backup if the first one fails)
• MicroSD 64gb : 13€ x 2 = 26€ (main and backup)
• average energy consumption : 0.41€ (2kWh) per month

With that, I run all services I need on a single machine, and I have a backup plan for recovery of both hardware and software.

Getting used to a UNIX shell and to UNIX philosophy can take some time, but it’s very rewarding in making everything more simple (thus more efficient).

I have both a resin printer and a FDM printer, I can confirm the price difference exists, but is not prohibitive (resin is about 2x PLA). The difference of quality is mind blowing, though (in favor of resin printer). If you’re building an army, I assume you will have many pieces? If so, the difference of printing time is also mind blowing in favor of resin printer. The reason for that being that if you print 10x the same mini on your build surface, with FDM it will take 10x the same time as a single mini (the printing head must move to cover each point) while with the MSLA (resin printer), it will take… 1x the same time. That’s because each layer is flashed from a PNG image, so all points of a layer are created at the same time. On top of that, there are things you can do with resin that you just can’t with FDM, especially because of supports needed for hanging parts : if your character has arms, chances are the hand will be lower than the shoulder, which means than when printing from bottom to top, the hand won’t be connected to the body until printing reaches the shoulder, so you need something to support it (a “tower” under the hand, that you will cut off). It’s easy to do with resin, because in a bath of dense liquid, Archimedes is your friend and you can build the support in wild angles, but it’s way more difficult in thin air (with a FDM).

An other thing to know, though, is that resin printing is way more messy. You will manipulate toxic products, that you can’t throw in the sink, you need gear to cover your hands and face, and resin ends up everywhere and is near impossible to clean. But it’s worth it, especially if you’re into minis. :) FDM, on the other hand, is unbeatable for functional prints (because those resin prints are damn fragile, and tend to not be perfectly at the scale you designed).

Oh, I see. Yes, that may very well be a matter of point of view. For me, modding the printer is part of the fun, not something I do to try desperately to stay on the cutting edge. :) The RepRap dream of “printers that can reproduce themselves” never fully materialized, but modding is the next best thing.

Are they still sold, anyway? I mean, sure, someone who has no printer should buy a more recent one. But that was not the subject, here : the question was if it was needed to replace an Ender 3. I certainly would not, personally, it would be throwing out a perfectly good printer for incremental upgrades. Of course, it depends on the usage. For someone who uses their printer professionally to serially print all day, sure, it’s probably worth it upgrading. Me? I really don’t care if my prints are slower. I really don’t find the Ender 3 hard to get a print right either. But I’ve been printing since the wooden Printrbot Simple about a decade ago, maybe I’m just used to it.

That’s the name we use to designate software like GitHub, GitLab and similar, which provide repositories hosting and tooling like issue trackers. It’s supposed to be named like that because of SourceForge, the oldest of such tools, although I didn’t hear the term “forge” before the last 5 years or so, long after SourceForge demise, so I imagine there is a bit of nostalgia in this name (not sure who is nostalgic of SourceForge, though 😂). The wikipedia page : https://en.wikipedia.org/wiki/Forge_(software)

The worst part is that this is a direct quote from Harness’ CEO, not from TechCrunch author. :) Maybe they have a great product, I don’t know, but it certainly feels like an amateurish launch. :D

There hasn’t been a new Git repo launch in almost a decade

Am I the only person annoyed they seem to mistake repositories for forges? It’s already annoying when casual users say “git” for “GitHub”, but those guys actually want to build a forge, explaining they’re going to do better than anyone else. Maybe start by properly using the terms?

Has there been so much going on in the market? I’m still using my Ender 3 and I’m not sure what I would add to it, it serves me well (I already added a BL Touch, in the early days I got it, and a glass bed, although I don’t see much benefit from that last part). It’s just doing the job perfectly. 🤷 That being said, I only use it for functional printing. I way more often use my Elegoo Saturn (a resin printer), as I use it to print my tabletop minis.

That sucks, sorry for you to have to go through that. Do you already know modeling/sculpting? If not, that’s the perfect time to get into it, and really be able to do anything with your printer when you get it. :)

I’m sorry to say that, but you get you’re definition wrong. “decentralized” means “which has no center anymore”. ActivityPub is decentralized. The usual criticism of the Fediverse by peer to peer networks such as Secure Scuttlebutt or Dat is not that ActivityPub is not decentralized, but that it will eventually “recentralize”, like client/server models tend to do, when one instance capture all the traffic (like Gmail with SMTP, we already see signs of that with mastodon.social, but we’re still very far from it to be a center). I think that maybe you’ve been exposed to that argument and misunderstood it?

What you really want to say is that ActivityPub is not p2p. You can criticize the fact that there is a server/client model behind it, which means that users don’t really own their data and can lost it if the server goes down - that’s a valid criticism.

To which I would answer that it’s a tradeoff. :) ActivityPub is built on top of HTTP, the well known protocol on which the web is built. This makes it dirt simple to build an ActivityPub app. The difference of adoption rate between SSB, Dat or IPFS and ActivityPub has nothing to do with luck. It’s HTTP and JSON, it’s just simpler (and easier) to build on top of ActivityPub. Not only that, but it’s a w3c standard. Which means, for people like me who have been burnt by building apps on top of the Beaker Browser only to see it abandoned, that we can trust there won’t be any rug pull. That matters.

And of course, you can also… run your own server (look into self-hosting if you’re interested in that, there’s a vibrant community here on Lemmy about that). If you run your server, then you own your data and the other servers become your peers. The idea that only others (presumably big companies) can have servers is a very centralized way of thinking.

I do enjoy the zen of NMS (nothing like piloting alone on the surface of a planet with the sound of the rain falling on the cockpit), but even after all those years and cool upgrades, it still feels so empty… If you enjoy tabletop RPGs and have an opportunity to play one with like-minded friends, I recommend you try Traveller. It’s all those things you mentioned, in a way, way bigger and denser scope. :) Also with actual civilizations, empires, politics, commerce, wars, fleets, etc.

Yep, as often, the extension of the standard comes from non standard features developed here are there (as you can see in the participating organizations block, most of the big names are working on this). The difference in ircv3 is that you can expect to see all those features everywhere, instead of having this software implementing this feature, that other one having that other feature, and you have to choose which one is the most important for you. Basically, it’s a rebase of the standard. :)

They do maintain the simplicity of the line oriented protocol, so I’m fine with that. :)

That’s the strongest point of IRC, IMO, and why it’s kept so simple : every instruction is a plain text line, period. It makes it incredibly simple to build on top of it. You don’t need to introduce a dependency to a project that probably will be abandonned in a few years, at which point you’ll have to rewrite your codebase to use an other dependency, for a few years. You just open a TCP connection, you read lines from the socket and write lines to it, each line is its own instruction structured in well known fields, and that’s it. It’s so simple!

As long as IRCv3 sticks to that, they have my blessing. :)