throwAGIway

Try it without having Google services on that phone. Most apps and especially the essential ones are dependent on unmodified phones with Google services.

You act like the explanation improved it in any way, but that just made it 10x worse. Tax homemade cakes sold on the open market, leave school cake fairs be and definitely don't open them to commercial entities. You say this doesn't affect individuals - my children competing with some business at their school cake fair and having to fill taxes after it definitely affects me and them.

Show me one example?

Indeed, and they saw that software of sufficient quality can't be funded merely by sales of these devices, and decided to create a platform where the software publishers share the cost with the end users.

I yearn for Windows Mobile but it has suffered from this problem greatly. Same with early Nokia and Sony Ericsson phones with smarter features like J2ME.

It shouldn't be tried by a country, it should be tried by people.

Why would you decide who can vote? Municipal voting right is by residency, no change in that. Everybody votes on the issues that concern all.

That still doesn't give you any right to just take what Apple built for free. Maybe there's no right option for you - I know there isn't for me, I'd prefer to have Windows Mobile (not Phone) again.

Nationality and citizenship are obsolete concepts and should be abolished ASAP.

Two (or more) tier society is a disgrace to humanity.

Apple built the city and you're free to go anywhere else.

You can't get biological computers without having very high speed computers though. This field of biology is very reliant on computer analysis.

I disagree, the support is very responsive. Try to let them know in advance about your plans and you will be fine.

It's an issue because CommonJS allows stuff that's forbidden in static ESM imports/exports, and it was normal to use. Newer code is usually fine, but there are many older backend libraries that can cause issues with Esbuild. Webpack had to learn how to deal with it because it existed at the time CommonJS was most popular, Esbuild didn't.

Turbo Pascal

Delphi

There's not much more to it yet, it's a large project and my first time trying something like this. I have selected few candidates and so far the cooperation with each of them was excellent, they are very skilled, proactive and keen businesspeople with good products for reasonable prices. I really wish the market here in EU was like that.

Basically the only forbidden thing is dynamically calculating import paths, or dynamically generating the module.exports object.

At least they replied, lol. I still have dozens of Chinese saleswomen wishing me good morning on WhatsApp more than two months after I sent my RFQ, the EU companies didn't even reply.

Yes, exactly. Pulling a huge npm dependency is usually not a problem if they didn't go out of their way to make it super hard to analyze at build time.

This is tree shaking though, dead code elimination means it will find code that isn't used at all and remove it - for example you might have if (DEV) {...}, and DEV is static false at build time, the whole if is removed.

So first it performs dead code elimination, then it removes unused imports, and then it calculates what is actually needed for your imports and removes everything else.

Sicstus Prolog

Yep, that's how it works - you first perform dead code elimination and then tree shaking exactly because it wouldn't remove everything otherwise. Agreed that you need both done one after another in most cases; however you can usually disable either one in bundler configuration and it's a separate step.

Dead code elimination is related to but distinct from tree shaking - it also means that unused code branches get removed, for example constants like NODE_ENV get replaced with a static value, and if you have a static condition that always results to true, the else branch is removed.

SWC doesn't bundle at all. Esbuild is a pretty good bundler but works well only if your code and dependencies use ESM, it's not as good as other options with CommonJS.

Bundlers take many - usually at least hundreds, often tens of thousands - individual source files (modules) and combine them into one or few files. During that, they also perform minification, dead code elimination and tree shaking (removal of unused module exports).

It's orthogonal to TypeScript - bundler will invoke a TS compiler during the process and also functions as a dev server, but that's just for nicer DX.

Package version resolution is done by package manager, not bundler.

That is a goal of the OS project, not the browser project. There is nothing wrong about moving on.

Andreas is one of the most qualified people on the planet to know where this new trail is and actually make it happen. Many foundational parts will probably look familiar or very similar, but he's been talking about the possibilities of a clean slate project since the beginning of the browser.

(He was working on the big browser teams before SerenityOS and Ladybird)

It's more terrifying that people have claims about things they didn't even check. Why exactly is it bad? Do you really think that a human quickly skimming few web pages is better than a bot quickly skimming few web pages? Or did you think it's pulling the data from its trained weights?

Yeah I know it is in the US, but military recruiters visiting a school class would be a major nationwide scandal here, comparable only maybe to visits of some political or religious figures. The only approvable way is a moderated discussion where both positives and negatives are (must be) voiced in age-appropriate way.

The entire culture around the separation of state, its components and citizens is very different here. We really don't want another 40 years of dictatorship - best to stop it right at the beginning.

Yes, but entirely unrelated to Scandinavia.

Yep, sure! Personally I don't like the Svelte programming model, and I like Preact signals a lot, and hooks are fine to me. But Svelte is definitely a good way overall.

Yeah, it will be called when you call render as in my original comment. Again, I don't think that passing a callback makes a framework.

It's not React, it's a jQuery mess from some low budget agency.

I am currently solving large cumulative layout shift on a WordPress site of my friend... I really don't think these problems are reserved to React.