You build workspaces with vscode but the real magic is you never have to switch to visual studio or spend time configuring plugins for a new workspace each time you start a new project
You build workspaces with vscode but the real magic is you never have to switch to visual studio or spend time configuring plugins for a new workspace each time you start a new project
So you could generate lists of 1, 2, and 3 character code items rather than looking at index +1 or something.
What’s incoherent about the first one? Why is index bad beyond standards
In what world is
for (int index = 0; index < objectToIterate; index++)
{
// DO YO THANG
}
less coherent than
for (int i; i < objectToIterate; i++)
{
// DO YO THANG
}
Not that I’m aware of but that’s a condition where you’re thinking with an index. What’s the difference you’re looking for?
Big same. Long feels complex until you go back later
JavaScript, TypeScript, and C# babyyyy
Index can be useful but start looking for mapping and sorting functions. Or foreach. If you really must index, sure go use index or I if it’s conventionally understood. But reading something like for I in e where p == r.status is really taxing to make sense of
Why though? Intellisense helps you write out the full name. And instead of response why not call it whatever the data you’re expecting to be
Iter works better than I for clarity
Using single character variable names is always bad practice
My company and literally every company I’ve worked for somehow has been deeply afraid of leaving .NET framework for .NET core or .NET 6, 7, or 8.
I just want to get away from needing Windows to run my programs locally
I mean. Americans have shown they’ll work off hours, that’s not the issue. It’s generally that it’s expected to be compensated well and to make up the hour deficit elsewhere in the week if that happens
You could use proton cloud storage to do 90% of the same thing you just would have to have local editors installed
DRM also costs paying customers performance generally
It’s easier said than done for sure
For a lot of open source at the moment the root level readme is fundamentally the homepage too. It absolutely should include screenshots, maybe even a gif. If your software has a GUI or TUI it should follow that a concise visual will do more to explain it’s usage than a text document
Yeah but then I have to call them
I think pcsx 2 let’s you put a PS2 CD in and run it through the emulator