sbszllr · HackerTrans

3개월 전discuss

It's possible and even likely there's industrial espionage going on. But imo, you don't need that. I've worked in cutting edge industries, and even when you don't know what your competition is doing, there are usually only so many logical next steps.

sbszllr

3개월 전discuss

It's interesting how OpenAI and Anthropic effectively mass dumped a bunch of similar features in the last two days.

I wonder what other features they're cooking right now.

sbszllr

3개월 전discuss

Maybe it just shows my lack of tolerance for process/overhead.

As a fellow rebase enjoyer, I will do it occasionally for smaller PRs but to me, it becomes unwieldy for large ones.

Do you have any tips or aliases that makes it more workable?

sbszllr

3개월 전discuss

Let's forget that this post is an ad. I feel like there is a use for LLMs that could help us do stacked PRs better.

Right now there are effectively three ways to do a PR:

- a bunch of small commits, some of them related to the feature, some fixes, some mixing both -> a PR with 'n' commits -> they don't really make sense as atomic commits, you have to review the entire PR to make the sense of it

- a squashed PR

- some uber principled reorganisation of commits that separates key implementation concerns into smaller commits (effectively stacked PRs but clean)

The last option would be desirable but it's unreasonable to expect anyone to do it by hand. So this is where <maybe> an LLM could parse my garbage intermediate commits, the final diff and generate a stack instead?

sbszllr

4개월 전discuss

Daisy chaining finally supported.

sbszllr

5개월 전discuss

I was thinking a similar thing when reading the article. Often, the validity of the input depends on the interaction between some of them.

Sure, we can follow the advice of creating types that represent only valid states but then we end up with `fn(a: A, b: B, c: C) transformed into `fn(abc: ValidABC)`

sbszllr

5개월 전discuss

> We already had that disaster where pop-ups fly out "do you want to accept those cookies". That is just a usability nightmare. People are forced into extensions, just to stop wasting their time here.

You’re perpetuating a gross misunderstanding of the cookie law. What it states is different from how the advertisers implement malicious compliance to bias people, like yourself.

Websites that implement basic functional cookies do not need to display any popups. They’re permitted to do so. Any cookies that are essential to the functioning of the website within reason are permitted. In fact at no point a website should serve you a cookie popup unless you seek it out because analytics and advertising cookies are supposed to be opt in.

So many websites do two things, serve you a popup that has everything enabled which is a clear violation; or a popup that has only functional cookies selected but the biggest highlighted button allows all of them.

The law is fine. Malicious compliance is to blame. The EU has been slow to rectify it.

sbszllr

6개월 전discuss

The quality and usefulness of it aside, the primary question is: are they still collecting chats for training data? If so, it limits how comfortable, and sometimes even permitted, people would with working on their yet-to-be-public work using this tool.

sbszllr

6개월 전discuss

I agree that is performant enough for many applications, I work in the field. But it isn't performant enough to run large scale LLM inference with reasonable latency. Especially not when we compare the throughput numbers for a single-tenant inference inside a TEE vs batched non-private inference.

sbszllr

6개월 전discuss

Interestingly enough, it is possible to do private inference in theory, e.g. via oblivious inference protocols but prohibitively slow in practice. You can also throw a model into a trusted execution environment. But again, too slow.

sbszllr

6개월 전discuss

These are fair points but the weight of their impact is a misconception. Times and times again, lower capital and investment risk aversion are shown to be the limiting factors.

sbszllr

7개월 전discuss

There's a lot of truth and real pain points in the article but others miss the point entirely. Two things that stand out to me in particular:

- C "standard" is quite flaky in practice, there are lots of un/underdefined things that compilers interpret quite liberally for the purpose of optimisations

- complaining about the syntax and symbols is unfair: rust offers all these semantics to represent the memory model of your codebase. The equivalent is not possible in C/C++, and when we try to do it, we're inventing our own constructs at the code level instead of relying on the syntax

sbszllr

8개월 전discuss

I've been camera scanning 4x5 and I'm happy with the results. Take two offset photos and stitch them in post. Mind you, I scan with pixel shift for higher res.

sbszllr

8개월 전discuss

As someone who has a mirrorless scanning setup for my film, and pondered getting a dedicated scanner... the price of this is quite steep given how inflexible of a tool it is.

A second hand DSLR setup is going to be roughly the same price or less. I'm also not sure what kind of workflow improvements it actually offers. If you want fancy and experimental, filmomat has arguably a more interesting but pricier offering.

But naysaying aside, I hope they manage to find a niche that allows them to survive as a company, and keep the analog photography revival alive.

comments