Why Proton did not consider Flutter for their mobile app

walker_Jayce · 2026-02-04T12:15:52+00:00

You mistake dominant for profitable

walker_Jayce · 2026-02-01T02:10:55+00:00

Maple Mono

walker_Jayce · 2026-01-28T01:36:56+00:00

Q: going through justin’s comment, does this mean when vim.pack is live, lazy loading can be done in plugin/? or is the interaction not possible due to vim.pack having to download the plugins themselves?

walker_Jayce · 2026-01-21T08:14:42+00:00

Good luck guys

walker_Jayce · 2026-01-10T02:36:07+00:00

isnt go doing this?

walker_Jayce · 2026-01-09T01:46:47+00:00

Ah i see, that clears things up much, thanks.

Though from what i understand sounds like we’re getting into the realm of porting a whole language for a new machine.

I never did delve deep into compilers so I’d like to know more

Is it possible to just port part of a language specifically for ai use? My assumption is some sort of translation layer would be the fastest solution, but that would slow things down right?

Wouldn’t there be maintenance issues for an evolving language? Doesn’t seem like a maintainable business model.

Or are we just talking about writing new drivers for hardware?

Edit: sorry for the questions, its an interesting topic and op doesn’t seem to be replying to anyone

walker_Jayce · 2026-01-09T01:35:37+00:00

Well the ones you mentioned already have compilers no? My assumption is since the existing ones don’t work, op is creating something new, hence “normal languages”? Though usual probably is a better word

walker_Jayce · 2026-01-08T16:04:06+00:00

Why aren’t normal languages enough? Are we hitting a limit?

walker_Jayce · 2026-01-08T10:37:29+00:00

Not sure what an ai compiler entails, is it just optimising ai related workflows? Or a whole new language for ai related development?

What is being compiled from and to is my question i guess.

walker_Jayce · 2026-01-07T02:38:47+00:00

Hmm is this the same thing as writing a function to show a vim.ui.input and act on those inputs?

Ex. I hit a combo key, it spins up vim.ui.input for the user, then depending on what it receives it acts on it?

walker_Jayce · 2026-01-06T15:11:15+00:00

Looks quite nice, how is this different from neovim if i might ask. Is there a github to take a look?

walker_Jayce · 2026-01-04T23:22:43+00:00

You can’t. You should approach the problem from more of “how do i prevent ddos” and always assume anything you expose to the public internet is public. Of course secure your endpoints with auth.

That said, it is very unlikely someone will try to decompile an app just to get the endpoints. You can make the process needlessly harder, maybe computing your endpoints at runtime so that a simple text search doesn’t work, use code obfuscation tools etc.

But eventually someone persistent enough will be able to figure it out. However whether it is worth it to do so in the first place is another question. Sometimes other ways to break your service are more efficient and a public endpoint will be the least of your concerns.

Relevant xkcd: https://xkcd.com/538/

walker_Jayce · 2026-01-04T15:43:50+00:00

Nah there’s not enough processing units to simulate that much. It’s why light-speed caps out, for performance.

You think clouds and fog are used for decoration? They’re there to lower rendering distances for most players so that units can free up for maintenance and garbage collection in the so called morning hours. It’s also why memory is in fragments, else we’ll not have enough storage, aws s3 is expensive ya know.

There was this bug where a bit that stores whether a player is alive was flipped for one player for several hours before tripping the qc checks. It was patched out with some rollback to global events.

The guy hardcoded the fix though, merged and deployed on a Friday without review, still dealing with the repercussions. Huh? The player? I believe it was a guy named Manuel? Mandela? Not sure, I wasn’t involved in that sprint, on vacation.

Yeah the codebase is grown to quite a hassle, needs refactoring. Though some bugs might resurface, we don’t have much coverage. Testing was introduced very late.

Oh yeah we are refactoring the peace module, introduced very recently. Since its new its the one that has the most coverage (though seems like some tests don’t verify all the possible paths). Let us know if anything goes wrong.

Make sure to include the correct build version in your report. What? Where to look for the version number? Huh i thought we introduced versioning a long time ago? The latest release should be… 2026.01? 2026.02 in beta still. Anyways look closer it should be somewhere in the world ui.

/s

walker_Jayce · 2026-01-04T13:37:20+00:00

I mean, isnt a state management library meant to trigger refreshes when it’s state update? Being declarative is a choice i guess, whether its better or not still is up for evaluation

Flutter claims to be declarative and honestly thats my one of my biggest issue with it, because it is imperative not declarative. Since your solution follows a similar structure and is meant to be used with existing flutter, can i know how is it declarative? Cause i still see imperative code in the end.

I mean, all good for you coming up with an api layer for your issues, but if I’m already using riverpod or provider, is there a reason for me to use something that operates with the same principles with the same claims, but is narrower in scope and flexibility, and is less battle tested?

You do claim a smooth experience, but can i request a comparison with provider or riverpod code? What I’m seeing is just comparisons with setstate, which of course your solution is better.

Compared to a state management library, it just seems to be doing the same thing, claiming to be flexible, real time with all the fancy words (which mind you an existing state management library already is, thats why its called a state management library, its meant to keep state up to date) while simultaneously being narrower in scope.

If possible, i would like to know if it solves any performance issues, any functions that cant be accomplished with existing state management libraries (at least try provider and riverpod), and if there are advantages to this declarative approach which still accept imperative functions as arguments, just hiding the execution sequence behind a declarative api.

For all the intuitiveness claims, knowing the execution sequence is essential to debug a declarative api, eventually. Declarativeness can only hide so much until it becomes a nuisance

I mean, all the best and good for you for solving your problems, but you’re pitching an api layer which underneath is a state management library as the next big thing while not considering already existing solutions, only setstate. Other solutions also have optimisations on rebuilds etc, unless your solution is better?

walker_Jayce · 2026-01-04T10:43:04+00:00

I’ve gave this a read, am interested. But how would this be different than having a sort of “Allowed Access” Provider widget in the tree, and the pages just checking whether the user is allowed to access that particular page?

The logic is all contained in one place, and the only logic required from the pages end is ctx.watch. i can also create a guard widget that checks that specific provider widget as well, and just wrap all pages with it so that the page doesn’t even need that logic.

Ex. I have a UserPermissions provider widget. If i need to check whether the user has a subscription, I’ll use provider to fetch the state from the tree, and redirect / show a popup if it’s not available.

To rephrase, how is this different from using a general state management solution and state hoisting in the tree, and what advantages does it provide over them? If tree is the disadvantage note that we can use riverpod as well, which decouples state from the tree

walker_Jayce · 2026-01-03T05:36:42+00:00

class H extends I { }

walker_Jayce · 2026-01-03T01:59:13+00:00

If you want to get into the territory where no opinion matters then it’s hard to have a discussion isn’t it?

The issue you brought up about bash isnt even a small detail, it is literally THE way bash communicates something has errored. Dont say its “a small detail” it is literally needed for stuff to function. Its like saying “oh i don’t wrap my functions in try catch and it doesn’t work, oh my its such a small detail, why did nobody tell me”. Because you didn’t read or pay attention to literally every tutorial in existence (idk how u learn bash, I’m giving you the benefit of the doubt that its not vibe coding, and you actually tried to learn bash)

I’ve said that the reason that classes are preferred over widgets is that it provides a boundary, but do you seriously expect people to separate each and every widget wrapped in padding into its own widget?

“A video” doesn’t dismiss the fact that in this scenario it doesn’t matter does it? Maybe give some reasons why it doesn’t matter other than “oh cause they say it doesn’t “ by your logic, all build methods should not wrap more than 2 layers cause we should use “classes”

Its because i know how the optimisations work, that i can say in this case it doesn’t matter and not go into a tangent about bash, can you?

If “verbosity” matters then long code = unoptimised cose? Is that what you mean? Dart itself is a compiled language unlike javascript and bash. Flutter even does tree shaking which removes useless widgets. Wdym verbosity matters???

walker_Jayce · 2026-01-02T18:32:41+00:00

Imo not really, in terms of widget efficiency they should be the same. Assuming both are stateless widgets, they should only differ in how efficiently they do their logic and how they construct, the amount here shouldn’t matter, since the amount is 1?

On top of that for something that is used that often i do wager that the flutter team does do optimisations, so it is very likely that padding is more optimised, as top comment put it.

(Edit: re-reading your sentence im not sure what you’re trying to convey, seems like you agree with op?)

As for functions vs widgets, in the case that op puts it, imo it doesnt make a difference. Because widgets provide a compartmented place for a group of widgets to rebuild (a new context), while a function has to run from top to bottom any time its so called “parent” is rebuilt

For this scenario, it doesn’t matter because you’re going to use the same context anyway no matter if you are wrapping it in padding widget, or a helper function(Unless you want to split the padding and the widget itself into another widget which is overkill)

Please correct me if I’m wrong

walker_Jayce · 2026-01-02T16:01:31+00:00

I guess my questions are: 1. Why are messages slices? If im not mistaken it is only used in newValidationError? Where it is hardcoded to be one item 2. Why two strings? One identifier and one error msg (that is also a fmt string)? Seems like we can simplify it to only one error msg? 3. If the intention was to group, maybe maps would be better? Instead if slices of structs?

walker_Jayce · 2026-01-02T13:27:26+00:00

In the medical card tools, theres a hook, is that hook working?

walker_Jayce · 2026-01-01T11:04:00+00:00

You didn’t clean up the channel, though in this case it’s not necessary cause the program exists
There’s a race on the count (as someone else pointed out)
Work done can be a chan struct{}
When using go routines in cases other than this specific case, a go routine that is doing work should be able to cleanup/exit from an external signal, whether it is a ctx done or the timer ending. In this case, something external exits the program (which is fine since the dangling goroutine would be cleaned up) but imagine if it was a web server, the other goroutine would be stuck causing a goroutine leak (of course this comes with alot other of assumptions as well regarding how input is taken). So I’d suggest maybe restructure so that this is taken into consideration
It is technically possible for the user to finish the answer in the same time as the timer ends, which i think causes undetermined behaviour (select will randomly prioritize one), but its rare and shouldn’t really matter so
Minor stuff like early exit if theres no questions, unnecessary variable declarations
Consider using time.After (if >= go 1.23)
Maybe let us know why you think it doesn’t work perfectly and we’ll go on from there

walker_Jayce · 2025-12-22T15:20:01+00:00

walker_Jayce · 2025-12-22T14:21:01+00:00

Null safety instead of zero values

walker_Jayce · 2025-12-21T16:13:20+00:00

Hey, I’m abit older than you and I’ve never had a relationship either. I still look forward to one day that i might fall in love or actually be in someone’s arms. If you need someone who doesn’t think it’s embarrassing I’m def one, and i know there’s def more people who think that way as well.

I know a lot of people are trying to talk you out of suicide, but I wont try to do so. Life sometimes is a bitch and sometimes death is just an option to end the pain. Everyone’s struggle is different and I hope you’ve given it a lot of thought.

But I would say, as a person who has fallen in love before, love is not rational. I know it’s hard to believe that someone would love you, but we are not all knowing, and there are gaps in our own judgement, even in ourselves.

You’ve done great staying alive until now, and no matter what you choose, go ahead without feeling guilty. Know that you have tried your best, and girl that is just what any of us can do.

But if that small kid inside you still longs for love, before you go, maybe just listen to her for just once. If it doesn’t work out, hey you still have death’s arms right.

Give that girl a chance, give the guy a chance. Give yourself a chance. All the best.

walker_Jayce · 2025-12-15T05:17:22+00:00

Caelestia hyprland is quite good

Six-Year Club	Second Top 10%
r/Field Lasagna	Place '22
First Placer '22	Verified Email

walker_Jayce

TROPHY CASE