black

🚀 Creator of Mylinx.cc ✨ | 🧙‍♂️ Lead Software Engineer @SheetJS | 📍 NYC | Data Science in JS?

Github

Dev Community

Linkedin

Twitter

Instagram

Email

My Blog

Lately, I've been diving deep into the world of parser and 

. It's been an exciting yet incredibly frustrating journey, and I've hit a roadblock that has me questioning my life choices.

, it’s perfectly acceptable for command names to double as variable names. Consider this simple example:

 is a command, while the second is simply a variable name. This kind of flexibility is intuitive for us humans, but it can turn into a real headache for a parser.

In my initial implementation, I ran into two major issues:

This created a impossible situation where the parser couldn't distinguish between commands and identifiers with the same name.

After some digging through parsing forums and documentation, I discovered that this isn’t an isolated problem. Many language implementers have wrestled with context-sensitive keywords. The common solutions often involve elaborate workarounds ranging from context-tracking mechanisms to entirely separate parsing passes.

Unfortunately, with my current Chevrotain setup, reordering token precedence isn’t feasible because Chevrotain is a parser generator library for JS that uses LL(k) parsing techniques.

It provides tools for building recursive-descent parser with full control over grammar definitions. This doesn’t mean it can’t handle token precedence it definitely can but it requires manual implementation, which involves considerable effort.

Chevrotain has built in support for contextual tokens. We could define our keywords as contextual and enable them only in certain parsing rules.

This is one is an interesting one post-lexing examines the token stream and reclassifies command tokens to identifiers based on their syntactic position.

Each of these methods has its merits and its tradeoffs. If anyone has tackled this issue from a different angle or has additional suggestions, I’d love to hear your thoughts.

After careful consideration, I went with the post-lexing token transformation approach. This solution proved to be the most practical for several reasons:

The key insight was that context sensitivity could be handled by examining token patterns after initial lexing. This approach effectively solves the "generate generate = 1" problem with remarkably little code.

Parsing Nightmares

As a software engineer working on data visualization and scientific computing projects, I've often found JavaScript's native math capabilities lacking. The hunt for robust standard library led me to 

The stdlib project caught my eye with its impressive set of features:

I ran benchmarks comparing stdlib-js against native JavaScript Math operations across 100,000 rows of data. The results were surprising:

Basic operations showed modest improvements:

Complex operations took a significant hit:

The precision differences were minimal, with a maximum difference of 4.441e-16. Most operations whoed identical results between stdlib-js and native Math.

There's potential for improvement - converting stdlib-js to WebAssembly could boost performance by running close to native speed, particularly for those complex operations currently showing significant slowdown. But until that happens, the choice between stdlin-js and native Math requires careful consideration of your specific needs.

stdlib-js is a solid library taht delviers on its promise of consistency and extended functionality. However, the performance trade-offs mean it's not always the best choice. For my projects, I'll be using native approach and maybe in the future will try to compile stdlib-js to WASM to test if its really faster.

Have you tried stdlib-js in your projects? I'd be curious to hear about your experiences with mathematical computations in JavaScript.

Better Math in JavaScript?

How I Built a Scalable, Free URL Shortener

Optimizing 🚀 V8 Engine: Cutting Memory Usage by 66%

Mylinx: Accessible and Affordable Bio Link Solution

The bio link space is full of tools that either lack key features or place them behind expensive paywalls. Customization, traffic analytics, and SEO control are often limited or inaccessible, with services charging $10+/month—unaffordable for users in regions like India, Africa, and Southeast Asia.

: Poor analytics, minimal customization, and lack of SEO tools.

: Core features locked behind costly subscriptions.

: Few platforms offer multi-language support, limiting non-English users.

Existing tools overlook creators in developing regions who need affordable solutions to build their online presence. High costs and limited options hinder their potential to grow.

To address these gaps, I built Mylinx in just three months, offering:

: Seamless integration for content sharing.

: Generate codes for easy offline sharing.

: Advanced tools to boost search visibility.

: Supports 11 languages, including हिन्दी, Русский, and عربي.

: Affordable, unlike other smart link services.

Mylinx has created 1,000+ pages and logged over 750,000 hits, empowering creators in emerging markets with accessible and affordable tools to grow their presence.

Another linktree clone?

My Projects

Mylinx - Launch your bio page in seconds

ReactAllPlayer - A flexible React web player.

AniTrek - Track, discover, and get alerts for anime and manga.

VSCode Spreadsheet Viewer

BinCode - Self Hostable JSFidlle

Tabeller - React Native Table Library

SheetSense - ESLint for Excel

Affiliate

Cheap Server $0.94/month 1GB Ram 1CPU

Cheap Production Server $5/month 6GB Ram 4CPU

🎶

Я тебя полюбил

BEHELIT

Behelit

[BERSERK] Behelit - Susumu Hirasawa

Chikar Kardi

Chikar Kardi (feat. Sepehr Khalse & Heliyom)

Behzad Leito & Sijal & Sepehr Khalse & Heliyom – Chikar Kardi

Leito, Sijal, Khalse, Heliyom - Chikar Kardi (Official Visualizer)

Leito, Sijal, Khalse, Heliyom - Chikar Kardi (Official Audio)

Gəl gözəlım (gel guzalim)

Lavender Sunflower

Tory Lanez - Lavender Sunflower

Asad Karimov

Check out Asad Karimov's Mylinx to grab their links!