"Source First License 1.1" is an interesting choice. Sounds like something specific to this developer (so far, at least). I'm not savvy enough to be sure, but it doesn't sound compatible with any of the commonly accepted-as-FOSS licenses.
In fact, there doesn't seem to be a spec or standard for it, outside of the de facto standard used by Clojure and the programs in its orbit. I guess nobody's bothered to write a standard, because the people who are already using EDN are doing fine without one, and the people who aren't either don't know what it is or don't see its value.
Is there an example of what it looks like in practice? The Wikipedia link above doesn't have it, its citation http://edn-format.org/ seems like it doesn't exist anymore, and this github page doesn't show a sample either.
Dont be pessimistic - you are still free to used it.
I used EDN outside of Clojure. The system needed a relatively large amount of config files, and I chose EDN as a better JSON. Looks familiar to everyone, but supports comments - the primary motivation for that choice.
JSON-5 allows a single trailing comma. EDN simply ignores commas. You can have them, trailing or not. But they are really redundant and incur visual noise.
Perhaps EDN can also be improved, but that's a good format. Convenient.
Maybe with:
1) Unicode escapes in strings.
2) Indentation support for multiline string literals, like in Rust, but even better.
3) Reading with "concrete syntax tree" (make the order of map elements, the comments, whitespaces, etc representable, so that one could write an EDN file with the same formatting as it was read, e.g. after patching it). Not sure if the spec changes are needed / will be helpful for that or better to just implement it in specific parsers.
Excellent ideas, especially having a parser keep order of parsed data.
I wonder if EDN reader/parser for different languages could be written once, then compiled through wasm to c (https://news.ycombinator.com/item?id=38602750) and linked in each language as c library.
Definitely would like to see EDN or slightly improved version as a modern and usable alternative to json/yaml (regardless of https://xkcd.com/927/).
It's certainly useful, but having it embedded within the hardware with no way to properly secure it makes the RP2040 a non-starter for any product I've ever written firmware for.
When you write a procedure that has to maintain an internal state between calls, stopping what you're doing and switching to functional programming makes sense.
The only difference between this and https://xkcd.com/1958/ is that this attack confuses cars from certain manufacturers but not human drivers, and I'm not sure that that distinction is important.
Is this attack actually in anybody's threat model?
It should be. We've seen real, in-the-wild attacks on self-driving systems: People putting cones on hoods.
There are people out there who don't want autonomous vehicles on the streets. Whatever their reasoning is isn't particularly relevant, because if someone wants to accomplish a given end, this has potential as an attack vector.
We live in a time where kids will call a SWAT team to someone's house because they don't like their twitch stream. I wouldn't underestimate what people will do for the lols, especially if there is a disconnect between their actions and the outcome.
This is false. It's true that staying at 100% is harder on lithium ion batteries than staying at 40%. However, the wear due to charge cycles is way, way more significant. Your battery will see much less wear if you keep it at 100% for some time vs discharging and recharging it a few times between (e.g.) 40% and 80% during that same time.
> the sentiment of this comment comes off as asking what the end game is for any hacker demonstrating vulnerabilities
GP isn't asking about the "endgame" as in "for what purpose did this author do this thing?". It was "endgame" as in "how is the story of LLMs going to end up?".
It could be "just" more cat and mouse, like you both mentioned. But a sibling comment talks about the possibility for architectural changes, and I'm reminded of a comment [1] from the other week by inawarminister ...
I think it would be very interesting to see something that works like an LLM but where instead of consuming and producing natural language, it operates on something like Clojure/EDN.
To respond more appropriately to that, I think truthfully we don't really know the answer to that right now (as implied my my previous comment). There are definitely people asking the question and it definitely is a good and important question but there's just a lot we don't know at this point. What we can and can't do. Maybe some take that as an unsatisfying answer but I think you could also take it as a more exciting answer as in there's this great mystery to be solved that's important and solving puzzles is fun. If you like puzzles haha. There are definitely a lot of interesting ideas out there such as those you mentioned and it'll be interesting to see what actually works and if those methods can actually maintain effectiveness as the systems evolve.
Does the Pi 4 have hardware video decoding in mainline Linux yet? I gave up on Raspberry stuff after buying a 4 and finding out that the mainline support was so much worse than expected.
It seems the answer is 'yes', especially for formats like h.264. Notably, they discontinued HW support in the RPI5 and chose to process it through software instead. This approach saves money since they don't need to pay for the intellectual property rights in the System on Chip (SoC). Additionally, the BCM2712 handles the video processing w/out breaking a sweat.
