If we can reduce the number of synaptic connections in the average human brain while we are working on improving the technology, we ought to get the two to meet much sooner than the few centuries that TFS predicts.
I'm just guessing here: It may be that sites which use Wordpress as a backend want to batch a bunch of requests together to reduce network connection overhead.
locked boot loaders like the MS Windows RT tablets
I suspect Microsoft will pull this one out of thir ass to force manufacturers to make the 'Windows only' vs 'Windows never' choice. And FUD will be invoked to let them know what happens to people who turn their back on the Beast from Redmond.
At some point, the ARM owners will sit down and calculate the lost opportunity cost Microsoft has caused them. And we'll have another round of Microsoft vs DoJ faceoff. The DoJ will take a fall in return for some more backdoors in Windows products.
Auto manufacturers have been told to limit NOx emissions to levels far below that produced by nature. So sure, they'll 'comply' with regulations written by a bunch of crazy hippies in California.
If what the greenies want is to eliminate cars, then why don't they just propose that law and get all the whining over with?
The number one tool of the developers pushing gentrification. The first Sound Transit light rail project cleaned the poor black people out of Rainier Valley. The next extension will push the hipsters out of the University District and Ravenna neighborhoods. Then it's northward, clearing the working class folks out of Northgate.
Meanwhile, King County Metro bus service is being eliminated where it parallels the rail lines. We don't want any stinkin' bus riding hobos in our shiny new neighborhoods.
A PE is an Engineer, but an Engineer doesn't have to be a PE.
Depends on the state in the USA. Not all states have an industrial exemption from licensing engineers working on their products.
Off topic somewhat: This raises interesting issues for designs produced in one jurisdiction (where the exemption exists) but manufactured in another (where the engineering must be produced by a licensed individual). One interesting example: Boeing designs aircraft in WA (which has an exemption) but manufactures them in SC (which does not).
The FCC's job is to manage the RF spectrum. And part of that involves thinking before making bad allocation decisions. It's one thing to fine a violator who has an operator's license as well as a site license at risk. These people are highly motivated not to incur penalties involving the loss of their livelihood. But to create an ISM band (unlicensed) where any hobbyist can solder together a contraption and then allow the FAA to utilize this for a safety critical application is just nuts.
But then, that's what ISM bands are for. And why it's the FAA's problem for hiring some morons to design their Doppler system. Their ability to do the R&D on these frequencies easily was bound to cause problems. And not just for WLANs, but anyone who expected to have access to spectrum for an RF development project. You can lock down WiFi, but that won't stop some completely unrelated application from stomping on weather radar. The only solution is to move TDWR to a licensed frequency.
Perhaps we should stop thinking that terraforming has to be modeled on properties of the earth alone. The question that needs to be answered: Why does Venus have a thick atmosphere and yet it also has a minimal magnetic field?
... this may be due, in part, to the ability to roll MAC addresses on WLAN devices. And the hissy fit that the NSA is throwing over the inability to track this as a unique identifier.
specific frequencies (channels 120, 124, 128) are prohibited in the U.S. and Canada
So, what do they do in the EU and the rest of the world to mitigate this problem?
Although it's too late to change now, how did these wizards allocate such a critical frequency band to unlicensed ISM use? What do we pay these clowns for anyway?
This works quite well when you're developing yet another web app.
Right. But that's a very small slice of the software development space. Lots of embedded applicatione don't even have the luxury of a real O/S. On the other hand, even with web apps (well designed ones) most of the interesting work is done by the time you get to where you can fling a few buzzwords at the APIs.
This can only happen at a point well along the development timeline. When you understand the functions and interfaces and have the data structures pretty well defined. Or you'll get groups that all say, "You people start coding and I'll go see what the customer needs."
If you split one big project into five smaller projects,
You will need someone to select the split points and manage the communications between the sub-projects. And when each is done, you'll have to integrate them and test the assembly. Not that this is necessarily bad. But that mangement layer adds complexity and overhead. Agile might work well in an environment where the sub-projects are just teams sitting in adjacent cubicles, working in the same organization. Where interface problems can be solved by grabbing a few people, finding a conference room with a white board and working things out. But not so well if the inter-project communications involves customer/vendor contractual negotiations. And management starts to get it's panties in a bunch over change orders.
In my experience, management is often selected based on the Dilbert Principle. Not the sort of people you want sitting at the nexus of the critical communications path between groups trying to get actual work done. Not to be totally down on Agile, it does formalize the inter-group communications, giving the PHBs well defined documents to rubber stamp and otherwise restricting their ability to invent new processes on the fly.
Slashdot Mirror
If we can reduce the number of synaptic connections in the average human brain while we are working on improving the technology, we ought to get the two to meet much sooner than the few centuries that TFS predicts.
MOST National Park land isn't anything that resembles wildnerness
My mistake. Wilderness areas and Washington DC both appear to be populated largely by bumps on logs. Sorry about that.
Why are insane amounts of passwords permitted?
I'm just guessing here: It may be that sites which use Wordpress as a backend want to batch a bunch of requests together to reduce network connection overhead.
besides my cock is much bigger than that pathetic little vienna sausage you call a penis
Oh yeah? (SFW)
Quick! Someone get over to Wikipedia and add a paragraph on this subject to the 'chicken' entry.
going too far down the rabbit hole.
Watch it there, buddy!
locked boot loaders like the MS Windows RT tablets
I suspect Microsoft will pull this one out of thir ass to force manufacturers to make the 'Windows only' vs 'Windows never' choice. And FUD will be invoked to let them know what happens to people who turn their back on the Beast from Redmond.
At some point, the ARM owners will sit down and calculate the lost opportunity cost Microsoft has caused them. And we'll have another round of Microsoft vs DoJ faceoff. The DoJ will take a fall in return for some more backdoors in Windows products.
Auto manufacturers have been told to limit NOx emissions to levels far below that produced by nature. So sure, they'll 'comply' with regulations written by a bunch of crazy hippies in California.
If what the greenies want is to eliminate cars, then why don't they just propose that law and get all the whining over with?
"Help! My owner has me trapped in these tight jeans!"
Build subways, railways, etc.
The number one tool of the developers pushing gentrification. The first Sound Transit light rail project cleaned the poor black people out of Rainier Valley. The next extension will push the hipsters out of the University District and Ravenna neighborhoods. Then it's northward, clearing the working class folks out of Northgate.
Meanwhile, King County Metro bus service is being eliminated where it parallels the rail lines. We don't want any stinkin' bus riding hobos in our shiny new neighborhoods.
I just scanned the articles and didn't see what sort of tank pressures these things use.
Also, do I have to use a tank of water? Or can I make my own as I go? One tank of LH2, one of LO2 .....
Bosch guys said it would be illegal to use this specific feature.
Forbidden!
A PE is an Engineer, but an Engineer doesn't have to be a PE.
Depends on the state in the USA. Not all states have an industrial exemption from licensing engineers working on their products.
Off topic somewhat: This raises interesting issues for designs produced in one jurisdiction (where the exemption exists) but manufactured in another (where the engineering must be produced by a licensed individual). One interesting example: Boeing designs aircraft in WA (which has an exemption) but manufactures them in SC (which does not).
The FCC's job is to literally fine violators
The FCC's job is to manage the RF spectrum. And part of that involves thinking before making bad allocation decisions. It's one thing to fine a violator who has an operator's license as well as a site license at risk. These people are highly motivated not to incur penalties involving the loss of their livelihood. But to create an ISM band (unlicensed) where any hobbyist can solder together a contraption and then allow the FAA to utilize this for a safety critical application is just nuts.
But then, that's what ISM bands are for. And why it's the FAA's problem for hiring some morons to design their Doppler system. Their ability to do the R&D on these frequencies easily was bound to cause problems. And not just for WLANs, but anyone who expected to have access to spectrum for an RF development project. You can lock down WiFi, but that won't stop some completely unrelated application from stomping on weather radar. The only solution is to move TDWR to a licensed frequency.
Perhaps we should stop thinking that terraforming has to be modeled on properties of the earth alone. The question that needs to be answered: Why does Venus have a thick atmosphere and yet it also has a minimal magnetic field?
specific frequencies (channels 120, 124, 128) are prohibited in the U.S. and Canada
So, what do they do in the EU and the rest of the world to mitigate this problem?
Although it's too late to change now, how did these wizards allocate such a critical frequency band to unlicensed ISM use? What do we pay these clowns for anyway?
"..... and that concludes my opening statement. You got a problem with that, punk?"
And I have the bumper sticker to prove it.
Because it's just a machine readable copy of the stuff already printed on your ticket in human-readable form.
retrieved from a remote (secured) system
Do you mean the systeme that's always down whenever they try to load an airplane?
At least they haven't stooped to using comfy chairs yet.
This works quite well when you're developing yet another web app.
Right. But that's a very small slice of the software development space. Lots of embedded applicatione don't even have the luxury of a real O/S. On the other hand, even with web apps (well designed ones) most of the interesting work is done by the time you get to where you can fling a few buzzwords at the APIs.
if you can break a project down into small parts
This can only happen at a point well along the development timeline. When you understand the functions and interfaces and have the data structures pretty well defined. Or you'll get groups that all say, "You people start coding and I'll go see what the customer needs."
If you split one big project into five smaller projects,
You will need someone to select the split points and manage the communications between the sub-projects. And when each is done, you'll have to integrate them and test the assembly. Not that this is necessarily bad. But that mangement layer adds complexity and overhead. Agile might work well in an environment where the sub-projects are just teams sitting in adjacent cubicles, working in the same organization. Where interface problems can be solved by grabbing a few people, finding a conference room with a white board and working things out. But not so well if the inter-project communications involves customer/vendor contractual negotiations. And management starts to get it's panties in a bunch over change orders.
In my experience, management is often selected based on the Dilbert Principle. Not the sort of people you want sitting at the nexus of the critical communications path between groups trying to get actual work done. Not to be totally down on Agile, it does formalize the inter-group communications, giving the PHBs well defined documents to rubber stamp and otherwise restricting their ability to invent new processes on the fly.
place multiple battery control under the duties of the operating system
No battery for you, Linux!