pornel

9 ms·

121.
by pornel 5mo ago
Usually performance was the reason for using native APIs rather than web views, but this doesn't seem to be true any more. Browser rendering engines are pretty mature at this point, with significant GPU acceleration, and over a decade
122.
by pornel 5mo ago
No, it would make it worse. This adds more computation and sacrifices throughput to improve latency of a serial single-user generation. Large scale providers run inference in batches, sacrificing latency to gain throughput.
123.
by pornel 5mo ago
What exactly people mean by "safe(r)" makes all the difference. It's simply not possible to include all the nuance of safety of a language and all software written in it a single word. This leads to all kinds of miscommunicat
124.
by pornel 5mo ago
That would add administrative overhead, and even higher incentive for submitters to endlessly argue they're right.
125.
by pornel 5mo ago
It looks nice. I've been searching for something like this recently, and was frustrated with rankings that lack latest models or don't clearly distinguish quantizations. Showing quality loss per quantization is nice. I'd pref
126.
by pornel 5mo ago
> what's preventing you from going to their website? Lack of links. It's a common annoyance when subsections of a site fail to link back to the parent.
127.
by pornel 5mo ago
It depends what you compare it to. If your reference is JS or C#, then Rust's async has more friction and annoying details. But Rust is generally harder due to being low-level and picky about memory management and thread-safety details
128.
by pornel 5mo ago
It's a rehash of a bunch of old misconceptions. I thought we've buried these when people got actual experience with Rust. The dumbest one is counting changelog lines. Have you even read them? These days most of them are "obsc
129.
by pornel 5mo ago
Why? It's the essence of "Simple Made Easy": you don't have other code to complect with. You have a smaller interface, focused on a singular goal. When a library has to work as a standalone project, it can't be ac
130.
by pornel 6mo ago
Yeah, the kids didn't like the broom closet.
131.
by pornel 6mo ago
This is very culture-specific. I've seen this in Poland. Under USSR rule frugality has been necessary to survive, but it left a lot of people forever stuck in that mindset, long after things got better. I know people who have a fortune
132.
by pornel 6mo ago
Indeed, std::fs suffers from being a lowest common denominator. Rust had to have something at 1.0, and unfortunately it stayed like that. Rust uutils would be a good place to design a more foolproof replacement for Rust's std::fs API.
133.
by pornel 6mo ago
The terminology confusion was too difficult to resolve. "REST" became associated with a good API design, so when people were told their API isn't a real REST, they interpreted it as having to implement more of Roy Fielding&#x
134.
by pornel 6mo ago
This is not sufficient to stop XSS, because an attacker can redirect users to file.svg URL as the top-level document, bypassing restrictions of <img>. If you're going that route, add CSP headers on HTTP level to disable scripting
135.
by pornel 6mo ago
He destroyed my trust in Apple in ways that can't be put in numbers. This growth comes from rent seeking. Greedy fees and lock-in they can sustain due to control of the platform and cultivated duopoly. Apple narrative around security i
136.
by pornel 6mo ago
Quake 1 ran game logic and model animation at 10 ticks per second (a reasonable choice when PCs running Quake at 20fps were impressive). Camera and linear motion of objects were interpolated to the framerate.
137.
by pornel 6mo ago
It wasn't deterministic. It didn't record the inputs. It recorded the basic state of the objects you could see. Deterministic game sync is a completely different approach more often used in RTS games. Quake had non-deterministic a
138.
by pornel 6mo ago
Browsers can deal with very long documents. Ctrl+F works like a breeze on HTML that's 100K lines long. Browsers only struggle to run heavy JS frameworks that wrap every line in a dozens of spans with dozens of handlers and mutate it al
139.
by pornel 7mo ago
Energy providers use whatever internet API there is for either chargers or cars. Octopus UK has a list of charger models and car brands they support for their special tariff for cheap off-peak EV charging. The charging cable has a protocol
140.
by pornel 7mo ago
For me EVs already won when charging got down to 20 minutes. EVs charge unattended. It takes less of my own time to leave EV plugged in parked next to a place I want to be at, than to go drive to a gas station and stand there holding a sm
141.
by pornel 7mo ago
This is what everyone is already doing, even for relatively small and slow dispensers. It's simply cheaper to have on-site batteries. It makes installation work with a smaller connection to the grid, and makes it possible to install ch
142.
by pornel 7mo ago
e-GMP platform (IONIQ 5, etc.) is really good for road trips. At least in summer temperatures it reliably charges to 80% under 20 minutes. Its range estimate is quite good, and I can depend on it to know when I can skip a charging stop (whe
143.
by pornel 7mo ago
It is supported in JPEG! It can reduce color bleeding along the axis that each chroma channel controls. For example, if you make sharp Cr and low-res Cb, you'll get sharper red edges with some yellow bleeding instead of completely blur
144.
by pornel 7mo ago
Everything after JPEG is still fundamentally the same, but individual parts of the algorithm are supercharged. JPEG has 8x8 blocks, modern codecs have variable-sized blocks from 4x4 to 128x128. JPEG has RLE+Huffman, modern codecs have conte
145.
by pornel 7mo ago
It's a perfectly pragmatic engineering choice. Blocking is visible only when the compression is too heavy. When degradation is imperceptible, then the block edges are imperceptible too, and the problem doesn't need to be solved (i
146.
by pornel 7mo ago
Gell-Mann Amnesia for code quality.
147.
by pornel 7mo ago
It's hard to see features through the programming language theory jargon, but solid theoretical foundations have worked well for Rust so far. Jargon terms like "sum types" or "affine types" may seem complicated, but
148.
by pornel 8mo ago
My comment was a summary of the situation, not literal prompts I use. I absolutely realize the work needs to be adequately described and agents must be steered in the right direction. The results also vary greatly depending on the task and
149.
by pornel 8mo ago
When a new technology emerges we typically see some people who embrace it and "figure it out". Electronic synthesisers went from "it's a piano, but expensive and sounds worse" to every weird preset creating a whole
150.
by pornel 8mo ago
Their default solution is to keep digging. It has a compounding effect of generating more and more code. If they implement something with a not-so-great approach, they'll keep adding workarounds or redundant code every time they run in

More ›