zffr

Yeah it’s strange that the project does not mention using redis, or even SQLite with a vector DB extension.

Just curious, why do you want to migrate from mongo (document database server) to sqlite (relational database library)?

That migration would be making two changes: document-based -> relational, and server -> library.

Have you considered migrating to Postgres instead? By using another DB server you won't need to change your application as much.

I was with you until this part:

> Thus any attempt at estimates is as futile as gambling to win, tasks are only ever done when they're done, and "successful estimators" are kings of retconning.

> It's all make-believe.

Software estimates are not futile or make believe. They are useful even if they are not always precise. That’s why the industry continues to use them.

Does anyone know why the industry is killing OpenGL?

I just tested this on my computer.

  1. Make a new Xcode iOS project and delete all files except for Info.plist
  2. Remove all keys from Info.plist
  3. In the build settings search for "storyboard" and remove all keys
  4. Add yellow.asm to project
  5. Link UIKit, and Foundation

After all that you can build and run on a simulator

> so it's almost certain that private APIs would get accessed

No it's not. Just like with ObjC or Swift, in ASM you have to be explicit about the APIs you want to call. I don't see how you would accidentally call a private API in ASM.

IMO the bigger risk is attempting to call a method that does not actually exist. ObjC or Swift would protect you from that, but ASM would not and may just crash at runtime.

To me a handle implies that the object is somewhat sturdy. It’s okay to have it bump against other things and to set it on the floor.

nit: the pure HTML example is not the same as the other examples. It would make a POST request to the server with the data using a form encoding instead of a JSON encoding. It's not a given that your server supports this encoding!

One challenge is that JSON is for data and HTML is for UI. When a client gets JSON it can transform the data to make it ready for the UI. With HTML, the client is locked into the UI chosen by the server.

What if the client wants to render the output of an API in different ways depending on what screen is visible? If the server API outputs JSON, this is trivial. If it outputs HTML the client is stuck into rendering what the server gives it.

What I like about TUIs are that they are forced to be simple, and are forced to load all data at once. I don’t prefer interacting with an app in a terminal window, but I do prefer the kinds of apps that are built with these constraints in mind.

There’s nothing preventing web apps from being built this way, but they just often are not.

Preview was just included in iOS 26

Apple’s typical process for releasing public API involves dogfooding it internally first. Sometimes it will take years of internal use before Apple will release API publicly.

With something as large as TextKit, I would be extremely surprised if Apple did not get several of its apps to adopt the new API and use it for a few years before considering releasing it publicly.

I'm at a cafe in NYC right now. Every single person here is on their laptop including me.

For people wanting to include URL references in things like books, what’s the right approach to take today?

I’m genuinely asking. It seems like its hard to trust that any service will remaining running for decades

PDFs don’t always contain actual text. Sometimes they just contain instructions to draw the letters.

For that reason, IMO rendering a PDF page as an image is a very reasonable way to extract information out of it.

For the other formats you mentioned, I agree that it is probably better to parse the document instead.

or I think if you right click and then open the app, macOS lets you run it.

How do you do server-side rendering without a framework?

If you use static pages, how do you make sure that shared UI like navbars all update if you decide to make a change?

My understanding is that SQLite is OLTP and duckdb is OLAP. Duckdb is column based so not a great fit for a traditional backend db

What’s the other candidate besides pocketbase?

What do you think the bottleneck was in your search?

Was it finding openings, getting interviews, or passing those interviews?

In my niche I’m finding that there are very few opening in the city I live in, but that getting interviews might not be too hard. Not sure how easy it would be to pass those interviews.

Out of curiosity, how did you end up with 6 months off between jobs?

I would love the opportunity to take ~6 months off, but I feel scared that if I just quit, it might take me a longer time to find a job again.

Why wouldn't you be able to switch back to using pip ?

Do you ever get threatening letters from the legal departments of these companies?

I once built a site like this for a popular social media site, and got an email from their lawyers claiming “Unlawful Use of COMPANY’s Trademarks / Service Marks”

You set a breakpoint directly before this line, and then step forward. If you need the breakpoint to only trigger when there is an error, then you can use a conditional breakpoint that triggers when err != nil

It’s not as simple as that. All people don’t get fat for the same reasons. I never eat junk food, and yet I still got fat during the pandemic.

For me the issue was that I stopped exercising during the lock down, but continued to eat the same amount out of habit. This led to me putting on a bunch of fat without realizing it.

To fix the issue, I primarily scaled back the quantity of food I ate without changing its composition too much.

The article is about being fat. The primary tool to lose fat is diet, not exercise.

Losing weight is all about removing things from your diet. It’s accessible to anyone if they are willing to tolerate a little hunger.

Why do you feel the stdlib needs a .sum() if using .reduce() is so simple?

If you do a lot with combine publishers, then you might also have a hard time with the type system

The read me says this approach is extremely maintainable, but I’m not sure I agree.

The design pattern is based on convention only. This means that a developer is free to stray from the convention whenever they want. In a complex app that many developers work on concurrently, it is very likely that at least one of them will stray from the convention at some point.

In comparison, a class based UI framework like UIKit on iOS forces all developers to stick to using a standard set of APIs to customize views. IMO this makes code way more predictable and this also makes it much more maintainable.