HN user

_bent

312 karma
Posts0
Comments78
View on HN
No posts found.

It goes against Postels law, but it's much simpler and less error prone to only accept data in the representation you actually use for further processing, vs writing an ad-hoc parser and normalizer.

just a quick example from the backtracking section:

"Here's the dirty secret of WFC: it fails. A lot. You make a series of random choices, propagate constraints, and eventually back yourself into a corner where some cell has zero valid options left. Congratulations, the puzzle is unsolvable."

It's extremely distracting to read heavily ai edited texts like these because every single aism throws me a curveball.

It doesn't help that the figures of speech ai loves to use are those that stress things and create tension and drama. And it uses one in every single paragraph, rendering the text into the literal equivalent of a deepfried faux HDR jpg (or a dialogue scene in a Michael Bay movie).

And beyond those practical concerns it's just hard to gauge how much the author truly understands of what he's writing about (and transitively if it's worth to continue reading)

Wero is a land grab by the banks who fumbled building a PayPal alternative for 20 years, now desperately trying to stop the digital Euro.

Sure I'd rather use Wero than PayPal -if it was decent- and building it on top of SEPA instant transactions is neat. But the lack of buyers protection is a deal breaker for me! And quite frankly I'd rather use a digital Euro governed by the ECB than some rent seeking hobby project by a bunch of private banks. Especially because they will inevitably enshittify it with ads and hostile BNPL like PayPal.

I think it would be better to defer the Workspace trust popup and immediately open in restricted mode; maybe add an icon for it in the bottom info bar & have certain actions notify the user that they'd have to opt in before they'd work.

Because right now you are triggering the cookie banner reflex where a user just instinctively dismisses any warnings, because they want to get on with their work / prevent having their flow state broken.

There should also probably be some more context in the warning text on what a malicious repo could do, because clearly people don't understand why are you are asking if you trust the authors.

And while you're at it, maybe add some "virus scanner" that can read through the repo and flag malicious looking tasks & scripts to warn the user. This would be "AI" based so surely someone could even get a job promotion out of this for leading the initiative :)

Blender 5.0 8 months ago

Not disagreeing that usage in large productions is something that Blender isn't really designed for, but I don't think that it's for a lack of Python API features (if a studio wants something specific it could just maintain an internal fork) or the ever changing Python API surface (the versions aren't upgraded during a production anyways)

Blender 5.0 8 months ago

What Blender achieved is that lots of university programmes have started teaching Blender or becoming 'tool agnostic'. Studios have also started diversifying their pipelines (this coincidences with studios adopting Unreal and increasing usage of Houdini).

So while Maya is currently the standard, I don't believe that it's growing. It'll probably be around still in 20 years, with lots of studios having built their pipelines and tooling around it, with lots of people being trained in it, and because it's at the moment still better than Blender in some aspects like rigging and animation (afaik).

I know you're looking for something more universal, but in modern video workflows you'd apply a chain of color transformations on top the final composited image to compensate the display you're working with.

So I guess try separating your compensations from the original work and create a workflow that automatically applies them

The original Affinity business plan included selling assets like brushes, textures, LUTs via their store. I guess this wasn't wildly successful and at some point every single person that would be interested in a professional grade design suite for 50€ each (often discounted to 35€) has already bought it.

macOS is the only OS you can write native applications for. On Linux there are with GTK and QT two different GUI frameworks that could be considered native on some distros. And on Windows there are so many different frameworks and approaches used by MS for the shell that even a Webview could be considered native

For final export? AVIF, JpegXL, maybe even WebP (lossless mode).

PNG kinda sucks for high resolution stuff because decoding is extremely slow. The way PNG does lossless compression also only really works with flat graphic design, anything with gradients or texture blows up the file size.

Thoughts on Omarchy 9 months ago

CachyOS is also an Arch based distro with a GUI installer including multiple desktop options, such as Gnome, KDE Plasma, but also preconfigured Hyprland or Niri with a Waybar, Alacritty and a spotlight-esque application launcher.

I'm currently dual booting Windows & CachyOS with Niri and installation was incredibly smooth, including setting up secure boot or playing Windows games.

https://cachyos.org/

Lytro light field cameras. The tech was impressive and the company was able to put two products on to the shelves, though unfortunately they hadn't quite reached the image quality needed for professional photographers.

But now with the new Meta Ray-Bans featuring a light field display and with new media like gaussian splats we're on the verge of being able to make full usage of all the data those cameras were able capture, beyond the demos of "what if you could fix your focus after shooting" of back then.

Beyond high tech, there's a big market for novelty kinda-bad cameras like Polaroids or Instax. The first Lytro has the perfect form factor for that and was already bulky enough that slapping a printer on it wouldn't have hurt.

iirc Atom was the original Electron project. Eventually VS Code came along and took all the good ideas - the modularity through extensions, and Electron / web based cross platform, but made it really fast and added IDE like language support through LSP. Atom may be dead now, but the idea lives on in VS Code and the new project by the original developers of Atom: Zed

Somewhat - Kling is explicitly 'apolitical' and this always attracts a certain ilk of people.

---

And - maybe this is a stretch, but you also have to consider that the competing product (Servo) is written in Rust, while Ladybird is C++.

From what you read on hn, I think Rusts community being very liberal sort of resulted in memory safety being perceived as a culture war thing by some; ("authoritarian big compiler is forcing you to not free this memory" vs "the handmade c programmer with his artisanal allocations"). So Ladybird not being written in a safe language might be part of the appeal.

And I know that Ladybird is supposed to adopt Swift, but I don't think any single LOC has been written yet?

It's annoying, but not for the error handling. To the contrary, I think the error handling is actually improved by this pattern. If you manually convert beforehand you easily run into working with a Result<Result<T, E>, E>.

What I find annoying about the pattern is that it hinders API exploration through intellisense ("okay, it seems I need a XY, how do I get one of them"), because the TryFrom (sort of) obscures all the types that would be valid. This problem isn't exclusive to Rust though, very OO APIs that only have a base class in the signature, but really expect some concrete implementation are similarly annoying.

Of course you can look up "who implements X"; it's just an inconvenient extra step.

And there is merit to APIs designed like this - stuff like Axum in Rust would be much more significantly more annoying to use if you had to convert everything by hand. Though often this kind of design feels like a band aid for the lack of union types in the language.