ehhhh I disagree. I definitely cringe when I hear a hipster who's lived here for 2 years try to inject jawn into every conversation. Feels very forced. Also Jawn being put on pins and shirts is also very cringe to me
> when I hear a hipster who's lived here for 2 years try to inject jawn into every conversation. Feels very forced.
Same thing happens with "y'all", even though it's nowhere close to being as esoteric/regional. A couple years ago, Twitter seemed to have become obsessed with incorporating it conspicuously into every other tweet. I didn't even know "y'all" had rules until that happened. (I couldn't really tell you what those rules are, but it was popping up in places that were so syntactically awkward, by people who were clearly not "y'all" natives. So they definitely exist.)
I love ya'll because second person plural is something that English annoying lacks.
I'm also a fan of habitual be because it's something that can be expressed in English, but it sounds verbose or relies on context whereas "I be" is self explanatory without any context -you know that the speakers means "I regularly do/feel ___ "
My favorite phrase puts them together: "ya'll be trippin" is IMO the most efficient way in the English language to tell a group of people that their behavior is unacceptable.
On the one hand "yous" fills this void in a way that is more consistent with the rules of pluralizing words, but on the other hand it also introduces a homophone with "use" which could hypothetically lead to confusion. So which is worse, inconsistency (y'all) or ambiguity (yous)?
Ultimately, since "yous" never fits in the same grammatical slot as "use" (different part of speech), there's never any real chance at confusion anyway. Therefore I weigh in on the side of "yous".
Once again New York has it right and the rest of yous be trippin.
Sentences that end with a y’all still come across as distinctly Southern. Sentences that begin with y’all, on the other hand, sound normal or dare I say even hip. To me that is.
"I definitely cringe" and "Also ... is also ... very cringe to me"
You certainly get plenty of mileage out of the word cringe. Is it a verb, is it an adjective - who knows? Your also ... also construct riffs on "either ... or", "both ... and" and the like. There must be a name for terms like that - you get them in Latin too so they've been around for a while eg nec ... necque (neither ... nor).
Jawn is just a colloquialism but I've seen also ... also several times before now. I've also seen very cringe too.
I am not taking the piss but I feel that I am watching language evolve right in front of me. I suspect that whilst this article and set of threads gets itself all whizzed up over jawn, it is missing the rather bigger point about language and conversations that travel at the speed of light instead of just sound and is distributed by the internet and not just the post office.
On HN we pontificators have an audience that a Roman Imperator could only dream of.
you'd have to be blind and deaf not to notice that gradual downhill slide of popular vocabulary. It may have been said with a bit more grace, but they're not wrong either.
"Gee, 20% of this paragraph is the same word, perhaps it would serve me well to mix it up."
Yeah. I feel like there's two types of people that actually use jawn: those that are very Philly and those that are trying, really, really hard to sound Philly. I can't say I've said jawn with a straight face since I was a little kid.
For Boston/Mass it's "wicked." You can tell when someone injects it naturally and they grew up with its various contexts, or you're a new transplant and it's usually used in every other sentence.
I was the latter circa 2012 but ~8 years in Boston tempered my use, haha.
I live in Philadelphia, commute was still 45min-1hr. Would either have to walk 15 min to the El, stay on its for about 25-30min, then walk another 15ish min to my office. Or take a trolley to 30th street then transfer to the El then walk.
When I moved to a different neighborhood, I'd take Regional Rail, which was about 40 mins door to door. Only advantage is there aren't people shooting up or getting raped on RR.
Driving actually would only take ~15min door to door if I left after rush hour. But then parking was very variable. It could be instant (finding spot right when I get there) or I'd have to drive around for 10 minutes.
Honestly, I liked commuting either of those ways (outside of finding needles on the El) since I'd just listen to music or a podcast.
There's artists building the game experience and CS people building the game technology.
The latter do use and reuse smaller software components to build the level editors, scripting interfaces, particle physics, path-finding, illumination, etc. The engine. This job is very much like other fields of software development, not actually behind.
The first might write code (e.g. scripting), but they are generally doing so in a restricted 'monolithic' environment provided to make their job easier. They do not have to build the technology, they can just direct it, if that makes sense. Their job isn't typical software development, more content development, thus it seems a bit alien, behind from a software developer's perspective.
Game Design and programming are two completely different sets of abilities.
Programmers can design a game, and game designers can do some programming, of course. But in modern days, the core way that both professionals interact with engine editors is completely different.
Game Design in general is closer to art or being director than to programming.
Hi are you me? I've been on literally several hundred flights in my life, starting at age 4. Then at 16 I had a panic attack before getting on a flight. So each new flight after that was always prefaced with this anxiety of having another attack.
It was like that for a few years, then I had a panic attack on a flight. But I still flew for a few years after that, usually just a couple times a year. I don't recall the last flight I took, but it's been a couple years. Maybe it was cross country from Philadelphia to San Francisco, so a fairly long flight.
I've since been taking Amtrak, which I FUCKING love. Outside of not having all the anxiety of the flight, going on a long train trip is the highlight of my year and hands down best sleep I get. Watching the scenery slowly change as I do work, play games, or just relax is one of my favorite things now. It's even better if I'm able to get my own private room. Now its not glamorous, but having your own toilet and bed really makes a huge difference.
Hopefully in the future I can start flying again if I HAVE to. But I don't think I'll ever stop taking the train if the timing is right for wherever I'm going.
The criticism may be justified but jeez the person who wrote that comes off like a HUGE asshole. Reminds me of people I've worked with in the past who think they know everything and have an arrogance so thick you could cut it with a knife.
Every Lisp programmer I've ever met is like this. I don't know why, but it's probably Erik Naggum's fault. They used to be called "Lisp weenies" and now would be called "abusers".
(The Clojure and Racket people are supposedly nice.)
I've seen Erik Naggum's name mentioned in this context before, but years ago I looked through a bunch of his contribution on comp.lang.lisp and couldn't see anything justifying this reputation. His articles rather looked quite eloquent and thought-through. Could you provide an example?
I just re-read Xah's notes and all of that rings a bell, but off of comp.lang.lisp Erik could be incredibly kind in helping other programmers. I was working my way through an early edition of _A programmer's guide to Common Lisp_ by Deborah Tatar and got absolutely stumped on the chapter on macros. Erik worked with me over email until we actually found what appeared to be a typo in the example source code and was incredibly patient with my dumb mistakes.
I've accessed that wiki.c2 for various discussions about programming before. However, I get confused with the format, specially here where it seems like a thread full of comments (no mention of usernames) there. (I like the relative minimalism and simplicity of the discourse though)
"God help you if you are going to write your first interpreter in C of all things... Without manual intervention[,] C programs do pretty much no error detection... I hate C with a passion." -- Hayley Patton, Don't Build Your Own Lisp
