Readit NewsI need this in my life.
Although for everyone else at least 5000 years will pass, so better say goodbye to family and friend.
Hm, not sure if that is really less depressing...
Also light isn't slow. A photon instantly travels to the end of time and yet it still takes a few minutes from the surface of the sun to us. Or about 100000 years from the center of the sun to its surface.
For sure you're not just sitting there watching people get born, live and die in second and shrugging your shoulders.
* It makes sense to tax capital assets as such.
* If companies do R&D and think the results are valuable enough to be kept secret, then obviously they're an asset.
* Depreciation is because real-world assets actually require ongoing maintenance or become worthless over time, but information does not.
* Finite-term IP grants (e.g. copyrights/patents) do become worthless over time, so a depreciation schedule makes sense.
* Trade secrets never expire, so it doesn't make sense to depreciate them. If they never get out, they remain an asset forever. So their development shouldn't be deductible. If they do get out, the company could release all of their (now presumably useless) info on it then for the deduction from their development.
The point about finding trade secrets to be dubious is that it seems natural to tax them as an everlasting capital asset (since that's what they are), and I don't see why we wouldn't do that since society doesn't eventually get the benefit of that knowledge, so incentivizing it runs counter to the purpose of IP law. Why would a knowledge economy provide a tax deduction for developing knowledge we don't eventually get?
You are going way out of your way to try to come up with ways to rationalize why JSON was a success. The ugly truth is far simpler than what you're trying to sell: it was valid JavaScript. JavaScript WebApps could parse JSON with a call to eval(). No deserialization madness like XML, no need to import a parser. Just fetch a file, pass it to eval(), and you're done.
Browser-zero days are why I factored out a way to distribute "web RPA agent creation" on any device, with no download - into its own product layer for browser-isolation. It's a legitimate defense layer but main barriers to adoption are operating friction, even tho it makes the task of hackers who want to compromise your network with browser 0-days much harder.
Because of that the RBI aspect is not as popular as ways its being used where you need a really locked down browser, with policies for preventing upload/download, even copy and paste, etc - for DLP (data loss prevention), for regulated enterprises.
Even so I think the potential applications of this tech layer are just starting.
Then it hit me: the only thing keeping a rogue website from sweeping your entire life is a browser's permissions popup.
In particular: stable and individually adjustable temperatures for bedrooms and living rooms; underfloor heating in some rooms (bedrooms), radiator-based heating in some others (living room), and combined UFH+radiators in some others (where UFH might not be enough during extreme colds).
I thought I can just pay someone some money and they'll set up the controls for me. It must be a simple exercise, right?
I could not have been more wrong. After spending a few hours of understanding the setups that "experts" have recommended, I figured out edge cases where they would be either wasteful or uncomfortable (meaning: unnecessary and inavoidable temperature overshoots or undershoots, etc.). I had many-many rounds with Honeywell, Tado, Siemens, etc. and every single one of them had _major_ issues.
The renovation got a bit stuck because of this, but the plumbing was ready so I wanted to see whether the pluming and pumps are working, at least. So I connected the pumps and valves to "smart plugs", i.e. Zigbee-controlled plugs, so that I can see that they turn on. They did, which got me thinking...
Right now I have $20 Zigbee temp sensors sprinkled across the house, $30 smart plugs and relays driving valves, pumps and the boiler, and Home Assistant is controlling the whole thing. Everything works perfectly and I could implement some features that simply no system would have done out of the box, for example in rooms where there's combined UFH and radiators I can drive both heating systems when the target temperature is far from the desired (so that the room heats up quickly) but as the room temp is getting closer to the target, the radiators are turned off so that UFH dominates heating (more comfortable and more energy efficient than radiators). In rooms with radiators, temp is +- 0.4 C within target, in rooms with UFH, it's +-0.1C within target.
My knowledge is that for UFH you run at temps between 40-50
C and radiators run at 60-70*C.> We rerun the repro. We look at the logged value. Math.abs() is returning negative values for negative inputs. We reload and run it again. Math.abs() is returning negative values for negative inputs. We reload and run it again. Math.abs() is returning negative values for negative inputs.
Regardless, that is beside the point. I was not arguing either way if this was a deterministic bug or not, I was pointing out that the author’s conclusion does not follow from the premise. Even if the bug had turned out to be nondeterministic, they had not done the necessary steps to confidently make that assertion. There is a chasm of difference between “this bug is nondeterministic” and “I haven’t yet determined the conditions that reproduce this bug”.
And if you go up or down by one (119 or 121) they appear to "rotate" left or right.
Very cool viz tool.