• 0 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • A game that was released last year has absolutely zero knowledge of this 8k PS5 so it’s not going to magically render at 8k or 40% improvement. Some might get a framerate bump if frame sync can be turned off - the game might have been GPU bound and therefore with a better GPU it yields a better framerate. Sometimes. And AI upscaling might give a pseudo > 4k effect but it’s not really true 8k.

    A handful of games might get patched to avail of the improved rendering capabilities when they detect PS5 Pro. Minimal stuff really. Maybe the config file will improve draw distance or turn on certain effects like raytraced shadows / reflections when it knows the console can handle it.

    Hardly seems worth the vast additional expense especially if somebody already owns a PS5 though. Moreso because Sony are trying to stiff people into buying the cheaper “digital” version which basically means any physical collection won’t work with it.


  • Nvidia is worth 42bn USD and employs 30,000 people.

    Nvidia’s has a market cap 30x of Intel’s. So it could issue more stock to raise capital for a buyout. It’s not the company equity but the market cap that it needs to have money to purchase. Even a controlling stake of > 50% would give them defacto control. Of course governments & regulators would probably block it or force Nvidia to divest bits of itself, and that’s probably the greatest protection Intel has against such a scenario.

    But if Intel weakens further, it may well be someone else tries to acquire it. I bet a lot of companies would love to snaffle it up. It’s kind of ironic that Intel used to be the big dog in the semiconductor space but even AMD is bigger than it these days and are potentially many others who’d like buy it out. In fact, for all we know Intel might be shedding all these jobs to make it look more attractive to potential buyers.





  • Concerning logs:

    1. You can still log to text if you want by configuration (e.g. forward stuff to syslog) and you can use any tools you like to read those files you want. So if you like text logs you can get them. You can even invoke journalctl to output logs on an ad hoc / scheduled basis in a variety of text formats and delimited fields.
    2. Binary allows structured logging (i.e. each log message is comprised of fields in a record), indexing and searching options that makes searches & queries faster. Just like in a database. e.g. if you want to search by date range, or a particular user then it’s easy and fast.
    3. Binary also allows the log to be signed & immutable to prevent tampering, allow auditing, intrusion detection etc… e.g. if someone broke into a system they could not delete records without it being obvious.
    4. You can also use splunk with systemd.

    So people object to systemd writing binary logs and yet they can get text, or throw it into splunk or do whatever they like. The purpose of the binary is make security, auditing and forensics better than it is for text.

    As for scripts, the point I’m making is systemd didn’t supplant sysvinit, it supplanted upstart. Upstart recognized that writing massive scripts to start/stop/restart a process was stupid and chose an event driven model for running stuff in a more declarative way. Basically upstart used a job system that was triggered by an event, e.g. the runlevel changes, so execute a job that might be to kick off a process. Systemd chose a dependency based model for starting stuff. It seems like dists preferred the latter and moved over to it. Solaris has smf which serves a similar purpose as systemd.

    So systemd is declarative - you describe a unit in a .service file - the process to start, the user id to run it with, what other units it depends on etc. and allow the system to figure out how to launch it and take care of other issues. It means stuff happens in the right order and in parallel if it can be. It’s fairly simple to write a unit file as opposed to a script. But if you needed to invoke a script you could do that too - write a unit file that invokes the script. You could even take a pre-existing init script and write a .service file that kicks it off.


  • arc@lemm.eetolinuxmemes@lemmy.worldSystemd controversy be like
    link
    fedilink
    arrow-up
    27
    arrow-down
    1
    ·
    edit-2
    8 months ago

    Kind of sad there are still people raging over systemd. When it flares up in discussions there is the usual debunked nonsense:

    • it only logs information to binary and this is somehow bad. Except it it can be configured to log to text as well and it uses binary so it can forward secure sign records to prevent tampering as well as offering database style query operations.
    • it’s insecure because the repo has millions of lines of code. Except that they compile into hundreds of small binaries running with least privilege, and often replacing the task of far more dangerous processes (e.g. there is an NTP client in systemd which sets the time and nothing else).
    • various rants about the primary author

    What is more bizarre is the nostalgia and hearkening back to sysvinit scripts when systemd didn’t replace sysvinit! Systemd replaced upstart which replaced sysvinit. Because writing 100s of lines of script to stop/start/restart a process sucked - insecure, slow, didn’t scale, didn’t capture dependencies and everyone knew it. Upstart was the first attempt to solve the issue and was used in Debian / Ubuntu, Fedora / Red Hat, openSUSE and others until systemd came along.






  • If you look at any modern desktop application, e.g. those built over GTK or QT, then they’re basically rendering stuff into a pixmap and pushing it over the wire. All of the drawing primitives made X11 efficient once upon a time are useless, obsolete junk, completely inadequate for a modern experience. Instead, X11 is pushing big fat pixmaps around and it is not efficient at all.

    So I doubt it makes any difference to bandwidth except in a positive sense. I bet if you ran a Wayland desktop over RDP it would be more efficient than X11 forwarding. Not familiar with waypipe but it seems more like a proxy between a server and a client so it’s probably more dependent on the client’s use/abuse of calls to the server than RDP is when implemented by a server.




  • arc@lemm.eetolinuxmemes@lemmy.worldLinus does not fuck around
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    11 months ago

    I define effective by the fact it was self evidently effective. No need to split hairs or dissemble here. Linux is objectively, indisputably the most important piece of code in the world. Everything else, such as a the context free boo hoo about some times when he has had a go at people is just noise.