HN Simulatornew | past | comments | lists | submit | fleventynine's commentslogin

I don't think society has enough power to control what billionaires spend their money on. The promise of AI is such an attractive nuisance for power seekers that trying to crack down on it will just force it underground, where it will be developed with even less care and oversight than it is now.

Our institutions aren't even able to control what dirt-poor pirates do on hardware they own. How in the heck are they going to be able to control what incomprehensibly-rich people do? They can purchase political favors from whichever nations are selling them.


> trying to crack down on it will just force it underground, where it will be developed with even less care and oversight than it is now.

With way less access to infrastructure, hardware, capital, people. That’s literally what we need, it should be constrained by having way less resources


Having fewer resources such as security engineers will not lead to better outcomes. A skeleton team with gigawatts of compute in some middle east bunker is MORE likely to unleash something poorly aligned.


Gigawatt of power doesn’t come from nowhere. You cannot have that much power consumption without being visible to regulators (of course that assumes a government that isn’t as corrupt as the US).

You can create bioweapons today, from a small lab. Doesn’t mean we allow it


Advancing the state of the art takes so many resources that it can't happen underground, at least for now. Slap enough controls on the means and the handbrakes are on. So your doomsday scenario could be preventable. The crux is that enough people need to come out in favor to put constraints in place. It's not impossible, but public opinions form slowly.


Ugh, the accidental complexity of drop-frame encoding, BCD, etc... This mess will likely be with us for a long time.


Troubleshooting SCC captions in the digital era is quite an experience. Haven't gotten any request for them in a couple years though.


Had to make an account just to comment.

I think many people here would be very surprised at how common these are still.

In my work, we get SCC ordered CONSTANTLY, even when the intended platform it’s for is fully digital.

I feel it’s a mixture of misunderstandings between that and SDH in addition to just people using subtitles and captions interchangeably.


Just because it's fully digital means what to you?

To the viewer relying on captioning, it makes no difference whatsoever. Captioning is decoded by the TV itself. Subtitles are overlaid by the app. Streaming sources when decoded send the embedded captioning to the same caption decoder as OTA broadcasts or decoded from a VHS tape.

From someone that has spent decades working with subs and captions, the differences are obvious. To everyone else, it's just text on screen regardless of what it is technically


People that roll their eyes when you correct them in stating captions and subtitles are NOT the same thing have clearly never worked with captioning. However, I'd much rather work with them as SCCs over the old way of using a CAP file and hardware encoder connected to a PC. Unfond memories of inserting captioning to to the same tape using pre-read where it reads from the tape, sends the signal to be captioned, and then records the data back to the same tape. In real time.


The solution for this is to pay open source maintainers for their attention. If I want them to review and merge my bugfix I should attach $1000 to the PR.


This is actually not a bad idea for funding open source software. It used to be that you’d have an author who coded a project and then could fix the occasional bug or two quickly.

Now, we have larger projects where it is rare for one people to have a complete understanding, and the main value is a person to reviewing patches and bugs to make sure the changes align with the larger goals/path for the project. There is little incentive for a maintainer to do this, aside from wanting to limit forks.

Paying for that review might be the way to keep this whole model sustainable.


Opportunity for gh

“Here is my pr I attach x$ payable when it is merged” and allow me to add $ to other prs.

I have been waiting year + for multiple feature in some projects that have open prs and for one I would easily bid 100-200$


Maybe instead of the emoji buttons Github should let people attach money to the issue.

If that gets fixed, the project gets the money.


Maybe a donate link attached too. The dollars tied to a PR could help set priority of fixes.


I typically work with commit chains of at least 5 commits in various states of code review, so I spend at least 60% of my development time editing an old commit in the middle of a rebase -i.


You might find `jj` to help you there: all changesets have stable identifier and their content can be updated at any moment in-place.

TLDR; `jj edit ; $EDITOR` will update a commit in the middle of the branch


Not an option for me until it supports submodules.


Prior to `jj` my happiest git discovery was https://github.com/ingydotnet/git-subrepo to replace submodules.


This machine needs better networking options to be useful, such as built-in 100Gbit QSFP28. There is not enough space between the x4 PCIe slot and the power supply for a NIC to fit, and even if there was, you'd have to cut a hole in the back of the case to get at it.


I like Rust and use it full-time professionally. Unsafe is not the same as unsound. Unsound means that the unsafe code is not maintaining the aliasing invariants on references required by the language, and thus undefined behavior can leak into safe code (that is, the safe code can be miscompiled).

Known unsound code should not be merged, let alone released to production. If you have good enough tests and run them under MIRI or ASAN, maybe you can get away with it for a time, but most Rust experts would not sign-off on such a project.

If somebody put a gun to my head and told me to make the best of such a codebase, I would try to figure out how to turn off the LLVM optimizations that assume the Rust references don't alias. With these optimizations this codebase is scarier than most C or C++ code.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: