Why was this written like this? It makes no sense. I’ll git blame it and ask them what’s going on. Oh it’s me…

Isn’t new York flooded right now?

I just peeked at the docs and right off the bat I don’t like how they have conflicting attributes like hx-get and hx-post. What happens if both are set at the same time? Why not just have hx-method?

Because it’s the country the company is based in.

By the end of the meeting you have 10 more questions and no answers and more meetings to discuss the new questions

“we organized to all quit at the same time”

“Noooooo! Not like that! 😭😭😭”

Thanks! This is a super helpful answer!

Can you be more specific? I’d like to know what it’s missing.

Getting over it?

Yes, it’s still a transpiler, I’m not saying it isn’t, but what I mean is that it doesn’t add any functionally specific to the typescript language. There’s a transpiler for TS that doesn’t even do any type checking at all and just does the type stripping and back porting. But of course, that’s not why people use typescript. All the features that are actually important to typescript could be done through a linter instead. If type annotations were added to JavaScript you could get most of typescript’s features with linting rules and just handle back porting in a more standard way.

It’s basically a book you can talk to. A book can contain incredibly knowledge, but it’s a preserve artifact of intelligence, not intelligence.

Learn to make your own, then sell them on Etsy, wait, oh no!

It can be overkill if you need something simple that doesn’t match next’s defaults, but if the default settings of next work for your use case I found the base project setup very simple to use.

Have you tried using an auto formatter? Let’s you write code however and fixes the structure automatically on save. It’s way easier for me to write curly braces then hit ctrl+s than have to select multiple lines manually and tab in and out. I feel the biggest gains I’ve made in productivity came after I learned to embrace tooling.

I was taught java my first semester. I certainly hope no schools teach dynamic languages in the first semester.

To be perfectly frank, I’ve only seen the drama on social media platforms. Outside of this one library Ive hardly seen anyone trying to fight typescript in the professional community.

deleted by creator

I view it more like a powered exoskeleton around a blob fish. IMO static typing is way more valuable than strong typing and I’d take static typing only over strong typing any day if I can only choose one.

I don’t see any practical use case for it as is as anyone wanting to use them would want the full TS feature set anyways, but I could see it being a good step forward for more meaningful features to be added in the future.

Curious if you’ve used next with react. React itself has a scope rendering design goal and leaves the rest of the app to the community, and next sets up all the stuff around it for you and I think they did a really great job with the defaults they close, and it’s still fully extendable.