ciarcode's comments

ciarcode | 1 year ago | on: A 10x Faster TypeScript

In the post, they specifically talk about two points that seems to address some of your doubts

1. “We expect to have a more curated API that is informed by critical use-cases (e.g. linting, transforms, resolution behavior, language service embedding, etc.).”

2. “We also can imagine opportunities to optimize, use other underlying IPC strategies, and provide batch-style APIs to minimize call overhead.”

Anyway, I’ve used the compiler API a lot too, and I really enjoy its huge capabilities, making possible practically everything on the source code (EDIT: and hijack the build process too). I hope we won’t miss too much.

ciarcode | 1 year ago | on: A 10x Faster TypeScript

I think they answered in their FAQ here: https://github.com/microsoft/typescript-go/discussions/455#d....

If I got it correctly, they created a node native module that allows synchronous communication on standard I/O between external processes.

So, this node module will make possible the communication between the typescript compiler GO process, that will expose an “API server compiler”, and a client side JavaScript process.

They don’t think it will be possible to port all APIs and some/most of them will be different than today.

ciarcode | 3 years ago | on: Will low and no code tools ever truly disrupt tech development?

In automotive, development of control algorithms for the engine is entirely “visual”, through simulink/matlab. You design the model on simulink, then it generates the C code. I don’t have direct experience outside the automotive sector, but I believe that this approach is used in other sectors like aerospace. Maybe designing models is better than writing low level code for control algorithms?

ciarcode | 3 years ago | on: Operating Systems: CPU Scheduling

I always think to priority-based scheduling in this way. Maybe it can help someone else.

The scheduler will always schedule the highest priority task among ones in the ready queue, but at different times.

- If preemptive, the scheduler will schedule the higher priority task (higher than the currently running one) as soon as it enters the ready queue.

- If non preemptive, the scheduler will schedule the higher priority task only when the running one terminated or explicitly call a yield() (call to yield --> cooperative)

In principle, you can mix both scheduling types, making some tasks "non-preemptable" and other tasks "preemptable".

ciarcode | 4 years ago | on: Ask HN: What programming tutorial/course/article/blog would you like to see?

I would be glad to find an integrated guide on how to build a state-of-the-art website and how to deploy/maintain it on a server like AWS or DigitalOcean.

I mean, I'm not interested in a html/css/javascript tutorial, we have enough resources on that. What I found really missing on the internet (maybe I'm not that good at searching), is a step-by-step detailed guide on how to deploy/update/maintain a website. An unordered list of thing that came up to my mind:

- How to deploy the website on a server

- Which server should one use

- How to expose it on the internet (buy domain name)

- Version control and hosting the repository (GitHub vs gitlab vs ...)

- Updating your website (CI/CD like Jenkins?)

- Reproducible environments (Docker?)

- How to integrate analytics

- How to integrate ads respectfully (of your users)

- How to integrate paying contents

- How to address security

- Ho to address scalability

ciarcode | 4 years ago | on: Self hosting is important

Not related to the discussion, but I need to say I didn’t know I could use NB (i.e., “nota bene”) in an English conversation. Thanks

ciarcode | 5 years ago | on: Some Were Meant For C (2017) [pdf]

yeah I know that, and I always wondered how they implement basic data structure like linked list or bst with static allocation. I guess that this will be never something really needed in an embedded system, and they can live with arrays and variables.
page 1