HNHacker News
TopNewBestAskShowJobs

winwang

897 karma · joined June 17, 2022

Effective efficiency. Building a hardware-accelerated (big) data platform.
submissionscomments
winwang··on uBlock Origin is no longer available on the Chrome Store
As much as I dislike their Chrome practices, I am rather against the idea of forcing them to sell Chrome.

For one, they simply have had a better product, at least in the past. Part of their large monopoly is due to just being better outright for a large portion of users (presumably). Are we to punish making overly-good products?

For another, sell to whom? And why would they be a good steward?

And yet another, there's literally Chromium, which other browsers (built by other corps) use, e.g. Edge, Brave, etc.

Did Google have to open Chromium? No.

Disclaimer: I hold these opinions weakly and would love to learn more about why they might be ill-premised.

winwang··on An update on Mozilla's terms of use for Firefox
Then comes the question: would it also obviously expand their domain of allowable actions to trespass on their users?

Since that is a resounding "yes" and they also have the extremely obvious finance incentive to do so...

winwang··on Introducing a terms of use and updated privacy notice for Firefox
Semi-crazy idea: Add clauses which destroy half the company if they change the deal without a year of advance notice.
winwang··on TypeScript types can run DOOM [video]
Counterpoint, it absolutely should be (barring the pedanticness of modding it a bit): https://news.ycombinator.com/item?id=37555651
winwang··on Neut Programming Language
Mildly disagree with your first statement. Well, I mostly agree that it's not particularly helpful for newcomers.

As a 0-tuple, it becomes a specific case of a more general concept -- there is some beauty/usefulness in not having to have a "special" construct for "Unit", which is (in a sense) not just "any" unit type. It also "justifies" the syntax of `()` and notes that it is a product type, all the while fitting into the idea of the "cardinality" of `(a1, a2, ..., an)` being the product of the cardinalities of each of its type params.

winwang··on Complex dynamics require complex solutions
And you know this to be true (indubitably), based on what, exactly? (I'm not even sure which country you're referencing either).
winwang··on Why does Mill use Scala?
Unfortunately, I find that real-world configs don't quite conform to easy understandability past tutorial examples, i.e. k8s and yaml.
winwang··on Why does Mill use Scala?
As someone who worked a bit with Bazel actions and uses Scala: I think Bazel cuts down on the area where arbitrary I/O happens. Also, many executables come from pre-defined targets (e.g. java toolchains). One way to deal with I/O is if Mill injected its own implementation of a JVM filesystem/network layer, which I'm pretty sure it can do.
winwang··on Developer Philosophy
I think it's fine if code is difficult for newcomers to understand (of course, to a point). Most programmers are taught in C-like languages and paradigms. Using FP (ML-like) languages is already "difficult to understand".

The question then becomes: how large is the disconnect between the "theory" in the mind of the newcomer(s) vs. the "theory" they need to be useful in the codebase -- and is this gap worth it?

For example, programming with explicit effects (i.e. `IO`) or even just type-safe Futures. There's not too much difficulty with simply getting started, and it builds up a general theory of effects in the newcomer, which would presumably be useful in many contexts of the codebase even outside of async effects, e.g. error-handling with `Either`.

winwang··on Efficient Reasoning with Hidden Thinking
Depends on if we can interpret the final hidden layer. It's plausible we evolve models to _have_ interpretable (final/reasoning) hidden layers, just that they aren't constrained to the (same representation of) input/output domains (i.e. tokens).
winwang··on Efficient Reasoning with Hidden Thinking
I believe the "continuous" in Coconut means that the CoT is in the continuous latent space, instead of being on output tokens (see Fig. 1).
winwang··on DeepSeek's AI breakthrough bypasses industry-standard CUDA, uses PTX
Here's a rather trivial example of using PTX: https://docs.nvidia.com/cuda/parallel-thread-execution/#spec...

For various micro-bench reasons I wanted to use a global clock instead of an SM-local one, and I believe this was needed. Also note that even CUDA has "lower level"-like operations, e.g. warp primitives. PTX itself is super easy to embed in it like asm.

winwang··on Nvidia’s $589B DeepSeek rout
Slightly tangential, but I want an LLM which can debug windows.
winwang··on Former tech CEO suing to get the record of his arrest removed from the internet
> despite a past conviction

What conviction?

winwang··on Nvidia announces next-gen RTX 5090 and RTX 5080 GPUs
Yep. I use ~80% and barely see any perf degradation. I use 270W for my 3090 (out of 350W+).
winwang··on Exposing the Honey Influencer Scam [video]
Thank you, this is incredibly relevant!
winwang··on Morris Chang and the Origins of TSMC
Although I agree, I think there is a mild hazard with the label of "model minority". Not saying a reaction like that is really warranted in this case, though.
winwang··on Morris Chang and the Origins of TSMC
"P(hard-work-pleasures | asian) >= P(hard-work-pleasures | ~asian)"

I'm not sure if that's true, but it's presumably what the other person was saying they observed. Though I think in casual conversation, the reality is that P(racism | <such a sentence>) is likely higher than "baseline", I'd prefer to give the benefit of the doubt on HN.

Also, much prefer a place where mentioning "race" doesn't immediate trigger strong reactions. "Race" being in quotations, because I think the original sentence has more to do with the culture of (certain parts of?) Asia rather than actual race.

A side analogy: I think that Asians are more likely to like Hello Kitty than non-Asians.

winwang··on Jeju Air Jet Crashes in South Korea With Over 170 Dead or Missing
...makes me wonder if we should do that. would it lead to safer driving?
winwang··on The humble for loop in Rust
glad to see another Scala fan :)

keep in mind that "for loops" are really "for comprehensions" and desugae into flatMap/map

winwang··on The Google Willow Thing
AI isn't magic. It's still subject to the limits of classical computing.
winwang··on Training LLMs to Reason in a Continuous Latent Space
Do you have strong evidence for this?
winwang··on The Google Willow Thing
For one, we could just start simulating quantum chemistry, though at that point it's more like "actually running quantum chemistry" rather than simulating.
winwang··on The Google Willow Thing
Note there's a caveat: problems in CS can be reduced to other problems in CS. If we solved SAT, well, no one cares about SAT, but traveling salesman obviously reduces to that.

(disclaimer: I don't think that's what is going on here, I'd have to dig into it more)

winwang··on Willow, Our Quantum Chip
Haha, classic race condition, but I appreciate your take nonetheless!
winwang··on Willow, Our Quantum Chip
Edit after skimming arxiv preprint[1]:

Yeah, this is pretty huge. They achieved the result with surface codes, which are general ECCs. The repetition code was used to further probe quantum ECC floor. "Just POC" likely doesn't do it justice.

(Original comment):

Also quantum dabbler (coincidentally dabbled in bitflip quantum error correction research). Skimmed the post/research blog. I believe the key point is the scaling of error correction via repetition codes, would love someone else's viewpoint.

Slightly concerning quote[2]:

"""

By running experiments with repetition codes and ignoring other error types, we achieve lower encoded error rates while employing many of the same error correction principles as the surface code. The repetition code acts as an advance scout for checking whether error correction will work all the way down to the near-perfect encoded error rates we’ll ultimately need.

"""

I'm getting the feeling that this is more about proof-of-concept, rather than near-practicality, but this is certainly one fantastic POC if true.

[1]: https://arxiv.org/abs/2408.13687

[2]: https://research.google/blog/making-quantum-error-correction...

Relevant quote from preprint (end of section 1, sorry for copy-paste artifacts):

"""

In this work, we realize surface codes operating below threshold on two superconducting processors. Using a 72-qubit processor, we implement a distance-5 surface code operating with an integrated real-time decoder. In addition, using a 105-qubit processor with similar performance, we realize a distance-7 surface code. These processors demonstrate Λ > 2 up to distance-5 and distance7, respectively. Our distance-5 quantum memories are beyond break-even, with distance-7 preserving quantum information for more than twice as long as its best constituent physical qubit. To identify possible logical error f loors, we also implement high-distance repetition codes on the 72-qubit processor, with error rates that are dominated by correlated error events occurring once an hour. These errors, whose origins are not yet understood, set a current error floor of 10−10. Finally, we show that we can maintain below-threshold operation on the 72qubit processor even when decoding in real time, meeting the strict timing requirements imposed by the processor’s fast 1.1µs cycle duration.

"""

winwang··on My second year without a job
My friends have successfully relied on Medicaid during financial hardships + unemployment. At least in NYC, the Medicaid plans are quite decent.

Also, for those who require plans similar to the one previously provided, COBRA (18 months) is decent -- expensive but presumably less expensive than "equivalent" in the marketplace if we're talking about a good corporate plan.

winwang··on How to pack ternary numbers in 8-bit bytes
PAM3 for data transfer: https://www.synopsys.com/designware-ip/technical-bulletin/pa...
winwang··on Message order in Matrix: right now, we are deliberately inconsistent
I break up my messages, as do many people.
winwang··on Prioritize work at the task level
I actually thought you meant that this was about applying QoS algos to real life, before I saw the link lol.
← PreviousPage 8 of 15Next →