fleventynine

5 ms·

31.
by fleventynine 7mo ago
At the end of the day, I'm being paid to ensure that the code deployed to production meets a particular bar of quality. Regardless of whether I'm reviewing code or writing it, If I let a commit be merged, I have to be convinced th
32.
by fleventynine 7mo ago
I upgraded to this exact CPU from a 200MHz pentium in the fall of 2000. Easily the largest jump in performance of any upgrade I've ever done.
33.
by fleventynine 9mo ago
Another impressive early HDTV example: https://youtu.be/eMefy5VK9TI - Toto, Montreaux, 1991
34.
by fleventynine 10mo ago
There are some reasonably affordable models like https://www.lcsc.com/product-detail/C5272996.html that are powerful enough for many tasks.
35.
by fleventynine 11mo ago
> Can’t offload everything into the compiler. It is already too slow. Speak for yourself. On embedded platforms I'd happily make my compiles twice as slow for 10% code size improvements.
36.
by fleventynine 11mo ago
When looking at the rv32imc emitted by the Rust compiler, it's clear that there would be a lot less code if the compiler could choose different registers than those defined in the ABI for the arguments of leaf functions. Not to mention
37.
by fleventynine 11mo ago
Rigid ABIs aren't necessary for statically linked programs. Ideally, the compiler would look at the usage of the function in context and figure out an ABI specifically for that function that minimizes unnecessary copies and register ch
38.
by fleventynine 11mo ago
Rustc does a good job of removing unused code, especially with LTO. The trick is to make sure the std library main/panic/backtrace logic doesn't call code you don't want to pay for. IIRC there's also a mutex somewhe
39.
by fleventynine 11mo ago
The Rust standard library in its default config should not be used if you care about code size (std is compiled with panic/fmt and backtrace machinery on by default). no_std has no visible deps besides memcpy/memset, and is compa
40.
by fleventynine 11mo ago
> This means there's no target too small for the language, including embedded systems. It also means it's a good choice if you want to create a system that maximizes performance by, for example, preventing heap allocations alto
41.
by fleventynine 11mo ago
It's still above where it was a few weeks ago. I don't see why this is news.
42.
by fleventynine 11mo ago
"My attention is a limited resource. In order to prove that you're a serious human, please donate exactly $157.42 to the Rust maintainers fund and paste the receipt link here".
43.
by fleventynine 11mo ago
No mention of 120Hz; I'm waiting for a 6k or higher-density display that can do higher refresh rates.
44.
by fleventynine 1y ago
Non-systems languages still need to interact with systems languages, over the network or directly. The lack of unsigned types makes this way more painful and error-prone than necessary.
45.
by fleventynine 1y ago
> If you call a method which returns an unsigned int, how do you safely pass it to a method which accepts a signed int? The same way you pass a 64-bit integer to a function that expects a 32-bit integer: a conversion function that raises
46.
by fleventynine 1y ago
Still no unsigned integer types in the standard library after 26 years?
47.
by fleventynine 1y ago
I don't know about gifted programs, but anything that separates kids who don't want to learn from those who do is a good thing; far to much time is wasted in America's schools catering to bad behavior.
48.
by fleventynine 1y ago
Yeah, I think to make a system using this really scale you'd have to add support for this protocol in your load balancer / DDOS defenses.
49.
by fleventynine 1y ago
Does anyone know what it looks like when you use a line scan camera to take a picture of the landscape from a moving car or train? I suspect the parallax produces some interesting distortions.
50.
by fleventynine 1y ago
Because i can produce 5 clean, properly sized commits in the time it takes to do one round of reviews, so they have to be stacked. It's important that the CI run independently on each commit, and each commit builds on the work of the p
51.
by fleventynine 1y ago
> Are there any improvements to be done to Git? Github's workflow for stacked PRs is still terrible. There's plenty of room for improvement.
52.
by fleventynine 1y ago
I've had a lot of success writing driver test cases against the hardware's RTL running in a simulation environment like verilator. Quick to setup and very accurate, the only downside is the time it takes to run. And if you want to
53.
by fleventynine 2y ago
Historically, the price difference between MMF and SMF transceivers was greatest at the highest speeds. That doesn't seem to be the case anymore for short-range transceivers.
54.
by fleventynine 2y ago
Apples to oranges. SR is for short runs inside a building. LR is for sending signals across a city. For short runs inside a building, the transceiver prices are much more comparable. Compare https://www.fs.com/products/
55.
by fleventynine 2y ago
Multi-mode transceivers used to be a lot cheaper than single mode, but now they're around the same price for short distances. From what I can tell, most datacenters appear to be making the switch to single mode even for in-room network
56.
by fleventynine 2y ago
> The difference is private companies that accumulate too much waste and useless things can fail and be replaced. Unfortunately, there isn't enough competition for this to be true. In many markets the largest incumbents are able to
57.
by fleventynine 2y ago
With the sheer volume of local exploits found in the Linux kernel, I don't really consider these SELinux/AppArmor mitigations to be that useful. Sure, they reduce the attack surface a bit, but if I actually need isolation between
58.
by fleventynine 2y ago
With 64 XGS-PON customers per SFP+ module, the only active equipment you need to terminate connections for over 60,000 customers fits into a single rack. Large centralized buildings are largely obsolete unless you want to offer services bey
59.
by fleventynine 2y ago
Geforce 256 and 2 were fixed-function; I don't believe the first shaders showed up until Geforce 3.
60.
by fleventynine 2y ago
Because of this mismatch there aren't many young folks with these skills; expect these salaries to flip around once most of the experts retire.

More ›