5,854 karma · joined September 17, 2010
The "10 days left" thing seems to be a hoax(?)
https://www.msn.com/en-us/politics/international-relations/m...
https://www.malaymail.com/news/world/2026/03/26/is-taiwan-ru...
If you work from home, your office at home usually does not qualify as a company office unless you make it one. In particular, that alone would not force you to pay Gewerbesteuer to the city, which is the tax specifically addressing local presence.
However, you're touching upon a very important point: If you live in Germany and your Estonian company pays you a salary (as opposed to dividends), you will be a proper employee and your company will also have to pay social security for you, and this might complicate matters significantly. In fact, this will likely (in the German tax authorities' eyes) establish that your Estonian company partially operates in Germany (which is a much broader thing than having an actual physical branch office). This then brings you back to square 1 – your company having to file taxes in Germany, too. Someone below linked https://eidel.io/posts/estonias-e-residency-is-awesome-and-s... which seems to confirm this.
> German tax authorities will see that as an illegal dividend payment from your company.
Could you elaborate? How is this illegal if you declare taxes?
So how would nested tags interact with albums? Will I also be able to share (or contribute to) tags like I can share (or contribute to) albums? Actually, aren't albums already "tag-like" in the sense that photos can be assigned to multiple albums at the same time?
> And while we're not prioritizing this specific feature, I don't think it is fair to say that we do not invest time into polish. We do care about our craft[0][1][2].
This was overly harsh, my apologies!
> I think it's important to offer a complete package
I agree. But doesn't that start with making one product (Ente Photos) good enough for people to actually be able to migrate? If Ente Photo really is your "home ground", as you say, shouldn't you prioritize accordingly? Specifically, in your response[0] to the GitHub issue I linked you say
> to pull it off with the finesse we would like, it will take us more than a quarter. […] I will mark this feature as unplanned until we have more engineering bandwidth.
But it seems you really do have the engineering bandwidth! You've just been prioritizing other products besides Ente Photos. I do understand that folder nesting in particular is a non-trivial change and if you look at the discussion on GitHub, I've actually been defending you rather heavily. But it's becoming increasingly difficult to do so – quite frankly, I am starting to doubt your product management is entirely on the right track if in 3 years you can't dedicate 3 months to the feature request with the highest number of votes by far. More generally, I am losing trust that any of your products will see enough polishing any time soon. (So I will definitely not put time into migrating anything else if I can't even migrate my photos yet.) And it seems I'm not the only one thinking that – your reputation among enthusiasts is starting to take a hit.
> There is no way Ente is going to let anyone else build a better photo app.
Words to live by! :-)
[0]: https://github.com/ente-io/ente/discussions/552#discussionco...
> Ente is becoming like Proton: too many products and a lack of focus, leading to lower quality and not delivering what customers want
https://github.com/ente-io/ente/discussions/552#discussionco...
> Today, you open facebook, the creators of React - normal drop-down with just a list of barely 5-6 items is a fucking component that makes 10 different requests. I would even argue this unnecessary forced interactivity is what perhaps annoyed users the most as everything always has to "load" with a spinner to the point of the platform being unusable.
That's a design decision, though. Sure, your point is basically that React is not opinionated enough and allows you to do anything. But in the same way you could criticize JavaScript or Python because they allow you to do "anything" and some people write shitty code.
"just" is doing a lot of heavy lifting here. Where do you store "pure" GUI state (button state, is expandable expanded, …)? Do you really want to setup Redux for this? (And no, the DOM is not an option in non-trivial cases.)
Is there really a difference? Angular uses RxJS in a pub-sub scheme. (At least it did when I last used it.)
It's not, and the authors doesn't have to. Using your definitions, `f . g` is a function of a single free argument (whether you call it x or y or whatever). Partial application occurs when you want to fix some parameters but not all of them. In the present case, however, there is only one parameter (x) and it's not fixed, so there's no partial application to speak of and one can omit the parameter as usual.
Put differently: (.) is a binary operator on functions, and length = f . g from the OP is an equation of functions. You can certainly write it down pointwise, i.e. length(x) = (f . g)(x), but that doesn't tell you anything you didn't know already, and it is unrelated to the case of partial application that the author is discussing.
Neither of these functions is being partially applied in the code you cited. While the placeholder $ can be used to indicate all "free slots" of a function, you would only have to use it in partial applications of that function. (Analogous to how in mathematics the abstract index notation for tensors[0] is only really useful when you start contracting tensors, etc. Otherwise, the plain objects/tensors without indices are much easier to write & read.)
Specifically:
- (+) was already a function of two arguments, so usage of $ is unnecessary since (+)($, $) == (+). Similarly with the length function (a function of 1 argument): length($) == length.
- Function composition was being used as a binary operator between two functions. You just replaced the infix notation with prefix notation.
- I read const(1) as the function that maps everything to 1. I.e. `const` is a function of one argument x, which returns a function that always returns x. Once again, no need to indicate slots there.
[0]: See https://en.wikipedia.org/wiki/Abstract_index_notation and https://math.stackexchange.com/questions/455478/what-is-the-...
[0]: https://mynixos.com/nixpkgs/option/programs.nix-ld.enable
I'm surprised! Pijul has been discussed here on HN many, many times. My impression is that many people here were hoping that Pijul might eventually become a serious Git contender but these days people seem to be more excited about Jujutsu, likely because migration is much easier.
Last year I switched to NixOS and while my impression is that it's going to be much more stable even than Ubuntu, installation also only takes me 5 minutes. That is, 5 min until my system is in exactly the state I want, including installed software, window manager config, keyboard shortcuts, desktop wallpaper, GUI theme, etc.
I ended up installing VMWare and using a full Linux VM. Yes, VMWare. That's how desperate I was.
That's what I thought should do the trick, too, but for me it worked neither in Firefox nor in Chrome. (I have a Pixel 10 Pro, so the resolution should definitely be high enough.)
"The only change" – with all due respect, are you even listening to yourself? The "only change" is that you, as a developer, will be completely excluded from publishing apps in the Play Store and that people effectively won't be able to install your app anymore! (Unless you were targeting only e.g. F-Droid users to begin with, which very few apps do.)
In essence, you are cutting down on the privacy of tens of thousands of honest developers around the world in the name of protecting users from scammers and you're pretending that 1) it's a nothingburger and 2) developers have a choice.
Note that the OP is about side loading, i.e. installing apps from non-Play Store sources and thereby circumventing developer verification.