murkt

What standard does reliably work to drive 8K at 60 Hz and how expensive cables are?

How far away do you sit from it? Does it sit on top of your desk? What do you put on all this space, how do you handle it?

I don’t think you’re maximizing one browser window over all 33 million pixels

That’s still around 2 km per kg of batteries.

You will need dictionaries with millions of tokens, which will make models much larger. Also, any word that has too low frequency to appear in the dictionary is now completely unknown to your model.

Remember booting from that floppy when I was a kid.

The only thing that would be even more impressive, if it also had a running .kkrieger FPS from the demo scene guys!

I haven’t ever used Litestar, but it seems like it would be possible to write your own decorator `@postform` that handles all of form-related stuff.

More updates means more changes and more instability. I have never seen dacite, but it’s pretty easy for a small library to just be complete. If it’s complete, why the need for constant changes?

What’s the story here, can anyone enlighten me? How can they make money being a Python library?

I can stretch my imagination about Astral monetizing their tools, but this one is too difficult

Powerbank is a wrong keyword here, what you want to look for is something like “USB-C power supply with battery”, “USB-C uninterruptible power supply”, etc.

Lots of results on Ali for a query “usb-c ups battery”.

I wonder if it’s possible to compile Postgres directly into a Python extension instead of WASM. Just import it and go forth, no node dependency, nothing.

I am not arguing against that language ideally should have less features. I am arguing with “Python is getting huge”, because it’s huge and has been for many-many years :)

This is a pretty simple and useful feature. I wouldn’t say that it bloats the language too much. Descriptors and metaclasses are much more complicated and have a lot more implications and have been in the language for a veeeeery long time. Is it decades already?

GP commenter complains that it’s not AI that came up with an idea and implemented it, but a human did.

In the few years we will see complaints that it’s not AI that built a power station and a datacenter, so it doesn’t count as well.

Just spent 10 minutes playing it, looks pretty fun!

If you formulate the warnings just right, you wouldn’t need to “force” it, as kids will be willing to look both sides themselves. They like to be alive.

Any age. There is no right age to jump out of the window on the 10th floor, no right age to cross a busy interstate by foot, no right age to set a bed on fire. You wouldn’t allow a kid to do it (and similar things) at any age. Would you? :)

Yep, it works for majority of children, but not for all of them. Folks that had a couple of kids with whom it did work spread it as a gospel.

You can try many other things, and maybe you’ll find something that works some of the time.

“What do you want?” can be “NOTHING!”, can be something. “You want this, but the reality is this and that. How can we deal with that?”

If kid is upset it usually helps to validate their feelings first.

Also, my kids are not yours, so take this with the grain of salt as well.

The world is much smaller than it was 200+ years ago.

Whenever we do recursive, or really long queries (not often), we’re dropping to basically raw SQL with sqlalchemy.text(). It’s really a lot to keep it wholly in SQLAlchemy: write a complex query in SQL, convert to SQLA, and remember how all the moving parts should be connected.

Should be much easier now with LLMs, though :)

Yeah! With SQLAlchemy as a query builder I can easily find all usages of a particular column with Find Usages action in PyCharm. With strings it’s not as easy, and some columns are not really greppable (id, author_id, user_id, etc).

Also, haven’t seen how sqlbind handles optional JOINs and especially optional LATERAL.

Haven’t seen a mention in readme, but I’ve found in the sources some nicety for INSERT/VALUES too!

That is a really neat library! Can see myself using it quite a lot.

No, you’re not naive. If it’s done by one-two people that know what they’re doing, it should be done much faster.

If it’s a big new team that doesn’t know what they’re doing, working separately from existing codebase, with lots of meetings… I see no reason why it would finish at all.

In my experience it doesn't matter if templates are pretty simple, or the database access is not optimized. Can matter if you're not careful.

Would love to see some benchmarks for all these libraries that compare them to Jinja2.

Yes, Starship needs legs to land on the Moon or Mars. They will be lighter than legs for Earth landings, as Moon/Mars have lower gravity.

Not sure about the amount of fuel needed to land, as there is much less atmosphere on Mars, and none on the Moon. I would still guess that it needs less fuel there as well.

Yes, when goal isn’t to support 100% of all the weird stuff, then it’s orders of magnitude easier!

Author hasn’t tried to highlight TeX. Which is good for their mental health, I suppose, as it’s generally impossible to fully highlight TeX without interpreting it.

Even parsing is not enough, as it’s possible to redefine what each character does. You can make it do things like “and now K means { and C means }”.

Yes, you can find papers on arXiv that use this god-forsaken feature.

155mm shells are $3k-10k per piece. So it’s more like 5-20x than FPV drone.

Python missed the race pretty heavily with 2to3 transition and still came out on top.

Imagine how different the Python ecosystem could be, if this was done 20 years ago.