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?
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?
By the end of the meeting you have 10 more questions and no answers and more meetings to discuss the new questions
If I understand it correctly it’s basically community to community federation, so when you subscribe to a community it also pushes other community posts it follows to your subscribed feed. Those posts would still show up as those other communities. A community becomes not just a place to post, but also as a curator that vouches for other communities as well. You could even potentially have a curate only community like a lemmy best community list to get newbies started, or category level communities.
I try and follow best practices always too, but when the linter is catching it for you it’s less to think about so you can focus on the important parts of the problem
Sure, in this case it was rich idiots spending millions, they’re only upset that they missed the opportunity to pawn it off to another idiot first
Even still, they take 30% of a studio’s revenue which is a ridiculous amount that’s only possible through a near monopoly
Typescript compiler enforces language requirements, the linter enforces language best practices. Best practices help you avoid bugs.
Same reason you use typescript. It helps you catch bugs and follow programming best practices. You also don’t need typescript, but with it your code is better. Typescript is technically just a really fancy linter. The actual compilation mainly just removes the type data and does some JavaScript engine compatibility.
Why do the typescript extensions to eslint exist then?
The benefit is that you could have a distributed marketplace. Instead of having monopolies like steam where one company accumulates a bunch of power they can abuse you could have multiple small companies band together to support a common standard of ownership so you could buy from any company and all the companies supporting the standard would respect it. You could also tie it to a legal contract so it’s actually enforceable.
Of course you could just do that with an centralized standard that’s backed by multiple companies too.
NFT buyers were also scammers since their intention was to sell it off to the next patsy
They weren’t even uniquely drawn, they just mr potato head combined a handful of components
And eslint and setting up tsconfig for your project structure.
They probably spent a year looking for a job and they’re suffering from imposter syndrome so they feel like if they aren’t constantly getting stuff done they might be fired, plus they haven’t worked enough to hit burnout and don’t know how to pace themselves.
Maybe there’s some edge case but in my years of using prettier I haven’t encountered one once.
It adds even more auto formatting rules so you can basically stop thinking about formatting entirely. I used to be opinionated about formatting but now I just go with whatever prettier does. It’s not always the best but it’s consistent and it’s a big chunk of my brain I can free up for things that matter. It also formats things safely so you don’t run into those weird edge cases where semicolons matter if you choose to turn them off.
I’ll add that to my mountain of reasons for using typescript
After switching to typescript with linting and prettier I simply hate writing vanilla JavaScript anymore. Some people complain about the extra project setup needed but I find that time pays for itself immediately.
I wouldn’t do it without an auto formatter. With prettier it will catch potential no semi colon issues.
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…