neutrinobro

Titan is completely dead, you can bet on that.

Yeah, I was equally surprised. I am using a patched version of ollama to run the models: https://github.com/austinksmith/ollama37 which has a trivial change to allow it to run with old versions of cuda (3.5, 3.7). Obviously this was before tensor cores were a thing, so you're not going to be blown away by the performance, but it was cheap. I got 3x k40s for $75 on ebay, they are passively cooled, so they do need to be in a server chassis.

I have a old system with 3 ancient Tesla K40s which can easily run inference on ~30B parameter models (e.g. qwen3-coder:30b). I mostly use it as a compute box for other workloads, but its not completely incapable for some AI assisted coding. It is power hungry though, and the recent spike in local electricity rates is enough of an excuse to keep it off most of the time.

These days you don't have to worry about endianness much (unless you dealing with raw network packets). However, you do need to worry about byte-padding. Different compilers/systems will place byte padding between items in your struct differently (depending on the contents and ordering of items), and if you are not careful the in-memory or on-disk placement of struct data elements can be misaligned on different systems. Most systems align to a 8-byte boundary, but that isn't guaranteed.

Just drill a small ~1mm hole in the seat/down tube of all bikes before each race. That shouldn't meaningfully affect the frame's structural integrity, but would easily disable any small motor attached to the crank.

This was bound to happen at some point, but probably net-on-net won't affect most users. I think it's pretty useful for a variety of tasks, but those tend to fall into a rather narrow category (boilerplate, simple UI change requests, simple doc-strings/summaries), and there is only so much of that work which is required in a month. I certainly won't be cancelling my plan over this change, but so far I also haven't seen a reason to increase it over the hobbyist-style $20/mo plan. When I do run into usage limits, its usually already at the end of the day, or I just pivot to another task where it isn't helpful.

Buried at the end of the article:

> A limitation of this work is that the resulting de-oxygenated titanium contains yttrium, up to 1% by mass; > After solving the yttrium contamination problem, applications to industrial manufacturing will be straightforward.

One wonders how much of a problem this is for most applications, and how easy it will be to solve...

You are free to use facebook.

I was half expecting a discussion of the eigenvalues of a random matrix, or something at least halfway plausible, but no, this is useless mumbo jumbo, a la Deepak Chopra. People with zero understanding of quantum mechanics should stop making analogies to everything else.

No, that's exactly why I clicked on it too.

I disagree, cppreference is pretty good. The information is very complete and useful examples abound. And just because you may not understand a template operator definition does not make it useless documentation.

In the past for this sort of thing I've used an interval tree

https://en.wikipedia.org/wiki/Interval_tree

However, that was mainly for the case where I needed to detect overlapping intervals. Depending on your application perhaps a K-d tree, in this case, K=2 (one dimension for start-time the other for the end-time)? If you know that all you intervals are entirely disjoint (no overlap at all) I don't think you'll be able to do better than just an ordered map or list.

They are not. Polygons are a terrible representation since unlike triangles they do not cleanly represent a unique planar surface. With more than 3 points you will always have an ambiguity (or several) about which (numerical) plane corresponds to the actual face. For some graphics applications this may or may not matter much, but it is very important for anything using the mesh for physical computation.

I will never buy another Asus product. Several years ago I had a laptop with onboard SSD cache that failed during the warranty period. After communicating with them and paying to ship it to them, they sent it back without even making an attempt at repairing it.

You're right, I think the only thing missing is the background with animated floating graph nodes.

Every month of this sliding calendar has 31 days.

I don't think Maxwell's equations are going anywhere anytime soon.

Ughh...the term B-field already has a very strong association with magnetic fields. I'm sure it sounded like a good name given the context, but these types of name-collisions generally makes searching for a specific topic more and more painful each year.

Can you really call JSON a programming language? Or for that matter...XML?

If you have any interest in single-particle tracking for ion optics. I'd encourage you to check out https://github.com/KATRIN-Experiment/Kassiopeia. It can do both exact and adiabatic tracking of particles (and will solve for B and E-fields in complex electrode geometries). However, as far as I know it only handles static electric fields for now.