yeah, you're right.

I like how peoples start to downvote me :)

But the joke is in that OP should use

if (result.recordset.length) {
  // do stuff...
} else {
  // don't do stuff ...
}

instead of creating separate function that returns true/false depending on if the array is empty.

This thread about !! and Boolean() does not make any sense from the very beginning.

Thanks!

bhaah return Boolean(result.recordset.length)

why not return result.recordset.length ? 0 is falsy value, and any other number is truthful.

Thank man. I didn't know about mutex. Now at least I can google and find more information about it.

Wow, I didn't think that someone could be hurt by a simple joke.

Welp, 10 minutes and 0 responses. And I thought that Rust developers were blazingly fast.

Yeah, functional programming goes brrr....

var ex is stores HTMLElement, not a word. You cant perworm replaceAll method to HTMLElemtn directly. Instead you want to apply that method to ex.innerText.

upd: Fixed code will be looking something like that

<div id="e111">"I'm kindly asking for HELP from kind helpful Redditors."</div>
<script>
  const element = document.getElementById("e111");
  const regex = /(HELP|help)/gi;
  element.innerText = element.innerText.replaceAll(regex, "[...]");
</script>

Looking at inconsistency in your code, I can almost guarantee that you stole parsers from someone else project. Like, using 6 space tabs instead of 4 spaces for indents...

Anyway, good job. But this tool is redundant. JSON is 1to1 representation of JS object/arrays. There is no needs in another parser on top of JSON parser. It would be more interesting to see if you made a similar library for a programming language that does not have a built-in JSON parser, for example C, Rust, C++, Go...

Cool. But how it's differs from just asking chatGPT or any other LLM?

Here is detailed guide. https://dev.to/rashidshamloo/deploying-vite-react-app-to-github-pages-35hf

There is library called gh-pages that helps for deployment vite apps on GitHub pages.

In short, you need to install this library, in the vite.contig.js you need to add this line before plugins: [react()],

base: "./YOUR_REPOSITORY_NAME",

Then simply build your project into dist folder and run command gh-pages -d dist.

Thank you man for the explanation. I'm going to reconsider how I handle Maps on my application.

Lol, you can't debug browser JavaScript code in IDE. You either should use node.js or simply use console.log for printing and debugger keyword for stopping execution of your code in browser and manually check every statement.

https://www.w3schools.com/js/js_debugging.asp

Assuming you're using node.js, here is guide for debugging: https://nodejs.org/en/learn/getting-started/debugging

If you already using PyCharm you may be interested in WebStorm - it's an IDE for javascript and frontend development overall made by same company.

VS Code is amazing, but it require configuration and bloating with extensions for comfortable work. I still prefer VS Code over any JetBrains IDE, though.

I heard about Konva.js library, simmilar to THREE.js but focused on 2d rendering aspect. But I never used it, because with 2d I prefer to use native canvas API.

And what benefit would that yield?

Managing 1001 arrays is worse that single but huge Map.

With arrays, you need to make two lookups: find element by x axis, then find element by y axis. In my experience with canvas, this method of looping is slower. If the order of rendering elements does not matter, then a map will be a bit faster. And you can add/delete rows/columns of the grid without problem, unlike an array.

In fact, the overhead you produce with your map is by a 100% magnitude worse than directly using nested loops.

It is interesting to hear what overheads are here?

^ this is correct answer

the other option is jQuery

What do you make the grid out of? Is this a div? table? canvas?

As a general rule, you should handle the size and position of elements to render only those that are currently in the viewport.

Something like that (this is example)

  isInViewport(camera: IViewport, canvas: ICanvas): boolean {
    const left = this.x + this.width + camera.left >= canvas.x;
    const right = this.x + camera.left <= canvas.width;
    const top = this.y + this.height + camera.top >= canvas.y;
    const bottom = this.y + camera.top <= canvas.height;
    return top && right && bottom && left;
  }

This code is for handling rendering on the canvas. But I'm sure you can adapt it for your needs.

upd:

As for rendering you can create a grid using double loop, and set it into a Map. Just make keys as `${x}-${y}`. Then you can loop over a map in single go to render all elements .

const elements = new Map<string, IElement>();    
elements.forEach((item) => {
  if (item.isInViewport(camera)) item.render(camera);
});

You probably want to use THREE.js for rendering 2d/3d animation on canvas.

JavaScript/TypeScript is the only option you need to make your game and for making queries to the backend. You can add React/Vue framework on top of your game to handle UI elements, such as registration/login and handling forms.

On backend you can use any language. Some are easier, some are harder but more performant. Python/Node.js is fine for quick prototyping. When you form your idea and make more or less stable API, you can rewrite it into Java or Go to handle more users.

For database, SQLite/MySQL/PostgreSQL are common option: very stable, very fast databases with good scalability.

Dude, don't expect that you send entire codebase and someone spends his time trying to understand how it works.

Write where exactly you think there is a problem. And what have you already tried to fix it?