mlunar

While I agree that there are lots of problems around security communication, I don't feel like the number of CVEs fixed is a good proxy for bad security, I would assume it's more the opposite. Like the more incident reports an airline company has, the safer it tends to be - the unsafe ones don't care to file them.

You are free to choose opening a consultancy yourself and take on the salary risk as well as reap the rewards.

Companies also currently aren't completely banned from firing people. If and when they do, it can look like you described, with adequate notice and compensation.

You are thinking of the continuity of work, colleagues, and responsibilities. Those are of course good to have, especially from the perspective of the company.

But from the perspective of the individual worker, a much more important continuity is the one of salary, insurance, and pension. This is the stability that the employee continues getting at Company D.

Mine is that: https://photofield.dev/ (but has fewer features)

I spent too long writing this so I might as well submit it here. It's about a weird Firefox? Fedora? AMD? performance regression, but actually not really as it's about Go image encoder file size & latency.

Not the author, but last time I checked (3y ago), the fonts CDN was surprisingly slow, like hundreds of milliseconds of latency.

As the website I was optimizing was selfhosted, also selfhosting the font had a noticeable effect on the page load time. See https://github.com/SmilyOrg/photofield/commit/12352667c01624...

I'm not sure what you mean with the rest of the comment though, it's a very small change and it gets cached by the browser like other static assets, so I'm not sure what is the overkill here.

Btw, there is a typo: renogiate should be renegotiate

It's a pretty deep rabbit hole. For semantic search CLIP and cosine similarity are just fine. SmolVLM(2) mentioned by spacecadet looks interesting though. I haven't integrated face recognition myself, but [deepface] seemed pretty complete.

I focused more on fast rendering in [photofield] (quick [explainer] if you're interested), but even the hacked up basic semantic search with CLIP works better than it has any right to. Vector DBs are cool, but what is cooler is writing float arrays to sqlite :)

[deepface]: https://github.com/serengil/deepface

[photofield]: https://github.com/SmilyOrg/photofield

[explainer]: https://lnar.dev/blog/photofield-origins/

Similar one I wrote a while ago using Pupetteer for the IoT low power display purposes. Neat trick is that it learns the refresh interval, so that it takes a snapshot just before it's requested :) https://github.com/SmilyOrg/website-image-proxy

You do not need a banner, you need informed consent. I'm sure there are other ways of getting consent other than a half screen pop-up with a big red accept button on first visit, but they probably won't get 70% "opt in" rate.

In Go you can do errorf("%w: %s", err, path) so that you get "file not found: foo/bar.json", while still being able to match on the wrapped error value with errors.Is(). The caller can do the same with this error and so on up the stack

Check out https://github.com/zombiezen/go-sqlite if you're interested in trying out Sqlite in Go again. Nice interface, negligible compile time impact, fast, compiles without CGO. It's very comfortable.

I agree that going from text to sqlite is a bit of a hurdle, especially if you're not writing C :)

APIs sure, installing on desktop, no. A bit further down on the page linked via the second link:

"On desktop:

    Firefox and Safari do not support installing PWAs on any desktop operating systems."

YMMV but Copilot (Bing w/ GPT4 toggle) does alright: https://gist.github.com/SmilyOrg/c0f60a41e9fcbbffdbf5454a500...

Obviously it could be completely wrong, but it certainly _seems_ to comprehend geometric algebra more than I do.

You're welcome!

I'm not sure how to respond to this, it just seems to be quite a distorted Apple-centric view. I will leave a few references and make of it what you will.

"only player in mobile space" iOS had 28% market share when the letter was published (Q2 2010), just after Symbian with 33% and Symbian was not on the same level of "smartphone". Android was 4%. So yes, what was supported in iOS had a significant effect on the industry as a whole. Source: https://www.statista.com/statistics/272698/global-market-sha...

"It was bad/slow/unstable" Sure, but that's irrelevant. It's not even the main problem Jobs had with it. It's that he lost control over the platform and, if you read between the lines, the App Store revenue. Read the letter and ensuing battle yourself: https://en.m.wikipedia.org/wiki/Thoughts_on_Flash#References

I'm not trying to say it was good on mobile, from many accounts it was apparently bad. But we never got to find out for real, did we?

It's irrelevant though as if Apple cared so much about preserving the user experience, they would also block slow or crashy websites, which they didn't, because they don't pose a threat to their business model.

And it doesn't pose a threat because they (still) control what is possible on iOS web by restricting browser engines to webkit only.

Thanks!

Well, mostly that it's text / XML you usually have to parse in full and boundaries are data heavy, so if you have anything more than a world map, I don't see that working very well.

In contrast with the OP or GeoPackage, you can query by tiles/range and only extract the boundaries you need if you're zoomed in somewhere. If you use Tiny Well-Known Binary compression, you can also shrink the data quite a bit while keeping the querying capabilities.

But if you only ever need to render the whole thing, topojson is probably the winner as it cleverly encodes only unique borders once, so it tends to be a lot smaller.

And of course if SVG works for your case, go ahead and use it, it's surely the easiest way to render vector gfx in the browser :)

SVG is kind-of terrible for maps, but you can get pretty small with GeoPackage (read: sqlite). I recently spent a bit too long on exactly this problem and ended up with the following.

116KB - 5MB for country borders

16MB - 52MB for ~50K city/county level borders based on geoBoundaries

The range of sizes depends on how much custom compression/simplification you put into it. The source files are about 10x bigger, but that's already pretty small.

Topojson might be even smaller though.

Check the repo for details /selfplug https://github.com/SmilyOrg/tinygpkg-data

For what it's worth as another Flash/AIR developer, this is exactly how it happened.

Apple is just very good at spinning the narrative in their favor, i.e. it was because of "stability/security/performance issues" and not "it's a potential App Store competitor, bury it now".

See also: Apple preventing apps from downloading/including scripts dynamically (read: AIR), which was a total security risk, until it wasn't when they lifted the restriction years later when AIR was not so relevant anymore.

Glad to be corrected tho

Hi! A while ago I had exactly the same problem and thought process, so I made this: https://github.com/SmilyOrg/website-image-proxy

Hopefully you find it useful :)