Viewing profile — maga
maga
HN member- Joined
- Fri, Jan 20, 2012, 9:27 PM UTC
- HN karma
- 892
- Public activity
- 240 items
- HN profile
- View on Hacker News ↗
About maga
denelxan@gmail.com
Recent public activity
-
comment
Comment #43526786
Thank you! > The trick then is a sliding scope context window: with a high-level design doc in context, iterate to produce an architecture document. Absolutely, I will be stealing …
-
comment
Comment #43526730
Apologies, no offence to New Yorkers (or the New Yorker) meant. If you find my handle, "maga", interesting..., I'll have you know that it's been around long before it was appropria…
-
comment
Comment #43526575
> It’s unclear whether the suggestions and techniques mentioned in the article came from personal experience or have otherwise been verified or experimented with with a real team a…
- story
-
comment
Comment #36711238
What was the reason behind not clearing outdated flows automatically?
-
comment
Comment #32084881
Code splitting is supported just fine for ESM bundles[1] (and there is little reason to use other formats nowadays), CSS handling works ok as well. I have been using ESBuild since …
- comment
-
comment
Comment #31245231
That's why we introduced the strict mode ("use strict" pragma)[1]. Among other things, it prevents from accidentally declaring a global variable this way, throwing a ReferenceError…
-
comment
Comment #31165066
Great to see dprint on the front page! While here it's speeding up prettier with caching/wasm, it can replace prettier altogether and be even faster (for example, with `dprint-plug…
-
comment
Comment #30941204
Leo, your comments save me a lot of typing on threads like this, and since I recently wrote[1] what beeandapenguin wrote above almost to a point (sans security), I feel obliged to …
-
comment
Comment #30731166
Yes, TS code is compiled to run in browsers. You can compile and bundle using `deno bundle` if your project is developed in Deno. Since I'm using Deno for library development, I us…
-
comment
Comment #30713204
Good catch, thanks!
-
comment
Comment #30712670
I have moved all my library development to Deno and described the experience in a blog post[1]. To summarize, the two killer features for me are Web APIs and the built-in toolchain…
-
comment
Comment #30370993
By any chance, are you aware of any good surveys comparing the open models to the cloud providers for other NLP tasks like speech recognition or POS tagging?
-
comment
Comment #30274752
If it's speed you are looking for, give dprint ( https://github.com/dprint/dprint ) a try, it has a vscode plugin too.
-
comment
Comment #30274725
Why not dprint[1]? Does it not "produce a concrete syntax tree (CST) that represents the original code completely, whitespace, comments and all"? I'm not terribly familiar with the…
- story
- comment
-
comment
Comment #30165503
In the end, I went with this library for now: https://github.com/chris-rudmin/opus-recorder There are issues reported with the latest iOS, though.
-
comment
Comment #30163655
A common reference to the modern (ergo enlightened) age in Terry Pratchett's Discworld series: https://wiki.lspace.org/Century_of_the_Fruitbat Sorry for the confusion, I'm high on …
-
comment
Comment #30163236
Sounds almost too good to be true, but here is hoping for the best. > Opus audio decoder (enabled) Considering the track record of codec support, I bet it only works when packaged …
-
comment
Comment #30157813
> You’re still missing much the point of the article: WASM isn’t for the browser only. WASI, for example, is a full environment you can run stuff in without any such interoperabili…
-
comment
Comment #30157184
You do realize that I didn't put up those benchmarks and wrote the article way back in 2017 just so that I can pick on a passage in this article? I was (and still am to a degree) e…
-
comment
Comment #30157068
And how is the data going to reach the "unshackled" WASM in the browser, for example? I'm not aware of any way for the web page to interact with WASM other than through the JS land…
-
comment
Comment #30157039
And that's another thing about JavaScript engines--they evolve and usually result in better performance. The article is written in 2017 and the results are from Node.js of the time…