True. Although Calvin looks to be only rotating the paper by 90°, which would work as long as the original line is continuously increasing on both axes. Not so much “upside down” as “right-side up”, tho.
True. Although Calvin looks to be only rotating the paper by 90°, which would work as long as the original line is continuously increasing on both axes. Not so much “upside down” as “right-side up”, tho.
Assuming that these have fairly impressive 100 MB/s sustained write speed, then it’s going to take about 93 hours to write the whole contents of the disk - basically four days. That’s a long time to replace a failed drive in a RAID array; you’d need to consider multiple disks of redundancy just in case another one fails while you’re resilvering the first.
Writing in ASM is not too bad provided that there’s no operating system getting in the way. If you’re on some old 8-bit microcomputer where you’re free to read directly from the input buffers and write directly to the screen framebuffer, or if you’re doing embedded where it’s all memory-mapped IO anyway, then great. Very easy, makes a lot of sense. For games, that era basically ended with DOS, and VGA-compatible cards that you could just write bits to and have them appear on screen.
Now, you have to display things on the screen by telling the graphics driver to do it, and so a lot of your assembly is just going to be arranging all of your data according to your platform’s C calling convention and then making syscalls, plus other tedious-but-essential requirements like making sure the stack is aligned whenever you make a jump. You might as well write macros to do that since you’ll be doing it a lot, and if you’ve written macros to do it then you might as well be using C instead, since most of C’s keywords and syntax map very closely to the ASM that would be generated by macros.
A shame - you do learn a lot by having to tell the computer exactly what you want it to do - but I couldn’t recommend it for any non-trivial task any more. Maybe a wee bit of assembly here-and-there when you’ve some very specific data alignment or timing-sensitive requirement.
Why buttplug for tachyons?
Yeah. Doesn’t take much optimising of disk writes to make things run much better on a Pi; they’re quite capable machines as long as disk i/o isn’t your limiting factor. Presumably the devs have been doing some tidying up.
My workplace is a strictly BitBucket shop, was interested in expanding my skillset a little, experiment with different workflows. Was using it as a fancy ‘todo’ list - you can raise tickets in various categories - to remind myself what I was wanting to do next in the game I was writing. It’s a bit easier to compare diffs and things in a browser when you’ve been working on several machines in different libraries than it is in the CLI.
Short answer: bit of timesaving and nice-to-haves, but nothing that you can’t do with the command line and ssh. But it’s free, so there’s no downside.
Ah, nice. Had been experimenting with using my Raspberry Pi 3B as my home Git server for all my personal projects - easy sync between my laptop and desktop, and another backup for the the stuff that I’d been working on.
Tried running Gitea on it to start with, but it’s a bit too heavy for a device like that. Forgejo runs perfectly, and has almost exactly the same, “very Github inspired” interface. Time to run some updates…
Nah - Doom (DOS): and Doom Eternal are on there, as are Baldur’s Gates 2 and 3.
Most common example would be a bicycle, I think - your pedals tighten on “in the same direction the wheel turns” as you look at them. So your left pedal has left-hand thread, and goes on and comes off backwards.
The effect of precession also means that you can tighten the pedals on finger tight and a good long ride will make them absolutely solid - need to bounce up and down on a spanner to loosen them.
Well; you could use that engine to produce something well-written, deep and interesting like New Vegas, but that still got dinged for being an absurdly bug-ridden release with serious performance issues. It was great despite the engine, not because.
There’s some slightly-shonky open world engines that support some really impressive RPGs (eg. Baldur’s Gate 3 on the Divinity engine - looks great but performance is arseholes) and some very impressive open-world engines that support some lightweight RPGs (eg. Horizon Forbidden West on the Decima engine - looks great and smooth as butter). And then you’ve got the Creation engine, which looks terrible and has terrible performance, and which runs bugs and glitches in a way that combines into (usually) very shallow RPGs.
Annoys me that “less” is always correct, which makes “fewer” completely redundant, and yet it’s a short word that could be valuable in conversation if opened up and reused for something everyday that has a long name.
“Before I leave the house, I always check that I’ve got my keys, phone, and fure in my pockets.”
Dang. It’s going to take a dedicated regime to fill up a one gallon jar with, eh, fluids.
Ironic, since 2B doesn’t have ass on any platform. My anaconda don’t want none of that.
Oh yeah. Partying like its 1989 and I’ve booted up my Amiga. Let’s get some unicycling friends in here and do some hacking in 3D.
Android has a massive built-in library of supporting functions that abstracts away most of the differences between devices, including support libraries for older versions of Android, and Flappy Bird is almost the “hello world” of gamws writing.
Super Mario Bros on the NES came in at 31 kB, and it was a bit more of a game. 100 kB for Flappy Bird isn’t all that impressive.
“Register bit twiddling.” Setting all the modes that all their various cards can operate in, with the associated code for sending the bit updates over the connection bus. Tedious stuff that’s very prone to copy-paste errors if written by hand.
At some point you have to take AMDs word for it that these codes = this functionality, but if the right graphics come out then it can’t be so wrong.
The one with Timothy Olyphant and Olga Kurylenko in it? It was fine, had a few good action sequences in it. Managed to both not be much of an adaptation of the game, but also trying to be enough of an adaptation that it frequently makes very little sense. Probably have been better if they’d cut loose a little more, had some more fun with it. Gets a completely OK / 10 from me.
Because if you disable browser autocomplete, what’s obviously going to happen is that everyone will have a text file open with every single one of their passwords in so that they can copy-paste them in. So prevent that. But what happens if you prevent that is that everyone will choose terrible, weak passwords instead. Something like September2025!
probably meets the ‘complexity’ requirement…
Having had one of the old Windows phones with a keyboard dumped on me at an old workplace, can confirm it’s completely possible for a phone to have a keyboard and be a complete piece of shit.
A good phone with a good keyboard may have some use cases. If you do a lot of writing but not any more computing power or screen space than a phone has, plus you want to be doing that on the move, then yeah. For me, can shitpost on forums using my phone in my spare time, and dealing with on-call work issues - having multiple tabs of Jira and Slack open, for instance - just isn’t really practical on a small screen.
If your job is very email-centric, then yeah, sure. Blackberry were very good for just having the stuff you need - email, vpn, ‘corporate’ office documents - in a form that worked.