he/him

Alts (mostly for modding)

@[email protected]

(Earlier also had @[email protected] for a year before I switched to @[email protected], now trying piefed)

  • 4 Posts
  • 192 Comments
Joined 9 months ago
cake
Cake day: March 14th, 2025

help-circle



  • sga@piefed.socialMtoFediverse memes@feddit.ukAmazing Art
    link
    fedilink
    English
    arrow-up
    6
    ·
    3 days ago

    as i said i do not have any issue with subject matter or meme. problem is that we have a rule “We are not YPTB”. so anything which is too community or moderation specific is not allowed (it is just so shit flinging between comms or instances does not happen).

    I just pointed it out. my general moderation style is to almost never delete unless blatant rules violation, and hence i asked if i am missing something.

    I am still not removing because comments seem shit free, so there is no need to do anything.

    I hope I have been able to explain my side.


  • i am not a web dev, so please correct me if i am wrong, but a runtime is essentially a specific version of browser in some capacity, more comparable to blink in some sense (minus the html+css parts). so there is a js engine (v8 or firefox’s spider if i am not wrong) and that essentially just executes the js, but it needs stuff around it (think for example io or cli interface). none of the run times implement independent js engines, as they are really hard, but surrounding stuff is relatively easier, and likes of deno/node/bun implement that.

    And as other commenter said - it has other stuff too, for example a package manager, transpiler (most common would be converting typescript to js i think), bundler (just makes a bundle kinda like java jar), etc.


  • sga@piefed.socialMtoFediverse memes@feddit.ukAmazing Art
    link
    fedilink
    English
    arrow-up
    7
    ·
    4 days ago

    Pardon me matey, but I am not sure if this post fits. This seems to be complaining what should or should not be posted in art share community (and i am not commenting on the subject matter here - I agree with your reasoning in disclaimer), but it is not a meme. it is specific to art share community. I an not removing it just yet, possibly because there is some meme that I do not understand, so if there is, please reply.




  • my guess is mostly lack of arrays in posix shell. there are other things as well, but arrays are really useful, especially when they are making other things easier to write. A stupid comparison i can think of is a compiled language targettng x86-64v2 or 3 instead of v1 because it has avx (i am not actually sure when avx was added, but imagine some instruction being added). without avx, your binary would be slower (in posix, for arrays, you essentially need to maintain a string and use awk/sed/cut to get particular elements, and many things would just not be possible). If they would target v1 (posix), it will run in more places, but it would be slower for a lot of people who have v2 or newer. And a lot of people have v2 or newer (bash).


  • to some extents - sunk cause fallacy and performance.

    I had a launcher script which required it’s run to complete under 50 ms to be usable. python just did not make the cut (it would call external stuff and more). I know i should not expect performancce from shell scripts, but started from essentially a find of about 20-30 files and a cat of at most 100 lines. It was fast enough then. then I kept adding stuff, it kept slowing down. I thought of converting to python, even did some initial bits, performance was not good.

    beyond a certain point, i kinda stopped caring optimising (i replaced bash with dash, made mos tif not all calls to external tools a minimum, and tried to minimise slow calls(think calling some tool again and again vs a vectorised operation, or not reading a variable multiple times in memory )). At some point it reached 300-400ms, and i decided to split it into 2 things - a executor part which cahes output of some commands with certain run conditions, and a launcher part which just read the output file (now almost a 1 miB).

    At some point i decided learning rust, and first thing i wrote was that launcher. implemented caching and run conditions better, moved larger files (now it read multiple megabytes(15+)) to /tmp dir, which is mounted in memory, and tried to minimise variable calls. now it lists 10 times more files, in less than a third or fifth of the time.

    tl;dr - a stupid person did not shift to a compiled program for a long time and kept optimising a shell script



  • as top comment has already mentioned - try wikis. think arch wiki or gentoo. you dont have to use those distros to know about linux, just read them. and even better, spin up virtual machine, and install arch/gentoo there. since you already use bazzite, you don’t have to redo stuff already done (like playing game or something), so you use the sandbox playground to just learn. if it breaks, redo, or make checkpoints.






  • should this not be a testament to arch? i have a custom bootloader (well not custom, it is uki, generated by a relativly new an niche uki generator booster), i started using rust coreutils since march or april, have swapped much of other core stuff, or have a relatively minimal system, and still be patient?

    Arch’s specialness does not end with installer. and this kinda is not unique to arch - arch does it, so does debian (but slower to get new packages i want), gentoo (maybe better than arch, but i do not want to compile everything), void (less packages), fedora (between arch and debian i guess), etc. most base distros allow you to swap stuff.


  • I do not know why this got so downvoted (maybe for cross posting too much?, if so, try to reduce that a bit). Someone has said wpaperd already, but there is also awww. As to exactly get the rate of switching.

    awww img <path/to/img>  
    
    # You can also specify outputs:  
    awww img -o <outputs> <path/to/img>  
    
    # Control how smoothly the transition will happen, as well as its frame rate.  
    # --transition-step: smaller values = smoother. Default is 2 if --transition-type is `simple`, and 90 if it is not.  
    # --transition-fps: Default = 30.  
    awww img <path/to/img> --transition-step <1 to 255> --transition-fps <1 to 255>  
    
    # There are also many different transition effects:  
    awww img <path/to/img> --transition-type center  
    
    # Note you may also control the above by setting up the AWWW_TRANSITION_FPS,  
    # AWWW_TRANSITION_STEP, and AWWW_TRANSITION environment variables.  
    
    # To see all options, run  
    awww img --help