my team was driving me insane with leaving console.log("here") all over the place in every pr, so now we have a "no console.log" eslint rule in ci.
I guess my answer is it depends on your team. good logs are different, but imo if they're just debugging statements they shouldn't even make it into the repo let alone prod.
if it's just you, do whatever you want lol, performance is almost certainly not significant and most users should end up ignoring them anyway
it legitimately is a neutral network, I'm not sure what you're trying to say here. https://en.wikipedia.org/wiki/Generative_pre-trained_transformer
they are the first thing that comes up when searching "cursor" in both ddg and google, so I think they're doing ok
idk if 2 users is fair, it may just be my circles but I see nixos mentioned more than almost anything else on lemmy/hn/etc in the past couple years
not sure what you're talking about but there's two things here.
TRAMP is great and you can run the lsp on the remote machine without installing anything assuming the linters and lsp are already installed. for comparison, vscode remote downloads and runs a shim thing when you connect.
I use doom emacs at work for large codebases all the time and haven't run into any problems. why does it only work for really small projects?
plenty of package managers have.
flatpak doesn't require any admin to install a new app
nixos doesn't run any code at all on your machine for just adding a package assuming it's already been cached. if it hasn't been cached it's run in a sandbox. the cases other package managers use post install configuration scripts for are a different mechanism which possibly has root access depending on what it is.
yeah there isn't really a general purpose react way to do that.
if order didn't matter then you could just have a Header component that registers itself in a context but there's no way to know where each component is relative to its siblings.
the other way is to break out of react and just walk the dom. pass a ref to your component and use that as the root to walk. only works assuming normal react dom renderer and no portals.
you can combine those two options too, use context for registration so you can attach extra info, then dom for position.
there are some libs that let you walk a component tree, but they're all focused on ssr and idk how they work in a browser. wouldn't go this route for anything prod.
last option is just store your content as data. have md/mdx/json/whatever files that are the content for your page, then as you parse them build up the tree. probably the most robust if it fits your use case. if you use MDX it seems like they already have some solutions
there's sort of ways to achieve this but none of them good react. what's the actual goal?
yeah that should just be a pip package instead, then install it any normal way
the social pressure of other kids
gitea has had some organizational problems so a lot of people have been using forgejo instead, which is just a community fork of gitea plus some more features