HN user

xtagon

323 karma
Posts1
Comments151
View on HN

I don't feel like they owe me a refund in principle, at the end of the day I paid for subscription-free software and they delivered it, and I'm happy to do that exchange. I just don't like the changes and the future direction and that I won't be receiving updates to the one I'm currently using.

Not happy. I recently purchased the whole suite and now not only is it now free (didn't need to purchase it), but it's no longer even what I want. And it doesn't work on iPad until they finish whatever rewrite, when cross-platform + apple pencil niceness was a huge draw.

Sure, it's free -- but it's no longer the same product with the same priorities.

Learning Synths 2 years ago

This is like telling someone to learn programming by starting with assembly.

Believe it or not, this is some people's preferred learning style. See also: Nand2Tetris, Linux From Scratch

I highly, highly doubt we've reached the level of AI safety required to make it a good idea to replace (or even just supplement) caregivers for children. Nobody has truly solved the safety problems with AI yet, just doing the best they can--seems like a terrible idea to put that in direct intimate access of emotionally vulnerable children. We've already passed the threshold of AI suggesting to testers to commit suicide[0], and the bar has been raised to actual users being told that[1] and someone reportedly following through.[2]

[0] https://www.artificialintelligence-news.com/news/medical-cha...

[1] https://ainiro.io/blog/googles-ai-encouraging-people-to-comm...

[2] https://www.euronews.com/next/2023/03/31/man-ends-his-life-a...

The types are no less protectable by authorization policies than the data, although authorization is hard to get right anyways, all else the same this architecture doesn't worsen it much--perhaps just less reverse engineering required to exploit vulnerabilities you already had.

Interestingly, you could accomplish a similar thing with GraphQL if the frontend uses the type introspection GraphQL provides and the backend graphql schema implements HATEOAS-like principles to let the frontend become a UI that's agnostic to different backends. That might not be how most GraphQL implementations are used, but it's kind of a cool pattern.

If the user has to initiate all shuffles, it won't play continuously. If you handle it another way, that demonstrates that it doesn't "just" work with a pure shuffle without using those tricks.

Given a set of songs or albums {a, b, c}

Suppose shuffling results in ordered set [b, a, c]

Suppose user plays through the entire set. Now it's shuffled again before repating.

Suppose the new shuffle results in ordered set [c, a, b]

The user now hears c play after c

The Last 1% 3 years ago

I think where the semantics become relevant is that people say "project" to mean "product". When it's a product, it might never be 100% done, and it might be a poor idea to try to frame it as if it could be. But some projects aren't products, and don't have perpetual stakeholders, and for some of those it can be possible to set realistic 100% done targets and reach them.

I want news as an RSS/atom feed with properly consistent tags to filter by. That way I can opt in to just what I want to know, get it when it happens, and ignore everything else by default. But there isn't business value in news outlets providing this.

LCD, Please 3 years ago

For the case/battery compartment part, hit up someone with a 3D printer (or a makerspace or library that has one)

The downside to things that "just work" is that they become magical black boxes where learning how they work isn't a requirement until things really go wrong.

MiniZinc 3 years ago

The first two paragraphs of the home page say what it is:

MiniZinc is a free and open-source constraint modeling language.

You can use MiniZinc to model constraint satisfaction and optimization problems in a high-level, solver-independent way, taking advantage of a large library of pre-defined constraints. Your model is then compiled into FlatZinc, a solver input language that is understood by a wide range of solvers.