vmasto

12 ms·

61.
by vmasto 9y ago
For front-end development some strong options in different languages are: Elm, TypeScript, Reason, Coffeescript (although Coffeescript usage has fallen dramatically every since the newer versions of JavaScript added a lot of its great featu
62.
by vmasto 9y ago
I was very intrigued by the title: Things nobody will tell you about React.js Immediately had high hopes that someone is going to try and give a well researched, novel critique that maybe can spur out some constructive conversation. And t
63.
by vmasto 9y ago
Unfortunately, I don't think it's fair to call Edge evergreen. Updates to Edge come via OS updates, which can be quite a hassle and many corporate environments might not perform at a regular basis. This article goes into more dept
64.
by vmasto 9y ago
Or wait until JavaScript gets arbitrary precision ints which is not unreasonably far away I would reckon (less than a year most probably).
65.
by vmasto 9y ago
Some of the API semantics are changing, e.g. componentWillMount can't be trusted any more (it can fire many times) but they're going to be pretty small.
66.
by vmasto 9y ago
Or the dedicated website on Fiber's progress. http://isfiberreadyyet.com/
67.
by vmasto 9y ago
The best way sure, not the only or even most popular way though.
68.
by vmasto 9y ago
:) Yeah, unfortunately JavaScript can only be improved by educating people not to use the horrible parts (rather than fixing/deprecating them which is not possible). const and let were extremely necessary.
69.
by vmasto 9y ago
For anyone interested and isn't aware yet Facebook is developing Reason, a layer over OCaml. I've been fiddling with it for the past couple of weeks and coming from JavaScript I personally found the experience generally enjoyable.
70.
by vmasto 9y ago
Interesting. I'd be interested in the maintenance strategies you have in place (if any). I assume that for plugins who don't output styles or scripts you use other methods, maybe some HTML output etc, so you've probably hard
71.
by vmasto 9y ago
Interesting, thanks Dan.
72.
by vmasto 9y ago
As long as we are extremely clear of the implications it's a good enough reasoning. Many people, especially newcomers, believe that just because their code initializes a class only N times it's being instanced exactly N times. Thi
73.
by vmasto 9y ago
Isn't this true for pretty much anyone that hasn't actually experienced it? It's not like you can describe it exactly, I've seen a lot of "the most accurate description of depression"s that really hit home, but
74.
by vmasto 9y ago
I recall the React team were discussing at what part of the build step they should include Prettier. I believe there was an idea of adding it as a pre-commit hook, a second one as a manual step and another one as a post-commit amend. Have w
75.
by vmasto 9y ago
> Users can place one tile every 5 minutes, so we must support an average update rate of 100,000 tiles per 5 minutes (333 updates/s). It only takes a couple of outliers to bring everything down. I'm not exactly well-versed in d
76.
by vmasto 9y ago
I've been trying to test audio and video with headless browsers (namely PhantomJS) but have experienced extreme difficulty, I wonder if headless Chrome is able to support/supports already HTMLAudioElement or HTMLVideoElement or an
77.
by vmasto 9y ago
I have to ask the obvious, Flow vs TypeScript. I'm sure as React users you took your time weighing the two; care to comment on what drove your final decision?
78.
by vmasto 9y ago
Although I don't use TypeScript (I'm looking at Flow more and more recently instead) I have to acknowledge Microsoft's huge contribution to the JS scene (and not only) with TS and VSCode, truly exceptional products. What&#x27
79.
by vmasto 9y ago
I'm not saying it doesn't, it's built on Chromium Embedded Framework. The author is claiming it's built on Electron, which is false.
80.
by vmasto 9y ago
I'll give it a go to call you on "bullshit": Spotify is not built on Electron. (Surprise, the author is wrong). It is and was, however, always built on Chromium Embedded Framework (the UI), even when you say it "was&quot
81.
by vmasto 9y ago
> I wanted to pick on Spotify and Atom more in my blog post, but both Spotify and Atom have cleaned up their act Can you please share how you came to the conclusion that Spotify is made with Electron? (hint: it's not)
82.
by vmasto 9y ago
I was under the impression that the pentagons would be 12, care to elaborate how it's only one? e.g. http://math.stackexchange.com/questions/2121175/is-it-possib...
83.
by vmasto 10y ago
That statement is highly uninformed. I would suggest starting reading from here https://github.com/WebAssembly/design/blob/master/FAQ.md#is-...
84.
by vmasto 10y ago
I find it extremely telling that both of the issues you linked are now included in the core language library, and what happened with left-pad will never happen again after amends were made by npm to make sure that it indeed never does. If y
85.
by vmasto 10y ago
Thankfully Yarn is here to solve most (if not all) of these problems.
86.
by vmasto 10y ago
As a (kind of) related matter, thought it'd be interesting to mention JavaScript is most likely getting arbitrary precision ints soon https://github.com/tc39/proposal-integer
87.
by vmasto 10y ago
I got extremely worried as well and it wouldn't have made a difference looking at the altimeter because I have no idea about how rocket engines behave.
88.
by vmasto 10y ago
That's very weird, does anyone have any insight about this decision on a technical level?
89.
by vmasto 10y ago
> The promise is simple and compelling: write once, ship twice. iOS and Android all in one shot While this is certainly feasible (largely depending on the requirements of your app), it is important to clarify that RN never promised &quot
90.
by vmasto 10y ago
Note that this data excludes the vast majority of Chinese software engineers (they represent just 0.4666% of the total survey responders)

More ›