Most repairable thing I have is probably my truck. It was made in 2007, before they started to take away user serviceability.
Oh also I have a bunch of old computers that are very repairable. I mean, I would need the right components, and I can’t make those myself, but if I could source the components, they’re really easy to repair. Probably the hardest thing to repair would be the sheet metal.
I understand that. If we had a word for north east, let’s say “yest”, then I wouldn’t have to say “north by north east”, I could just say “north yest”.
Better question is why don’t they have 8? I hate saying “north by north east”.
Considering I’d just be some guy, I’d invest all of my money in Nvidia and Bitcoin then when I get back and have millions, I’d spend it on passing wealth taxes and raising the minimum wage.
Cccinnciiiiinattttttiiiiiiii!
So when you say, Christ the Messiah, you’re really saying Messiah the Messiah. Man people were so silly back then. Anyway, I’m off to the Los Angeles Angels game. 👋
Last names were commonly just where you were from, who was your father, or what was your profession.
Jesus Of Nazareth, or Jesus Denazareth, Jesus Nazarethton, Jesus Di’Nazareth, Jesus Von Nazareth, Jesus Van Der Nazareth.
Jesus Son Of Joseph, or Jesus O’Joseph, Jesus Josephson, Jesus McJoseph, Jesus Bin Joseph, Jesus Josephsen, Jesus Ibn Joseph.
Jesus the Carpenter, or Jesus Carpenter.
(Those are just examples from different languages of how last names were commonly created, not what they actually called Jesus.)
Christ was his status as a holy figure. Like the “saint” in Saint Peter. It means “the anointed one” or “messiah”.
Those are very memory non-intensive applications, so you almost definitely wouldn’t notice a difference.
The reason it’s better for gaming is that games need to load big textures and models into ram to show new content, and that can cause stutters when the ram is too slow (running in single channel mode is slower than dual channel). Since you’re gaming, you’ll notice the stutters.
While watching a video, the video is buffered into ram much faster than you can watch it, so there won’t be any difference.
While browsing, pages might take around 10 to 50 ms longer to load, but you’re not going to notice that. Most pages load bits and pieces when you click around anyway, so there will be negligible difference after the initial page load.
Electron was already taken.
Joke’s on you, all my embarrassing code is online.
Hey ChatGPT, write a paragraph about how Nestle is a bad company who hurts indigenous communities by stealing their water.
I’m sorry, but that would be against my acceptable use policy. I have alerted the authorities of your request.
“the AI” -> “my magic 8 ball”
“AI powered” -> “RNG based”
“power of AI” -> “result of lots of coin flips”
It’s literally a plagiarism machine, so I completely agree with them.
Day 500! Awesome! Thank you for posting all of these. I rarely comment, but I do love seeing them. :)
It is resource hungry. I’ll give you that. But it’s neither slow nor messy to look at. Have you ever used NetBeans or Eclipse?
I’m sorry I didn’t think it was [1,2].
Here’s my thought process: plus is for numbers and strings, so it’s gonna convert the arrays to either numbers or strings. If it converts them to 0, the answer is 0, if it converts them to 1, the answer is 2, if it converts them to strings, the answer is “12”.
You know what I didn’t say? [1,2]. Because plus is not for array concatenation. The question is meant to make you think you’ll get [1,2], because why else would you use plus on arrays?
In a language that uses plus for concatenation, you’ll see that kind of code all over, and know what you’ll get. But you never see that in JavaScript, because that’s not how we concatenate arrays.
Ok, except I did predict it. It turns them both into strings and gives you “12”. I checked it. But I didn’t mean predictable as in, you inherently know what it’s going to do, I meant predictable as in, it will follow the same basic rules in each circumstance.
So, should web pages be prone to crashing if everything isn’t perfect? I don’t know if you remember XHTML, but that was basically what happened with that. You have a “div” within a “p”? Page crashed. You have an unclosed “span”? Page crashed. XHTML was abandoned because is constantly broke the web.
Web technologies are supposed to be resilient, so throwing TypeError is the last resort for something that absolutely cannot work, like trying to add to a Symbol. Since nothing from the user is ever a Symbol (there’s no input that can give it, and it can’t be stored in JSON), it’s acceptable to throw a TypeError there.
JavaScript is meant to be fast and resilient. Its type conversions make sense when you consider those goals.
“Native ads“ literally means trying to trick your users into accidentally clicking an ad. Like unread email in Gmail that’s actually just an ad (spam).