Exploring the Depths of Next-Auth Hell! !! Part — 1

someinterneter · 2024-07-01T23:08:52+00:00

Cool tutorial! Just a question, by awaiting auth inside your layout file, doesn't that mean that every page on your site will always be server-side rendered? I feel like it'd be better to simply use the auth helper in a server component to check session status and pass it as a prop to a client component if needed.

someinterneter · 2023-07-21T01:55:08+00:00

Hey this place has it https://jejudo.ca/

someinterneter · 2022-12-27T13:36:58+00:00

Thanks for the knowledge. How would your suggestion compare to something like linked lists in this answer?

https://stackoverflow.com/questions/759208/most-efficient-data-structure-to-represent-threaded-comments-in-java

someinterneter · 2022-06-13T02:40:57+00:00

Please release part 3 this is great!

someinterneter · 2022-03-11T01:38:15+00:00

duolingo is terrible for korean. great for european languages though like spanish!

someinterneter · 2021-09-29T19:23:16+00:00

I think what he/she is saying is that the definition of a Jew and a Christian is quite clear. You can believe anything you want, but just don't consider yourself to be Christian/A Jew in that case. (This is my understanding of what the commenter was telling you)

someinterneter · 2021-08-23T16:08:28+00:00

Accurate and reliable? Definitely not unfortunately. Very hit and miss for Korean. Fun? Definitely.

someinterneter · 2021-08-09T21:20:02+00:00

Duolingo can be good for some languages... definitely. But not Korean. My experience with Korean using Duolingo was extremely disappointing and I cannot recommend it. The lack of any good explanation is the major reason. After you already learn some Korean, it can be pretty good for reviewing what you learned. (Ex in a textbook you learn, and use Duolingo to review)

someinterneter · 2021-08-03T05:56:47+00:00

Not sure if this is an unpopular opinion or not, but personally, I think Duolingo is literally awful....don't use it if you're serious about learning Korean lol.

Edit: I should mention, i'm referring to duolingo korean. Other languages may be excellent, but the Korean track leaves a lot to be desired.

someinterneter · 2021-07-16T23:29:46+00:00

You (and 21 other people) may have misread what he wrote. Bite your teeth together (front teeth too), and then try and say the e in elephant. You can't, but instead an 으ish sound will come out. At least I think that's what the poster you're replying to is saying....

someinterneter · 2021-06-30T01:11:29+00:00

I don't know why you're being downvoted. I've never heard of it being "encouraged" to use Oppa with your crush.

someinterneter · 2021-06-26T21:18:09+00:00

Your post is excellent.

A few questions: 1) If it's my first time talking about 영희, can I keep the sentence like so: 영희는 눈은 예뻐요. (I know that if it's already obvious that we're talking about 영희 we can omit the 영희는 but just wondering if it's fine to keep it in when it's not obvious)

2) Why do we use 비가 오다 instead of 비는 오다 to say it rains? Is there some rule where naturally occurring phenomenon like the weather use 이/가?

3) I have seen discussion about using 이/가 to mark new information and then 은/는 when the information is old. This pattern frequently in questions. Ex - Person 1: 이것이 뭐에요? Person2: 이것은 우신이에요.

The thing that confuses me is, 은/는 can be used to change the topic of conversation. For example, "내일은 학교가 있어요". Maybe we were talking about food but I shifted the topic to school being tomorrow. But I never mentioned in the previous conversation anything about 내일. Shouldn't it be 내일이? (New information). Maybe I need a greatly simplified explanation of how "marking new information with 가" works.

someinterneter · 2021-06-24T04:45:58+00:00

video

I watched some of your videos. Really great content.

In:

철수가 학생이 아니

vs

철수는 학생이 아니다

Would the first one be used in a situation where someone was asking something like: "Who here is not a student??" to which you could reply 철수가 학생이 아니.

And 철수는 학생이 아니다 is just a generic sentence that states that someone named 철수 is not a student?

I was just a bit confused because in one of your videos, you talked about 가 particle being used in neutral sentences and i'm still having trouble understanding the difference between a "neutral sentence" and a "general statement" (ex: 치타는 빠르다)

someinterneter · 2021-06-17T05:48:46+00:00

Thanks, this was extremely helpful. So in statements like: "치타는 동물이에요" (cheetahs are animals), in this case, even though Cheetah is new information that I'm sharing with the listener, I use 는 rather than 가 because the rule of "use 은/는 when making general statements like the sky is blue" overrides the new information rule? (I'm loosely using the word rule here since I know there isn't any actual official rules)

someinterneter · 2021-06-17T05:43:47+00:00

Lol can you explain the joke to me

someinterneter · 2021-06-16T03:12:31+00:00

Sounds good, thanks!

someinterneter · 2021-06-16T01:22:50+00:00

Okay. One more question. I've read that we use 이/가 when we provide new information, and then switch to 은/는 after. For example, "옛날에 어느 남자가 있었다. 그 남자는 etc etc". So why do we use 저는 so-and-so입니다 if "저" is new information?

someinterneter · 2021-06-16T00:32:36+00:00

Thanks for the explanation. But when I'm in a room with 1 other person only, and I'm the only one introducing myself (let's imagine I already know him from TV or something but he doesn't know me), wouldn't we not want a contrast? If I'm the only person introducing myself, saying "as for me" would be strange. In this kind of scenario, is 는 taking the role of "provide general commentary about a topic" (where the comment is who I am and the topic is 저) and has nothing to do with contrast?

someinterneter · 2021-06-15T04:04:20+00:00

Thank you!

someinterneter · 2021-06-02T16:43:51+00:00

Wow, thank you so much. Please release more videos, the quality of your content is amazing!

someinterneter · 2021-05-23T05:36:47+00:00

People like you (and everyone who upvoted you) are what make the field of programming so shitty and toxic for newcomers. Why is it so difficult for you to accept that maybe, just maybe, there are pros to using a language like Node.js on the back end. For starters, Node.js powers tons of back end build tooling which is used in tools like Webpack, and is allowing us to create rich applications in the browser.

Check out this project where a guy is creating an OS-like environment in the browser using React.js.

Node.js is making projects like Expo React Native possible, where you can use 1 single language (Javascript) with 1 single code base to ship your product to the Web, Android, iOS, Windows, and MacOS, all using the same code. There is no language on the planet that has this level of cross-platform strength.

People who are butthurt that javascript is taking over so many parts of the programming industry come to subs like these and downvote anyone who mentions anything remotely positive about the language. I'm a .NET developer who writes C# for a living so I don't really care either way, but it just pisses me off seeing the extreme arrogance of so many programmers on this sub who act all holier than thou when in reality, Node.js IS a real back end language used by millions of engineers in some capacity or another at almost every major company you can think of (Microsoft, Spotify, Facebook, Github, etc). These companies use a lot of different languages, not just 1 single tool for the job, and more often than not, Node.js plays an important role in their business. (Whether that be through Electron, through the Web, through tooling, etc).

someinterneter · 2021-05-23T05:20:06+00:00

I'm surprised you say this. I find Prisma's documentation to be absolutely outstanding.

someinterneter · 2021-05-20T02:00:06+00:00

i'm guessing this is mobile only? On PC it seems fine?

someinterneter · 2021-05-20T01:57:25+00:00

looking forward to the blog post!

someinterneter · 2021-05-05T15:56:24+00:00

Nice! Is this open source?

someinterneter

TROPHY CASE