opinionated | An opinionated Go application starter framework | GraphQL library

I have a Vue/Vuefify project and I'm using the vkbeutify lib to format XML and then display it in the Ace Editor. The Editor opens in a modal dialog (full screen mode) and all works fairly well when the amount of XML is small.

I have to parse about 2.5MB+ of it (about 2,500,000 characters when formatted in Notepad++) and then Ace becomes unusable (it eventually displays the XML, but it takes a very long time).

I created a simple test page with a textarea and the Editor and the formatting and display goes extremely fast. The page does exactly the same thing as this: https://www.webtoolkitonline.com/xml-formatter.html (this uses Ace and vkbeautify to format xml)

I tried pre-formatting the XML in an text area before passing it to the child dialog, tried subverting Vue and populating the editor container in the mounted() function by getting the DOM contents directly.

Standalone test page:

Does destructuring assignment (in my case with Vue composables) has any performance gain/tradeoff?

For example I have component that displays current language choosed in vue-i18n.

I can do this with destructuring:

I need to sync a moderate amount of data regularly from a service into a local database in Azure.

I could write the code for that and I would have been done with this 10 times over if I did, but where's the fun in that, right?

I thought, let's use some fancy Azure services and see how that goes. It may lead to some better maintainability if I have something workflow and node-based.

So I made an ADF pipeline and a copy job to an Azure Table, which works fine. The json from the service is parsed correctly and I could insert the json fields as table columns.

In a next step I want to copy the data further to a Azure SQL Database and convert some types properly:

• One field is either missing or has one of two fixed string (not "true" or "false" though), and it should be a bit in the database.
• Another field has a very opinionated date format and needs to be parsed properly.

I don't think this works in the copy job. The mapping tab seems to be limited and the dynamic thingie ("add dynamic content" in that tab) appears to not be able to refer to the fields I need to transform.

Am I correct in assuming that I now need to use either a data flow (executed on some Java cluster I believe) or an SSIS package?

I tried creating a data flow, but it appears it can't use Azure Tables as a source - at least that source isn't offered in the respective selector.

Since I'm not even sure that a data flow is necessary, I'm asking for help at this point.

It may be opinionated and not belong here, but I don't seem to find any info about this.

I have a 'sales' resource so I can GET, POST, PUT, DELETE sales of my store.

I want to do a dashboard with information about those sales: e.g the average sales per day of the last month.

Since REST is resource-oriented, that means I have to manually retrieve all sales of the last month and calculate the average per day on client using GET /sales?sale_date>=...? That doesn't seem optimal, since I could have thousands of sales in that period of time.

Also, I don't think REST can allow a URL like GET /sales/average-per-day-last-month. What is the alternative of doing this?

I'm building a site using Laravel 8 and Jetstream. Jetstream is opinionated about the javascript / css framework, which is great, but I'm needing to add an external javascript library to one of my components, and I don't see anywhere to add them in the default app layout. So I added a stack for the css /js like this in the default app layout:

Please do correct me if I'm wrong about anything:

The JS runtime engine agents are driven by an event loop, which collects any user and other events, enqueuing tasks to handle each callback.

The event loop runs continuously and has the following thought process:

• Is the execution context stack (commonly referred to as the call stack) empty?
• If it is, then insert any microtasks in the microtask queue (or job queue) into the call stack. Keep doing this until the microtask queue is empty.
• If microtask queue is empty, then insert the oldest task from the task queue (or callback queue) into the call stack

So there are two key differences b/w how tasks and microtasks are handled:

• Microtasks (e.g. promises use microtask queue to run their callbacks) are prioritised over tasks (e.g. callbacks from othe web APIs such as setTimeout)
• Additionally, all microtasks are completed before any other event handling or rendering or any other task takes place. Thus, the application environment is basically the same between microtasks.

Promises were introduced in ES6 2015. I assume the microtask queue was also introduced in ES6.

What was the motivation for introducing the microtask queue? Why not just keep using the task queue for promises as well?

Update #1 - I'm looking for a definite historical reason(s) for this change to the spec - i.e. what was the problem it was designed to solve, rather than an opinionated answer about the benefits of the microtask queue.

• In depth: Microtasks and the JavaScript runtime environment
• HTML spec event loop processing model
• Javascript-hard-parts-v2
• loupe - Visualisation tool to understand JavaScript's call stack/event loop/callback queue interaction
• Using microtasks in JavaScript with queueMicrotask()

I'm doing leetcode questions to get better at solving problems and expressing those solutions in rust, and I've come across a case where it feels like the most natural way of expressing my answer includes unsafe code. Here's what I wrote:

What is the correct way to require a node module? Is it more accurate/understandable to declare the module in the global scope, or is it more accurate/understandable to declare the module in the local scope?

For example, which of these makes the most sense:

Global:

I am building a Go service that communicates with multiple third-party providers. This go-service acts as an interface between these multiple providers and my internal applications consume just one API from this Go service.

My application has the below structure now