Heavy use of interactivity is hard. React makes it maintainable. It was hell before.
I've been working with React (and RN) since it came out and I've had nothing but good experiences, especially compared to the previous decade before React.
My motto is local-first, the more stuff the client does, the cheaper it is to scale and less bridging between the server you have to do.
Move everything to the client, especially the database. Let the database do the syncing. Plus you get offline and undo/redo basically for free. Pagination? Fuggetaboutit.
The more stuff the client does, the higher the payload is going to be and the more complex the bundling and tooling will be.
I'm in a company with around 100 devs now and I can certify you that front-end SPA do not scale at all unless you throw a insane amount of devs hours in the tooling, even then it barely does.
That's not mentioning the insane npm churn that you have to maintain, the testing story which is pretty abysmal outside of a few top libraries, the typescript tooling which is eating so much ram that I'm changing my laptop.
And I'm not sure why you mention the pagination as a plus where it's one of the big downsides of the front-end stack, there's a lot of hacks to make it behave okay in most situations.
> I'm in a company with around 100 devs now and I can certify you that front-end SPA do not scale at all
What is the difference between SPAs and other monolithic architectures, e.g. on desktop, that makes it so?
Why can’t you go with OSGI-style plugins, for example? Loose coupling, separate SDLC and deployments etc?
The reason it works fine in a native app and not on a browser is that the browser streams documents over the network. It's pretty much the worst place to download large payloads on demand.
Native apps do not suffer from this problem, your binary can add an extra 20mb without much downsides
Native apps do network downloads of comparable or even bigger size too. I do not see how this can be an argument in SPA vs MPA decision making. „Rich client“-server architectures existed long before SPA became a thing and on much slower networks, so pretty much every problem modern SPAs face, from UX to performance to change management, was already solved by someone. Isn’t it actually ignorance of JS frontend community which has reinvented many wheels in rather ugly way, that causes the trouble?
It's fine to stream 20mb in a browser as long as it's not part of the core JS.
Browsers can handle many GBs of storage. You can even store them via OPFS directly on the native filesystem if supported. There's also Chrome File Storage API and if all else fails IndexedDB (which is more limited, but works decent for synced databases).
This isn't the use case of an SPA though since those extra megabytes would end up in the bundle, this is more like a game. Ironically I would agree that games are better suited to the browser than SPAs because you can afford to wait, you use wasm and you don't have to reinvent the wheel of the basic browser features.
I'm aware of that, that's why I pointed out the insane complexity of the bundler tooling. Splitting in chunks isn't a solution, it's adding fuel to the problem.
Not really, it's just a solution to the need of complex apps and the need to support the ability to load pieces of the app without having to download and install it like a native app.
Native apps can do similar things with dynamically linked libraries, and there's a lot of complexity when it comes to compiling native code.
The web bundler tooling really isn't that complex nowadays, especially with Vite. It's one file usually 10 lines long. It can use SWC and LightningCSS, written in Rust. They're safe, fast, and require minimal config.
I'm also aware of those, that's exactly what we're using in my company. It's a power hog, so much so that I had to change my laptop to run the SPA properly. The local experience is absolutely terrible since it has to disable the bundling to use hot reload (at least that's what I guess is happening) and each browser reload takes >1min to load.
Then there's the complexity of the caching in continuous deployment, we literally have a custom metabase dashboard to make sure the caching isn't too bad and lasts a few days.
Then the default config doesn't scale either as you can guess and we have our own.
There's a reason I have this opinion, I know what I'm taking about, I've been using all those tools and they add a lot of complexity to your app.
The reason it works on an native app is because loading a dynamic library is essentially free, it's just stored alongside the binary.
That's exactly what I meant by "not scaling". Sure if you have much less developers than us and you don't make 100 deployments per day, maybe an SPA can work. I can assure you that when you need to support a complex product, it absolutely doesn't scale at all, even with some developers full time to try to fix the stack.
Our full bundle itself is close to 70mb and still growing every week, that's absolutely insane.
There's a reason why Vite has a default bundle chunk warning of 500kb.
There's really no reason it should be that large. If you just lazy load each route your chunks should distribute into manageable size pretty much automatically.
It sounds like you may also have a bunch of dependencies. Which can happen in a native app, but in a web app as you know you'll have limited resources so size is important.
You're all over this thread saying "We couldn't scale it, so you little plebs certainly can't." I'm sorry it didn't scale for you, but it's telling that you think your experience is THE experience. Facebook uses it, I think your company of 100 devs could scale it fine, as many do.
> Heavy use of interactivity is hard. React makes it maintainable. It was hell before.
Agree, React is great for UI interactivity.
> ...the more stuff the client does, the cheaper it is to scale and less bridging between the server you have to do.
Disagree. The most costly form of scaling is people. UI + business-logic + data-modeling + data access (ACL) all held in async client concepts is a complexity nightmare in my experience. Even for my team-of-one side-projects.
Server <-> client bridge is a feature for managing complexity over time. I may agree that added ceremony could make 95% tile app experiences default harder. But for anything that's not a toy, the #1 risk is always team/people/communication complexity.
You're making multiple conjectures to get to that conclusion, of which the only evidence presented is another company based in a different country than Proton.
It may be true, it may not be, but there needs to be more information or facts before we get to the original comments statement that Proton gives data to expose protestors to protect "the powers that be".
If a government says "Give us everything you have on this user", and Proton gives them a sheet of paper that says "Here's the primary email for the account, we don't have access to anything else", the order is legally complied with.
Granted, I don't know much of how Swiss legal processes work, but I do know Switzerland has the best privacy laws when it comes to VPNs (which is why a lot of VPNs use Switzerland). Switzerland even has laws on their books that prevent them from compelling no-log VPNs based in Switzerland to log specific users.
I provided an instance of Proton giving the IP address and Device ID of a user after the French authorities requested it.
In their own policy:
> “In addition to the items listed in our privacy policy, in extreme criminal cases, ProtonMail may also be obligated to monitor the IP addresses which are being used to access the ProtonMail accounts which are engaged in criminal activities.”
So there's no question whether or not they do it, it's more of how often they do it and for what. The French case was a big deal because it didn't seem to meet the "extreme criminal case" threshold, and yet the logging was still carried out.
Feels to me after reading the article they earnestly try to do their best to offer privacy enhancing alternatives and push back often. What percent of these requests do Meta, Google or Microsoft fight? Ratios like that matter
Proton is extremely transparent and said:
If you are breaking Swiss law, ProtonMail can be legally compelled to log your IP address as part of a Swiss criminal investigation. This obligation however does not extend to ProtonVPN (see VPN privacy policy here). Additional details can be found in our transparency report.
> What percent of these requests do Meta, Google or Microsoft fight? Ratios like that matter
What others are doing doesn't matter, that's whataboutism. Yes there's many shittier services, and Proton is much better than them.
What matters is if you can trust Proton to be private, and the answer is... mostly.
Yes I like Proton and I use Proton as my daily email driver, because I don't expect privacy from governments, I just don't want Google tracking.
But a lot of people see the "no logs" thing and think that there's never any logs, which is not true, they add them on request, and they've done it based on foreign government requests, for questionable searches, as I've linked above.
If you want privacy in your hands, use Tor when accessing Proton and pay in crypto obviously.
Those are techniques needed for privacy because they can access that data and you can't trust them to safeguard any data they can access because they legally can't.
It's not their fault, it's just the system, but you must expect it.
Yeah, that's shitty, and it's no excuse, but I understand that, as a company, Proton will still have to comply with Swiss law, and if Swiss law requires IP Address monitoring in "extreme criminal cases" which I doubt Proton has the ability to decide whether it fits that or not.
I saw in the article that Proton also offers an onion address, which will make the IP Address monitoring useless anyway. So they, legally, have to do the monitoring, but provide a tool that makes their "monitoring" useless.
No, I totally agree. I'm talking about the mindset difference. I'm not saying "SpaceX is 'cheating'" or anything like that. Just the mindset differences are leading to what we see here in terms of iteration cadence.
There was a lot of horse shit everywhere before cars.
You could go back to bicycles but that's not great when you have a family of groceries and kitty litter to carry home in the rain.
Or when need a trip to the hospital or any other emergency.
So yes, many people need a car, and it enables personal freedom.
I live in a small town you can walk end to end in 15 minutes, it has everything you need in a small area, but a car still makes life easier and more fun.
How do you propose we structure society where you don't need cars?
Not having cars doesn't mean not having motorized transport, it just means restructuring our priorities around much more efficient forms of mass transportation, ranging from increased walkability and cycling infrastructure on a local scale, to buses, trams and trains on a larger scale, with specialised vehicles like ambulances and cargo-taxis for those rare cases where you really do need a whole motorized vehicle to yourself.
So what does society look like where you can still have ambulances and taxis but not a car for yourself?
Don't you still need roads for those? So just normal civilians can't have them?
And I won't hold my breath for local politicians to improve public transportation.
I'd love better public transportation, in addition to cars.
-- I hit some sort of post limit, replying to below --
Civilians are still allowed to have and drive their own cars, even in Europe.
I'm all for better designed cities in America though, but it's not a car problem, and especially not a universal issue (towns are perfect).
Instead of hating on cars I think a more useful approach would be to contact your local politicians that are in charge of zoning and public transportation.
Horses release methane. The scale of horses you would need would certainly be worse. It was a problem in the past at a much smaller scale. Plus with shit you have disease and rats, which means more disease.
I have, and there are bicycles littered everywhere and huge amounts of traffic on them.
And no it doesn't solve the problems I listed. Those things are still difficult.
If I'm feeling sick I guess my wife can hook a wagon to the bike and pull me.
Don't get me wrong I bike around town all the time, but some days are really hot, some are really rainy, some days I need to carry more stuff than is possible on a bike, some days I'm not feeling well enough to bike.
Bikes, (non humiliating) public transport, and more compact city design all have to work together.
I think cars in small towns are pretty sweet - but they suck for everyone in big cities. They take up huge amounts of space during rush hour, and move very few people compared to any form of transit you like
There are very few people for who cycling is not possible; there are so many options to make it accessible for almost everyone. Here is an example for people in a wheelchair: https://www.roam.nl/runner-handbike-20/a3535 , it basically hooks up to their existing wheelchair and turns it into a hand-operated tricycle.
I don’t understand the point you’re trying to make. Because you can make up some edge case for whom cycling is not feasible the 99.999% for which it is shouldn’t either?
> No, people are able to drive long after they can bike.
Like hell they are.
> The only thing that basically stops you from being able to drive is your vision, which will impact biking as well.
Looking at some studies, vision is not a major factor in accidents caused by the elderly. The reasons are mainly mental: reduced reaction speed, reduced ability to quickly grasp complex situations in traffic. Physical reasons are mostly around reduced motor functions: reduced muscle strength and fine motor skills.
Biking is impacted a lot less by these cognitive changes since you don’t go 130 km/h on a bike. Elderly are more likely to get hurt in a cycling accident, as they are more frail, but they are less likely to cause an accident.
> Handicap and elderly people are not edge cases.
Are you saying the majority of people are either elderly or handicapped ?
> We adapt our society to fit the disabled everywhere, as we should.
And we do. There are many options for both the elderly and disabled people to cycle, as I have shown in my earlier posts. None of those are exceptional, I regularly encounter those ‘in the wild’.
> Bikes do not work for many, many people and situations. It's not an edge case problem, it's a fundamental problem.
Cars do not work for many, many people and situations. Lots of places are simply not reachable by car. What do you think is easier for an elderly person: driving their bike right up to a store and walking 5 meters or driving their car to the edge of the city center and then having to walk a kilometer or more to get to the store they need to go to?
TekUI integration with a builder might be an interesting feature. It's a bit dated but the latest release compiles just fine and examples work. Years ago I tried it also on a small Allwinner ARM board with output to the framebuffer (no Xorg) and it worked fine.
I wonder why it is still semi-unknown.
It's an IDE, but it allows building full GUI apps. It's itself written in Lua using wxlua/wxwidgets toolkit, so has access to the majority of the modules availables in wxwidgets. The binaries are also bundled with the IDE for all supported platforms, so you can develop and package your own application in the same way.
This is correct, and is very different from both the Midler and Waits cases. The courts are never going to tell a voice actor she can't use her real voice because she sounds too much like a famous person.
And besides, it sounds more like Rashida Jones anyway. It's clearly not an impersonation.
> Your can point to the "Her" tweet, but it's a pretty flimsy argument.
I'm not making arguments which are not already explicitly written in my post.
My argument is simple: jorvi commented that you can hire "a real-life voice actress" to "try to imitate Scarlett Johansson’s voice as best as she could", and that is not illegal.
I said that the legality of that is more complicated. What jorvi describes might or might not be illegal based on various factors. And I pointed them towards the two references to support my argument.
I explicitly didn't say in that comment anything about the OpenAI/ScarJo case. You are reacting as if you think that I have some opinion about it. You are wrong, and it would be better if you would not try to guess my state of mind. If I have some opinion about something you will know because I will explicitly state it.