Static_Rocket @ Static_Rocket @lemmy.world

Posts

0

Comments

251

Joined

2 yr. ago

I strive to replace bill. I only work on undocumented code from 3rd parties.

Yeah, the only thing kind of close is GPL3's infectious license and that still allows for profit use assuming the code is opened. (Harder to be evil here but technically still possible.)

Unfortunately this will cause issues if the community attempts to do anything with this package later as well. See the fiasco with Multimc and Polymc. Nobody came out of that looking particularly inviting for devs. I feel bad for the one guy that walked the line between the two licenses for as long as he did. I just ended up jumping to the community fork because they addressed my issues faster and their license ended up being more permissive.

You know what, if it keeps me from getting weird phone calls from my gramps once a month it's good enough.

Eh, I've seen some software internally prefer 0::0 instead of just ::0 or :: . Notation wise though you are correct, it is unnecessary.

0.0.0.0/0 0::0/0

You didn't specify it couldn't be in CIDR block notation...

Just be a little careful here. There are distro live images that Ventoy does not support. They are rare but they do exist.

Yeah, I've noticed occasional regressions in video decode performance between kernel releases but they tend to fix them in the next release.

Otherwise smoother sailing than Nvidia for sure.

https://github.com/intel/media-driver/

https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/intel/meson.build?ref_type=heads

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915

Yeah. Only thing missing is the GUC/HUC firmware source and loading that should be optional still.

Also those type of blog posts tend to rub people the wrong way when they are written by the creator. Apparently other people see them as a call-out post more that something informative.

Bottom for life (or at least until something with more stats comes out)

That's... that's the point. Vanilla, as in no modifications.

https://github.com/ValveSoftware/csgo-osx-linux/issues/3402

Only true if the printer supports IPP Everywhere or one of the offshoots. Otherwise you need drivers. Sometimes you still need drivers for ink level reporting (glaring at the HP printer in the corner of my room).

If you're going to marginalize a subset of an already marginalized community then nothing will ever be enough. What kind of an argument is this anyway?

Not relying on your own custom implementation of GL that completely breaks embedded platforms...

Have they finally dumped the required js stub loader?

No, no, they've got a point. The architecture of Wayland is much more sane. Because of the way refresh events are driven its also much more power and memory efficient. I'll miss bspwm and picom but man there is a lot riding on simplifying the graphics stack under Linux. The X hacks, GLX, and all the other weird interactions X decided to take away from applications made things non-portable to begin with and a nightmare for any embedded devices that thought GLES was good enough.

Eh, I don't mind learning a new config if the tool requires it. I just want to define run commands in yaml and have it auto generate pods and startup scripts.

It just bothers me that I have to use a tool outside of the ecosystem for that. Doesn't it also behave differently though? Like doesn't it assume everything is root when you use the socket required for docker-compose?