Whereas if you tax at extraction this is automatically take into account at every step of the supply chain. The market does all the hard work for you.
1,857 karma · joined September 3, 2020
Whereas if you tax at extraction this is automatically take into account at every step of the supply chain. The market does all the hard work for you.
If he wants to join the board he needed to have filed correctly disclosing his acquisition of the shares earlier. To do otherwise is illegal and the SEC will surely take legal action. Filing now can't make everything OK, Elon can't go back in time and retroactively disclose the purchase.
Go's GC is optimized for latency, it doesn't see the same kind of 1% peak latency issues you get in languages with a long tail of high latency pauses.
Also consider API design - Java API (both in standard & third party libs) tend to be on the verbose side and build complex structures out of many nested objects. Most Go applications will have less nesting depth so it's inherently an easier GC problem.
System designs that rely on allocating a huge amount of memory to a single process exist in a weird space - big enough that perf is really important, but small enough that single-process is still a viable design. Building massive monoliths that allocate hundreds of Gb's at peak load just doesn't seem "in vogue" anymore.
If you are building a distributed system keeping any individual processes peak allocation to a reasonable size is almost automatic.
This wasn't a huge PR challenge, all the statement needed to say was "Sorry, some lawyers we contracted applied for the trademarks in error, we have not progressed the applications and aren't claiming any ownership of the terms WASM or Webassembly".
Wasmer only has controversy because basic PR like this statement has been mishandled over and over again. You need to come off as good-faith actors participating in the WASM ecosystem. Defensiveness when you have obviously done the wrong thing, arguing with commenters under what is supposed to be an apology, employees posting supportive comments of their employer on said apology without disclosure... surely it is obvious how these actions are bad PR?
I know this reads really negatively but please understand that it's intended as sincere feedback. It's really important that Wasmer can reform it's image problem. There isn't any reason you guys should be perceived so negatively, if you can stop screwing up PR at every opportunity.
Oracle owns the Javascript trademark because it was originally owned by Sun, who trademarked it under an agreement with Netscape who are the original authors of Javascript. Oracle at least has legal claim to the trademark.
There obviously is not a way to get trademarks on WASM or Webassembly.
If you admit the trademarks were applied for in error, why continue pretending there was a chance they would be granted?
Bytecode alliance is a non profit organisation whose members involve some of the tech giants involved in promoting WASM development. Bytecode alliance have developed their own open runtime.
It's not obvious why we need a seperate WASM runtime developed by Wasmer, or why they would be good stewards for a "Webassembly foundation". Their recent efforts with the closed source Webassembly Package Manager reek of trying to copy the npm business model: take commercial advantage of a non-commercial programming language.
If Wasmer want to be trusted they need to stop acting like they are official stewards of Webassembly. Focus more on building good WASM products than on pretending to be leaders.
You can even see (unattributed) supportive comments from Wasmer employees in this comments section. It just feels off.
Whereas with a dividend, you pay tax immediately when the dividend is issued.
Or is this just fancy binning? If you get a die with 10 working cores, assign the weakest 4 as E cores and the best 6 as the P cores? This would be a great value proposition for Intel & the customer, cores that aren't up to snuff are not a complete write off for Intel like previous designs.
Extra RAM and more PCIe lanes don't really help single core performance benchmarks that much. You can build something much more cost effective than the test system in the article.
And in fact it’s actually worse given that many titles are available digital only.
Providing more restricted types that can replace raw pointers for many use cases makes languages safer.
Software is less affected by these issues because it's inherently more flexible. If I install some wonky experimental Linux feature, it doesn't really matter and I can just revert. Different story when this is baked into hardware. The startup costs for independents to contribute to a software only ecosystem is also much lower. How many organisations have the talent to contribute to RISC-V, but wouldn't be able to afford purchasing a license?
Didn't mean to sound so negative but I worry in the hardware space that the advantages of such an open design are not as great.
Nearly every pointer bug is caused by the programmer wanting one of these two properties, and not considering the consequences of the other.
Non-nullable references and pass-by-value optionals can replace many usages of pointers.
x86 would be more competitive in the mobile space if Intel had offered efficient chips. Is the instruction set the biggest blocker that prevented this? Or is it the licensing model? Perhaps if Intel had licensed their architecture and instruction set to others, like ARM does, they would be in a better position?
ARM's licensing model get's a lot more eyes on instructions sets and chip designs. It allows big companies like Apple come in and run the show, licensing just the instruction set. Why wasn't Intel working with large customers with an interest in custom x86 designs? In hindsight it seems presumptuous to assume there is no x86 talent outside Intel/AMD.
Really impossible to know how much the actual instruction set is holding Intel back without being on the inside.
But they also provide a hook so the game has a chance to save and sync to the cloud before being suspended, so the user can pick up from the same point on another steam device. Loading the game normally of course.
The camera sensor is not a trusted input. Nothing can prevent somebody pointing their camera at a high resolution screen displaying a manipulated image. Or a staged scene. No image signing mechanism can prevent this kind of attack.
There are manipulation detection techniques, but they are imperfect. And even if you verify the image is an unmodified camera original, you still have to analyse the context surrounding the image (what is portrayed in the image, does it line up with other reports, who is the photographer etc.) to determine if it is actually a true.
It is trivial to digitally sign text, but a signature on a string doesn't mean that string is telling the truth. It just means someone signed it.
Highly recommend http://www.hackerfactor.com/blog/ for in depth digital image forensics content.
If some shenanigans were to happen upstream in GCC it would not be the end of Linux.
Some game engines solve the jittery rendering issues by moving the world relative to the player/camera, rather than the opposite (though it may be more intuitive). This way all your shaders work in nice accurate low floats relative to the camera at the origin, no matter the player location in the world.
But to implement worldgen with relative coordinates would be much more complex.
FCC has allocated radalt's 200Mhz, with another 200Mhz guard on either side. If these devices are not properly filtering out frequencies outside of this massive 600Mhz range, those devices are faulty and should never have been certified by the FAA in the first place.
It's reasonable for the FCC to assume that spectrum users will not be affected by interference from so far outside their allocation.
I don't want to see the same result repeated 5 times across different stack overflow mirrors.
Instead Sommelier exams are subjective - candidates are judged by another Sommelier on subjective criteria rather than objective measurement. In my opinion they judge it as a dramatic performance: how quickly can the candidate rattle-off various flavours? How "high class" is the language they use to describe the flavours? How does the candidate present themselves? Sommeliers dress in fine suits, but this should have no impact on actual wine tasting ability. Yet I am sure if I showed up in a draggy old t-shirt I would fail regardless.
The whole industry seems allergic to objective scientific measurement. I am sure Sommelier's do have some ability to identify varieties, but are they actually tasting all those subtle hints they list off? I doubt it.
One of the most chaotic wikipedia pages I've seen. Sadly today it's much cleaner.
Meanwhile Facebook is "just" an app. It's pure software, and doesn't have the same ecosystem tie in. It's not a platform in the way that android/ios/windows are. Starting a new social network is much cheaper than creating a new mobile platform.