dcsommer

5 ms·

1.
by dcsommer 4d ago
That's reductive. Without coordinated cooperation, enough actors will defect so game theory plus market forces will force acceleration on the frontier overall.
2.
by dcsommer 6d ago
For an informed take (from a professional musician, composer, and arranger) on where this is going for musicians and the music industry, I really recommend Adam Neely's video essay "Suno, AI Music, and the Bad Future": https
3.
by dcsommer 2mo ago
Sure they care about elegance, or at least brevity. Minimizing tokens out, or generally "token efficiency," is part of the objective function for these systems. It doesn't mean they are perfect at it though.
4.
by dcsommer 2mo ago
What is the binary size comparison including wasm + js?
5.
by dcsommer 3mo ago
https://www.memorysafety.org/docs/memory-safety/
6.
by dcsommer 4mo ago
Codecs are difficult and expensive to develop. Therefore they get reused in many contexts, including security critical ones. Sandboxing is shown over and over to not be a great security solution, so what this means in practice is that secur
7.
by dcsommer 4mo ago
Performance should not be priority #1. Security should be. Why do we slow down all CPUs to prevent SPECTRE attacks yet continue to write in C? As rav1d shows, the perf loss is far less to migrate from C to Rust than it is to apply SPECTRE m
8.
by dcsommer 5mo ago
How is this POV compatible with the exploitable vulnerabilities, caused by memory safety, found in openh264, x264, dav1d, and practically every video decoder out there?
9.
by dcsommer 5mo ago
We must not continue to develop media codecs in memory unsafe languages. Small, auditable sections can opt-out perhaps, but choosing default-unsafe for this type of software is close to professional negligence.
10.
by dcsommer 7mo ago
I think GP is simply identifying a potential popular niche that could be satisfied in a future city builder game, which seems quite on topic.
11.
by dcsommer 8mo ago
Just for reference, Wamedia ships on the major Meta apps and on iOS, Android, Desktop, and Web platforms.
12.
by dcsommer 8mo ago
We invested a lot into build system optimizations to bring this number down over time, although we did accept on the order of 200 KiB size overhead initially for the stdlib. We initially launched using a Gradle + CMake + Cargo with static l
13.
by dcsommer 8mo ago
Great reading to see beyond the clichéd, sanitized retellings of that era. It really makes you consider the prices paid for what some call progress.
14.
by dcsommer 10mo ago
Great work by the MS team. It is great progress to shift OOB access into a controlled crash. These kinds of panic bugs are then easy to remediate, with clear stack traces, as we see in the turn around time from the report.
15.
by dcsommer 11mo ago
> basically fine How many type confusion 0 days and memory safety issues have we had in dynamic language engines again? I've really lost count.
16.
by dcsommer 1y ago
Is there a straightforward path to building Zig with polyglot build systems like Bazel and Buck2? I'm worried Zig's reliance on Turing complete build scripts will make building (and caching) such code difficult in those determinis
17.
by dcsommer 1y ago
It would be cool to build a "library clout" measure for all open source software. First collect for all deployed software systems measures of usage per platform and along other interesting dimensions like how that system relates t
18.
by dcsommer 1y ago
This is interesting if true, but without data I can't take this claim at face value.
19.
by dcsommer 1y ago
Neither are high and low surrogates - those are big ranges of code points that are illegal except for one specific (and not recommended) encoding (utf-16). Yet, there they will remain in Unicode. Digits definitely are a form of text though.
20.
by dcsommer 1y ago
Seems more proper to call it a `ProbabilityDistribution` type. It's a more general and intuitive way to handle the concept.
21.
by dcsommer 1y ago
Enforcement needs to be on the sales side, as enforcement at the consumer level is obviously impossible to scale. Also, class 2 (and 3) should not be allowed in bike lanes. If you have a throttle, you're not a bike; you're a motor
22.
by dcsommer 1y ago
Unsafety in a language is fine as long as it is clearly demarcated. The problem with Go's approach is there no clear demarcation of the unsafety, making reasoning about it much more difficult.
23.
by dcsommer 1y ago
"Strongly typed" is stretching it. Type checking is bolted on and not part of `erlc`. Typing is quite unergonomic in Erlang/Elixir (similar to Typescript bolted onto JS). The type system is one of the weakest parts of the bea
24.
by dcsommer 1y ago
> 40% of Americans believe that God created the earth in the last 10,000 years. Citation needed. That claim is not compatible with Pew research findings which put only 18% of Americans as not believing in any form of human evolution. ht
25.
by dcsommer 1y ago
Have there been any studies or economists predicting macro-level benefits to the US economy with the tariffs? I'm not aware of any (much the opposite), but I'm interested if they exist.
26.
by dcsommer 2y ago
Yet I feel that AI gives such instant gratification that the boredom and struggle required for imagination is short-circuited and atrophies.
27.
by dcsommer 2y ago
For what languages would removing 'std::' realistically cause ambiguity for practicioners?
28.
by dcsommer 2y ago
If the goal is brevity, the rules could first replace 'std::' with nothing.
29.
by dcsommer 2y ago
It preserves a left to right reading of the code. You don't have to jump visually elsewhere.
30.
by dcsommer 2y ago
I think Rust could use some syntax improvements for pointer manipulation. It has suffix .await, so maybe the community is ready for suffix .* for dereference now too. Visually scanning left and right, along with the extra parentheses, makes

More ›