- Joined
- May 4, 2021
This is even gayer than killing the social blade stats by ruining the subscriber numbers.
Tech you miss/ new tech trends you hate - ok boomers
- Thread starter Kenobi
- Start date
- Joined
- Mar 29, 2014
- Joined
- May 4, 2021
It was showing youtube subscribers in real time etc.
it was relatively easy to spot botting and fake subscibers because they usually arrived as a big block, instead of the more organic random times. Now you wouldn't be able to tell because YT aggregates subscriber numbers intro blocks...
- Joined
- Sep 7, 2016
They can do that, the program just needs to alert windows to not go to sleep, shut down or hibernate until it's done.
Telling unattended Windows Update that now is not the time is harder.
- Joined
- Mar 22, 2021
Here's a laptop that isn't proprietary, you might like it.
- Joined
- Oct 6, 2020
Probably the only "modular device" concept that might actually have some legs, but it'll be one hell of an uphill battle. They definitely have the right idea with the laptop though.
The problem with all these modular devices has always been practicality and cost, but in a few circumstances, just retarded design.
Remember Phonebloks?
- Joined
- Jan 8, 2020
I'd love to find a G5 Power Mac or a Mac Pro with the revised G5 case. That and the aluminum Powerbook G4 were the peak of Apple design.
- Joined
- Jul 7, 2021
Reminds me of computer class at school with our suspected fat, paedo teacher. Memories.
- Joined
- Feb 3, 2013
I have a late run G5 tower with PCi-e slots and DDR2, it's cool to own until the PSU goes bad due to being 16 years old and having to support the power strain of a G5 processor nonstop for a local school, then comes the fun with needing automotive grade torx screwdrivers and entire service manuals to replace it because they chose to use these weird ass metal prongs behind the motherboard instead of a normal 24-pin header, and that's on top of screws beneath the CPU heatsink and the power/usb front panel using a friction fit pin contact method that makes removing it require total patience.
Also, good luck getting any GPU besides a Geforce 6600 for cheap because PPC got dropped like a rock fast enough to not get decent picks for cards. The whole end of PPC is cursed with weird tradeoffs.
fuckidunno
kiwifarms.net
- Joined
- May 24, 2019
I remember Jeff Goldblum narrating the Tv adverts
somehow fitting.
.....
.....
uh oh, just took a nostalgia trip and I got triggered -- tell Sophie ole Jeffery needs to be twitter cancelled.
"That would be like changing my sex" (abt 13 seconds in)
- YouTube
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
www.youtube.com
- Joined
- Feb 24, 2021
I was trying to come up with some algorithm for game physics in 6502 asm. I had this autistic divine intellect idea of using self modifying code in some parts to save some cycles and memory as well. Then it had occurred to me that the 65C816 used in the SNES has the option to expand the registers to 16 bit, so it might be enough to just do 16 bit fixed point math in the accumulator and shift the result 8 bits right.
Well, turns out that the 16 bit part has been implemented in a retarded way. You see, there aren't special opcodes for 16 bit operations. For example on the 68K you have moveq and move.b/w/l depending on whether or not you're dealing with bytes, words or long words. But on the 65C816 you can either do 8 or 16 bit operations at any given time, depending on whether or not you have the CPU set in native or emulation mode. There is no lda.w or sta.w, which means that you can't avoid burning one extra cycle and eating one extra byte with immediate instructions. Yeah, you could switch back and forth between emulation and native mode, but guess what! Say goodbye to the upper byte of a register! Now, it does sound dramatic, but it appears to still be faster per cycle than on the 68k.
BUT, what I then realized is that doing 16 bit math is unnecessary for this scenario anyways, as the shifting part burns a lot of cycles, no less than 16 cycles for shifting by 8 bits, and it also eats up an additional 8 bytes due to only being able to shift one bit at a time. Now PyFags and PyTards are probably gonna be shocked and confused, but you are better off using the 8 bit mode, and 8 bit math, which saves some bytes and cycles. Now, you still want 8 bits of fractional precision, which is fair enough. However, you can just abuse ADC immediate, BCS, and INC value on some zeropage address if Carry is set. Turns out it's actually faster. Oh, the value in the accumulator will just wrap around after it goes over $FF.
Now, the PyFags and PyTards are probably seething or sperging out about me being a nigger retard using immediate values because that would mean that I can have only one fixed speed. Nigger, this piece of code is supposed to be in RAM, so should the speed change, I can just overwrite the immediate operand with the new value. I don't even need to write a macro that would generate 256 ADC immediate combinations. Besides, ADC immediate is 33% faster than ADC value in zeropage. And you'd have to store the new speed value anyways, so you might as well use this. In the end it's almost twice as fast compared to taking advantage of the 16 bit functionality. Now, I have yet to take a look at how many cycles would such a thing burn on the 68K, but I have a feeling that it would burn more of them. The PC Engine's CPU would especially benefit from this, due to it being a 6502 on steroids running at the same speed as the 68K in the Megadrive.
Here's a screenshot of some sort of mockup I made in Notepad.
Edit: I was being a tard, turns out I forgot to add a sta instruction. And of course, if you're storing a byte you have to switch back to emulation mode. Bumping the total cycle count to over 30 cycles.
Well, turns out that the 16 bit part has been implemented in a retarded way. You see, there aren't special opcodes for 16 bit operations. For example on the 68K you have moveq and move.b/w/l depending on whether or not you're dealing with bytes, words or long words. But on the 65C816 you can either do 8 or 16 bit operations at any given time, depending on whether or not you have the CPU set in native or emulation mode. There is no lda.w or sta.w, which means that you can't avoid burning one extra cycle and eating one extra byte with immediate instructions. Yeah, you could switch back and forth between emulation and native mode, but guess what! Say goodbye to the upper byte of a register! Now, it does sound dramatic, but it appears to still be faster per cycle than on the 68k.
BUT, what I then realized is that doing 16 bit math is unnecessary for this scenario anyways, as the shifting part burns a lot of cycles, no less than 16 cycles for shifting by 8 bits, and it also eats up an additional 8 bytes due to only being able to shift one bit at a time. Now PyFags and PyTards are probably gonna be shocked and confused, but you are better off using the 8 bit mode, and 8 bit math, which saves some bytes and cycles. Now, you still want 8 bits of fractional precision, which is fair enough. However, you can just abuse ADC immediate, BCS, and INC value on some zeropage address if Carry is set. Turns out it's actually faster. Oh, the value in the accumulator will just wrap around after it goes over $FF.
Now, the PyFags and PyTards are probably seething or sperging out about me being a nigger retard using immediate values because that would mean that I can have only one fixed speed. Nigger, this piece of code is supposed to be in RAM, so should the speed change, I can just overwrite the immediate operand with the new value. I don't even need to write a macro that would generate 256 ADC immediate combinations. Besides, ADC immediate is 33% faster than ADC value in zeropage. And you'd have to store the new speed value anyways, so you might as well use this. In the end it's almost twice as fast compared to taking advantage of the 16 bit functionality. Now, I have yet to take a look at how many cycles would such a thing burn on the 68K, but I have a feeling that it would burn more of them. The PC Engine's CPU would especially benefit from this, due to it being a 6502 on steroids running at the same speed as the 68K in the Megadrive.
Here's a screenshot of some sort of mockup I made in Notepad.
Edit: I was being a tard, turns out I forgot to add a sta instruction. And of course, if you're storing a byte you have to switch back to emulation mode. Bumping the total cycle count to over 30 cycles.
Attachments
Last edited:
- Joined
- Feb 3, 2013
Couldn't stay away, could you Byuu?
- Joined
- Feb 24, 2021
Oh shit, oh shit, oh shit! OH SHIT!!! Looks like Byuu really is dead, and that his ghost had possessed me! Eh, fuck it, don't call the exorcist yet. I actually like the divine intellect. If I start considering trooning out, only that will be the time to exorcise Byuu's ghost out of me.
- Joined
- May 4, 2021
Archive.org has Winamp Skins, and they are even interactive.
You can even put mp3 files into them and play it.
This is nice.
Winamp Skin: Purple Glow : Free Download, Borrow, and Streaming : Internet Archive
Winamp Skin: Purple Glow
archive.org
This is nice.
- Joined
- Jan 28, 2018
I remember playing MP3s on an old Pentium and it was pretty mindblowing to get music down to that size to be honest. You have to think that normal harddrives end-users used to have back then usually did not have enough capacity to store the contents of an entire CD (or had very little spare left when they did) and mp3s really changed the availability of music on computers. Also funny is that said Pentium was under a fair load just by decoding that mp3. The absolute limit where the late generation 5x86 processors by Cyrix that could do it in a 486-style system, if you didn't try to do anything else while listening to music.
Around that time, I used to have two PCs running because one was literally not enough for all I was doing and the "bleeding edge" of computer technology changed every 6-8 months so I'd always have the new one and the former generation, "obsolete" one next to it. Crazy, ain't it?
Around that time, I used to have two PCs running because one was literally not enough for all I was doing and the "bleeding edge" of computer technology changed every 6-8 months so I'd always have the new one and the former generation, "obsolete" one next to it. Crazy, ain't it?
- Joined
- Feb 24, 2021
About mp3 playback, CPU Galaxy managed to get decent quality stereo MP3 running without issues on a 486DX4 100, so I am sure that a Pentium 90 would still be able to run Doom decently. Now, another system you may not have known to handle MP3 is...the N64. No, seriously, the N64 is powerful enough to decode MP3 audio, Conker's Bad Fur Day being one of the games using MP3 audio.
- Joined
- Mar 17, 2019
There's an interesting article about that here:
Audiokinetic Blog
Yeah WinAmp on a real early Pentium was definately pushing it. I think there are specialist DOS players that could play 128-192 MP3s on a DX4 easily enough, but you still wouldn't want to be doing much else (that's what MODs and MIDI music is for).
- Joined
- Feb 24, 2021
Well, seeing that a 486DX4 100 could decode much higher bitrate MP3, I am sure that the 94 MHz MIPS CPU could decode 24 Kbps MP3 just fine, especially with the RSP's help. It would also be possible to predecode it to regular N64 PCM, since there is plenty of RAM for speech quality audio.
Billy Beer
kiwifarms.net
- Joined
- Apr 23, 2021
Recently started listening to LPs for the first time in my life. No I'm not a hipster, I'm building a man cave and decided to get a full stack hifi, never had one as a kid because poors.
The audi faggots are right, the sound quality of an lp is much better than cd. And I've been trawling around record shops looking for cheap vinyls to listen to, maybe discover a few bands along the way.
Which made me realise how shitty our on demand society is. The majority of my best memories and experiences are built upon waiting, expectations and surprises. We have none of those today.
The audi faggots are right, the sound quality of an lp is much better than cd. And I've been trawling around record shops looking for cheap vinyls to listen to, maybe discover a few bands along the way.
Which made me realise how shitty our on demand society is. The majority of my best memories and experiences are built upon waiting, expectations and surprises. We have none of those today.
- Joined
- Jun 13, 2016
Most likely because vinyls are mixed and mastered properly without being fucking brickwalled. Can't brickwall a vinyl record or the grooves would collapse.