- thadtNuclear measurements, where the speed of a gamma ray flying across a room vs a neutron is relevant. But that requires at least nanosecond time resolution, and you’re a long way from thinking about NTP.
- What does a "digital education" look like, specifically?
Having spent several years teaching kids to code everything from games to lightbulbs on Chromebooks, I can confirm that there are certainly difficulties - but they're tradeoffs. I could spend my time coming up with a way to work through the platform restrictions, or I could spend my time maintaining a motley crew of devices and configurations. Having done it both ways, they both have different pain points.
- Well, it depends on the granularity of the time scale right? When you're measuring milliseconds, then the cable length probably isn't a thing factoring into your latency calculation.
When we're measuring time on the scale of nanoseconds then, yes, cable length is definitely something we care about and will reliably show up in measurements. In some situations, we not only care about the cable length, but also its temperature.
- When I see juries in American courts, for example when I've served on one, it seemed like a group of people who take their job quite seriously. You are correct in that what a jury gets is a very curated set of information. The intention being to keep the jury focused on the details of a very specific situation with evidence that is processed in such a way as to be as "reliable" as possible.
It is by no means an accurate or incorruptible system. When we design and prove out a better, more robust alternative, I'll be eager to learn about it.
- Well, it's fascinating right? Can we cleanly separate out military, politics and sociology? A whole lot of military capability comes down to not just technology and tactics, but the entire culture and makeup of the people. When we think of famous examples such as the Spartans at Thermopylae, the whole Spartan culture is important to understanding the how and why.
Context is really important. As you correctly note, many of the people the Romans were conquering could be even more ruthless as well (by 2025 standards). My point was more that historians wear a lot of different hats, depending on what they're doing. When you're wearing your 'investigator hat' learning how and why things worked, your thoughts might be different than when you're wearing your 'builder hat' and thinking about the society you might want to live in today (and tomorrow). It isn't a contradiction to weigh the tradeoffs that various people in history have made when designing their culture (and politics, and military capabilities).
- Weird right? My wife studied Nazi Germany, and doesn't really like the Nazis either.
History is messy - we can and should learn from those that came before, both the good and bad. One can both admire the things the Romans accomplished while simultaneously despising the way they went about accomplishing them. It isn't a contradiction.
- Fortnite & Call of Duty
If I could travel back in time and prevent my kids and nephews from ever learning about Fortnite, I might do it. Instead I'm out here trying to keep from getting sniped by a Simpson character.
Fortunately, it seems like the rest of the family is getting tired of COD's ceaseless churn, and might be willing to pick up something else.
- Pretty much the only reason I boot to Windows anymore is to play games with my kids and family. The direction of this thing is dangerously close to being all I'd care about from a desktop computer.
If Valve pivoted into making a well-supported laptop with good hardware that ran Linux and played games...
- Oh hey, the AEGIS poll looks like it's due today [1].
Committing, better performance, random nonces - let's go.
[1] https://datatracker.ietf.org/doc/draft-irtf-cfrg-aegis-aead
- > Random IDs > Latacora, 2018: Use 256-bit random numbers.
> Latacora, 2024: You should get 100 lava lamps, point a camera to them and use the frames as seed for a PRNG.
Man, is my boss gonna be surprised what's getting requisition ordered this morning.
- Yesterday my wife burst into my office: "You used AI to generate that (podcast) episode summary, we don't sound like that!"
In point of fact, I had not.
After the security reporting issue, the next problem on the list is "trust in other people's writing".
- Can you expand on what you find to be 'bad advice'?
The author uses an LLM to find bugs and then throw away the fix and instead write the code he would have written anyway. This seems like a rather conservative application of LLMs. Using the 'shooting someone in the foot' analogy - this article is an illustration of professional and responsible firearm handling.
- 100%. I’m with y’all - this is what I would also call a “no-backend” solution and I’m all in on this type of approach for static data sets - this is the future, and could be served with a very simple web server.
I’m just bemused that we all refer to one of the larger, more sophisticated storage systems on the plant, composed of dozens of subsystems and thousands of servers as “no backend at all.” Kind of a “draw the rest of the owl”.
- S3 is doing quite a lot of sophisticated lifting to qualify as no backend at all.
But yeah - this is pretty neat. Easily seems like the future of static datasets should wind up in something like this. Just data, with some well chosen indices.
- Not scared, time limited.
The world is a complicated place, and there is a veritable mountain of things a person could learn about nearly any subject. But sometimes I don't need or want to learn all those things - I just want to get one very specific task done. What I really appreciate is when an expert who has spent the time required to understand the nuances and tradeoffs can say "just do this."
When it comes to technology 'simple' just means that someone else made a bunch of decisions for me. If I want or need to make those decisions myself then I need more knobs.
- It's an interesting risk tradeoff to think about. Is 14k lines of LLM generated code more likely to have an attack in it than 14k lines of transitive library dependencies I get when I add a package to my project?
In the library case, there is a network of people that could (and sometimes do) deliberately inject attacks into the supply chain. On the other hand, those libraries are used and looked at by other people - odds of detection are higher.
With LLM generated code, the initial developer is the only one looking at it. Getting an attack through in the first place seems harder, but detection probability is lower.
- No, we would use something similar to S-Expressions [1]. Parsing and generation would be at most a few hundred lines of code in almost any language, easily testable, and relatively extensible.
With the top level encoding solved, we could then go back to arguing about all the specific lower level encodings such as compressed vs uncompressed curve points, etc.
- * Opens Github repo
* Opens Cargo.lock [1] and pnpm-lock.yaml [2]
* Closes Cargo.lock and pnpm-lock.yaml
* Goes to find a Tylenol
At least with open source we can see the sausage getting made...
[1] https://github.com/votingworks/vxsuite/blob/main/Cargo.lock
[2] https://github.com/votingworks/vxsuite/blob/main/pnpm-lock.y...
- It's been a few years since I've slung code with it, but I'm pretty sure IAR had their own compiler (along with it's own special occasional bugs). Of the IDE's I've used, it wasn't that bad. But QT Creator was better. Bringing together IAR's tech and reach with QT's expertise does make a lot of sense.
- It’s useful for someone to be wrong on the Internet.
I’ve learned a lot from watching constructive disagreements between other people. Regardless of whether they’re “right” or not, healthy disagreements sharpen our perspectives.