Unity is absolutely being squeezed between the two. I can't really see how it can compete with Godot at the low end; it's hard to compete with free, and most of the goodness in low end games is the gameplay logic, not graphics or animation. And Godot can only get better; look at how Blender ate the CGI tools market. This leaves Unity having to either compete with Unreal at the high end - a very high bar - or somehow finding a new business model. The switcheroo they tried to pull on their customer base can best be viewed in that light.
RL would reasonably be expected to work if the market had some sort of discoverable static behavior.
The reason why RL by backtesting cannot work is that the real market is continuously changing, as all the agents within it, both human and automated, are constantly updating their opinions and strategies.
Monophasic waveforms are generally considered less safe than biphasic waveforms. That's why many TENS units have an output stage based around a pulse transformer, so they can deliver two pulses, one in each direction, shortly after each other. Leaving this out seems to me to be a false economy when you've gone to all the effort of building the rest of the system.
What makes trading such a special case is that as you use new technology to increase the capability of your trading system, other market participants you are trading against will be doing the same; it's a never-ending arms race.
Even more than 20 years on, people are finding new ways to improve kernel internals. This is the sort of subtle, intelligent work that distinguishes excellent software from the rest.
There is absolutely nothing to prevent anyone from generating arbirary DOM content from XML using JS; indeed, there's nothing stopping them from creating a complete XSLT implementation. There's just no need to have it in the core of the browser.
I found the whole 'activation' model deeply confusing and annoying. The underlying mechanism of venv is simple and elegant, but the original interface is terrible piece of design.
No, they're not electrically powered, but given that you can buy an electrically-powered 5-horn kit from eBay for $20, it's certainly the cheapest way to go for a typical HN-reading hobbyist/hacker. Getting 14 horns is then $60, and the rest is relays a microcontroller, and a bit of 3D printing for the horns.
This is fantastic. The one-handed organ keyboard is a work of genius, and it all feels like very simple organic technology: sets of tuned car horns are really cheap, and the rest is just a matter of wiring.
I'm severely tempted to buy a bunch of car horn parts and build my own MIDI-controllable one - every bit of this I can either buy on Amazon or 3D print.
This is exactly what makes this such an interesting development. Standardization is part of the process of the CPU industry becoming a mature industry not dependent on the whims of individual companies. Boring, yes, but also stable.
I would have thought that those participants who are published in peer-reviewed journals could be be used as a trust anchor - see, for example, the Advogato algorithm as an example of a somewhat bad-faith-resistant metric for this purpose: https://web.archive.org/web/20170628063224/http://www.advoga...
It's about time. Critical infrastructure still written in C - particularly code that parses data from untrusted sources - is technical debt that is only going to get worse over time. It's not as if Rust is that much more difficult to write than C. Rust is explicitly designed to be what you'd get if you were to re-create C knowing what we know now about language design and code safety.
If 32-bit x86 support can be dropped for pragmatic reasons, so can these architectures. If people really, really want to preserve these architectures as ongoing platforms for the future, they need to step up and create a backend for the Rust toolchain that supports them.
People are absolutely part of an ISA's ecosystem. The ISA is the interface between code and CPU, but the code is generally emitted by compilers, and executed in the context of runtimes and operating systems, all designed by people and ultimately dependent on their knowledge of and engagement with the ISA. And for hot code in high-performance applications, people will still be writing directly in assembler directly to the ISA.
You may see a mixture of sodium and lithium batteries in grid storage; one for providing very short-term grid stabilization of the order of seconds to minutes, the other for long-term large-scale storage, which is by far the largest application. Possibly both within the same battery farm.
You can also put internal heaters within the battery compartment itself, as with current EV batteries, and have the batteries manage their own temperature automatically.
I can't stress enough how big a development this is in the process of making renewable energy not just the cheapest form of power, but one of the most reliable, something that will drive decarbonization in general, which will in turn drive world politics.
This article leads to a paywall where I am, making it of no use. Perhaps someone else has done a better job of summarizing the paper elsewhere, and that should be posted instead?
We are lucky it's even a duopoly. All it would take is the demise of Firefox, and the entire web would be defined entirely by the implementation of Chrome/Chromium.
Servo is very welcome; a third leg to the stool makes real diversity possible again.
Grounding programming languages in mathematics like this is essentially the goal of Strachey and Scott's denotational semantics, which has been very influential in programming language theory:
I had a client with a system just like this. EBS, S3, RDS, Cognito, the lot. It cost $00s per month under almost no load, and was a maintenance nightmare - which was the real problem, not the cost, as it stopped working altogether eventually. A bit of hacking later, it all fits on a single VM that costs ~$10/month to run and is far easier to build, deploy and maintain.