Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
Posted on 20-01-02, 06:49 in I have yet to have never seen it all.
Custom title here

Post: #801 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by tomman
Raymoo learns that error money IS serious money.

(Touhou + numismatics?! Hell, why not?!)
That's fantastic, and I say this with near-zero knowledge of the touhoumons.

--- In UTF-16, where available. ---
Posted on 20-01-04, 04:38 in Games You Played Today REVENGEANCE
Custom title here

Post: #802 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by funkyass
do people not know what a head spreader does?
Gets in the way of cooling/protects the die from crushing.

Heat spreader is a pretty name, but they're actually armor.

--- In UTF-16, where available. ---
Posted on 20-01-05, 05:03 in Games You Played Today REVENGEANCE
Custom title here

Post: #803 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Well, it IS called Dead Space, not Alive Elevator.

--- In UTF-16, where available. ---
Posted on 20-01-07, 00:48 in I have yet to have never seen it all.
Custom title here

Post: #804 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by sureanem
I think there's a far simpler explanation, Occam's razor and all.
An ambitious program of cost-cutting, outsourcing, and digitalization had already begun.


What's the expression in English? Wise for a penny, stupid for a pound?

"Penny-wise, pound-foolish" as I've heard it. And as I've heard it used, it describes the opposite situation, where someone is very thrifty and frugal on very inexpensive purchases, but very willing to just throw money at large expenses.

Think of someone that just spent two grand to build a high-end gaming PC, then attached a shitty ten-dollar mouse because "gaming mice are too expensive"

--- In UTF-16, where available. ---
Posted on 20-01-07, 05:11 in I have yet to have never seen it all.
Custom title here

Post: #805 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by kode54
Which sort of explains my dad's situation with the iMac I gave him for Christmas a few years ago. He prefers the shitty corded Dell mouse that came with the shitty Dell minitower he bought before I gave him that machine, to the slightly annoying and terribly not ergonomic Apple Magic Mouse that came with the iMac.
In fairness, an expensive mouse can still be shitty. Apple's proven that MANY times over the years.

--- In UTF-16, where available. ---
Posted on 20-01-07, 09:30 in Misc. software
Custom title here

Post: #806 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by kode54
WizTree is like the best of WinDirStat and Everything, a disk space usage analyzer that uses the MFT directly. Of course, that optimization only works with NTFS volumes, but most Windows users are on that, right?
I don't think Windows can even install on a FAT partition anymore. :(

--- In UTF-16, where available. ---
Posted on 20-01-07, 09:34 in I have yet to have never seen it all.
Custom title here

Post: #807 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by kode54
But I absolutely love the touch scrolling, and some of the gestures.
Obviously diffrent people value diffrent things. Otherwise there'd be exactly one mouse in the market.

--- In UTF-16, where available. ---
Posted on 20-01-08, 11:21 in I have yet to have never seen it all.
Custom title here

Post: #808 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by sureanem

It has one physical button. How am I supposed to right click with it?
Using the POWER OF YOUR MIND.

And why would I want to use it with Linux?

Because you're a masochist, I guess? I mean, you're already using Linux.

--- In UTF-16, where available. ---
Posted on 20-01-11, 23:57 in I have yet to have never seen it all.
Custom title here

Post: #809 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
That's... impressively incompetent.

--- In UTF-16, where available. ---
Posted on 20-01-13, 00:16 in I have yet to have never seen it all.
Custom title here

Post: #810 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by sureanem

While we're at Stupidville, here is your daily reminder to get your shit fixed for Y2K+:
https://it.slashdot.org/story/20/01/12/0221226/this-years-y2k20-bug-came-directly-from-a-lazy-fix-to-the-y2k-bug

Don't see what's so wrong with it. Surely they can just expand it again? Not too much work to re-window to say 2060, when all of the people working on it will have retired.

The problem is obvious. You're saying what they said in 2000. And, well, what they said when the original programmers wrote this stuff in the 1960s.



I don't like how all the stuff has to be Unicode and 4-digit dates and ISO god-knows-what compliant. There's a beauty to keeping it simple: 7-bit text (for international users, ISO-8859 or classic 16-bit Unicode), 2-digit years, and 1 pixel = 1 pixel (no god-damned "virtual pixel" nonsense). Localization is UB.

7-bit isn't even enough to encode a full set of punctuation alongside a full english alphabet and roman numeral set.
2-digit years were a memory-saving hack that was relevant when we measured memory available in bytes, and has no place in the modern world.



In a few short years, we won't have too much stuff left from the 1990s, so we can return to using 6-digit dates, as one should. Will be really beautiful and I look forward to it.
Nope. These databases still contain data reaching back to 1960, sometimes for regulatory purposes.
The past will never go away, and every computer program going forward needs to be able to handle dates from any point in computing history AT A MINIMUM.
Also, two-digit years will break again in 2100, which is a single lifetime away. Three-digit years is a minimum requirement for any new software development.

--- In UTF-16, where available. ---
Posted on 20-01-13, 04:51 in I have yet to have never seen it all. (revision 1)
Custom title here

Post: #811 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by funkyass
Windowing is a good solution, because it means you don't need to touch the data in the archives, but would need re-assessing the fix yearly - which no one ever did. Fixing it now means either moving the window, or maintaining three systems - one for pre y2k data, one for the windowed dates, and the system that uses a 64-bit integer timestamp that handles time-zones and leap-seconds.

the WWE2K20 game is a code base from the PS1 era, if anyone was wondering why it happened.

It is a good SHORT-TERM fix that keeps things working while you create a real fix. But the real fixes weren't created and it just created an ongoing upkeep cost as the "fix" is reworked over and over and over.

Also, the WWE2K20 date code isn't from the PS1 era, because the PS1 didn't have a clock or network connectivity. Regardless, it contained date code that HAD been hacked to keep working through Y2K, but not truly FIXED.




Posted by sureanem

Posted by CaptainJistuce
The problem is obvious. You're saying what they said in 2000. And, well, what they said when the original programmers wrote this stuff in the 1960s.

And was there a problem in 2000? No, because they fixed it. And they did so without making everything ugly.

It's disgusting. Instead of YYMMDD, a nice compact number, you get yyYY-MM-DD, where the first 2 digits are just pointless decoration.

They fixed it in a fragile, non-extensible way that was guaranteed to break again, and the cost of millions of dollars and countless manhours. Because no one ever thought "Hey, maybe computers will still exist in thirty years and we should make more robust code".

Also, I know of one major corporation still operating systems flagged as non-Y2K-compliant after Y2K. They had special update and reboot procedures to keep them working in spite of everyone, because management refused to authorize expenditure for replacements.

2-digit years were a memory-saving hack that was relevant when we measured memory available in bytes, and has no place in the modern world.

They have a place in my mind: 20200113 is hard to parse, why you need dashes, 2020-01-13, and suddenly you've almost doubled the size from a nice, clean, 200113.

Two-digit years is fine for a presentation format, but not a data format. Hyphens shouldn't be stored in the date, they're a part of the presentation, just as a choice of slashes or hyphens is presentation, or year presented at the beginning or end of the date, or even suppressed entirely.

Here's how serious and respectable countries with well-established traditions of record-keeping handle dates:
Iceland: The number is composed of 10 digits, of which the first six are the individual's birth date or corporation's founding date in the format DDMMYY. The next two digits are chosen at random when the identification number is allocated, the ninth digit is a check digit, and the last digit indicates the century in which the individual was born (for instance, '9' for the period 1900–1999, or '0' for the period 2000–2099). An example would be 120174-3399, the person being born on the twelfth day of January 1974.

So you're saying that they solved the century rollover by extending the date in a backwards-compatible manner? That's fantastic!


As you can see, a lot of different solutions can be used, none of which involve appending on extra junk.

As you can see, Iceland created a robust solution that will serve them for centuries to come without risk of overlap or confusion.
Also, birth dates on state-issued IDs are a limited case of date handling, as it is almost always obvious from other parts of the ID what century the birth date is.

Incidentally, my state issues an 8-digit ID number that does not encode any of that data. Birth date is presented as a separate field, in the form of MM/DD/YYYY. And did so in late twentieth century as well(I've seen my parents' old drivers licenses, and they had 4-digit years).


The thinking man, I think, would in legacy systems use the excess space in the day field to encode the century. 01-32 1950-2049, 33-64 2050-2149, 65-96 2150-2249. After that, the months field can be used.

That is a super-ugly hack. It is so revolting that I want to inflict bodily harm on you for suggesting it.
It is also incompatible with databases storing the date fields in BCD, or using ugly five-bit fields for binary storage of M and D. Or that simply store D as 0-356 and leave the month to the presentation layer.

Nope. These databases still contain data reaching back to 1960, sometimes for regulatory purposes.

That does seem to be a problem, but presenting stuff with 4-digit years is still unacceptable. A hidden single-bit field "centuryLSB" set to 1 for the third millennium seems like a more sensible solution.

That's a good fix, and kicks the can a century down the road instead of twenty years down the road. Presentation and storage format do not have to match, and never have.

But since most every piece of hardware made in the last fifty years is byte-oriented, you may as well allocate a whole byte to the century field as an unsigned integer. If centuries are back-allocated for "legacy dates" then that'll get us to AD 25599 with no issues in the date format. And quite bluntly, if that code is in use long enough for there to be a Y256K bug, then whatever society descended from us deserves it.

On the topic of Unix time, leap seconds are disgusting. They should have went with GPS time and had the timestamp been the amount of second-sized time intervals since the epoch. It's not like they subtract 3600 each time DST hits, right?

On this I agree with you. Unix time should be a continuous count forward, and adjusting for leap-seconds should be an issue for presentation formatting(which makes even more sense when you consider that the Unix time format already abandons the concept of years, months, days, hours, and minutes).

and every computer program going forward needs to be able to handle dates from any point in computing history AT A MINIMUM.

No. The applications here are games, they certainly don't. Mission-critical software shouldn't be relying on string representations of dates.

No, the applications here contained a game. While we can argue the transience of entertainment software, the article said four of five of ALL Y2K fixes were windowing, which is a cheap hack that had to be reworked to make it over the end of the window.

Dates definitely shouldn't be stored as strings. String dates are a sign of inept database management. If we're storing Gregorian dates(or Julian, those are still in use some places!), I'd expect 3 fields in BCD or unsigned-integer. A field for year, another for day, and one more for month. In any order you please, because that is a problem for the presentation layer.

Not that an 8-bit unsigned integer for the year meant software was Y2k-compliant, as plenty of software dutifully advanced the year to "19100" due to in-built assumptions.


Also, two-digit years will break again in 2100, which is a single lifetime away. Three-digit years is a minimum requirement for any new software development.

Three-digit years is the worst of both worlds. Then I would rather have four, which at least encodes a legitimate concept. This is an absurd conversation anyway. What about the year 10K problem? What then, huh? Meanwhile, 253402300800 is a perfectly legitimate 64-bit integer.
I'd rather store a four-digit year too.
But a three-digit year is used by Iceland's ID system, and they clearly know what they are doing.


Posted by kode54
I don't care if this is painful, you can't expect every single user to have identical hardware.

You can, you should, and it's regrettable they don't.
Terry Davis had the right idea, but he was too extreme. I think 24-bit 1920x1080 / Windows 7 / Stereo / 100 Mbit would be a good default. Enthusiasts can use IPS panels or homemade scaling solutions.

We clearly should've all stuck with Commodore 64s as the one true computer.
ZX Spectrums for Europe, it's what they deserve for allowing the british to popularize the ZX Spectrum.

No, mandatory fixed hardware standards are a terrible idea. I'm still mad at 1920x1080 becoming one. I'm glad that displays have started to advance meaningfully beyond what I was running in 1999. (1280p@70Hz > 1080p@60Hz, since we only do one-number resolutions these days.)

--- In UTF-16, where available. ---
Posted on 20-01-13, 05:57 in I have yet to have never seen it all.
Custom title here

Post: #812 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by kode54
Also, since Jistuce made me read it...

PH33R M4 1337 M1ND C0NTR0L P0\/\/44!


Fuck you, Windows 7 dies in less than two days. Good riddance, it was already replaced years ago. There are many choices for alternatives that continue to receive updates. Not the least of which is Windows 10.

And if you don't want patches, Windows 2000 is better than Windows 7... or really, any other Windows. It is objectively the best Windows.

--- In UTF-16, where available. ---
Posted on 20-01-13, 06:54 in I have yet to have never seen it all. (revision 1)
Custom title here

Post: #813 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by creaothceann
Posted by sureanem
Isn't anything serious stored with Unix time anyway?

Yeah, about that...

Posted by CaptainJistuce
And if you don't want patches, Windows 2000 is better than Windows 7... or really, any other Windows. It is objectively the best Windows.

But what about my DOS games?! Also, Windows 95 had that sweet extra 3D shading.

Didn't 2000 have the same 3D shading and title bar gradients? I admit it has been a while.

For DOS games you use DOS. Boot floppies for the win. :P

--- In UTF-16, where available. ---
Posted on 20-01-13, 10:20 in I have yet to have never seen it all.
Custom title here

Post: #814 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Ahhhhh. I see it. Subtle difference, but it is there.

--- In UTF-16, where available. ---
Posted on 20-01-13, 16:22 in I have yet to have never seen it all.
Custom title here

Post: #815 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Windows 10 is nice. And doesn't require a 3D accelerator to display multiple 2D windows properly.

I don't even think the Win8 Start Screen was a fundamentally bad idea, though it definitely needed polish.
The Start Menu wvs garbage when it was new and isn't improving with age. And most complaints about the Start Screen can be summed up as "it isn't the same Start Menu we've been kludging fifes onto since 1995."

--- In UTF-16, where available. ---
Posted on 20-01-22, 06:27 in Monocultures in Linux and browsers (formerly "Windows 10") (revision 1)
Custom title here

Post: #816 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by tomman
First MS ruined the calculator, by replacing it with some Metro UWP webshit.

Now MS also is in the works to ensure your base OS install will ship with absolutely no usable applications:
https://news.slashdot.org/story/20/01/21/1614225/microsoft-is-testing-ads-in-wordpad-in-windows-10

Not that I care about Wordpad - if you need a texteditor for large files, there are plenty of them available, at several price tags. For Win32/64, portable editions included! And if you need to edit actual documents, LibreOffice is still free, if you don't want to contract herpes pirate pay for Office.
But still, why bother injecting ads in base OS accessories!?

I didn't knew Redmond, WA got relocated to Silly Valley, CA...


Who even uses Write Wordpad? It has long been this thing that was either not good enough or way too much, depending on what you were doing. There was once a time when it was the right tool for the job, but that hasn't been true for many years.


I'm not even dignifying Birdcock's ageism with a response.

--- In UTF-16, where available. ---
Custom title here

Post: #817 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Posted by sureanem

I'm not going to dignify the other millennial's brash personal attacks with a response.




--- In UTF-16, where available. ---
Custom title here

Post: #818 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
If you WANT to be a homicidal robot, that's your call.

--- In UTF-16, where available. ---
Posted on 20-01-23, 23:24 in FUCK hsts
Custom title here

Post: #819 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
HSTS is functioning as intended. The entire POINT of HSTS is that if there's an issue in the security, the exchange fails instead of providing a way to move forward insecurely.

Arguably, this is the way HTTPS should have been spec'ed from the beginning.

--- In UTF-16, where available. ---
Custom title here

Post: #820 of 1154
Since: 10-30-18

Last post: 4 days
Last view: 1 day
Boomers are of japanese make.

--- In UTF-16, where available. ---
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
    Main » CaptainJistuce » List of posts
    Get an ad blocker.