I can’t honestly recall or put my finger on it what I did wrong.

Choose fedora because it used my laptop subwoofer and wasn’t a rolling release. I remember each time (x2) reading about how to update the distro and each time my system was completely borked. I went to debian, read upon alsa, made my subwoofer work with a homegrown script and never looked back.

To this day I am wondering if people recommending redhat are trolls or paid.

Never have I ever successfully updated a fedora system. It was always a reinstall.

Your selfless wish may be granted wwussh @TheBananaKing@lemmy.world

Graphics driver for sc8280xp are already a thing. There are more issues in convenience daily driving linux, currently. From the top of my head:

• firmware update path
• dtb update/loading path
• no virtualization
• no universal dock compability
• missing HDMI/DP features

I suspect that these issues are common between their ARM chips and will be addressed for both chips almost simultaneously. But I have no real idea on kernel development. And their documentation is only shared with linaro so one can only guess.

That’s beyond my experience but I would say functional languages can perform similiarly.

I suppose - and honestly do not know if - aggregation is done via synchronization into some persistance unit.

Therefore I would eypect that a functional language like Elixir, Lisp etc. would outperform a language with manual memory management in terms of maintainability.

Depending on the capabilties of packing structs into close memory or traceability and elaboration of compiler it may outperform single or multi-threaded.

Though outperforming recent JREs may be hard, since they may trace hot paths. Default configuration Java vs. a proficient developer of a functional language I assume that latter at least go even.

But I can’t judge. Even on the repository of said program I did not even bother to look at the contents of the gradle.build or Dockerfile to be honest.

I do think that maintainability of functional languages, when only the common denominator between any functional language is used, is better to spaghetti Java source code. But that’s another issue, right?

// edit: Spaghetti Source Code is a good thing in my opinion. And sincr I did not adsress your question directly: A proficent developer is more likely to write faster Java then functional code, since Java is just a layer above C with one of the best compilers there is. Functional languages require carrying some non-neglectable knowledge of the compiler to make use of the fastest paths through the code. On the other hand Java is just ALGOL-Syntax and therefore imperative; Which translates more easier into *.asm.

// edit2: Synchronization into some db isn’t depending on the nature of the language but there may be overhead where some concepts of languages simply perform better. So I would expect that transitions from some interpreted language is slower then compiled languages. Note that even though Java belongs to the former it is conceptually compatible with the latter. I’m out. You called me out. I’m a still a newbie. Had to append so much.

There is Sublink but it’s written in Java, I don’t think I want to deal with Java’s runtime environment.

Don’t hate Java just for the sake of it. According to the repository they ship a Dockerfile and use gradle to build it. Everything should be abstracted for you.

When comparing environments for a program between Java and Python you should probably prefer Java’s. Years of experience and build from the ground up for enterprise deployment. Python module system is hacked together. It ain’t even be fair for python to compare itself in this regard.

Also this project is spot-on within Java’s main territory. It makes absolutely sense to me to use Java for such a program.

Plus monitoring/maintaining a Java application is way better then any python program.

Modularity of software ranked way too low.

It is bearable but feature complete. Every month linaro and the community add functionality. The most recent things include a custom power-domain mapper implementation and apparently camera support.

If you are running wayland you can simply install any os and its working oob.

The laptops weight and heat production is awesome. Very practical. Also the body is exceptional sturdy and worth mentioning (even in comparsion to a T14, e.g.).

But:

• external monitors are not detected at boot
• no hibernation
• battery time is very depended on the task. It ranges from 4 to 13 hours.
• no virtualization support, so one is stuck with tiny code generator runtime when using kvm
• audio is pretty quiet, so depending on the environment an external source is required.

I followed almost all patches on the lkml. It appears to me that the upcoming chip can benefit from the sc8280xp hugely. It sufficies for my use cases but I promised myself a little better, yet.

Man. I bought Lenovo ARM. I wanted to buy a tuxedo so badly. Now I’m stuck with this thinkpad.

Your awesome for correcting me (I use vim BTW)

Plus emacs and lisp are superior. But I didn’t managed to jump ships.

One could point to the inclusive or environmental aspect to this approach.

How goes the saying? 32 MB of RAM and always swapping?

This should get their slogan. Any linux should have this slogan :) Have fun on your endeavors!!

You can use LFS to… Install targeted-kernel Setup AUR/pacman as package manager Use a minimal DE if needed. Otherwise just use the x.org kiosk to start your applications without any de.

Corporate rated this strategy viable

Rehire obv.

I think he’s coming from here:

As an developer you create a solution to a problem from yours. You release it under a FOSS license.

Your job is done - You shared your work. The community may find your project useful and builds upon it. Their interest is to get their changes upstream. You have no obligation to help with onboarding and implementing features for others.

So if they are requesting a merge you may reject it since it does not meet your standards. Maybe you have to make your stance clear and create a CONTRIBUTION alongside your code.

With this mindset you wouldn’t hang out on a non-indexable platform.

Your project mostlikely is requesting explicit participation. Maybe this is the point in between you guys.

Now go on with the discussion :)

Especially on servers I make sure to attend in the software packages survey. Just so that the holy-gods and kings of maintainers are aware of me, the peasant running old packages.

No yield saya. I’m sorry.

change own’uh

But chroot is schrude!

Plugins may introduce some risks imo. Non-standard behaviour may be a b*tch.

E.g. the idea of a plugin which posts tags:

How are these elected and shares across instances? And displayed on clients? Are they modifying the actual data written by the user in order to sync?

Maybe they are attractive to admins. But they can mostlikely already query and modify the database, right?

I do not want to be against it just mentioning that it may introduce problems on its own which in turn needs to get adressed. E.g.: When multiple plugins do a task at the same hook; How is the ordering managed? When are transactions committed? Should there be a maximal amount of time spend on plugins at some hook? How are resources shared then?

Let’s think about bad actors: Meta _deploys provides a plugin which compresses and decompresses post content and saves plenty of ressources for the admin. After a couple of years they put it to the grave or change the compression methods such that old posts cant be retrieved. But their instance surely still can access those.

I admire beeing lean. Had some projects where bad plugins raised in popularity and become the defacto standard. But they were resource-hungry and badly written or barely maintained. Workarounds spread back to the original program.

Just looked the first time into the lemmy code and it appears to be very neat and clean. I would recommend to stick to it. But then I am no maintainer and a nobody shrugs

//edit: To me plugins are good to aid customization and enlarging the user base. I do not see how this contributes to the fediverse and instances in the long run.