MIT license includes: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
The argument is that AI models trained on open source should include the copyright info for all projects blended into the weights. And since they don’t, it violates the terms of the license.
Very interesting you identified “carries” as well. I have been working on a claude.md to effectively ban this as well as forms of “hold”, “spells”, “sitting”, using “where” instead of “when” (except in SQL), and “pins” other than when pinning an assumption or version of something. This has helped a bit, but Opus 5’s prose is really quite bad.
In the section “Hardware-accelerated WAL checksums” he explains how the JIT compiles away the hardware support stuff depending on the exact capabilities of the system its on. With AOT you don’t get this - it’s way more coarse like x64 vs ARM
TypeScript tried to accurately model (and expose to language services) the actual behavior of JS with regards to null/undefined. In its early days, TypeScript got a lot of reflexive grief for attempting to make JS not JS. Had the TS team attempted to pave over null/undefined rather than modeling it with the best fidelity they could at the time, I think these criticisms would have been more on the mark.
I am a C# dev by day and love working with it. I miss interfaces, Linq, and the nicer pattern matching features of C# when using GDScript, but overall GDScript is quite adequate for what it needs to do and the game dev loop feels faster when using it. They can interop as well without too much friction, so if you have the .NET version of Godot, it can have some code in C# where (if?) you need it and other code in GDScript when you don’t.
The shuttle’s solid rocket boosters splashed down in the ocean via parachute, and were recovered and reused. The main engines and thrusters/rcs were also reused. Only the external tank was disposed. The issue with the shuttle (among many) was that the reuse was not actually economical due to the maintenance required between each launch.
In some software platforms, the tooling makes it really easy to use a debugger to see what’s happening, so it’s common for everyone on the team to use them all the time.
The comment you’re responding to mentioned pulling code into a function. As an example, if there’s a clever algorithm or technique that optimizes a particular calculation, it’s fine to write code more for the machine to be fast than the human to read as long as it’s tidy in a function that a dev using a debugger can just step over or out of.
If you want to experience the Neuromancer vibe (but not story line), in 2025, from a contemporaneous source, I can’t recommend the Commodore 64 adaptation enough.
Saw these guys on JoCo a few weeks ago. Great set. Birdhouse in your soul was one of our wedding songs. Hard to believe Flood is 35 years old. Thanks for linking this.
Excited for this release! Have you heard from Intel yet? “Core 2 Duo” was the name of one of their processors in the early days of multicore on a single package.
Record selector to drive a data grid. Ex: Filter employees by location, or active/terminated, or salary/hourly, etc. and let the user choose one or many of these filters.
Agree. With patterns like this you are leaning on your db server’s CPU - among your most scarce resources - versus doing this work on the client on a relatively cheap app server. At query time your app server knows if $2 or $3 or $4 is null and can elide those query args. Feels bad to use a fast language like Rust on your app servers and then your perf still sucks because your single DB server is asked to contemplate all possibilities on queries like this instead of doing such simple work on your plentiful and cheap app servers.
no barge for super heavy- the point of the catch is to save weight on the massive legs that would be required. It “soft landed” in the Gulf a few miles off shore, meaning they did a burn and it entered the water not in freefall (though it still looked faster than I expected).
yes the booster’s structure is very strong vertically but not nearly as strong horizontally. There may be some “squeezing” forces from the chopsticks but this is effectively for fine positioning only. It will not support the weight. The booster will “land” by getting its pins (which stick out a bit) on the top rail of the arms.
Yes. The booster has two pins that stick out at the top that are designed to hold the weight of the entire booster when empty. The plan is for the booster to return to the launch tower, position itself between the arms which will close on it and then the pins will “land” on the arms, completing the catch.
The 2038 bug is less than 14 years away at this point. There is an astonishingly greater amount of software out there compared with 24 years ago. I don’t want to be a doomsayer but it’s probably time to keep this in mind anytime you implement an epoch going forward.