tjallingt · HackerTrans

Seems quite similar to https://sizzy.co/

Looking really cool! Hope there will be talks about implementing this and the benefits that it will bring.

Is this also coming to IOS or are there app store regulations that would prevent apps including Hermes from being uploaded?

tjallingt

7년 전discuss

theres the AbortController [1] that can be used on a few new promise based APIs such as the Fetch API [2]

[1] https://developer.mozilla.org/en-US/docs/Web/API/AbortContro...

[2] https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API

tjallingt

8년 전discuss

React team members seem to be hinting at some sort of official "adopt" (https://github.com/pedronauck/react-adopt) api which would allow for a slightly nicer way of getting access to render prop arguments. (although you still done get access to them in lifecycle methods). In the meantime this seems pretty nice: https://github.com/Astrocoders/regenerator

tjallingt

8년 전discuss

Would be interesting if it would be possible to take the Rust approach and guarantee at parse/compilation time that the DOM interactions are safe without runtime overhead. Probably a terrible idea for mobile devices though...

tjallingt

8년 전discuss

The graphs for major programming languages shows a decline in the number of monthly active users using JavaScript, interestingly this decline seemingly coincides with the incline of TypeScript users. I'd love to see whether people who stopped using JavaScript started using TypeScript instead.

tjallingt

8년 전discuss

Its called literate programming; for example https://wiki.haskell.org/Literate_programming

tjallingt

8년 전discuss

Some examples of "transpilers" targeting Javascript but writen in other languages:

https://github.com/google/closure-compiler

https://github.com/BuckleScript/bucklescript

https://github.com/fastpack/fastpack

Seems like on the average it does offer a boost in performance.

And there is some aditional work providing javascript parsers for rust (which you could build tools like babel on top of): https://github.com/dherman/esprit

tjallingt

8년 전discuss

I agree so much. The first season was amazing with the split story line between the main crew and Miller on Ceres but it all went downhill when the proto-molecule was introduced and suddenly there were massive shootouts (with characters who admitted only episodes earlier to never having killed/fired a gun)

I really love the political aspects and cultural differences between the various factions though.

tjallingt

9년 전discuss

the `=>` de-sugars to:

    var currentUrl = function(_) {
        return window.location.href;
    }

the underscore is used so they don't have to type `() =>` instead

tjallingt

9년 전discuss

Not a Japanese reader so i can't fill you in on what exactly the characters mean but they are characters from the Japanese katakana script. Katakana are generally used for loanwords and each character represents a sound:

ツ - tsu

シ - shi

ソ - so

ン - n

The reason these are difficult to learn is because the tiny differences in stroke angles (especially when handwritten) make it easy to confuse them.

tjallingt

9년 전discuss

How funny, I recently started working and also opted for a 36 hour work week and use it to get fridays off every other week :D

tjallingt

9년 전discuss

``` var dividers = { 2: function divideBy2 (lhs, unused) { return lhs >> 1 }, 4: function divideBy4 (lhs, unused) { return lhs >> 2 }, undefined: function divideByNumber (lhs, rhs) { return lhs / rhs } } ```

Does this actually work? I tried it out in the Chrome Debugger and it didn't work. It looks like the author is confusing it with Rusts match statement.

tjallingt

9년 전discuss

All he said was that they refunded the guy, seems like information that is pretty OK to share publicly especially in response to the claim that their customer support was terrible. In addition to that the person who commented shared a large amount of information about the support ticket themselves so it seems like they are fine with sharing at least that much information about this case.

All-in-all this hardly seems like a reason to feel "violated"...

tjallingt

10년 전discuss

Except that if you use a western keyboard you still need to learn Pinyin or Romaji in order to be able to type the language. In my own attempts to learn a little bit of Japanese I've noticed that it is indeed difficult to associate the 'new' characters to the correct sound without using Romaji as an intermediate representation but my hope is that the more I learn and interact with the language the less this is the case. I think that, especially when using online learning tools, learning Romaji is inevitable and don't think that learning the phonetic system 'from scratch' makes it easier (if it is even possible to completely forget about your own phonetic/alphabetic system).

In short, as a starting learner of Japanese I acknowledge that the problem you describe exists but think that 'really bad' is an overstatement and it is almost inevitable that your brain associates your old knowledge of English (or other languages) to the new language.

tjallingt

10년 전discuss

Interesting read, although the shtick got a bit old near the end. I really wonder how this compares to inferno.js as that has some real optimisation magic to make it super small and super fast while also being, close to, compatible with React.

tjallingt

10년 전discuss

Fair warning: I don't know much about compilers.

Maybe it's an idea to make this a native Typescript compiler as it will profit much more from being compiled than pure JavaScript will?

This way it would probably still be possible to compile pure JavaScript but providing type information would allow the compiler to apply many more optimisations.

If I'm not mistaken V8 already does something similar to this with WASM (and I think asm.js).

tjallingt

10년 전discuss

That is a great explanation and after looking at the source code and reading the example more closely that is indeed what appears to happen. I do think that, albeit very clever, it's a confusing pattern though...

tjallingt

10년 전discuss

Aah of course; By reading the source code of the children function I figured the array of elements returned was appended to the parent element. The strange thing was that it was also adding them to `el` object but indeed it appears this is done to maintain a reference to the children so they can be modified later (which I would have seen had i read the example a bit more carefully :S )

I'm still not sure how I feel about that bit of code though but it sure is clever...

tjallingt

10년 전discuss

I've never seen this before:

    children(el => [
      el.email = input(props({ type: 'email' })),
      el.pass = input(props({ type: 'pass' })),
      el.submit = button(text('Sign in'))
    ])

Can someone explains what this does and why it is used here? As i understand it this function both modifies the `el` object (whatever that is) and returns an array containing the input elements, but why would you want to do both those things at the same time?

comments