klysm

62 ms·

661.
by klysm 2y ago
Spin coat as a circle then cut out a rectangle perhaps? I have no idea where the costs end up
662.
by klysm 2y ago
I’d imagine most things are designed in rectangular constraints
663.
by klysm 2y ago
What do they do with the leftovers? I’m curious I mean even if they do start using rectangular wafers for _some_ things, there is so much supply chain momentum in circular wafers that surely you have some fairly significant job security.
664.
by klysm 2y ago
That makes sense, but I wonder if it would still be better to cut out a rectangle from the circle.
665.
by klysm 2y ago
The LLM can’t verify anything - it just generates what it thinks is plausible
666.
by klysm 2y ago
That's the kind of thing where verification is really hard, and things will look plausible even if incorrect.
667.
Lossless Visualization of 4D Compositional Data on a 2D Canvas(arxiv.org)
2 points by klysm 2y ago|0 comments
668.
by klysm 2y ago
I’m curious what gently looks like at these speeds
669.
by klysm 2y ago
This seems like a massive API design mistake
670.
by klysm 2y ago
I think that’s really the difference though: tooling. That’s all you need to make it easy
671.
by klysm 2y ago
I don’t think it’s very good reasons. We could definitely have binary first serialization protocols and good tooling built into the browser. But no, we encode everything as text, even binary stuff as base64, and whack that into strings
672.
by klysm 2y ago
In what context is json slower than protobuf?
673.
by klysm 2y ago
It not changing is not an indication of its adequacy. It’s merely an indication of backwards compatibility and lock-in effects. It’s not practical to change it even if we did have something better.
674.
by klysm 2y ago
Bottleneck suggests optimization for throughput. I care about latency more
675.
by klysm 2y ago
It’s always crazy to me that we have picked encodings for data that are human-first to send between computers. JSON is in a similar boat. Absolutely enormous amounts of computing power are spent on serialization and deserialization. That la
676.
by klysm 2y ago
Welp yeah that won’t work
677.
by klysm 2y ago
Stopping reading something because of one sentence you disagree with doesn't exactly resonate with your stance.
678.
by klysm 2y ago
React is a very good framework for writing _web_ frontends in my opinion. Writing web frontends is complex, there is no getting around that. React being complex isn't a fault of react, it reflects the nature of the problem.
679.
by klysm 2y ago
As long as it’s not near my back yard - America
680.
by klysm 2y ago
Encoding the sequence like that seems like a really clever workaround for some of the data dependency limitations of GPT.
681.
by klysm 2y ago
What about systemd credentials?
682.
by klysm 2y ago
Fantastic job on the 2D plots stretched out over time in 3D. That's really hard to pull off. How were they made?
683.
by klysm 2y ago
It is good when it’s actually implemented, the annoying part is suggesting a rewrite without doing anything
684.
by klysm 2y ago
I find most apps give up an enumerating the possibly modes of consistency violation that can occur in an app. I’ve tried and failed to do it “right” before and it’s incredibly difficult.
685.
by klysm 2y ago
This is the most Microsoft error message I have ever seen
686.
by klysm 2y ago
Google disagrees
687.
by klysm 2y ago
I mean there is reader mode but your mileage will vary depending on the site markup
688.
by klysm 2y ago
This would be amazing to see in the US. Unfortunately I feel like lobbying is too powerful with the death grip publishers have. If you were to do a popular vote, it would be nearly unanimous I expect.
689.
by klysm 2y ago
Don’t really believe in cause and effect there. It’s hard to get to PMF while having high quality code unless you have an abundance of money and time. I don’t even think it’s a good idea to do that.
690.
by klysm 2y ago
It’s so much harder to sustain the business though. Obviously it’s better for the consumer, but way harder to run

More ›