You didn't quite get the point I think. C is used for anything in industry, you'll be having a hard time finding a serious embedded programmer using JS for example. Inherently C allows cost effective implementation where JS doesn't stand a chance. But most of this type of use cases will never show up on github. As pointed out by others the dialects for PLCs and LabVIEW would rank pretty high if this was a true representation as well. VHDL and Verilog would also rank readonably high, but these are all use cases which are difficult to monitor. So yeah it is funny working in industry if you see these lists knowing they're heavily skewed towards hobbyists. IEEE did a fairly decent attempt though.
Our cable and PotS system in Belgium was originally built by the government (well one of our 7 governments...) and works like a charm. Reliable 200 Mbps connections!
This is why I still drag around my 2.6 kg ThinkPad on a daily basis, even after buying one of those ultra portables over half a year ago. In theory they sound fine, but the keyboard is too small to work on for any extended period of time, and the computing power is still quite limited since the battery life sucks so badly if you actually use it anyway. They also lack any sort of display connector typically, or it goes through the single USB port (and no hubs support this USB -> HDMI bullshit as far as I know) or god forbid WiDi which not a single projector seems to support. In the meanwhile my ThinkPad will run CAD software on battery for 4 hours and has an actual graphics card instead of a crappy on-board thing that chokes up on HD videos. enough ports for almost anything. And sure sometimes a piece of plastic breaks off the case, but at least it doesn't bend or twist constantly.
API description doesn't equal actual code though. So yeah this is a lot of drama for a list of supported functions and methods essentially. The majority of the work (the code behind the API) is still protected. So bugger off.
Not really, bittorent can run high latency so you can bundle and compress packets over busy links if you must. Stop thinking circuit style network about package switched networks. It's mostly a matter of strategic investments at the right points of the links, these investments aren't necessarily expensive. But companies like AT&T their actual product is asking their users to bend over while they run away with the money, not provide good connectivity. It's funny how this issue doesn't arise in countries where the local equivalent of the FCC wasn't chained and shackled by lobby groups.
Oh and on QoS, your argument is bullshit, all it does is increase latency if implemented correctly. No one notices a few extra milliseconds loading webpages or getting mail. Speed is maintained but realtime applications are given priority treatment (aka guaranteed delivery within a reasonable delay), as traffic isn't constant you can still get through more than enough data in most cases.
Yes there is, it's about DSL lines. Each subscriber has a unique twisted pair copper line to the PBX. The interference between the lines near the PBX is less of an issue these days because the cards (PBX end) got very good at canceling it out. From there on its fibre (or god forbid: microwave) for whatever network topology you use. Both are trivial to extend the capacity of, it's simply a matter of will. Or did we forget about that time a large US ISP refused to extend capacity claiming cost concerns, which proceeded in them getting laughed at in public by Level3? All they needed was an interface card of a few grand and a fibre patch cable of ten bucks. And this would have solved all netflix related congestion on their network. Before you continue your lame PR campaign for AT&T realise most of us do know network topology and what the congestion points are.
We both know this isn't due to lack of finances, but rather decades of mismanagement and lobying to permit such situations. The cost of the required hardware is quite minimal in the case of AT&T, it's only the will to do it that's missing. In the end its mostly the PBX end that needs upgrading if their excuse is valid, so it's not some insurmountable task. And caps don't solve this, if your network capacity is limited you lower speeds and use QoS based policies. (e.g. voip gets priority over your cat pictures.)
Learn the difference between peak load and subscribers times promised bandwith please. Aiming for sustained peak load simply means you statistically predict how much actual load you'll get for x customers at the busiest moments and you build for that +5% or +10% based on your datasource. This isn't exactly rockey science, every self respecting engineer can do these calculations. It simply requires you continuously monitor your network status and do preventative upgrades. You know there is even management software for ISPs that'll detect bottlenecks?
It shouldn't matter really, your network should be able to handle peak load without negative traffic routing interactions. This is just a sad (typically American I might add) company trying to improve its substantial profit margin by screwing over customers.
Nah you're related to them. Or you're a butt hurt app developer, either works.
You fail to grasp the difference between scooping up a dog's "business" and asking if you can throw it in the trash can or doing the same and then burying the trash can with a dump truck of shit. ES File Explorer isn't so great that it gets the right to be so abusive to their users WITHOUT WARNING. Especially the latter is completely unacceptable.
Believe it or not, some of us hate malware infecting phones that are used as communication devices and login authentication tools. So by all intense and purposes the developers became inconsiderate douchebags. In app adverts sure, but outside influences: NO!
Changes nothing to the principle. Again nothing spectacular to summarize it... I'll put it this way: I've seen EE students come up with the same principle multiple times, and using multiple frequencies is a common technique to limit errors due to propagation path differences in the environment. Will still bugger out around big fat metal objects though.
The only reason they get to call this an invention is because they're MIT... Phase detection/time of flight using multiple frequencies is nothing new; main limitation is the shitty clock most things have. Combined with the fact that you need fairly good signal chain components to do it properly. This system will still fuck up I'd guess when large metal objects come in play.
Meh, good engineers are confident at the very least...
However software engineers are the only exception to that. The funny bit then is that the closest related field (electronics) generally already is a huge difference. Was really noticeable in college: the IT engineering students were playing games on their laptop in the cafeteria while we were hanging out with the (mostly female) chemistry majors.
And then about the *hire more women* stereotype. Confidence is a major asset for technical staff anywhere, we have absolutely no use for people who are so afraid of making a mistake that they don't dare to do anything. Sadly this description fits many of the female engineers I've met, luckily not all. Keep in mind engineers are hired to push the technical limits and to lead a team of technicians generally, so start behaving like one and you might land a job and boyfriend / girlfriend at the same time.
Ah yes, but that's because you live in the US... If you let power companies decide it'll be less redundant, since redundancy costs money. That's privatisation for you, it still amazes me that such a large population consistently chooses what's worst for themselves.
It's fairly normal that faults on the high voltage distribution grid lead to this. Generators and high voltage transformers (of any type of plant) take months to replace.
And stop assuming that a plant just stops working immediately if there is an issue at the power generation side, the inertia of the turbine and generator gives you some response time. This is enough for the gas plant(s) on load balancing duty to go up to full power, and you can always inject steam in the gas turbines to squeeze out some extra power if you need it. This might cause a voltage drop from 230 to 220 volt during peak load moments, but gives you enough power to fire up the hydroelectric pumping stations. (Yes, you need a push from the grid to start those.)
A far more important factor in grid reliability is putting cables underground. Heavily reduces the risk of downtime due to weather conditions.
In a funny coincidence those deaths are included already, in an attempt of greenies to make nuclear look bad the forced the industry to include those numbers...
The economics for wind don't work out either once you include operational and (de)commisioning costs. And those for solar panels are based on some miss understandings. (e.g. unless we boost their efficiency CdTe will get displaced, and CdTe demand won't stay high forever). In the case of a well designed nuclear plant one could remove the reactor at the expected end-of-life and throw in a new one. But paranoid idiots such as yourself prevent us (the engineers who build these sort of things) from letting these plants reach their full potential. And then you go off shouting *zomgr inefficient!!!!!!!!!! Dangerous!!!!!111!!!1111"* (Yes, you do sound like that.) It's a sad reflection on reality that uninformed know-it-alls have so much influence.
Slashdot Mirror
You didn't quite get the point I think. C is used for anything in industry, you'll be having a hard time finding a serious embedded programmer using JS for example. Inherently C allows cost effective implementation where JS doesn't stand a chance. But most of this type of use cases will never show up on github. As pointed out by others the dialects for PLCs and LabVIEW would rank pretty high if this was a true representation as well. VHDL and Verilog would also rank readonably high, but these are all use cases which are difficult to monitor. So yeah it is funny working in industry if you see these lists knowing they're heavily skewed towards hobbyists. IEEE did a fairly decent attempt though.
It'd be useful if some jerks park next to you within a distance of 5 nanometer (like they always do) in a parking lot.
Our cable and PotS system in Belgium was originally built by the government (well one of our 7 governments...) and works like a charm. Reliable 200 Mbps connections!
An idiot seeking cruise missile would also work, but we'd need to build a hell of a lot of those things :)
This is why I still drag around my 2.6 kg ThinkPad on a daily basis, even after buying one of those ultra portables over half a year ago. In theory they sound fine, but the keyboard is too small to work on for any extended period of time, and the computing power is still quite limited since the battery life sucks so badly if you actually use it anyway. They also lack any sort of display connector typically, or it goes through the single USB port (and no hubs support this USB -> HDMI bullshit as far as I know) or god forbid WiDi which not a single projector seems to support. In the meanwhile my ThinkPad will run CAD software on battery for 4 hours and has an actual graphics card instead of a crappy on-board thing that chokes up on HD videos. enough ports for almost anything. And sure sometimes a piece of plastic breaks off the case, but at least it doesn't bend or twist constantly.
API description doesn't equal actual code though. So yeah this is a lot of drama for a list of supported functions and methods essentially. The majority of the work (the code behind the API) is still protected. So bugger off.
Not really, bittorent can run high latency so you can bundle and compress packets over busy links if you must. Stop thinking circuit style network about package switched networks. It's mostly a matter of strategic investments at the right points of the links, these investments aren't necessarily expensive. But companies like AT&T their actual product is asking their users to bend over while they run away with the money, not provide good connectivity. It's funny how this issue doesn't arise in countries where the local equivalent of the FCC wasn't chained and shackled by lobby groups.
Oh and on QoS, your argument is bullshit, all it does is increase latency if implemented correctly. No one notices a few extra milliseconds loading webpages or getting mail. Speed is maintained but realtime applications are given priority treatment (aka guaranteed delivery within a reasonable delay), as traffic isn't constant you can still get through more than enough data in most cases.
Yes there is, it's about DSL lines. Each subscriber has a unique twisted pair copper line to the PBX. The interference between the lines near the PBX is less of an issue these days because the cards (PBX end) got very good at canceling it out. From there on its fibre (or god forbid: microwave) for whatever network topology you use. Both are trivial to extend the capacity of, it's simply a matter of will. Or did we forget about that time a large US ISP refused to extend capacity claiming cost concerns, which proceeded in them getting laughed at in public by Level3? All they needed was an interface card of a few grand and a fibre patch cable of ten bucks. And this would have solved all netflix related congestion on their network. Before you continue your lame PR campaign for AT&T realise most of us do know network topology and what the congestion points are.
We both know this isn't due to lack of finances, but rather decades of mismanagement and lobying to permit such situations. The cost of the required hardware is quite minimal in the case of AT&T, it's only the will to do it that's missing. In the end its mostly the PBX end that needs upgrading if their excuse is valid, so it's not some insurmountable task. And caps don't solve this, if your network capacity is limited you lower speeds and use QoS based policies. (e.g. voip gets priority over your cat pictures.)
Learn the difference between peak load and subscribers times promised bandwith please. Aiming for sustained peak load simply means you statistically predict how much actual load you'll get for x customers at the busiest moments and you build for that +5% or +10% based on your datasource. This isn't exactly rockey science, every self respecting engineer can do these calculations. It simply requires you continuously monitor your network status and do preventative upgrades. You know there is even management software for ISPs that'll detect bottlenecks?
It shouldn't matter really, your network should be able to handle peak load without negative traffic routing interactions. This is just a sad (typically American I might add) company trying to improve its substantial profit margin by screwing over customers.
Those perform automatic face lifting and eye lid modification surgeries.
Learn2BuckBoost stupid vapers
Nah you're related to them. Or you're a butt hurt app developer, either works. You fail to grasp the difference between scooping up a dog's "business" and asking if you can throw it in the trash can or doing the same and then burying the trash can with a dump truck of shit. ES File Explorer isn't so great that it gets the right to be so abusive to their users WITHOUT WARNING. Especially the latter is completely unacceptable.
Believe it or not, some of us hate malware infecting phones that are used as communication devices and login authentication tools. So by all intense and purposes the developers became inconsiderate douchebags. In app adverts sure, but outside influences: NO!
Changes nothing to the principle. Again nothing spectacular to summarize it ... I'll put it this way: I've seen EE students come up with the same principle multiple times, and using multiple frequencies is a common technique to limit errors due to propagation path differences in the environment. Will still bugger out around big fat metal objects though.
The only reason they get to call this an invention is because they're MIT... Phase detection/time of flight using multiple frequencies is nothing new; main limitation is the shitty clock most things have. Combined with the fact that you need fairly good signal chain components to do it properly. This system will still fuck up I'd guess when large metal objects come in play.
Meh, good engineers are confident at the very least ...
However software engineers are the only exception to that. The funny bit then is that the closest related field (electronics) generally already is a huge difference. Was really noticeable in college: the IT engineering students were playing games on their laptop in the cafeteria while we were hanging out with the (mostly female) chemistry majors.
And then about the *hire more women* stereotype. Confidence is a major asset for technical staff anywhere, we have absolutely no use for people who are so afraid of making a mistake that they don't dare to do anything. Sadly this description fits many of the female engineers I've met, luckily not all. Keep in mind engineers are hired to push the technical limits and to lead a team of technicians generally, so start behaving like one and you might land a job and boyfriend / girlfriend at the same time.
Ah yes, but that's because you live in the US... If you let power companies decide it'll be less redundant, since redundancy costs money. That's privatisation for you, it still amazes me that such a large population consistently chooses what's worst for themselves.
It's fairly normal that faults on the high voltage distribution grid lead to this. Generators and high voltage transformers (of any type of plant) take months to replace. And stop assuming that a plant just stops working immediately if there is an issue at the power generation side, the inertia of the turbine and generator gives you some response time. This is enough for the gas plant(s) on load balancing duty to go up to full power, and you can always inject steam in the gas turbines to squeeze out some extra power if you need it. This might cause a voltage drop from 230 to 220 volt during peak load moments, but gives you enough power to fire up the hydroelectric pumping stations. (Yes, you need a push from the grid to start those.) A far more important factor in grid reliability is putting cables underground. Heavily reduces the risk of downtime due to weather conditions.
Are you certain it's not built into the author?
In a funny coincidence those deaths are included already, in an attempt of greenies to make nuclear look bad the forced the industry to include those numbers...
No, the intake is big to lower the velocity of the water.
The economics for wind don't work out either once you include operational and (de)commisioning costs. And those for solar panels are based on some miss understandings. (e.g. unless we boost their efficiency CdTe will get displaced, and CdTe demand won't stay high forever). In the case of a well designed nuclear plant one could remove the reactor at the expected end-of-life and throw in a new one. But paranoid idiots such as yourself prevent us (the engineers who build these sort of things) from letting these plants reach their full potential. And then you go off shouting *zomgr inefficient!!!!!!!!!! Dangerous!!!!!111!!!1111"* (Yes, you do sound like that.) It's a sad reflection on reality that uninformed know-it-alls have so much influence.