enough | How strange it is to be anything | Runtime Evironment library

I have the wackiest bug. Like....the wackiest! If any of ya'll want to put eyes on this, awesomesauce! I really appriciate it! I am creating a survey with REACT, Redux, SQL, HML, Material-ui, and CSS.

I've created a graph of information with am4charts using data from a database. Everything is working and will show up on the page......but not on page load. What I am seeing in my console is that the page will load, it fires off my get request but doesn't return with the data fast enough (I think). By the time that the get request loads, my graph has populated with no data.

Here is the code that I have for the page that I am rendering. What is really odd is that, once my code has run, I can cut a line of code (I've been using a console log). And then the graph will render and load.

I'm a student learning about database design and currently learning about the relationships of - one-to-one, one-to-many, many-to-many. I understand the concept well enough, but feel like I'm lacking experience/information on how it would be implemented in a real production scenario.

My question is this

If I have a blog website with a Blog Post as an entity and comments for each blog post, how would you handle the comments in the database?`

Would you use a one-to-many relationship and just store all the comments in a single table. Then link those comments to each blog post and user who created it?

What if each comment had a sub-comment? Would you create a separate table for sub-comments and link it to a single comment? Would that cause too much overhead and confusion within the DB itself?

I get the concepts and all, but don't understand best practices for handling what seems like basic stuff.

Thanks in advance!

When a divide-and-conquer recursive function doesn't yield runtimes low enough, which other improvements could be done?

Let's say, for example, this power function taken from here:

I have a given, unmodifiable table design which resembles:

I implemented an xsd scanner, which creates an targetNamespace= catalog. Includes are filtered, so the catalog has only the root files of the targetNamespace. With this catalog I'm resolving the required files (using a LSResourceResolver) to validate incoming xml files.

Map

I got another little question...

I want to make multiple variables which I create with 'setattr'

That works quite fine. It creates these variables:

Take the following build.xml snippet:

I am trying to sort the values of my columns depending on the date (d/m/y + hour: min: sec). Below I will show you an example of the format of the given data:

I have spent some hours playing with Electron and I have observed that it consistently takes more than 2.5 seconds to draw a trivial html file to the screen. The timeline is roughly as follows:

• 60 ms: app ready event is triggered; we create a window using new BrowserWindow()
• 170 ms: a blank window appears on the screen
• 2800 ms: the window shows the specified HTML

I have set up a repository with my code, which is derived from Electron's quick start docs.

Regarding my machine, I am running Windows 10 on a ThinkPad T460 from 2016 with a SSD and enough memory.

Shipping an application that shows a blank window for so long upon startup is a no-go for me. I assume most people developing Electron apps think similarly. Hence my first question: am I doing something wrong? Or is this the expected loading time for a trivial Electron app?

Assuming this is normal behavior, what is the common way to deal with this problem? Some ideas come to mind:

1. Asking Electron to show a splash screen: unless there is specific built-in functionality for this, it seems like a no-go, since the splash screen itself would be shown only after 2.5 seconds.
2. Hide the app's window until it is rendered (using the ready-to-show event), so no blank window is shown. This isn't ideal, since it means that the user doesn't get any feedback whatsoever that the application is actually loading.
3. Create a wrapper application (using native code) that displays a splash screen, launches electron and hides itself once the electron window is shown. Kind of defeats the purpose of using Electron in the first place, because you end up writing native code and adding accidental complexity.
4. Setting the background color of the window to something resembling your app, as suggested by the docs. This just doesn't look very well.

Given this must be a common problem, I hope standard solutions have been found by the community. I'd be glad if someone can point me in the right direction.