Shouldn't most comodity GPS receivers also be GLONASS compatible (I get that Galileo is more niche and might not be included).

Does the Sensor Apple uses not use GLONASS in Russia? Or is it cheapo Android Phones picking up the tag and then sending GPS coords into cloud?

edit: Nvm, I might be dumb, I guess unless your jamming includes all commodity GNSS it's pretty useless.

They have had GLONASS for ages too, but obviously they have to jam everything, otherwise it's not going to prevent drones and such from working

> Or is it cheapo Android Phones picking up the tag and then sending GPS coords into cloud?

AirTags have no integration with Android devices. There's a shitty app from Apple you can install that allows you to scan for AirTags nearby, one shot. It's supposedly against stalkers, but it's practically useless. There a bunch of other community apps with varying features like finding and notifying you there's an AirTag nearby. But you can't even track your own AirTags from an Android device, because Apple have decided you must do it from an iDevice. No browser, no Android app. You can check your iPhone's location via the browser, but not the AirTag.

The Android ecosystem has an alternative thing, but depending on the phone manufacturer you have to opt in to your device being used to track trackers around you.

When I travel to places with low iPhone market share, I always have one tracker of each ecosystem, just in case.

Oh, thank for the correction. I must've muddled it up in my mind with the contact tracing integration that had during Covid.

Was this done heavily LLM assisted? Especially the PDF Edit tools have user-interaction quirks and bugs that a human developer would catch immediately during the regular manual testing when developing.

I'd suggest you at least try and mitigate that by having the LLM do extensive e2e testing if you aren't interested in using your own product.

Yeah, and I have the feeling it is not tested at all.

It offers Word -> PDF conversion. Just for interest I tried it and it doesn't even get the simplest page right. It puts the filename into an header. The test page had 4 images, one svg, one pdf (from svg), and another variation of the first 2. The generated PDF only contains 2 of those images with wrong sizes. The later two are missing. So it's basically completely useless.

The free of charge LibreOffice gives much better results with its own caveats.

It’s still a work in progress. I used an LLM to speed up development, and I’ve done the testing, but I’ll keep improving it no doubt

How much of this is LLM derived and how much of it is yours?

I don't even care about that. My suggestion to him was earnest. I don't have a problem with LLMs. Just with how people use them. I just don't like "slop". I see the same user-interaction problems every time.

I just don't want people to litter their heavily polished immaculately styled products that have so clearly bad user-interaction design. E2e testing and closing the loop on LLMs does seem to help here.

Though I really would prefer people click around their own product for at least 5 minutes.

It matters to me. Depending on the ratio there is a line between 'LLM assisted' and 'LLM derived'. There are enough samples of open source code around this theme out there that this could be one of either and the goal to commercialize it is a messy one if the provenance of the code isn't clear. It would be great to see this sort of thing litigated so that there is at least some clarity rather than just a moral stance.

That's whataboutism, we're not discussing Claude Workspace, we're discussing 'Pdfwithlove' so you are avoiding answering the question.

don't want to go in debate. It's ok, I used LLM to make a product faster

None of it is them, all of it is LLMs.

I would not have guessed that iOS allows enough access to APIs to implement anything vpp-based. Very cool to see. I also enjoyed working with vpp (for the brief 6 months that I had with it).

I was thinking that's hard, but I noticed that vpp get ported to FreeBSD using epoll shim library, and I learnt apple Darwin use some some userland of FreeBSD to do POSIX compatibility, then after some tests and hacking, most related to minor POSIX API adaptation such as mmap and one major coroutine need add some assembly code, and it work! But I think most disappointed to me is that apple do lack some vectorized network IO unless do some kernel extension or other sort non standard ways.

> Python is heavily OOP, everything is an object in python for example.

I strongly disagree. How is everything being called an object in any way "heavily OOP"? OOP is not just "I organize my stuff into objects".

You can write OOP code with python but most python code I've seen is not organized around OOP principles.

>I strongly disagree. How is everything being called an object in any way "heavily OOP

Do I need to spell it out? The O in OOP stands for object.Everything is an object therefore it is Object Oriented. It's not much more complex than that man.

And I don't mean that it supports users writing oop code, I mean that the lang, interpreter and library are themselves written with oop. Inheritance? Check. Classes? Check. Objects? Check. Even classes are an object of type MetaClass.

Don't know if you need to compile, you might want to but I think interpreting might seem reasonable if size/complexity is a concern.

Is the runtime really that large? I know with wasm 2.0 with garbage collection and exceptions is a bit of a beast but wasm 1.0? What's needed (I'm speaking from a place of ignorance here, I haven't implemented a WASM runtime)? Some contiguous memory, a stack machine, IEEE float math and some utf-8 operations. I think you can add some reasonable limitations like only a single module and a handful of available imports relevant to the domain.

I know that feature creep would almost inevitably follow, but if someone cares about minimizing complexity it seems possible.

Could you try to address the obvious point being made instead of trying to obfuscate? There's plenty of bad outcomes besides death. Not all fentanyl users die. If some fent wholesaler were to provide unrefutable evidence that Noone died from his fent you wouldn't go "Oh alright then, nothing wrong with what you're doing".

Very appropriate as well because the machines are given a bunch of feed to digest multiple times and to spew it out the other end as a big steaming pile.

Although I don't think the comparison is 100% fair: at least you can get some tasty beef off of a bull.

You can math that out pretty well. If your code has a breakage chance of 50% and your dependencies all have a breakage chance of 1% then with 70 dependecies you get to 50.5% breakage chance from dependencies.

I don't think you're arguing against anything that was said in that post. There was never an "at all cost". The author was hedging even in the headlines ("indiscriminately", "before you know you need one" and "always, always").

Have a hard time imagine when you would benefit from just html files (unless it is literally a one pager that will never change)

You make it sound like there isn't a very wide range of solutions between "just write html files" and "use a complete website framework". There's a space in there where a large percentage of web projects used to be located in.

You can already subscribe to projects or single issues/PRs on github and reply via email to post comments.

I can understand not wanting to use GitHub/GitLab/etc. for various reasons. But I don't understand how usability vs mailing lists is one.

How is a set of 9+ mailing lists any better? It has significantly worse discovery and search tools unless you download all the archives. So you're creating a hurdle for people there already.

Then you have people use all kinds of custom formatting in their email clients, so consistent readability is out the window.

People will keep top-posting (TOFU), transforming the inconsistent styles in the process. Creating an unnecessarily complicated problem for your email client to "detect quotes", or you have to keep reminding people.

Enforcing structure of any kind in email lists seems so tedious. I'm not advocating for bugzilla style "file out these 20 nonsensical fields before you can report anything" but some minimal structure enforced by some tooling as opposed to manual moderation seems very helpful to me.

It's not about usability for newcomers (a mailing list is really not ideal for them) but usability for regular contributors and especially for lengthy discussions.

Call me old fashioned but there is no better way of discussing stuff online in an asynchronous way (OTOH video calls are better, but face to face doesn't scale) than a threaded medium. We don't have a better tool to manage threaded discussions than what mail clients (or Usenet clients but they are almost identical in handling).

Linear discussion forums (which GitHub issues are) are just inferior.