is there still more to do in protein folding after AlphaFold?
https://www.isomorphiclabs.com/articles/alphafold-3-predicts...
9,719 karma · joined June 9, 2011
L6 @ Grafana
https://github.com/leeoniya
leeoniya_at_gmail
is there still more to do in protein folding after AlphaFold?
https://www.isomorphiclabs.com/articles/alphafold-3-predicts...
if LLMs arent being used by https://patents.stackexchange.com/ or patent troll fighters, shame on them.
now let's invalidate probably 70% of all patents
"The World's Largest Subterranean Lake Is A Vibrant Scuba Diving Paradise In Missouri"
[1] https://github.com/leeoniya/uMarks (WIP!)
[2] https://www.w3.org/TR/SVG/implnote.html#ArcConversionCenterT...
i suspect humans had to invest millions of hours into writing the code, the tests, and validating the outputs.
let's see how that holds up against "author does not understand own PR"
i refuse to review PRs that are not 100% understood by the author. it is incredibly disrespectful to unload a bunch of LLM slop onto your peers to review.
if LLMs saved you time, it cannot be at the expense of my time.
would you ever trust safety-critical or money-moving software that was fully written by AI without any professional human (or several) to audit it? the answer today is, "obviously not". i dont know if this will ever change, tbh.
Previously:
“All of humanity’s problems stem from man’s inability to sit quietly in a room alone.”
-- Blaise Pascal (~1650)
is it OSS? i'd like to benchmark it against my csv parser :)
if i had a nickel...
c'mon, you're talking about 200 LoC here. anything except BrainFuck would be maintainable at this scale.
have you ever had to fix a non-trivial third party WordPress plugin? the whole API used to be a dumpster fire of global state and magic functions. i dont know what it is now, but 15 years ago it was a total nightmare.
https://www.socialscience.international/making-deepseek-spea...
can you share some tech details?
they're marginally better since they have a platform-defined way to deliniate static from dynamic parts. ivi _can_ work without a runtime or build-time JS parser, while JSX cannot (because jsx has to be parsed out of full blobs of js)
on the dx/ide side, sure there's not a huge amount of difference if both had the same effort invested.
for perf, s/JavaScript/DOM, i think.
good DX comes from ecosystem and amount of time invested in making good tooling. JSX would be a non-starter without IDEs helping autocomplete, linting/format, syntax coloring, and webpack/babel to do the compilation.
tagged templates could reach at least the same level of DX as JSX if the community invested the resources to make that better. i'm not saying it's the right solution for a standard, but it would be way better than jsx, since tagged templates are already a standard.
there are multiple frameworks now that do fine-grained diffing without relying on signals, proxies, or any other reactive primitives. they basically have the top-down react model but much faster and without the weird concepts like hooks and manual/wasteful dependency arrays.
my favorite one is ivi-js: https://github.com/localvoid/ivi
it's just 8% slower than the fastest / ugliest / imperative / unmaintainable vanilla js you can eventually arrive at if all you care about is winning benchmarks.
https://krausest.github.io/js-framework-benchmark/2025/table...
an expert can write 10 lines of code that will be hyper fast while an LLM will write 30 lines that are super slow. both "will work", but one will fall over under load and will be hard to maintain and the other will not.
AI is not an expert programmer [today]. and it doesnt take an expert programmer to arrive at that conclusion.