What's wrong with promises? Polyfills exist for older browsers. They're just a standardization of API callback mechanism, which has the added benefit of making them composable.
Would you prefer every library have its own way of handling asynchronous callbacks, errors, state and cancellation? And in that case, are you ok with having to write error-prone, ad-hoc code for using multiple such libraries together.
No. Promises make doing this trivial. Especially with typescript's async/await.
i just hope that companies like netflix will give a discount to those users that predominantly use their service over fair (un-classified) internet connections. this would help to promote fair & local ISPs over the likes of comcast & verizon.
but this is just plain false. netflix arranged a more efficient method to get its traffic to comcast, a method that would have been cheaper per bit for both of them. there's no reason for comcast to require additional payment, it just saw that its network wasn't going to be capable to handling the additional bandwidth and wanted to pass the blame/cost onto someone else.
the thing is that the "ISP" (ie comcast, etc...) is not the internet. it's just the end user's connection to the internet. the content providers (netflix etc...) have their OWN ISP which they're already paying. comcast wants the content providers to pay double.
IPMI has been a thing since the late 90's and similar proprietary systems existed long before that. ok, so now it's on-chip, but that doesn't change the fact that you should know about what traffic is on your LAN.
> So make the reverse argument and say, Windows runs in VirtualBox, so just run that on your Linux system if there's Windows stuff that is critical.
that would make perfect sense if 1) windows wasn't clearly the better desktop environment, and 2) linux wasn't more suited to virtualizing in a terminal.
imagine if you could run linux software on windows without having to run a virtualized kernel!
i think i must have answered "no" to the "do you want spamware?" question when i installed it, because i never see any ads. the only thing i get notified about is when security updates are ready to be installed.
the signal going down a coax is a capacitavely-coupled RF signal. the antenna's ground and the receiver/transmitted ground are completely independent. the similarities between this and audio gear go as far as "it's a copper wire", that's it.
Slashdot Mirror
> You can't have net neutrality in one state on a practical level to begin with
yes. you. can.
net neutrality is all about the last mile. and guess where that last mile is in Montana?
IT'S IN FUCKING MONTANA
100 million miles on one tank of gas!
The 'drag drop API' has NOTHING to do with JavaScript.
What's wrong with promises? Polyfills exist for older browsers. They're just a standardization of API callback mechanism, which has the added benefit of making them composable.
Would you prefer every library have its own way of handling asynchronous callbacks, errors, state and cancellation? And in that case, are you ok with having to write error-prone, ad-hoc code for using multiple such libraries together.
No. Promises make doing this trivial. Especially with typescript's async/await.
Typescript does exactly that, and more.
See typescript's a sync/await
Nobody's forcing them to do anything. They can stay outside dunk if they want.
Stalin was a liberal?
Lol!
i just hope that companies like netflix will give a discount to those users that predominantly use their service over fair (un-classified) internet connections. this would help to promote fair & local ISPs over the likes of comcast & verizon.
but this is just plain false. netflix arranged a more efficient method to get its traffic to comcast, a method that would have been cheaper per bit for both of them. there's no reason for comcast to require additional payment, it just saw that its network wasn't going to be capable to handling the additional bandwidth and wanted to pass the blame/cost onto someone else.
you pay comcast for your internet bandwidth. netflix pays its ISP for its internet bandwidth.
now for some reason comcast wants either you of netflix to pay them again? for what?
the thing is that the "ISP" (ie comcast, etc...) is not the internet. it's just the end user's connection to the internet. the content providers (netflix etc...) have their OWN ISP which they're already paying. comcast wants the content providers to pay double.
you can see the curvature of the earth from 6 feet above sea level. not to mention ships & planes transiting the horizon.
how is this even news? these limited time dev VMs have been available for eons.
you're a Sanders supporter? did you vote for the democratic candidate in the presidential election?
The 1996 act was an act of congress, introduced by a Republican, voted for almost unanimously by Republicans.
moral & political relativism, right there.
And he world is _flat_, damnit!
Not easily, you can't.
Meanwhile anyone with anything longer to say can just take a screenshot and tweet that.
What a bunch of fucking morons.
IPMI has been a thing since the late 90's and similar proprietary systems existed long before that. ok, so now it's on-chip, but that doesn't change the fact that you should know about what traffic is on your LAN.
> So make the reverse argument and say, Windows runs in VirtualBox, so just run that on your Linux system if there's Windows stuff that is critical.
that would make perfect sense if 1) windows wasn't clearly the better desktop environment, and 2) linux wasn't more suited to virtualizing in a terminal.
imagine if you could run linux software on windows without having to run a virtualized kernel!
i think i must have answered "no" to the "do you want spamware?" question when i installed it, because i never see any ads. the only thing i get notified about is when security updates are ready to be installed.
The problem with NASA printers is that while they're pretty cheap, the new ink cartridges are about $1,000,000 each.
nonsense.
the signal going down a coax is a capacitavely-coupled RF signal. the antenna's ground and the receiver/transmitted ground are completely independent. the similarities between this and audio gear go as far as "it's a copper wire", that's it.