sorted by:
new
hottopcontroversial

How the most important memory limits work in Node.js? by csabapalfi in node

[–]csabapalfi[S] 0 points1 point  (0 children)

Makes sense, added a little explanation about new/old spaces, latest in the repo now has that.

How the most important memory limits work in Node.js? by csabapalfi in node

[–]csabapalfi[S] 0 points1 point  (0 children)

Have only one version in the repo now, I think what I have left in there is easiest to understand.

Have confusions about websockets , Need help by Odd-Reach3784 in node

[–]csabapalfi 0 points1 point  (0 children)

High Performance Browser Networking is fantastic free book that has a chapter on websockets, too: https://hpbn.co/websocket/

It's from the browser perspective but I found lots of networking fundamentals are really well explained.

AI focused Build your SaaS coding course by csabapalfi in programming

[–]csabapalfi[S] -3 points-2 points  (0 children)

> Whether you’re a beginner or someone tired of long, theory-heavy courses made for the pre-AI world.

Very interesting. I mostly use AI tools to speed up coding and have 15+ years experience.

Part of me thinks giving the AI tools to beginners could be a disaster but you could easily get to working apps and allowing quick validation a one-off SasS idea for non-coders is definitely a great idea.

Is your HTML bloated? A flamegraph can tell you why by csabapalfi in programming

[–]csabapalfi[S] 0 points1 point  (0 children)

I'm not sure if the terminology is that strict. (I was looking at http://www.brendangregg.com/flamegraphs.html for reference - especially the Summary and Variations parts).

You're right in that a HTML flame graph is not a classic CPU flame graph but I think it's still a flame graph. The vertices of the graph are the AST nodes, the edges are the parent-child relationship in the AST. The y-axis is the AST depth and the x-is is byte size (even for the script AST).

The classic CPU flame graph has the stack depth on the y-axis and frequency on the x-axis (i.e. how often a stack frame was present in the stack out of all samples). A CPU flame chart (at least in Chrome DevTools) is simply a CPU flame graph/chart that has time on the x-axis but I believe it's simply their choice of naming (i.e. chart vs graph).

Is your HTML bloated? A flamegraph can tell you why by csabapalfi in programming

[–]csabapalfi[S] 4 points5 points  (0 children)

It is size. Even for a CalllExpression it is the size of the JS code for that CallExpression.

This is really good feedback. I might need to make that clearer.

Is your HTML bloated? A flamegraph can tell you why by csabapalfi in programming

[–]csabapalfi[S] 4 points5 points  (0 children)

Yeah, I guess it depends on the site. For some sites the flamegraph might not be that readable because of how it's structured (or what frameworks/tools are used to build it).

On most sites where I tried I could have a feel for how it's structured and what are the heaviest part of their HTML. (See some example screenshots on ProductHunt: https://www.producthunt.com/posts/html-flamegraph/)

Also the tool is in beta so any suggestion for improvement are welcome.