Is that really good idea when looking at the possibility of introducing bugs in the transpiler?
258 karma · joined August 11, 2013
Is that really good idea when looking at the possibility of introducing bugs in the transpiler?
I will not let them get away with this pricing model. Keeping my trusted Nokia 2700 :)
It's so fast now.
What we hate is jspm is extremely slow in development for us. There are two main causes:
- The amount of xhr. This is solvable with http2's server push (but
our dev server is in Ruby, and there's no http2 webserver yet).
- Apparently jspm doesn't cache the result of Babel's compilation,
so for each page refresh every file has to be recompiled again.
We will look at Webpack2 when it's released, if it allows us to use these legacy libraries and wins us some development speed we will not look back.As an outside watcher I have no clue (I am also stupid). Hopefully people working there have better insight than myself.
With Vim (or Emacs)... that's kind of obvious.
Gromia is an early stage startup aiming to digitalize home rentals and make agents a thing of the past. We are looking for a:
- Frontend Developer (https://www.gromia.com/jobs/frontend-developer)
If you apply mention you come from HN :)
irb
xs = %w(indian antichi ramen vietnamese bue pastificio)
xs[rand(xs.size))]
Otherwise we talked to one another.OTOH I will be able to use vim (or a fork of it) 20-30 years from now and become more and more productive with it during the timeframe.
Luckily I've been burned really early in my programming career by TextMate to know better: all my tools must be OSS and cross-platform.
if (check_cfunc(ci->me, rb_obj_equal)) { return rb_obj_equal(recv, obj); }
and trusting the compiler to inline rb_obj_equal (or using inline), although I reckon you don't probably want rb_obj_equal to always be inlined.
It was annoying to me because I worked on a application that did the same thing internally and where SDL was not a hard dependency. But well, it's not that bad as I make it sound.
If you can reproduce it, I'd love a bug report.
It always uses the BT.601 colormatrix to perform the YUV -> RGB colorspace conversion. While for HD material one should use the BT.709 colormatrix.
In practice you will notice darker reds that are closer to purple for this implementation error.
The switch changed from mplayer/mplayer2 and mpv uses the new hwaccel api where available (instead of the custom decoder).
The formula also builds `mpv.app`, I use that to open files directly from the Finder.
I think many distributions would consider mpv a duplicate of mplayer, so for one to be packaged officially the other would have to be removed. Realistically that's not going to happen anytime soon.
Minimalism is also something people are interested in. mpv has 1/5 the code of mplayer and 1/6 of VLC but still has relevant features.
They appeal to different kind of users. For example, even if I am in the mpv team, I will recommend VLC to my 'average Joe' friend as I know he would be put off by the CLI usage and config file editing.
mplayer still doesn't support mkv segment linking.