The third party shared library doesn't know your company exists. This means the third party dependency doesn't contain any business or application specific code and is applicable to any software project. This in turn means it has to solve the majority of business use cases ahead of time and be thoroughly tested to not break any consumers.
The problem has fundamentally gone away and reduced itself to a simple update problem, which itself is simpler because the update schedule is less frequent.
I use tomcat for all web applications. When tomcat updates I just need to bump the version number on one application and move on to the next. Tomcat does not involve itself in the data that is being transferred in a non-generic way so I can update whenever I want.
Since nothing blocks updates, the updates happen frequently which means no application is running on an ancient tomcat version.
That 3rd party library rarely gets updated whereas Jon’s commit adds a field and now everyone has to update or the marshaling doesn’t work.
Yes, there are scenarios where you have to deploy everything but when dealing with micro services, you should only be deploying the service you are changing. If updating a field in a domain affects everyone else, you have a distributed monolith and your architecture is questionable at best.
The whole point is I can deploy my services without relying on yours, or touching yours, because it sounds like you might not know what you’re doing. That’s the beautiful effect of a good micro service architecture.
I was trying to think of better terminology. Perhaps this works:
Two services can have a common dependency, which still leaves them uncoupled. An example would be a JSON schema validation and serialization/deserialization library. One service can in general bump its dependency version without the other caring, because it'll still send and consume valid JSON.
Two services can have a shared dependency, which couples them. If one service needs to bump its version the other must also bump its version, and in general deployment must ensure they are deployed together so only one version of the shared dependency is live, so to speak. An example could be a library containing business logic.
If you had two independent microservices and added a shared library as per my definition above, you've turned them into a distributed monolith.
Sometimes a common dependency might force a shared deployment, for example a security bug in the JSON library. However that is an exception, and unlike the business logic library. In the shared library case the exception is that one could be bumped without the other caring.
<1MB is also relatively easy to reach with swiftui apps. I had two fully working ones in the app store below 1MB. They are removed now since I didnt pay the yearly 100€
Yes. I have a bike helmet with integrated cameras. The company (Cyclevision) that made it is gone. So no Apple account. So no app for my helmet anymore.
You could check if consumerrights.wiki already has a page on that company and if not create one. It's a great resource that will also be used to justify demands for changes to the DMCA.
This is yet another example of why open bootloaders to allow alternative firmwares for all gadgets must become legally required. Stuff turning into eWaste (or at least losing what some folks would likely call major functionality) because the creators went out of business and the gadget was locked down is a disaster for both the planet and for the concept that you actually own the stuff you buy.
i am still skeptical about HDR as pretty much all HDR content I see online is awful. But this post makes me believe that Lux/Halide can pull of HDR in a way that I will like. I am looking forward to Halide Mk3.
Annas Archive has both books in their archive, but they also have other datasets that connect a book ISBN to the metadata (title, author, publisher, ...).
In my visualisation https://isbnviz.pages.dev you can see which books they actually have the files of (blue) and which ones they know exist because they have the metadata from some other source (like google books, ...) (red). Finally, there are also ISBNs not contained in any of the sets that Annas Archive has, and these are either assigned or not assigned. A lot of the 979 prefixed ISBNs are not assigned, that means, no country/publisher has the right to assign them to a book. Other ISBNs are assigned to a publisher, but they just haven't published a book with that ISBN yet. Or they may have published a book, but Anna's archive doesnt know about the book because its not in their (or the ones they scraped) dataset.
But in terms of comparison of yours to bwv, I don't agree that bwv's is technically superior in every way. It lacks comparison, ISBN selection and link creation. bwv's main focus looks to be that one feature to highlight the rare books without trying to get the other requirements that AA wanted.
Congrats to you too! Indeed, I think they could have improved the visual and comparison part, its a bit dark and not too interesting to look at. But I am envious of how smooth their tiling is. My tiles are 4096x4096 which allows me to satisfy both the 20,000 file limit and the max 20mb file limit imposed by cloudflare. I had some issues with smaller tiles, and wanting to host it on cloudflare restricted me from doing 512x512 tiles iirc. Also I really like that they extracted the publisher information and put that as a pmtile vector, thats something I attempted but ultimately ran out of time with.
Its due to how those ISBN ranges were handed out - I think they probably gave a block like 978-53 (for example) to those countries, meaning the right to distributed ISBNs 978-530-000-000 to 978-539-999-999 and then later they ran out or had all subblocks distributed to publishers, and then they got a new block further away (so not 978-54 in my example) and therefore those blocks are not numerically close to each other and thus also they are separate "islands" in the hilbert space.
Thanks! That is indeed all thanks to using the hilbert curve fractal which has the property that it maps numbers which are close together onto 2d (or higher dimensional) coordinates which are close together, its a very cool property! Its used in lots of contexts for that reason
I’m glad you said that, because I was also surprised by the fact that the bwv-1011 only made it to honorable mention even though its technical focus was on visualizing the rarity of books, which ostensibly was the primary objective of the whole effort.
I really like that your page talks about _why_ a Hilbert curve is good. I don't remember ever learning about those before, and now hopefully if I'm ever trying to visualize 1D data, I might remember that :)
I think the language problem will become less of a problem in the future due to (1) more (young) people living in citys and (2) all young people in cities speaking english. At least compared to previous generations imo. This could be my subjective view based on luxembourg, netherlands, and visiting other european cities.
Don't overestimate "young people speaking english" especially with current demography you still need to tap ones that are excluded from English as there will be much more of those.
I do see opportunities with LLMs as making all kind of platforms language agnostic - you should be able to write your own language and read your own language even if other person is from different country using different language.
This is close to the idea of convex splatting (recent paper) in which convex shapes are used to approximate these real 3d objects as they are better suited than gaussians
I sometimes reminisce about the 2010-2020 deep learning and reinforcement learning etc era, as a student I did some projects in that domain back then and it felt very approachable and relatively easy to get into it compared to how I (most likely subjectively) see it today as a developer (in a different field).
I remember I doing a project in my second bachelor semester, where I generated random 64x64 images of a simple maze with a start and finish and then I tried to train a RNN algorithm that could navigate unseen mazes. There are so many better ways and algorithms to do it, but I learned a lot of cool tech anyway with this approach.
reply