PSone.css – Playstation 1 style CSS Framework
micah5.github.io
micah5.github.io
https://github.com/sw-yx/spark-joy/blob/master/README.md#fun...
Copy pasting random CSS around is why, as an example, a project I work on has multiple subtly different shades of blues, why margins and paddings are not consistent even on the same page, etc.
Sounds like a lot of work compared to npm update.
Speaking as someone who builds massive web projects for a billion dollar company, I can state that nothing you describe is necessary if you document your work, maintain standards, and have recurring maintenance events.
CSS maintenance is not hard. It's just boring.
You wanted a fun website but what you got is a dependency manager with a production CI/CD pipeline taking 15 min to check that yes, the sentence you wrote can in fact be written.
Package managers work, but isn't there some middle ground that doesn't involve depending on a runtime that itself is continuously updated ?
The existance of other methods doesn't preclude you from doing it whatever way you want to. The CSS file is right there on github to download https://github.com/micah5/PSone.css/blob/master/PSone.css
You could use the upstream URL, but that'd be a privacy issue.
You could proxy the upstream file, but that rules out static serving.
Maybe use a Makefile that fetches the last version and uses it ?
That would be a package manager lol.
You don't, because you're rendering a simple html page, and whatever minor changes are in the new version are largely irrelevant.
Unfortunately, this is the state of much of software development today. It's why most webpages are enormous. It's why massive increases to speed, processing power, and communication bandwidth have resulted in no real net increase to web-browsing speed for the last 10 years.
It's why massive increases to speed, processing power,
and communication bandwidth have resulted in no real
net increase to web-browsing speed for the last 10 years.
There are clearly cases where complex build/CI/CD pipelines make sense, but people now believe they need big enterprisey FAANG-scale solutions even when they don't.
jsDelivr is pretty nimble in the regard. It mirrors GitHub and npm (and caches and (optionally) minifies the result) so depending on the project, you can get a specific release, or just pull from the master branch, by simply changing the URL of the CSS file.
There wasn't really a unifying UI on the PS1 anyway except for the BIOS
The cursor here seems inspired by it: https://www.youtube.com/watch?v=0jZ0DxwRm-0
https://fantasyanime.com/emuhelp/images/epsxe-memory-card4-t...
I really liked the visualizations built in as a kid. It was my CD player for years.
I think the biggest reason was the desire to cram more data onto the disk. Uncompressed redbook CD audio fills up your whole disc... fast.
It's also hard (impossible? I think?) to do seamless looping playback with CD audio if you're just streaming redbook because the laser has to seek back to the beginning of the track. This is a common issue in games where the background music for a level might be e.g. 1:30 of looping music.
Lastly, storing naked redbook audio on the discs may have been been seen as affecting game CD soundtrack sales, which were often a pretty big deal in Japan.
(I had an EU PS1 bought ~1997)
It would make for a nice blog theme. In fact I might give it a go myself.
But then I think that as a blog author your primary concern should be to get people to read your blog in the first place and this may not be super easy on eyes and readability.
Better to keep it simple stupid.
Maybe you have an extension interfering?
No longer can edit previous comment.
It's been a thing since forever to show the actual button graphic in-game during tutorials or menus or whatnot. But the PS5 D-Pad's individual buttons, out of context of being part of the cluster, makes them look backwards.
As a result, I spent most of my time with Diablo 2 Remastered, drinking the wrong potions.
Seriously, check this out and tell me what arrow directions they mean to suggest while sitting 10 feet away on a couch: https://ibb.co/KxM4bf4
The two points in the icons provide two exactly opposite messages, and the wrong one is larger than the correct one, thus GP's confusion.
You pretty much have to have a very specific image of a d-pad in mind. It helps that that d-pad is also the one in your hands, but you shouldn't have to look at the controller, or have its detailed look memorized, to figure it out.
I think what happened here is obvious: there’s a very longstanding software design pattern that was broken by a perfectly sensible hardware controller design. The solution is likely to just stop using that software pattern. Make analogous icons or whatnot.