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

help-circle
  • I’d be happy if plasma looked a bit more like WinNT. Completely functional, all the information there at a glance. Nothing hidden away in hamburger menus, no guessing about what you can and can’t click on. Does what it needs to then gets out your way. The best-designed that Windows has ever been.




  • I dunno. Oxygen Not Included looks crisp on a 4K monitor. And it makes my job easier, being able to have an absolute tonne of code on-screen and readable. I reckon I could probably use an 8K monitor for those things.

    Yeah, I generally have FSR running on any 3D game made in about the last decade - even if I can run it at 4K at a reasonable framerate, my computer fans start to sound like a hoover and the whole room starts warming up. But upscaling seems a better solution than having separate monitors for work and play.


  • Google Stadia wasn’t exactly a responding success…

    From a previous job in hydraulics, the computational fluid dynamics / finite element analysis that we used to do would eat all your compute resource and ask for more. Split your design into tiny cubes, simulate all the flow / mass balance / temperature exchange / material stress calculations for each one, gain an understanding of how the part would perform in the real world. Very easily parallelizable, a great fit for GPU calculation. However, it’s a ‘hundreds of millions of dollars’ industry, and the AI bubble is currently ‘tens of trillions’ deep.

    Yes, they can be used for other tasks. But we’ve just no use for the amount that’s been purchased - there’s tens of thousands of times as much as makes any sense.









  • Interesting, but misguided, I think.

    If you’ve selected Python as your programming language, then your problem is likely either to do some text processing, a server-side lambda, or to provide a quick user interface. If you’re using it for eg. Numpy, then you’re really using Python to load and format some data before handing it to a dedicated maths library for evaluation.

    If you’ve selected Go as your programming language, then your problem is likely to be either networking related - perhaps to provide a microservice that mediates between network and database - or orchestration of some kind. Kubernetes is the famous one, but a lot of system configuration tools use it to manipulate a variety of other services.

    What these uses have in common is that they’re usually disk- or network- limited and spend most of their time waiting, so it doesn’t matter so much if they’re not super efficient. If you are planning to peg the CPU at 100% for hours on end, you wouldn’t choose them - you’d reach for C / C++ / Rust. Although Swift does remarkably well, too.

    Seeing how quickly you can solve Fannkuch-Redux using Python is a bit like seeing how quickly you can drive nails into a wall using a screwdriver. Interesting in its way, but you’d be better picking up the correct tool in the first place.




  • Oh, that’s obnoxious. I thought it was another ‘button along the bottom’, but it takes up the space that should be ‘right control’? Bastards. Hopefully you can rebind it to something useful, even if the keycap symbol sucks.

    Mind you, I’ve already got caps-lock rebound as ‘control’ and alt-gr rebound as ‘compose’. My laptop has the ‘penguin’ key (it’s a Tuxedo laptop, no Windows key here) used for Sway. (My desktop keyboard is a Model M from before the days of Windows keys, have had to bind ctrl+alt as the ‘Sway Key’.) I’ve already got some ‘useless keys’ that I could rebind to other things - looking at you, print screen - but one you could press with your thumb while chording would always be nice.

    Those ZBooks look like fine laptops. If you installed Arch on them, obviously ;-)




  • Indeed.

    In some ways, this kind of thing is ideal for Rust. It’s at it best when you’ve a good idea of what your data looks like, and you know where it’s coming from and going to, and what you really want is a clean implementation that you know has no mistakes. Reimplementing ‘core code’ that hasn’t changed much in twenty years to get rid of any foolish overflows or use-after-free bugs is perfect for it.

    Using Rust for exploratory coding, or when the requirements keep changing? I think you’ve picked the wrong tool for the job. Invalidate a major assumption and have to rewrite the whole damn thing. And like you say; an important choice for big projects as choosing a tool that a lot of people will be able to use. And Window is very big.

    They’re smoking crack, anyway. A million lines per dev per month? When I’m doing major refactoring, a couple thousand lines per week in the same language, mostly moving existing stuff into a new home, is a substantial change. Three orders of magnitude more with a major language conversion? Get out of here.