hajile

63 ms·

961.
by hajile 4y ago
It's more common for pattern matching Java's new syntax, Erlang, Elixir, StandardML (fat arrow), F#, Kotlin, Ocaml, Haskell, Rust (fat arrow), Ada (fat arrow), Scala (fat arrow), Zig (fat arrow), and probably a bunch of others too
962.
by hajile 4y ago
That's why I prefer the F# version where it's just the names of functions or anonymous arrow functions. Nothing magical about them. It just calls the functions in order from top to bottom.
963.
by hajile 4y ago
Sure, but I'd rather reserve that for a pattern-matching switch statement.
964.
by hajile 4y ago
Your example is bad. Fetch resolves the promise even if you get a 400 or 500 error. If your project is going to be robust, you MUST intercept the result and check before asking for JSON. const resp = fetch(`https://api.weath
965.
by hajile 4y ago
Objects carry prototypes and mutability with them. Further, all primitives/value types of the language are immutable. Adding those features to an Object would still necessitate creating a new primitive. At that point, you might as well
966.
by hajile 4y ago
I've been wishing for this for years. It opens up whole new ways of doing stuff when tuples and records are just primitives. They never mutate, so representing them efficiently right from the start is possible. They are primitives, so
967.
by hajile 4y ago
They should repurpose `do` so that `do {}` (without the `while`) is an expression that you can put statements inside and return the last statement. It would be great if we had expression if..else too (instead of just the tertiary operator)
968.
by hajile 4y ago
Mozilla created SweetJS over a decade ago[0]. It added hygenic macros to JS and I'm sure everyone on the TC39 committee is familiar with it. There's a lot to like about it, but macros in such a complicated language as JS are hard
969.
by hajile 4y ago
The top example relies on Lodash/fp having curried functions you can use. The middle example would be using native stuff which is why you have the wrapper function (kinda like you'd have a function wrapping a callback)
970.
by hajile 4y ago
I'd far rather save that for an alternative switch expression with pattern matching. const slowSum = (lst: {x: number}[]) => switch(list) { [{x}, ...y] -> x + slowSum(y) //not tail recursive
971.
by hajile 4y ago
The F# syntax looks/acts a lot better here (especially paired with lodash). I also feel your code example wasn't done in the way people would actually use pipes. import {map, join} from 'lodash/fp' /&#x2F
972.
by hajile 4y ago
Price's square root law states that half of the literature on a subject will be contributed by the square root of the total number of authors publishing in that area. It seems to play out well in the teams I've been with too. If y
973.
by hajile 4y ago
It is strange to see JS taking ideas from a derivative of PHP.
974.
by hajile 4y ago
Because x |> f |> g |> h is much easier to read than h(g(f(x))) for most people.
975.
by hajile 4y ago
They should have stuck with the F# proposal. The hack proposal just takes one more giant step toward turning JS into Perl. Hack proposal value |> foo(%) for unary function calls, value |> foo(1, %) for n-ary function calls,
976.
by hajile 4y ago
v8 is compacting while JSC is not. I think it's telling that v8 released a new GC in 2018 to massively improve their GC performance while in 2019 JSC redid their bytecode and execution engine to radically improve execution performance.
977.
by hajile 4y ago
The bulk of the browser's memory usage is the rendering engine and surrounding stuff rather than the JS on the page. v8 has a compacting GC[0] while JSC does not[1]. This was the result of the v8 team taking out a bunch of time to writ
978.
by hajile 4y ago
In my general experience, JSC is 20-50% faster in a lot of things, but uses about 2x the memory. I'm not sure how much of that is memory/speed tradeoff, but I suspect a lot of it is "we spent our budget on fast and skipped wo
979.
by hajile 4y ago
That's to upsell their new iPhone feature where you can use your iphone as your camera instead. More seriously, there just isn't room in the 2-3mm thick screen to put a better camera and lens. I'd also note that megapixels ar
980.
by hajile 4y ago
Apple's CPUs do very well in sustained performance. They fit 8 high-performance CPUs and 2 efficiency cores into a 40w peak power envelope while hitting peak clockspeeds (that 40w includes all the IO, mostly idling GPU, idling NPU,
981.
by hajile 4y ago
Actually, it's the reverse. The JS spec accidentally baked in the x86 description of int/float conversion. This is done a LOT in JS because the JITs are actually using integers instead of floats all over the place for improved per
982.
by hajile 4y ago
Kate has the best VI command emulator out there bar none and got a lot more usable for a lot of stuff when it added LSP support. Kate is the core editor of KDevelop IDE too. https://www.kdevelop.org/
983.
by hajile 4y ago
Good GFCI receptacles are almost 10x the cost. Adding them everywhere would add a few thousand extra to building costs. In any case, new houses must use arc fault breakers which do the same thing and more for most things. I would add that b
984.
by hajile 4y ago
I'd guess it's familiarity and encouraging sales. If I were to guess, it's wargaming like everything else. Wargames were popular as you control an entire army, but D&D originally meant to answer the question of what thing
985.
by hajile 4y ago
As a collector of different systems, I can assure you that d20 is one of the worst systems ever created. Most people who've played a handful of other systems will prefer one of those systems to d20 in basically every scenario. The syst
986.
by hajile 4y ago
It really is a kind of spiritual successor to Real World Tech and Anandtech. The number of enthusiasts is at an all time high, but the number of in depth tech articles seems to be at an all time low. Everything is just high traffic cursory
987.
by hajile 4y ago
You can have an optional length prepended to arrays that use that feature.
988.
by hajile 4y ago
chipset != chiplet
989.
by hajile 4y ago
I'd also add that Typescript would be a very bad language choice anyway. If we're going to have a backward-incompatible change, we should do things the right way (after all, we're stuck with it forever). Don't make a typ
990.
by hajile 4y ago
You can get a million hours of playback with enough battery. Thin and light laptops with typical sub-50w/hr batteries are going to have a very hard time going over 20-25 hours. I'm also super-skeptical of AMD's claim becaus

More ›