Ok…
So your point is that a bad logging implementation is bad. And I agree.
I’m not seeing how that’s extendable to implementations as a whole. You’re conflating your bad experience with "log aggregation is bad’.
Just because your company sucks at this doesn’t mean everyone else’s does.
Yeah, ofc it is.
I’m working in a system that generates 750 MILLION non-debug log messages a day (And this isn’t even as many as others).
Good luck grepping that, or making heads or tails of what you need.
We put a lot of work into making the process of digging through logs easier. The absolute minimum we can do it dump it into elastic so it’s available in Kibana.
Similarly, in a K8 env you need to get logs off of your pods, ASAP, because pods are transient, disposable. There is no guarantee that a particular pod will live long enough to have introspectable logs on that particular instance (of course there is some log aggregation available in your environment that you could grep. But they actually usefulness of it is questionable especially if you don’t know what you need to grep for).
These are dozens, hundreds, more problems that crop up as you scale the number of systems and people working on those systems.
Damn, that’s just cancerous
I love this.
Especially being written in a language like C#. Which makes it incredibly accessible to work on, performant, and long-lasting.
Straight to the personal attacks, I’m sure this can only end well.
This is not how you promote a project…
Yeah I had literally no idea what you were talking about until you mentioned the actual name in the comments.
NPM almost universally refers to node package manager in any developer or development adjacent conversation in my experience. Given that both the site, the command, the logo, and the binaries are “npm” makes that more appropriate.
Nginix proxy manager is far to niche to be referred to universally by acronym when it’s only ever used as an acronym when the context for it’s usage has already been defined (ie. In it’s documentation).
This becomes much more clear when you Google the acronym.
It is, but also it’s worrisome since it means support is harder, which means risk of abandonment is higher and community contributions lower. Which means “buying in” is riskier for the time investment.
Not really criticizing, 10/10 points on making something and then putting it out there, nothing wrong with that. Just being a user who’s seen too many projects become stale or abandoned, and have noticed that the trend has some correlation to the technology choices those projects made.
I’ve been looking a platform for personal blog, portfolio, and what not that’s kind of fun to play with without having to build the whole thing myself.
What’s your opinion of this project?
As of today I’m actually in a lucky position where I am now able to set up a secondary NAS at my brother in laws and use that as a backup server that I can back up to essentially in real time.
All it’ll cost me is the hardware and the electricity.
Yes.
I’m sure one can reasonably infer that I do not mean 30 meters.
Conveniently at highway speeds 30 minutes and 30 miles away are essentially equal.
I’ll try and use appropriate notation next time
I might be crazy but I have a 20TB WD Red Pro in a padded, water proof, locking, case that I take a full backup on and then drive it over to a family members 30m away once a month or so.
It’s a full encrypted backup of all my important stuff in a relatively different geographic location.
All of my VM data backs up hourly to my NAS as well. Which then gets backed up onto the large drive monthly.
Monthly granularity isn’t that good to be fair but it’s better than nothing. I should probably back up the more important rapidly changing stuff online daily.
The error posted in the app is from the website itself. It’s likely that the password manager is injecting something into the page which is causing errors.
There are many ways for this to go wrong, it has nothing to do with the web service itself.
We’re on Lemmy are they afraid of being censored because they are writing software catered for NSFW uses?
Other social media’s chilling effects are pretty deeply engrained unfortunately…
And there’s also the live sync extension which allows you to have live document syncs in real time via your own self-hosted CouchDB instance
PHP for sure can have a negative effect depending on how they are handling their data access through.
The application code itself running on PHP probably isn’t a problem but the influence that PHP may have over your data access patterns can be a source of significant performance problems.
Shipping’s too long.
That’s not how it works.
Since the voltage is half and the amperage is the same half the wattage is supplied to heat water. This means it takes longer not that it doesn’t work.
OP also said they received hot water in a kettle not that they received an electric kettle in which to heat it in.
And here I am running NFS as the backing storage on an R720xd for 4 other M630 VM hosts.
Connected via SFP+ DAC. I get max bandwidth saturation, and ~65k IOPS!! NFS is great 😅
You could use things like AWS S3 or similar offerings from other providers like digitalocean. They have plenty of documentation that guide you through how they work.
So, essentially, really poorly written malware? Given the number of assumptions it makes without any sort of robustness around system configuration it’s about as good as any first-pass bash script.
It’d be a stretch to call it malware, it’s probably an outright fabrication to call it a virus.
The language it’s written in has very little, almost nothing, to do with how efficient larger applications are.
This is almost entirely up to the design and day-to-day decisions of the developers. These almost always outweigh the efficiencies of the underlying languages themselves (within reason).
A single location of poor data access patterns could negate the aggregate performance gains of your entire application, as an example. A framework that prevents you from making simple mistakes and drives you towards more efficient patterns goes much further than the language is written in.
Between Rust, C#, Java, and Go you’re essentially even on performance for large applications (with C# pushing ahead of the pack). What you are not even on is engineering efficiency, it’s going to take considerably longer to build the same set of features in rust than any of the others listed. And the performance is likely the same, potentially even worse depending on the maturity of the ecosystem.
Rust is a great systems design language and a great language to choose when developing high efficiency libraries & frameworks for I/O and data processing. It’s not really a great choice for application development due to how slow it is to actually get things done in.
I fully expect to see alternate backends written in more operationally efficient languages over the next decade that will catch up to the official Lemmy codebase, and potentially even replace it. It actually sounds like a super fun project, funding is always a problem though.