They should be related to a #language#technology task, able to be automatically evaluated, with training and test #data able to be distributed to participants at low- or no-cost, and should be fun!
Is there a concept in #programming for whether an #API is inward or outward? For example, suppose I have an interface whose intention is that other code can implement it, but it's only supposed to be called by the internals of my code: it's public for implementation, but internal for callers.
I'm doing some monitor shopping and am looking for recs. I do #programming, so I look at code and browsers all day. Priority is for screen real estate and text sharpness. There's a budget, but it's sizeable enough to not be a (big) factor here.
@xavdid I have the LG version of that 40” Dell ultrawide. I like it pretty well, though the pixel density is still not ideal for use with Apple. I find myself wishing I had the 5k2k resolution in a 34” or 38” ultrawide instead. It’s also silly expensive. Text is good on it, but still not “Apple good”. It rules for doing video and audio editing though (anything with a horizontal timeline). Also I’ve liked running D&D from it.
@xavdid That 27” Apple display is gorgeous, but a single 27” screen may feel too limiting. I also hate the stupid non-removable cord situation and that you have to pick a stand type at purchase time and can’t self-serve a change to a vesa mount.
What I really want Apple to make is a Retina ultrawide, probably in the 34-38” range.
Lukewarm take: every supposedly simple solution to a #programming problem just means you’re pushing the complexity somewhere else. There are no simple solutions to complex problems.
@virtulis I’ve never really understood what node-gyp actually is or why I need to care about it, just that it occasionally pops up in build error messages and when I see it I get irrationally angry.
@davidbisset one thing i found that can convince a lot of developers to stop doing those one liners "because its fewer vars and faster" is if the language can stop being compiled at an assembly stage.
the compilers of most languages will end up making ::temp# variables to assign the results of each call to, ergo being the same as if you had declared them yourself.
Why use chat-to.dev compared to other technologies
It's better than stack overflow because you can have a conversation if you need help instead of having a long comment thread. It's better than IRC because the feed exists even when you're not online, without you having to create an inbox bot. It's better than discord because discord is a ball. And it's better than language-specific forums because sometimes you just have a general question that isn't framework/lang specific. So don't waste time and register now and have fun programming. https://chat-to.dev