• 1 Post
  • 137 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle


  • Reads like Intel will be using Nvidia’s stuff for integrated systems, and doesn’t say anything at all about discrete graphics cards.

    If you’re integrating a GPU, then it’s going to be either for a laptop, in which case performance-per-watt and total die size are very important, or it’s for a generic business PC, in which case ‘as cheap as they can get away with’ takes over. A B580 might be the best mid-range graphics card, but those aren’t the areas where it shines. Using someone else’s tech makes sense.


  • I got myself a remarkable after seeing a colleague use one and thinking they were cool. An astonishing price for what is essentially a kindle that you can write on, but that is essentially the entirety of its functionality right there. No web browser, no ebook integration, no keyboard, just a thing for scribbling notes with a big battery life. No distractions.

    As such, it’s completely ideal for my work diary, meeting notes, D’n’D notes, maps for games that I’ve been playing, random scribbles, all sorts. Quite a lot lighter than the thousands of sheets of paper that would be required otherwise. Also not as rude as popping open a laptop when you’re meeting someone - they can see you’re just making notes and writing to-dos.



  • The harpoon works just fine too, one-hits the stick insects and does her some damage as well if you can line it up. She’s not very dangerous if you know her moveset, but that’s an education learned by many runbacks.

    Doesn’t say they’ve fixed the comedy bug where if you look at the map while on one of the collapsing platforms, then when you fall through then the game stops accepting input, Hornet just stares at it forever. Only glitch I’ve found, quite impressive for a day one purchase.





  • Oh sweet baby Jesus. That is some astonishing code for validating the title and body of a PR.

          - name: Create PR message file
            run: |
              mkdir -p /tmp
              cat > /tmp/pr-message.txt << 'EOF'
              ${{ github.event.pull_request.title }}
              
              ${{ github.event.pull_request.body }}
              EOF
    

    Put a single-line EOF in your pull request body, follow it up with a completely arbitrary set of Bash commands, whatever you damn well like, put all the environment variables with the repository secrets into a webhook request and send them off somewhere, make sure you terminate it with another cat > /dev/null << 'EOF' to match the other EOF. Now you can compromise the entire project by raising a pull request.


  • 4K for me as a developer means that I can have a couple of source files and a browser with the API documentation open at the same time. I reckon I could use legitimately use an 8K screen - get a terminal window or two open as well, keep an eye on builds and deployments while I’m working on a ticket.

    Now yes - gaming and watching video at 8K. That’s phenomenally niche, and very much a case of diminishing returns. But some of us have to work for a living as well, alas, and would like them pixels.


  • Speaking as a developer; I’ve a 4K screen which is amazing for having loads of source files open at the same time, and also works for old or undemanding games. Glorious Eggroll’s version of Proton has all the FSR patches in it, so you can ‘upscale anything’. Almost any modern game, I’m going to be running at lower resolution, usually either 1440p or the slightly odd 2954 x 1662. Generally, highest-quality graphics and upscaling looks better than medium-quality native to me, for games where I have to compromise.

    I would be interested in an 8K display for coding, as long as the price is reasonable. I’m not spending five grand, that would be crazy. But I’d still be upscaling for playing games, as basically no GPU could drive that many pixels.



  • The Android dev kit includes a copy of QEMU that’s set up to emulate ARM with a selection of popular screen sizes and revisions of the OS, so that you can test your app on a variety of ‘potential phones’ before you upload it to the marketplace. Snapdragons are amazingly performant CPUs for how gently they sip at the battery, but they’re not that strong in the big scheme of things - any random x86 processor should be able to emulate them while using fifty times the power. A Steam deck ought to be able to do it; the request will then be ‘we’d like to play Android games better’, which to me is a much more reasonable ask.



  • addie@feddit.uktoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    13
    ·
    1 month ago

    The ability to do some basic calculations is what was missing in CSS from the start, IMHO. You don’t want paragraph text to be too narrow or too wide as it would become unreadable, so a rule like “at least 20 ems, and then whichever is smaller of 100% or 80 ems centered on the page”. But that required either really convoluted layout and rules, or just to work it out with JS after the page is loaded.

    Would have been even better if we’d got Donald Knuth involved in the early CSS efforts, with some LaTeX-like attention to the details. There’s no reason that computers can’t render beautiful text, but it’s rare for one person to be an expert typesetter and an expert programmer.



  • The ‘traditional’ way of storing a database is on a mainframe or supercomputer, where all the information is stored in tables with the information all uniquely stored, frequently containing id references to other tables. For instance, an ‘orders’ table would have a customer id in it, and the ‘customer’ table would have their name and address. The programming language for databases like that is SQL - PostGres and Oracle are examples. That model gives you a lot of advantages - the data is always consistent, changes are either made completely or not at all - but every query has to go through one machine, so performance can suck, and you waste a lot of time ‘joining’ tables together for certain kinds of query.

    If you’re storing eg. a blog with comments on it, that model doesn’t make sense. Each page has a varied selection of comments, comment will have a username and maybe their icon, which will rarely change, but will need to be evaluated by the database every time. It would make more sense to output the pre-rendered page as a JSON blob, and you could have a hundred machines with a few pages each to share the load. Updating people’s icons and adding new comments would need to be done by telling each machine to make a certain update if they’ve a copy of that page; you’d ‘eventually’ be consistent, but if you don’t care about that then you get a very scalable robust solution quite cheaply. Examples of such ‘NoSQL’ databases are MongoDB, Hadoop and DocumentDB.

    Linux foundation have looked at DocumentDB’s license and said ‘yes, free enough for us’, so they’ll adopt it.