I've had 2 now from different manufacturers and the firmware seems alright due to the integrated nature of the API making them all fairly homogenous.
9,549 karma · joined March 24, 2011
I've had 2 now from different manufacturers and the firmware seems alright due to the integrated nature of the API making them all fairly homogenous.
Cyberpunk is a good example of a game that straddled the in between, many of it's performance problems on the PS4 were due to constrained serialization speed.
Nanite and games like FF16 and Death Stranding 2 do a good job of drawing complex geometry and textures that wouldn't be possible on the previous generation
Feature phones were already outpacing PC growth by then and Intel decided to snub the market. Canceling XScale was a truly stupid decision.
However there was significantly more oxygen in the atmosphere back then. There could be a metabolic component related to that since absorbing O2 was probably easier.
Nowadays almost nobody cares about OpenCL.
They didn’t put the game file download process behind an auth layer until very late in the system’s life.
>and most disturbingly (because they suggest destructive violence against children's toys, and against the child in all of us) a ceramic Angry Birds figure and a stack of rubber emoji ball.
Are you fucking serious man? It's just an ad
It's getting embarrassing that every other mobile and desktop OS has no problem doing this but not Ubuntu.
Essentially the state was rebating the corporate tax they would have received in lieu of the income tax revenue obtained from the new positions along with the increased competition for high paying tech roles in the city.
The program was deliberately structured to be revenue neutral in terms of absolute tax revenue while increasing overall tax revenue by increasing state GDP
Besides, the program is structured such that they wouldn't get the rebate if they didn't hire so what does it matter?
The only real "subsidy" in the NYC deal was a land grant where an old plastics factory used to be that required significant environmental clean up. The land is also next to the notorious Queensbridge projects.
Really considering we mostly work in this industry, the amount of ignorance surrounding the deal, its incentive structure, and how it went up in flames is staggering.
Even the talking point about how Amazon opened up new NYC offices anyways is completely innumerate, so far they've created about 1/5th of the positions that they were projected to create under the HQ2 proposal.
Here's the one about this subject: https://www.youtube.com/watch?v=3vQ55ToQeWI
The clear reason why they are bundling this service with their existing products at a loss is to expand their market share at the expense of interoperability.
This bundling is clearly an antitrust issue, I have a hard time believing all these arguments defending the wealthiest corporation on Earth aren’t being deliberately obtuse.
C++ templates allow for declarative nested inlining into a single compilation unit that is extremely difficult to achieve with C macros.
See elsewhere in this thread for discussion of boost, it's not applicable.
For me it mostly looks like a reject pile for a stdlib that I must also reject most of the time.
The alignment of incentives between these library authors and people that use C++ for high performance applications is just off.
There's also a lack of traits that can describe what's required of a specialized allocator. For example, std::map only needs to allocate 1 object at a time in practice while std::vector needs to allocate a contiguous count of objects.
I really wish the std would drop this pretense and focus on C++'s strong point: Continue being the fastest systems language possible.
Everywhere in the std lib you can see compromises that require rewriting substantial portions for any real time application.
Things like: shared_ptr eagerly using atomics whenever possible; std::string allocating; the lack of built-in faster std::allocator replacements like bump allocators, memory pools, etc; no lockless and wait free concurrency primitives; no architecture-aware thread pools or even architecture descriptions; no IPC primitives; etc.
Considering how many C++ developers are working on things like games, high performance server applications, databases, and operating systems, it's just bizarre how inappropriate the standard headers are for these tasks.
Even something trivial like casting bytes off the wire to a packed struct is an exercise in frustration due to aliasing rules that should have been encoded in the type system and invisible to the user.
In particular, you can add a 7840U laptop to the comparisons to see how the 23W Qualcomm part compares to the current low power AMD CPU with a comparable wattage.
If a distro's default theme breaks an app then it's something the distro and app will have to work together and fix. But throwing system themes out in favour of app specific themes like the article is arguing for sounds absolutely awful.
It got so bad that we mostly ignored them. It wasn't good for either VLC or QuickTime.