sylware

For low bandwidth and personal web sites, aka small and not hacker juicy targets, probabably depends on the user tech tastes more than anything else.

The CA concept itself is flawed, unless normal users were able to cherry pick the CA they do trust, dream. And even with that, they must keep in mind that many authorities and/or mafias have very probably rogue certificates for browser invisible man-in-the-middle.

Unless the money of the investors is going somewhere else...

whatwg javascript gated.

Any other links?

What? Stick to simple PNG. It is simple, runtime and SDK, beyond good enough and has 16bits per color component support (which webp does not have).

RAM price?

Issue: valve announced the beta steam client was finally 64bits clean and nope it cannot start games if you remove 32bits support since their "reaper" command is still 32bits....

Unless I missed something? Yeah? Anyone to enlighten me?

Hopefully, this will end up in its foundation or even the linux one, with most motherboard manufacturers behind it.

But... it should be binary specifications with "human-like" assembly implementations since you have to remove the "compiler" issue from the SDK.

DUDE!

VULKAN!

(and shaders written with a SPIR-V assembler, no glslang!)

Handrolled assembly is always better (on the long run).

You can read this assembly code the same than C until your data structures are properly exposed and documented.

There are some tricks though: avoid abuse of macro pre-processor (ffmpeg was bitten by just that), reasonable name mangling/hierarchical namespaces (usually done with a pre-processor that to avoid too long identifiers on deep projects). Ofc those pre-processors should be as small and lean as possible runtime and SDK included (don't python and don't hesitate to include their code in the project, yep, better if handrolled assembly too).

This issue is much broader than that.

This is for _anything_ you don't use all the time at high frequency. And then, you have the other way: in the routine, you'll mechanically make mistakes without even noticing.

And you'll discover that some people hardly forget anything compared to others, and that over very long periods of time, including the most unimportant things. Some, to a scary level.

linux "C"... Linus T. is holding the line on syscall ABI stabitily but failed at keeping plain and simple C with assembly source files to uncouple linux code from the few compilers able to build it and unlock smaller alternatives (for instance cproc/qbe).

I don't really mind though as it seems the far away real future is something like everything RISC-V assembly, "C" would only be the binary specification.

And some python/javascript/etc interpreters written in RISC-V assembly themselves, because sometimes my code can be slow and non-rigorous.

This should definitely by a binary specification with various ISA assembly implementations.

I would be more interested at generating directly "human" assembly code following some binary specification, or at best in plain and simple C (which does not require exactly gcc ar clang to compile). Read some news on HN here announcing that some coding savvy people are doing exactly that for their everyday software.

I don't want computer languages with complex syntax anywhere near me: that's why transpilers of those very languages to languages with a simpler syntax (usually plain and simple C or directly "human" assembly) are in my opinion so much important (we have a c++ to C transpiler and a microsoft rust to C transpiler, coded with the assistance of AI, and those should only improve from there).

For me, the current main issue of "AI" is their gatekeeping using the whatwg cartel web engines, yes, technical access to "AI" will have to be hardcore regulated if it becomes ubiquitous, and I said 'technical access', not AI itself, the difference is abysmal, it is an interop issue.

Ofc. An advanced chat bot.

Enlighten me, is android userland an abomination for some java runtime only? OR is this a set of binary interfaces I could even reasonably code in assembly?

This is where you would be surprised. You can prototype binary specifications with a classic computer language (like plain and simple C, I don't know how much micosoft rust support binary layout definitions and language independent core ABIs), then you can "plug" implementations in any language, the benchmark being assembly (have a look at dav1d, and probably dav2d). The only thing to keep on eye on: the runtime dependencies, for instance a generic memory allocator (usually not a good idea), and for assembly the abuse of a macro pre-processor (ffmpeg was bitten by it).

I would prefer assembly in various ISAs.

Does the C code generated by the rust->plain and simple C transpiler work?

The real mistake was to connect such food critical equipment to the internet. I don't know who dared to do that, this has been part of the common knowledge for a while now.

You still can do it, but it better be a super low level private network: basically a super low VPN/crypto without using any off-the-self kludge, open source or not, probably directly implemented in some hardware driver in assembly for machine code/hardware control (if traffic was "big", it would have been FPGAs, probably). And you ** _MUST_ ** have a permanent and significantly sized and competent "security" team 24/24 7/7 ** you can trust ** for monitoring and looking for "pertinent" flaws.

Mechanically, the effort required is some exponential of the machine code (compilers are a [trust] problem, not a solution) size, complexity and code unstability (change over time).

No, trusted compilers of comfy computer languages do not exist by definition, eat the bullet.

Related to crypto: I wish we had some open source binary specifications implemented in various ISAs for some micro-architectures. You want machine code here, not even C or whatever (or at best only for those binary specifications).

And don't be a fool, ASIC trust will be a thing: some features will have to be disabled, or you better be ready to change some micro-architecture, yes, would be better to have several micro-architectures based on the same ISA (i.e. RISC-V for zero IP lock) ready at proper scale.

The level of this answer left me with no other choice:

Are you an AI chat bot?

Android is linux.

Only the userland is some java based abomination... well was a long time ago, maybe after all those years, the android userland has a minimal set of simple binary interfaces and simple file formats, which I could even code reasonably code directly in assembly (this is the benchmark).

Something is wispering to my hears: "nooo! there is no such things as minimal system interfaces and file formats on android linux". Wrong?

If there is one game dev studio which can do big cross-platform QA (console,"linux" PC,macos,mobile?,etc) is them... so... it looks like lazyness, or they are sleeping with microslope in the backroom, since they would be the only beneficiary. We all know that with current modern 3D engines, serious and honest work, the only thing which can be tricky: conservative 3D programming which does include the shaders (lower the level the better).

defeat the whole purpose of simplicity, runtime and SDK.

From a panel point of view, this is "end game": for a color component, you can get one discret color component value per line/column. Color banding is gone with a good panel in sRGB on large chunk of the panel with very gradient oriented image data.

PNG compression is zlib (deflate)

With lossless compression and the "modern" internet, it is a matter to indeed allocate more to image bandwidth, from an internet point of view, that would be the price of 'end game' image format quality (lossless and 16bits per component).

You are missing critical metrics: the absolute values which are now very important in our super high speed internet and beyond powerfull consumer hardware.

It is a bit like linux on steam: 6%... but millions, ratio is little, but the absolute is so huge that it you cannot ignore anymore their market value (like macOS though).

+1

But I want to run locally the full weight frontier model on my system to get the best result quality (I am targetting coding prompt).

I already know I'll know a lot of RAM and it will be slow.

I thing the endgame is lossless PNG with 16bit color components with basic compression like gzip or at best bzip2. Or a format without the weirdness of PNG 'line based loading' which is obsolete nowdays. The "expensive part", apart from the compression algorithm, being the meta data storage without kludge.

GTA 6 will probably be software as a service to some extend, namely the code will change all the time at somewhat high frequency for any port. If I am not too mistaken a big chunk of the GTA community does play online.

"AI porting" able to follow? (If that AI thing is actually true)

Unless GTA 6 is not hardwired to AMDGPU hardware at release, if they have a cross-platform engine, for PC, it is to click the right export button... and do the QA and debug to please the various 3D drivers out there.

Consumer hardware will need a lot of RAM...