At some point 1:N becomes prohibitively expensive for the sender, but that doesn't mean that there is wasted work.
edit: To clarify, not really promoting the idea per say, just commenting on the proof of work statement.
963 karma · joined June 14, 2012
At some point 1:N becomes prohibitively expensive for the sender, but that doesn't mean that there is wasted work.
edit: To clarify, not really promoting the idea per say, just commenting on the proof of work statement.
> It looks like you’re using a browser we don’t support yet.
> To have a better experience in Webflow Designer we
> recommend using Google Chrome 62+ or Apple Safari 10.1+.
> You can still look around, but your changes will not be saved.
I'm on firefox and the whole things seems to be working just fine so not sure why you are giving me this message, but anyhow it doesn't speak well for your product if the output only works in select browsers.This is perhaps the best bang for your buck until you actually know what the bottlenecks are as it otherwise becomes a brute-force approach to "scale everything individually". Unfortunately "our code is ready to scale" doesn't quite sound as cool as "we run a thousand micro-services".
> Calling the Mac Mini “mini” is absurd in 2018.
doesn't make much sense. Mini is not an absolute unit of measurement, and the mac mini is still the smallest mac you can buy.The rest of it I agree with though and am patiently awaiting for a new mini or a better pro.
(I use native in quotation marks because we can probably not even agree on what that is.)
This attitude seems to be common here but everyone hating on electron seems to ignore any positive aspects of it and only focuses on the fact that it is slower and/or more resource intensive then had it been written in <native-language-of-choice>.
You can dislike Electron on a technical or principal level, that's fair, but until there is an alternative that would be considered better by most things will simply not change.
Until then, repeating the negatives over and over again only serves to de-value the efforts of those actually producing and shipping code and the only possible outcome is another "tabs vs spaces" holy war.
[1] https://ipfs.io
Was a good source of inspiration, sad to see it go nonetheless.
I've also done it through a cheap digital ocean instance but compilation speeds are much worse and running tests takes longer, but it's a bit easier to set up and try out I guess.
It takes a while to get a product to market and this would seem to answer most of the criticism the pro market has had with the mac pro so far, the macbook pro is a different beast.
I should add that the above is the main reason the kaby lake release is so lackluster. There is very little reason to upgrade your desktop to a 7 series (laptops get power optimization and 4k playback support).
It's also the main reason why AMD might look appealing, lack of worthwile upgrade from Intel while AMD delivers twice the cores/threads for not a gread deal more then a 7600K.
Maybe it's the way the timer is handled when computing the physics, since they would have to compute the deltas based on previous step and the timers in JS are not exact maybe they are producing slightly different deltas between frames accumulating to the difference.
The tracking wasn't great, but maybe that was intentional to illustrate a point.
I want my laptop to last 10h while being very portable, so I will gladly sacrifice performance there whereas when I am at my desktop I do not have the same limitation.
If I could simply unplug this from my desktop and plug into my laptop to resume my work that would be interesting to me, or work to home etc., but as is it feels more like a gimmick.
Every now and again I forget about the mess and try again and usually give up after a few days when I start remembering it all. I'm sure some people thrive in that kind of environment but I just need to get work done and when the OS gets in the way of that, it doesn't matter that "you just need to configure ..."