logo Sign In

yhwx

User Group
Members
Join date
23-May-2016
Last activity
9-Jun-2023
Posts
6,256

Post History

Post
#988072
Topic
Random Thoughts
Time

dahmage said:

yhwx said:

dahmage said:

yhwx said:

dahmage said:

yhwx said:

TV’s Frink said:

yhwx said:

The infinite-repeatedness of GIFs sometimes drives me insane.

Try looking at it on a MAC. It will break much sooner so you won’t have to watch it any more.

Seven. Years.

boring.

that’s how old my win7 laptop that i use at work is, but the difference is, i can buy any damn SSD drive i want and put it in.

Could still do that with this old a Mac.

But now SSDs come pre-installed on all laptops and are faster PCIe models. Checkmate.

false. i will leave it up to you to research.

http://guides.crucial.com/Guide/MacBook+Pro+13-Inch+Unibody+Mid+2010+SSD+Installation/411

http://www.apple.com/macbook-pro/specs-retina/

Checkmate.

stop saying checkmate

you are providing wrong articles as they don’t relate to what i was saying.

What you were saying wasn’t clear. You didn’t even explain what the hell you were talking about, leaving it up to me to figure it out.

but it turns out i am out of date in my info, osx 10.10.4 or later allows 3rd party ssd again it seems:
https://arstechnica.com/civis/viewtopic.php?f=19&t=1291757

Mac OS has never disallowed SSDs, they’ve just disallowed the use of TRIM for 3rd party SSDs. TRIM is a cleaning system for SSDs, which can get easily bloated. (It’s complicated) It was disabled for safety reasons.

Post
#988068
Topic
Random Thoughts
Time

dahmage said:

yhwx said:

dahmage said:

yhwx said:

TV’s Frink said:

yhwx said:

The infinite-repeatedness of GIFs sometimes drives me insane.

Try looking at it on a MAC. It will break much sooner so you won’t have to watch it any more.

Seven. Years.

boring.

that’s how old my win7 laptop that i use at work is, but the difference is, i can buy any damn SSD drive i want and put it in.

Could still do that with this old a Mac.

But now SSDs come pre-installed on all laptops and are faster PCIe models. Checkmate.

false. i will leave it up to you to research.

http://guides.crucial.com/Guide/MacBook+Pro+13-Inch+Unibody+Mid+2010+SSD+Installation/411

http://www.apple.com/macbook-pro/specs-retina/

Checkmate.

Post
#988064
Topic
Random Thoughts
Time

dahmage said:

yhwx said:

TV’s Frink said:

yhwx said:

The infinite-repeatedness of GIFs sometimes drives me insane.

Try looking at it on a MAC. It will break much sooner so you won’t have to watch it any more.

Seven. Years.

boring.

that’s how old my win7 laptop that i use at work is, but the difference is, i can buy any damn SSD drive i want and put it in.

Could still do that with this old a Mac.

But now SSDs come pre-installed on all laptops and are faster PCIe models. Checkmate.

Post
#988032
Topic
Last movie seen
Time

A part of Star Wars that does feel dated is how there’s no real cross-galaxy instant communication. While Star Wars does have a lot of advanced technology, it takes a lot of time for information to get around. It almost feels like the world a couple of centuries ago: We did have newspapers and such, but there was no Internet, or even television. Everybody lived in a village.

Post
#988004
Topic
The Say Something Nice About Another Poster Thread
Time

TV’s Frink said:

yhwx said:

Possessed said:

  1. That could have easily been one post

True.

and 2. Neither of those posts say anything.

They do. The first one was about my disagreement that my posts in those threads are a old man yells at cloud feeling. Now, maybe I could have added what I think it was, but that doesn’t make the core purpose of the post invalid.

Now, for the second post, you could have more of an argument. However, it still says something. It gives away a feeling of confused thanks for being supposedly bad, as accused by you, in one area, but not in a more severe area. It might have not totally necessary to post, but it still had a purpose.

This post didn’t say anything.

Yes, it did. It mainly explained my feeling of disagreement with Possessed, and reasons for that disagreement.

Post
#988000
Topic
The Say Something Nice About Another Poster Thread
Time

Possessed said:

  1. That could have easily been one post

True.

and 2. Neither of those posts say anything.

They do. The first one was about my disagreement that my posts in those threads are a old man yells at cloud feeling. Now, maybe I could have added what I think it was, but that doesn’t make the core purpose of the post invalid.

Now, for the second post, you could have more of an argument. However, it still says something. It gives away a feeling of confused thanks for being supposedly bad, as accused by you, in one area, but not in a more severe area. It might have not totally necessary to post, but it still had a purpose.

Post
#987849
Topic
MAC or PC
Time

DuracellEnergizer said:

yhwx said:

Desree said:

So, did YHWX ever explain why file types extensions in file names are wrong? Other than he doesn’t personally like them, I mean. Something was said about how it was wrong on a technical level, but I never really saw anything that explained why. Just curious.

File name extensions are wrong on a principled (and technical, as well) level:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Hopefully I’ll get to discuss why file name extensions are stupid.

I think you’re confused on the meaning of “hopefully.”

It’s really interesting, I promise.

Sounds fishy.

Back in the day, Macs had a unique way to identify file types: Type/Creator codes. In the resource fork of a file, the OS would store the type of file (basically the file name extension) and the creator of the file (the application you used to create the file). This system has many advantages, including the most important one (to me, at least): You can name the file whatever you want, and it’ll still open correctly.

The impossibility of this is what makes file name extensions terrible: You can’t give the user control of their data. Coding the file type in the file name is a fundamentally bad idea. Would you put the date created in the file name? Size? Metadata? You’d probably say no. These are all file metadata that are as important as the file type. But, no, file type is a-ok because that’s how it’s always been outside of the Mac world! That’s just how things are, isn’t it?

It is, but it doesn’t have to be this way.

Apple solved the problem again eleven years ago with Uniform Type Identifiers. This system has solves many major problems with type/creator codes, file name extensions, and MIME types. It first solves specificity problems: Type/Creator codes are limited to four characters, which is small enough to have collisions with other file types. (This is also a problem with file name extensions, as file name extensions can theoretically be as long as possible, Microsoft & Co. refuse to break from the EIGHT.THREE file naming convention of yesteryear) It also doesn’t need a registration with a standards committee, which is a problem with MIME types. There’s also many more benefits and intricacies to Uniform Type Identifiers, which you’ll have to see the link I linked above to get all the juicy details on.

Now, Apple has been far from perfect in this arena. Back around the transition from Classic Mac OS to Mac OS X (Windows users: Think of the transition from Windows 9x to XP, but much bigger), Apple basically abandoned Type/Creator codes, making file name extensions the required form of file type identification. This lasts until today, which many Apple users (such as myself) are grumbly about. (Along with the lack of a new file system — but that’s on the way!)

Also: http://arstechnica.com/apple/2005/04/macosx-10-4/11/

I guess I can’t blame you.