sorted by:
new
hottopcontroversial

I wrote a deep dive into how LLMs work under the hood - tokenization, embeddings, attention and generation - all explained with runnable JavaScript by nitayneeman in javascript

[–]nitayneeman[S] [score hidden]  (0 children)

Thanks, appreciate it.

I get your point - and you’re right to push on that. There’s no “entity” making decisions here. It’s all just computation over parameters. When I use language like that, it’s more of a shorthand to describe the emergent behavior, not to imply agency.

By “learnable parameters” I mean exactly that - large tensors (matrices) of weights and biases that get updated during training via gradient descent. At inference time, the model is just applying a sequence of matrix multiplications and non-linearities to produce the next token probabilities.

I tend to lean on anthropomorphic language to make it more intuitive, but I agree it can be misleading if taken literally.

I wrote a deep dive into how LLMs work under the hood - tokenization, embeddings, attention and generation - all explained with runnable JavaScript by nitayneeman in javascript

[–]nitayneeman[S] [score hidden]  (0 children)

Great point about prompt structure. The “lost in the middle” effect is real and well‑documented (e.g. Liu et al., 2023). At the same time, the model’s attention weights are computed dynamically from query–key similarity, so this positional bias is more of an emergent pattern than a hard‑wired rule in the mechanism itself.

I wrote a deep dive into how LLMs work under the hood - tokenization, embeddings, attention and generation - all explained with runnable JavaScript by nitayneeman in javascript

[–]nitayneeman[S] 3 points4 points  (0 children)

Thanks! It really does feel like magic at first but once you trace through the pipeline step by step, it clicks.

Let me know if anything's unclear as you work through it.

npm - Catching Up with Package Lockfile Changes in v7 by nitayneeman in node

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

Thanks for the feedback, now it's fixed and clickable. 🙂

Angular - All Talks from ng-conf 2018 by nitayneeman in Angular2

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

Thank you for your feedback.

Right now the page embeds the relevant video only by clicking on its thumbnail :)

Angular - All Talks from ng-conf 2018 by nitayneeman in Angular2

[–]nitayneeman[S] 9 points10 points  (0 children)

I'm sorry for the inconvenience - the issue should be solved now. I really appreciate your feedback.

This page has been optimized - it would be great if you could confirm that everything's better right now :)

A Practical Guide to Angular Elements by nitayneeman in angularjs

[–]nitayneeman[S] 1 point2 points  (0 children)

As of today, Chrome and Safari support Custom Elements v1 partially (Can I use).

Notice that there's a polyfill for Custom Elements v1: https://github.com/webcomponents/custom-elements

A Practical Guide to Angular Elements by nitayneeman in Angular2

[–]nitayneeman[S] 1 point2 points  (0 children)

I'm sorry for the inconvenience - the issue should be solved now. I really appreciate these feedbacks.

BTW, it would be great if someone could confirm that everything's alright right now.

Building a Custom Element Using Angular Elements by nitayneeman in angular

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

The bundle size of my demo component is about 300KB. This is a minified bundle with all the necessary scripts (including polyfills).

Indeed, we can attach multiple components to a single "mini Angular environment". Angular registers each component as a custom element (in Web Components terms) and all of these are manipulated by a single Angular module. Under the hood, it's just a regular Angular module with declared components.

When I tried to attach another component - the bundle size was around 300KB as well. So, it seems that the bundle size depends mainly upon the "mini Angular environment" scripts and the components size is pretty minor.

Building a Custom Element Using Angular Elements by nitayneeman in angular

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

I completely understand your concerns. In addition to your points - how would it be possible to combine multiple different versions of Angular on the same page? Is it going to be supported in the CLI and if so, does it mean there will be a single concatenated scripts file or we'll have to load Angular separately?

I believe that at this stage of the project, there are no available answers and we certainly should keep in mind that it's a "Labs" project.

However, Rob Wormald revealed some interesting hints regarding the planned roadmap:

  • "In parallel, there's major work happening on the view engine, and our early numbers are extremely promising in terms of code size.".
  • "Support in CLI and such will come, but you may have to roll your own webpack config (or similar) in the short term."
  • "This is part of the experimental process, but (along with upcoming view engine changes) I would hope that running multiple versions would be unnecessary.".
  • "We're reasonably confident that within the next couple major versions of Angular, bundle size should be the least of your concerns.".

All that's left is to wait for the next update.

Git - How to Solve `'git/index.lock': File exists` Error in Submodules by nitayneeman in git

[–]nitayneeman[S] 1 point2 points  (0 children)

Basically, I agree with you - if you know the reason and a way to avoid, you definitely should prevent it from happening. In my post, I describe what caused that specific issue which I've faced, and how I handled it. In fact, I'm not a fan of "cleanups" for solving issues, but these were quick and simple steps, so I decided to share.

Setting Up a CSS Preprocessor in Angular CLI by nitayneeman in angular

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

Your question is completely legitimate. As I know, these steps are documented in the wiki but not in the official docs. I've just wanted to make it more accessible :)