Wolf480pl
> just like cache the filesystem in RAM
This has been implemented for ages now.
>then just have pointers to objects and store those in other objects
Pointer chasing can be pretty bad for performance. In many cases, you'd be better off with a local sqlite3.
Wolf480pl
@natecull
>Essentially, a database is its own little OS, with its own little list of users and passwords, which is... silly if you already have an OS
umm... OS doesn't have transactions.
I get what you're trying to say, and I agree that the data should be owned by the users, not by the applications, but I don't think oversimplifying the role of databases like this is not fair.
Wolf480pl
@pfm it's a one-off situation. It usually doesn't work like that. But usually we don't organize a programming competition for half the Europe.
Wolf480pl
@pfm You wouldn't want to state in the rules that contestants will be able to do $X, without having $X implemented, would you?
Wolf480pl
@pfm can't. Need to get this working by tomorrow, before we release the final version of the contest rules.
Wolf480pl
@pfm this isn't funny at this point
Wolf480pl
@rysiek
But you said before that it can't do any harm...
Wolf480pl
@pfm
No.
The code is bad for language-agnostic reasons.
The problem I have when refactoring it, is that there's no static types, which makes it a lot harder to know things like:
Is foo is an instance of that class to which I added a bar() method a moment ago? Can I foo.bar(), or will it throw an AtributeError at the most unexpected moment?
Wolf480pl
Refactoring legacy code to be able to not use obsolete workarounds for obsolete problems is exhausting.
Especially if the code is written in Python.
Wolf480pl
@rysiek
Do your best! :)
Wolf480pl
@mulander oh, makes sense.
In my case I had the server start hedgewars in an Xorg with dummy screen, join a game as a spectator, and livestream it to beam.pro
Wolf480pl
@mulander
But it was on purpose.
Wolf480pl
@thog boaaard
Wolf480pl
@enkiv2 Right now I have 900 package sinstalled on my Arch laptop.
I can't imagine how I could possibly review each of them for quality and malice, figure out the build flags, and then keep track of the updates.
Also, most of my strong opinions align with those of Arch maintainers. Some don't. But I don't mind. For me it has the best cost/benefit ratio I've seen so far.
Wolf480pl
I always felt like snappy/flatpak/appimage were stupid ideas, but didn't exactly know why.
Then someone wrote this article
http://kmkeen.com/maintainers-matter/
and suddenly it all makes sense.
Wolf480pl
@quad
oh, no, that's memorable and unique but not secure.
It's unique because they use a different password on every site.
It's memorable, because you only need to remember to reverse the domain name.
It's not secure, because the method has been posted on mastodon, and now everyone can figure out what password for domain X such a person would use.
Wolf480pl
@kensanata @david_ross hence, an advisory (as in, being only an indicator) "venting/shouting at clouds/no comments pls" flag would be helpful.
Wolf480pl
Finally, if a person is doing advocacy, i.e. trying to spread their opinions and convince others to share their ideas, then we should discuss that person's opinions, even if that person explicitely doesn't want discussion.
A position of "hey everyone listen to me, you must agree with me, if you don't agree with me you musn't reply or I'll call it harassment" is IMO unacceptable.
Ofc it's exaggerated, I haven't seen it happen like this.
Wolf480pl
@david_ross
If you make a post that is hard to understand to anyone other than you, because you have weird definitions of some words, inconsistent with how most of other people understand those words, then don't be surprised that people either ask you to define those words, or assume a meaning that is different from what you intended.
If you don't care if people understand your post, why publish it?
If you do care, pls put some effort to help them understand.
Wolf480pl
@quad maybe it's a bug?
Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.
All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.