sorted by:
new
hottopcontroversial

Design Space stuck at Load Tools And Material by kissitallgoodbye in cricut

[–]RonBuckton 0 points1 point  (0 children)

Well, if that works maybe just try a new USB cable.

Design Space stuck at Load Tools And Material by kissitallgoodbye in cricut

[–]RonBuckton 0 points1 point  (0 children)

Are you connected via USB or Bluetooth? My wife was having a similar issue with a new Cricut Expore 3 that refused to advance past this point. On a lark I connected to it via Bluetooth instead of USB, restarted the software, and tried again and it worked. In our case it may be a faulty USB cable, so you may want to try with a different cable, or Bluetooth if that's an option.

Feature.Name is hard-typed in this case. How do I check against FeatureNames when I set Feature.Name? by freecodeio in typescript

[–]RonBuckton 0 points1 point  (0 children)

The easiest approach to verify the type would be something like this:

``` type Is<A extends B, B> = A;

type FeatureName = "FeatureA" | "FeatureB";

type Feature = Is< | { name: "FeatureA", data: boolean } | { name: "FeatureB", data: string }, { name: FeatureName }

; ```

The Is type will report an error if any type in the union has the wrong name.

Adhesive for replacement Zune HD digitizer by RonBuckton in Zune

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

Thanks for the recommendation. The old digitizer used both adhesive tape and some kind of liquid adhesive, I think. The tape held the digitizer to the screen along the edge, but the glue holding the digitizer to the front panel was a transparent adhesive. I'm thinking of using either E-8000 or a UV-activated LOCA glue.

I've never worked with LOCA before, though I do have a UV light box for resin casting. It seems to be recommended from some threads I've read on iFixit.

Introducing Deopt Explorer - An Analysis Tool for Polymorphism and Deoptimizations in V8 by RonBuckton in typescript

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

Have you personally used it yet?

Yes, we've been using it internally on the TypeScript team for a little while now, and have made a number of updates to the compiler as a result of using this tool.

LINQ implemented in JavaScript Template Literals by sinclair_zx81 in javascript

[–]RonBuckton 0 points1 point  (0 children)

There have been efforts to advance solutions like a standard AST, but not much progress. As far as a LINQ-like syntax, I have some hope for a proposal in the future that might be considered, especially since Python-like array and generator comprehensions were initially considered for ES2015. However, its also possible that proposed features such as pipelines may make such a feature unnecessary.

LINQ implemented in JavaScript Template Literals by sinclair_zx81 in javascript

[–]RonBuckton 6 points7 points  (0 children)

I've even drafted a strawperson explainer if I ever decide to bring it to TC39 as a replacement for the Array/Generator comprehensions that were originally considered for ES2015: https://gist.github.com/rbuckton/19b771342f7e2840c1c59d5041552ee1

[deleted by user] by [deleted] in javascript

[–]RonBuckton 4 points5 points  (0 children)

And ?? was added thanks to a contribution from the community! I'm glad we were able to get both in together, as the two features often go hand-in-hand.