HN user

vapemaster

363 karma
Posts10
Comments31
View on HN

not hating on the great amber - but why LEaP on the front page of HN with no context...?

happy to see some light shown on the grim state of comp chem file formats and their shockingly lossy interconversion but I'm not sure that was the OP's intent?

long time windows user that switched to mac due to Apple Silicon dominance on the laptop experience.

This, 1000x this.

It's utterly bizarre that the window management paradigm is "let 'em all stack up and make it easy to spread 'em all out"

At first I thought I didn't get the paradigm. Now I get that I don't get the idea behind the paradigm.

Rectangle (pro version) fixes some of this and adds some really cool features. And because of the Apple app hegemony, it does work nearly OS level good. But why, oh why does this have to be 3rd party?

It's like some any UX pattern baked in since Lisa?

I immediately had to get Karibiner to at least give me my home and end keys back on a external keyboard.

I've been to aggressively remapping that I don't then create a similar problem when using another machine I don't own but maybe I'll give in and go the more custom route

agreed, I'm almost to muscle memory with it so it's not the "i have to think about it" annoyance, it's that my whole hand has to move to make it work... noticeably slower than my windows workflows..

cool i'll check out raindrop, thanks for the tip!

but i just wish there were some talented engineering teams at the leading browser creators (cough couch google, mozilla, MS, apple, etc) that would integrate this as a first class feature. a design goal, not a supported extension.

If someone criticizes your paper, and it gets pulled from publication, then thats the same as having never published anything in the first place. Therefore, the technique to survival is to write your paper in such a way that repels criticism as much as possible.

Not trying to be snarky, but that's not how publishing works.. you don't get a paper retracted for criticism, you get it retracted if there was scientific malfeasance. And retractions are actually exceedingly rare.

In fact having criticism / debate around your paper is a great way to get more citations, the real publication currency in academia...

When I read web3 co.'s product/ tech description it almost always feels like some form of tech. literacy gaslighting. I always feel initially like there's something elusive that I'm not grokking b/c I'm not a blockchain zealot.

Then I sit back and realize that it's usually because most of the examples I read are trying to solve non-technical problem (attribution, trust, etc.) with a buzzy tech solution all wrapped in a serious bit of speculation.

I think there's a lot of room for improvement in the tech of our law, banking, and logistics systems (COBOL--> anything else?), but the kneejerk to some "decentralized" system that needs total but in from it's participants to work actually seems more fragmented and fragile than our current institutions...

Hard Startups 6 years ago

So where is the geographic location that does fund hard problems?

SV $ is far from perfect but it is surprisingly audacious and fault tolerant.

A few examples old and young:

Genentech

SpaceX

Joby

TAE Technologies

That's like saying the single hardest problem in AI is having a beyond human intelligent general AI.

Sorry not trying to be pedantic but predicting what xenobiotics (ie foreign molecules) will do in the human body, much less a diverse sample of them is a really really really hard problem. One that will only be approximated and poorly at that. I'm sure there will continue to be approaches to reduce risk but clinical trials only exist because they have to. The only way we can evaluate safety and efficacy is empirically.

Predicting things like hERG toxicity is somewhat doable. And I think the realistic bright future of AI in medicine will include better on target tox prediction and some off target effects. But it's hard enough to design the drug to bind the target, imagine predicting it's affinity for all other proteins and their isoforms in the population...

interesting point. though this ignores the (surprisingly) successful re-purposing strategies to reduce future regulatory burden and and reduce or even eliminate high throughput screening campaigns. that well will dry up sooner or later but other discovery platforms ie phage display etc. have become commoditized and robust enough that they are pretty accessible to even low capitalized startups if finding a ligand is what you need to get off the ground.

Yup. And judging by their team and strategy they are likely using a highly empirical ligand discovery platform (ie DEL) and using the (admittedly best in class) MD for guiding med chem. Taking the hard problem of drug discovery and then saying you are going to do rational design (a road riddled with dead bodies) on dynamic alloseteric sites of challenging targets is a lofty goal to put it mildly..

So stoked this popped up. Literally woke up this morning debating about moving away from bs4 and wrapping the functionality I needed in lxml. I was just thinking I wish there was a requests equivalent for parsing...

what is the split that has to do with 2vs3? Really it just seems like some devs are still griping about fairly minor backwards compatibility issues. the whole print vs print() is obviously a straw man. but the major one, strings, unicode, and bytes, changes for the good in py3. the fact that people have to go back and "un-hack" their code is time, effort, and more commits but it's for the best.

<rant> i think the real split is between CPython + C-Extensions and the JIT (PyPy,Numba) gang for heavy lifting in python. I for one wish Guido would embrace the effort of integrating the GILectomy into CPython and make python thread parrallism real for CPU bound work as opposed to the high overhead multiprocessing approach.

Also, including mypy in the stdlib to make genuine optional static typing would make python a defacto standard for much of what it does now without the "we love python but...." production code pain points. </rant>