A "typical marginal cost curve" is anything but typical. Nobody builds a factory that runs at peak efficiency when it's half full. No firm has a cost structure that matches your Econ 101 text book.
I highly recommend the work of Steve Keen in this area if you want to know more.
Ah, "risk averse". Such a stupid concept when it comes to financial advice. The better way to plan a portfolio, is making sure you can meet your short to medium term cash needs without being forced to sell any long term investments if they temporarily turn south.
Distressed selling is the worst thing that can happen to your portfolio, and you should plan ahead to make sure you can avoid it as much as possible.
Forcing every developer in the same office to separately download a complete copy of the full history is inefficient. But then git does have a way to reference objects files from another path.
For large (but probably not Windows large) git repos, you could add a "git alternate" reference to a network share for your ancient history. So long as you are careful in how you manage that folder, and never remove anything from it, this can work quite well.
Giving each team a low latency, local mirror of this folder would be enough for many use cases.
So run your own streaming server and keep everything at home. Plex is fairly easy to setup.
It's not too hard to automate ripping DVD's so the only user intervention required is swapping discs. Then you can use software like FileBot to organise everything consistently. But getting episode numbers of TV show DVD's right is a fiddly process.
By not paying NBNco enough of their CVC charge. IMHO the CVC charge should be abolished. NBNco are building a fiber network that should be able to cope with future speed requirements. But they are price gouging everyone, and treating that bandwidth as a scarce resource.
Seriously? You have no idea how fork actually works.
fork() exploits the MMU by marking every page in the parent process as readonly, then sharing these pages with the child process. There is no immediate copying of memory.
Then whenever *either* process attempts to write to any of these pages of memory, the kernel will trap & duplicate the page before allowing the write to occur.
fork() is pretty quick. But you have to be careful to pre-initialise as much immutable state in memory as you can, then keep your mutable state centralised.
fork()-ing a new browser tab from a pre-initialised process may save you a lot of startup time. But if you then go and write small values all over the place, you could easily lose a lot of those gains.
Everyone likes to obsess over the government's debts. But it is the debts of private citizens that should be your biggest concern.
During a boom, tax receipts go up and welfare payments go down. So the government debt can be reduced. If you want to blame the government for something, blame them for not saving during recent booms.
Now we are in a slump. Tax receipts will be down, welfare payments up. The government *should* be spending (responsibly...) to cushion the blow, but they actually have little choice in the matter. Austerity policies now would be a huge mistake. Taking money out of circulation, when the flow of money in the economy is already reduced, will just make a bad problem worse.
Many IOT devices have some kind of incoming data stream from the internet so that you can control them from your phone. This might be is via some company run cloud service, with questionable security.
it's a device that infringes my copyright, gives you root access in response to trivial credentials, has access control that depends entirely on nobody ever looking at the packets, is sufficiently poorly implemented that you can crash both it and the bulbs, has a cloud access protocol that has no security whatsoever and also acts as an easy mechanism for people to circumvent your network security
You could probably build a new initramfs and install a key logger there to capture the encryption password. But if you have console access to the machine while it's booting you could probably do that anyway by removing and reinstalling the boot disk.
This pre-existing bug was at worst a rare memory leak. Something that most systems could ignore for a very long time before it became a problem. Logging a warning & letting the memory leak happen is bearable in this case.
I'm not wrong, I didn't say hashes. Sure modern AV software is using more complex heuristics, but it's still just blacklisting known patterns of "bad code".
The standard Steam refund policy applies to No Man's Sky. There are no special exemptions available. Click here for more detail on the Steam refund policy.
It's a bad sign when they have to remind you of their refund policy. I bet their support system is completely overloaded with complaints, asking for a refund.
As far as I can see from available information, the HoloLens has a focal distance somewhere around 2 meters away from your face.
Whereas in a "true" hologram, you capture the interference patterns of all light rays that pass through the volume of your photo sensitive film. Shining a laser through that film will recreate light rays with the same direction and intensity. As if you were looking through a window at the original scene.
exploiting software doesn't even rank among the top five plays in the attacker's playbook
Only *because* you've been "Playing whack-a-mole with software vulnerabilities". If you stop applying patches, using exploits would be more productive.
Activities and Views are fine, I guess. But forcing serialisation of state between screen rotations sucks. A good presenter model with lifecycle management, baked in from the start, would have been nice.
IMHO Google made things worse with Fragments. If you follow the code examples, you end up repeating yourself with lots of nearly empty Activities, just to host your fragments on a phone instead of a tablet.
In previous years, they had been quite careful to inform people to pre-fill their form before census night, and submit after. This year they were expecting only a minor increase in peak traffic.
Then they go and blast the message, "Fill in your form online, ontime or face massive fines", all over the media.
So what did we all do? When the majority of 9-5 workers got home, we all tried to login and submit at about the same time.
Sure they screwed up their network config, but it was a combination of poor planning and poor communication that triggered the whole mess.
Slashdot Mirror
MR=MC, maximum efficiency.
Bullshit. Utter, utter crap. Mathematically false. Empirically false.
A "typical marginal cost curve" is anything but typical. Nobody builds a factory that runs at peak efficiency when it's half full. No firm has a cost structure that matches your Econ 101 text book.
I highly recommend the work of Steve Keen in this area if you want to know more.
Ah, "risk averse". Such a stupid concept when it comes to financial advice. The better way to plan a portfolio, is making sure you can meet your short to medium term cash needs without being forced to sell any long term investments if they temporarily turn south.
Distressed selling is the worst thing that can happen to your portfolio, and you should plan ahead to make sure you can avoid it as much as possible.
Forcing every developer in the same office to separately download a complete copy of the full history is inefficient. But then git does have a way to reference objects files from another path.
For large (but probably not Windows large) git repos, you could add a "git alternate" reference to a network share for your ancient history. So long as you are careful in how you manage that folder, and never remove anything from it, this can work quite well.
Giving each team a low latency, local mirror of this folder would be enough for many use cases.
So run your own streaming server and keep everything at home. Plex is fairly easy to setup.
It's not too hard to automate ripping DVD's so the only user intervention required is swapping discs. Then you can use software like FileBot to organise everything consistently. But getting episode numbers of TV show DVD's right is a fiddly process.
... with all participating ISPs competing ...
By not paying NBNco enough of their CVC charge. IMHO the CVC charge should be abolished. NBNco are building a fiber network that should be able to cope with future speed requirements. But they are price gouging everyone, and treating that bandwidth as a scarce resource.
All managed by a python script to download, install & switch whenever you want. https://github.com/RoliSoft/WSL-Distribution-Switcher
Seriously? You have no idea how fork actually works.
fork() exploits the MMU by marking every page in the parent process as readonly, then sharing these pages with the child process. There is no immediate copying of memory.
Then whenever *either* process attempts to write to any of these pages of memory, the kernel will trap & duplicate the page before allowing the write to occur.
fork() is pretty quick. But you have to be careful to pre-initialise as much immutable state in memory as you can, then keep your mutable state centralised.
fork()-ing a new browser tab from a pre-initialised process may save you a lot of startup time. But if you then go and write small values all over the place, you could easily lose a lot of those gains.
users aren't streaming YouTube music for hours in a row
Actually, some users are. (eg)
Everyone likes to obsess over the government's debts. But it is the debts of private citizens that should be your biggest concern.
During a boom, tax receipts go up and welfare payments go down. So the government debt can be reduced. If you want to blame the government for something, blame them for not saving during recent booms.
Now we are in a slump. Tax receipts will be down, welfare payments up. The government *should* be spending (responsibly...) to cushion the blow, but they actually have little choice in the matter. Austerity policies now would be a huge mistake. Taking money out of circulation, when the flow of money in the economy is already reduced, will just make a bad problem worse.
Many IOT devices have some kind of incoming data stream from the internet so that you can control them from your phone. This might be is via some company run cloud service, with questionable security.
For example,
it's a device that infringes my copyright, gives you root access in response to trivial credentials, has access control that depends entirely on nobody ever looking at the packets, is sufficiently poorly implemented that you can crash both it and the bulbs, has a cloud access protocol that has no security whatsoever and also acts as an easy mechanism for people to circumvent your network security
music permeates almost every aspect of my life
Sure, but you can tune it out to get on with life. Games generally require all of your attention.
You could probably build a new initramfs and install a key logger there to capture the encryption password. But if you have console access to the machine while it's booting you could probably do that anyway by removing and reinstalling the boot disk.
The Unicode consortium should have published glyphs like these as part of the effort of defining the standard.
Why did it take a separate private company to do this?
This pre-existing bug was at worst a rare memory leak. Something that most systems could ignore for a very long time before it became a problem. Logging a warning & letting the memory leak happen is bearable in this case.
I'm not wrong, I didn't say hashes. Sure modern AV software is using more complex heuristics, but it's still just blacklisting known patterns of "bad code".
Antivirus software is merely a curated blacklist of known bad code. It can't do anything about newly designed bad code.
Exactly what kind of credentials?
Meanwhile the Fairphone is a modular android phone, with end user replaceable parts that exists today.
The standard Steam refund policy applies to No Man's Sky. There are no special exemptions available. Click here for more detail on the Steam refund policy.
It's a bad sign when they have to remind you of their refund policy. I bet their support system is completely overloaded with complaints, asking for a refund.
As far as I can see from available information, the HoloLens has a focal distance somewhere around 2 meters away from your face.
Whereas in a "true" hologram, you capture the interference patterns of all light rays that pass through the volume of your photo sensitive film. Shining a laser through that film will recreate light rays with the same direction and intensity. As if you were looking through a window at the original scene.
exploiting software doesn't even rank among the top five plays in the attacker's playbook
Only *because* you've been "Playing whack-a-mole with software vulnerabilities". If you stop applying patches, using exploits would be more productive.
Activities and Views are fine, I guess. But forcing serialisation of state between screen rotations sucks. A good presenter model with lifecycle management, baked in from the start, would have been nice.
IMHO Google made things worse with Fragments. If you follow the code examples, you end up repeating yourself with lots of nearly empty Activities, just to host your fragments on a phone instead of a tablet.
In previous years, they had been quite careful to inform people to pre-fill their form before census night, and submit after. This year they were expecting only a minor increase in peak traffic.
Then they go and blast the message, "Fill in your form online, ontime or face massive fines", all over the media.
So what did we all do? When the majority of 9-5 workers got home, we all tried to login and submit at about the same time.
Sure they screwed up their network config, but it was a combination of poor planning and poor communication that triggered the whole mess.
Started seeing "suggested post"'s today. This filter seems to work; "##[data-xt]"
They blast all over the media that we *have* to do it on one particular day, or be fined for every day late. Just what did they expect us to do?