lakpan

> they're becoming a joke again

Are they? I don’t see it. They’re more profitable than ever and are still extremely competitive in multiple markets.

The arguments against this have been the same for decades: Apple is overpriced, Apple’s product are inferior to competition, and yet here we are with large chunks of the market share and larger chunks of market gains.

Some products are stupid, but it’s not like Steve hasn’t pushed dead products out before.

Warning is not possible, have you seen the amount of spam the web has?

What’s possible though is a better handling of these scenarios. Don’t lock me out of my entire account, but stop the specific service/action breaking the ToS.

Hire a non-metal band to play for you in the room.

The most interesting part of this tool is that it has enterprise features and it’s still free. I mean why. You’re producing a product to handle large amounts of money and you don’t want a cut?

Sorry but your argument makes no sense. The 10LOC/day guy is not to be singled out from the 1000LOC/day people because 1000 LOC could be just as trivial; 1LOC could have taken hours to discover.

So, AppleScript for the web?

Not really. Regular users send links to themselves all the time as a way to bookmark things.

And then something happens and you lose it.

A million editors and you pick the least capable. My go-to is a sublime text window, even if ST is not my code editor.

Why does this feel so relatable?

It’s not generated JS, it’s concatenated JS (plus some glue). Rollup make this clear.

In web extensions you can’t quite use sourcemaps unless you include the sourcemap in the .js file or upload it to your own server

The question is: is the output as good as Rollup? I haven’t seen a bundler that outputs code that isn’t junk that must be minified to be any good.

With rollup, I can just ship it as a web extension and it’s still 100% readable.

It’s called reader view and it’s great. I’ve been wishing additional support for things like comments etc, but yeah I really hope that we’ll soon have an “AI browser” that just extracts what we want from the pages we open.

I’m confident that someone already wrote an extension that does this automatically for every page, and that someone else is writing a Chromium wrapper.

The only thing holding us back at the moment is cost/computing.

I’m in my 30s and resident at my parents house, on a continent I spend 30 days/year on average. My company is registered there even. Most people have a “home” (or mailing address) even if they don’t live there.

> web standards are really a thing now.

Chrome starts a proposal, implements it and “intends to ship” it before anyone really has time to discuss it. Recently (2 months ago?) they introduced a new WebExtension API that nobody cared about nor really understood the need for, but it’s still there, making it look like it’s a “standard”

See, you don’t know how npm works. Npm does not care about the lockfile of dependencies. “Someone checking out my project” always gets the latest version of each dependency within the semver range, until their lockfile locks a version into place.

Yeah but that's rarely the case, you can't offer that as a generic "solution" to the problem at hand. It's just Mithril's choice to both publish to npm and to officially link to unpkg. Packages can make different choices, like publishing to GitHub releases or just to include the file in the GitHub repo.

The reality is that only frameworks and very popular browser-specific packages do that.

> when compared to Google Photos

You’re comparing apples to oranges. Google Photos is not E2E. Explain how you can do ML without having the key. Either you hand them the key or you don’t.

Of course they mention it as an alternative to Google and Apple Photos, but that doesn’t imply that they have 100% of the feature set of each.

You plug your phone in at night, so it probably has 7 hours a day to do that work.

iOS does the same. They cannot do it on the server because they don’t have access to them.

When I was young, kids in middle school would pick up smoking. Just because it didn’t happen to you it doesn’t mean it didn’t happen.

I’m against the general “what about the kids” rhetoric, but in this case it’s both important and easy to implement, because sellers already card you for the aforementioned purchases.

What kind of question is this? If drugs are sold without limits, then children will also be affected.

The right answer is that they would still need to be controlled just like cigarettes and alcohol.

Unpkg just serves the raw files, which may contain require() calls or import from other npm packages. That won’t work.

The closest service is https://esm.sh, but you can’t download from it.

> Is there anything where I can search for browser only

There used to be bower, thankfully that’s now gone.

> JavaScript has improved a lot

So has its ecosystem. Setting up parcel or Vite is straightforward and should get you out of those problems. The time when you could just download a .js file and stick it in your vendors folder is long long gone. Please bundle and minify your files before serving them.

I wanna see you write it from memory. Now do it without bugs fixed in 2013 in that package.

> Someone else who checks out your code will get different results.

> I was hoping for something like Go’s minimum version dependency resolution.

Uh and that’s different how? The default semver range is “minimum dependency version” with an upper bound in the current major.

Bun’s goal is to be an actual superset of node, so you can write just for node and expect it to work in bun.

As for deno, I think if you publish ESM you’re mostly covered since deno can install from the npm registry.

> a couple problems became clear: 1.) Duplicated dependencies

I’m sorry but that did not come up when designing the system? It’s the whole principle of semver ranges that deno decided to do away with. I cannot believe nobody saw this as a drawback. It’s the first thing I thought when I saw hardcoded versions.

JSR is almost literally a subset of npm in features. Npm allows publishing of anything, JSR only actual TS/ESM. Whether those modules have dependencies doesn’t expand the set IMHO

Type inference in dependencies does not reduce performance for users, but just for JSR. Here they’re going “the Google way” by adding some random metric that benefits them, not users. Once generated, .d.ts files do not contain inference.

You’re 110% on point.

Publishing is too complicated? Let’s add something else: https://xkcd.com/927/

This is all node and npm’s fault, they’re sinking billions of dollars of developer time worldwide and they should be called out on it.

I don’t think WebKit is garbage. That title belongs to Gecko. Apple picked up their slack with Safari a long time ago. They do have faults with these decisions to intentionally break or not support some features for years, like Push Notificafions.