Sensors aren't omnipotent. They can't see around obstructions any better than humans can, although some things that are obstructions to humans aren't to sensors. Still, if someone hides behind a parked car and then jumps into traffic, no sensors on the vehicle are going to spot them. The only hope is that they get a warning from a vehicle ahead, who saw the person as that preceding vehicle passed.
It doesn't. Those paths are as wide as two traffic lanes. They look like they're there so that maintenance crews can get around, and also to be able to get their vehicles out of the road.
I find that really cheap electrical tape (dollar store stuff) is ideal for this. It's thin enough that some light leaks through, meaning you can tell the light is on by looking, but won't see it otherwise. I use it for the blue status LEDs that seem to be mandated by some sadistic standards organization for use on laptops and monitors. Better quality tape will work too, if you poke a pinhole through it first.
The adhesive on gaffer tape will dry out and leave a horrible mess in a matter of months to a couple years. Gaffer tape is intended for temporary rigging only, and you will get undesirable results attempting to use it long-term for anything. It's not even good for covering up gaps in the covers of black instrument cases. In the short term it works fine, but in the long term it makes the problem considerably worse by falling off and leaving a crumbly white patch where it used to be. Exposure to heat greatly accelerates this process -- if you were to use gaffer tape to patch torn upholstery in a car that gets parked outdoors, you could expect it to fail in as little as a few weeks.
It's never been convincing, since anyone can simply trade battery life for illicit cargo capacity. Instead of a nine-cell battery, you can have a three cell battery and 1/3 the run time -- but the machine will still operate just fine for that shorter time. The space formerly occupied by the other six cells can be filled with whatever you like. The risk has gone down over time as the machines get smaller and smaller, thus leaving less space to substitute contents.
If they go over 300 phones, they have to buy a second batch. If they exceed 600, they'll spring for an unlimited package and the incremental cost of cracking a phone will go away. Or, they'll throw in with their county or nearby cities and operate out of a single unlimited account. $30,000 a year is not a large amount for a police force. That's less than two cars (they pay about $20k a car) and quite a bit less than the cost of one employee for that same year.
The only reason for buying the smaller package is that they don't see a need for more than 300 uses in the next 12 months -- this time.
I ran GalliumOS + WINE when I had a GNAWTY. I was also the tester for the initial attempts to run Windows on Bay Trail. Actually, we succeeded, but performance was so incredibly horrible that it was unusable. I ended up selling that off, and buying the (4GB) C720 for only $21 more than I got for the CB3-111. Then I dropped another $80 for a fast 250GB M.2 SSD.
Windows support for the Bay Trail Chromebooks has matured a great deal in the past year and a half, enough that it runs about as well as could be expected for a machine with 2GB of RAM. I still wouldn't go back.
I'd rather flash the firmware and then install Cloud Ready, Windows, and GalliumOS. Or at least I would if I cared that much about CrOS. My C720 practically always runs Windows 10, booting into GalliumOS only when I need to unfuck something Windows won't let me unfuck.
Talking about music is great for those people who already understand the subject. You can of course convey the subjective reactions people have had to the music, such as the riots after the debut of The Rite of Spring, but can text alone convey why it caused this reaction? If you already know the piece, then maybe you don't need snippets of the music. But if you've never heard it before, and you're not a musician, words alone aren't going to get you there.
It depends on the subject. While descriptive text almost always helps, talking about music (without actually allowing the reader to hear any) is like dancing about architecture.
QB64 is not Microsoft's product, and frankly I wouldn't want it to be. Their current development practices are rather messy and non-optimal, but they're getting results.When I filed a bug report, they asked me to help define what the correct behavior should be and to help test the fix, which came inside of two weeks. Not only did they enable proper support for stereo sound (it had been getting downmixed to mono due to a poorly written routine), they decided to really fix it and implement full surround sound with an arbitrary number of channels -- because they knew someone would ask, even if I personally only wanted stereo to work. When I filed a report of missing functionality, they disagreed that it qualified as such but implemented it anyhow because I was able to demonstrate how it would make certain operations much simpler to perform. I don't think I would have gotten either of those results from Microsoft.
As for the disadvantage of not being bundled in the OS, merely having enough exposure that people check things out on their own is a serviceable substitute.
I bet it will be pretty good in some contexts, and most likely an improvement overall compared to content-aware fills. However, when it completely falls on its face I bet it will be even funnier than the way content-aware fill blows up. Lower rate of occurrence, but much more hilarity when it happens.
The entire summary is about how using a computer has gotten much easier, widening the gap between users and programmers.
If someone just wants to learn to program, they shouldn't have to learn system administration first.
Yes, they should, if only to know where the hell they're writing their output files.
If someone just wants to learn to program, they shouldn't have to learn operating system concepts first.
Yes, they should, because computers multitask now and a program simply cannot be allowed to stomp all over the operating environment as it could in the DOS days.
For someone who grew up with a Commodore 64, learning to program was hard enough. For someone growing up with a cloud-connected mobile device, it is much harder.
No, it's not. It's that the population of computer users has widened enormously while the population of people that want to program has not widened by the same ratio. It's exactly as hard to learn to program now as it was then -- you can just program vintage hardware or emulations thereof if that's the point. Or you can write in QB64, which is no harder than Qbasic was and in many cases is far easier.
By the time we're building a Dyson sphere (or more likely, a Dyson swarm), we should be able to cannibalize the planet Mercury. It's basically just an iron-nickel core with most of the rock blasted away.
Slashdot Mirror
Sensors aren't omnipotent. They can't see around obstructions any better than humans can, although some things that are obstructions to humans aren't to sensors. Still, if someone hides behind a parked car and then jumps into traffic, no sensors on the vehicle are going to spot them. The only hope is that they get a warning from a vehicle ahead, who saw the person as that preceding vehicle passed.
It doesn't. Those paths are as wide as two traffic lanes. They look like they're there so that maintenance crews can get around, and also to be able to get their vehicles out of the road.
And how do you propose forcing someone to confront their biases? Like this?
MCM is best buddies with Paul Manafort.
https://therealdeal.com/2017/08/31/meet-paul-manaforts-real-estate-fixer/
Also, AvE has detailed the hive mind verdict: The smoking gun.
We'll always have his brilliant career as a gangsta rapper.
L@N would have been better and non-colliding.
I find that really cheap electrical tape (dollar store stuff) is ideal for this. It's thin enough that some light leaks through, meaning you can tell the light is on by looking, but won't see it otherwise. I use it for the blue status LEDs that seem to be mandated by some sadistic standards organization for use on laptops and monitors. Better quality tape will work too, if you poke a pinhole through it first.
The adhesive on gaffer tape will dry out and leave a horrible mess in a matter of months to a couple years. Gaffer tape is intended for temporary rigging only, and you will get undesirable results attempting to use it long-term for anything. It's not even good for covering up gaps in the covers of black instrument cases. In the short term it works fine, but in the long term it makes the problem considerably worse by falling off and leaving a crumbly white patch where it used to be. Exposure to heat greatly accelerates this process -- if you were to use gaffer tape to patch torn upholstery in a car that gets parked outdoors, you could expect it to fail in as little as a few weeks.
It's never been convincing, since anyone can simply trade battery life for illicit cargo capacity. Instead of a nine-cell battery, you can have a three cell battery and 1/3 the run time -- but the machine will still operate just fine for that shorter time. The space formerly occupied by the other six cells can be filled with whatever you like. The risk has gone down over time as the machines get smaller and smaller, thus leaving less space to substitute contents.
If they go over 300 phones, they have to buy a second batch. If they exceed 600, they'll spring for an unlimited package and the incremental cost of cracking a phone will go away. Or, they'll throw in with their county or nearby cities and operate out of a single unlimited account. $30,000 a year is not a large amount for a police force. That's less than two cars (they pay about $20k a car) and quite a bit less than the cost of one employee for that same year.
The only reason for buying the smaller package is that they don't see a need for more than 300 uses in the next 12 months -- this time.
If you're looking for truth in Constantinople, it'll be waiting in Istanbul.
Wonder Showzen already went there.
Great news, everybody! Letter N is out of rehab.
First Lady of the Night
I ran GalliumOS + WINE when I had a GNAWTY. I was also the tester for the initial attempts to run Windows on Bay Trail. Actually, we succeeded, but performance was so incredibly horrible that it was unusable. I ended up selling that off, and buying the (4GB) C720 for only $21 more than I got for the CB3-111. Then I dropped another $80 for a fast 250GB M.2 SSD.
Windows support for the Bay Trail Chromebooks has matured a great deal in the past year and a half, enough that it runs about as well as could be expected for a machine with 2GB of RAM. I still wouldn't go back.
I'd rather flash the firmware and then install Cloud Ready, Windows, and GalliumOS. Or at least I would if I cared that much about CrOS. My C720 practically always runs Windows 10, booting into GalliumOS only when I need to unfuck something Windows won't let me unfuck.
Disney would prefer to forbid Redbox from buying the discs at all, but haven't yet come up with a method for doing so.
Talking about music is great for those people who already understand the subject. You can of course convey the subjective reactions people have had to the music, such as the riots after the debut of The Rite of Spring, but can text alone convey why it caused this reaction? If you already know the piece, then maybe you don't need snippets of the music. But if you've never heard it before, and you're not a musician, words alone aren't going to get you there.
It depends on the subject. While descriptive text almost always helps, talking about music (without actually allowing the reader to hear any) is like dancing about architecture.
QB64 is not Microsoft's product, and frankly I wouldn't want it to be. Their current development practices are rather messy and non-optimal, but they're getting results.When I filed a bug report, they asked me to help define what the correct behavior should be and to help test the fix, which came inside of two weeks. Not only did they enable proper support for stereo sound (it had been getting downmixed to mono due to a poorly written routine), they decided to really fix it and implement full surround sound with an arbitrary number of channels -- because they knew someone would ask, even if I personally only wanted stereo to work. When I filed a report of missing functionality, they disagreed that it qualified as such but implemented it anyhow because I was able to demonstrate how it would make certain operations much simpler to perform. I don't think I would have gotten either of those results from Microsoft.
As for the disadvantage of not being bundled in the OS, merely having enough exposure that people check things out on their own is a serviceable substitute.
You keep using that word. I do not think it means what you think it means.
I bet it will be pretty good in some contexts, and most likely an improvement overall compared to content-aware fills. However, when it completely falls on its face I bet it will be even funnier than the way content-aware fill blows up. Lower rate of occurrence, but much more hilarity when it happens.
It took a while, but you have QB64.
The entire summary is about how using a computer has gotten much easier, widening the gap between users and programmers.
Yes, they should, if only to know where the hell they're writing their output files.
Yes, they should, because computers multitask now and a program simply cannot be allowed to stomp all over the operating environment as it could in the DOS days.
No, it's not. It's that the population of computer users has widened enormously while the population of people that want to program has not widened by the same ratio. It's exactly as hard to learn to program now as it was then -- you can just program vintage hardware or emulations thereof if that's the point. Or you can write in QB64, which is no harder than Qbasic was and in many cases is far easier.
By the time we're building a Dyson sphere (or more likely, a Dyson swarm), we should be able to cannibalize the planet Mercury. It's basically just an iron-nickel core with most of the rock blasted away.