3,569 karma · joined August 4, 2018
You mean restrained. More specifically what you're proposing can formally be referred to as controlled natural language with executable semantics. Some attempts similar to this have been Attempto Controlled English and ClearTalk. (And Logos that someone showed here recently.)
>text would not just require reading; it would require executing algorithms embedded in the language itself
Arguably mathematics is just that.
>just like LaTeX for scientists
Future doesn't look very bright for LaTeX with Typst getting traction.
As overall note, AIs when you prompt "apply concept X in Y" (or anything really) will tell you what a great idea and then output something that without domain knowledge you've no idea if it's correct or if even makes sense at all. If don't want to do a literature research/study, recommend at least throwing the design back to the machine and asking for critique.
https://github.com/AlexanderGrooff/mermaid-ascii/blob/master...
https://github.com/lukilabs/beautiful-mermaid/blob/main/src/...
But seems, as others have also noted, although the mean quality decreases, the quality of those reaching front page increases.
That said port/clones have always been trendy. What has joined their ranks is the significant amount of what are essentially minimal prompt wrappers.
That'll be dope. The tokens used (input,output,total) are actually saved within codex's jsonl files.
Also, someone made a similar comment not too long ago. So people surely are curious if this is possible. Kinda surprised this project's submission didn't got popular.
>without using any 3rd party libraries
Seems to be an easier for coding agents to implement from scratch over using libraries.
That's true. Could even expand on this and make it have a --check-msg mode that returns 0/1 (good/bad) if commit messages lack the reasoning for the changes they're doing. Although, linting commit messages is last thing I want to do.
Meanwhile
curl -X POST -F "file=@file.csv" https://www.analysisxyz.dev/upload
# responses with report because processing is server-side afterall
Vibe coding for real. Claiming client-side and not even checking whether indeed this holds. (Though an API-driven report-as-a-service is kinda cool; few years ago will've even been a commercially-viable startup.)https://github.com/tkenaz/semantic_diff/blob/main/semantic_d...
The Intent in this report just paraphrases the well-written commit message. But what about things not written? Funnily the tool catches up the drifts:
2. Why was 196 lines of CLAUDE_NOTES.md removed? Was this intentional cleanup or accidental deletion of important project context?
The diff shows massive content reduction in project documentation with no explanation in the commit message. This could represent loss of architectural decisions, bug tracking, or development history.
So... why? No answer is given because not possible. 6. Why skip dependabot PRs specifically? Shouldn't dependabot updates also be semantically analyzed to catch breaking changes in dependencies?
Dependabot PRs could introduce security vulnerabilities or breaking API changes that semantic analysis would catch. Skipping them entirely might miss important issues.
Good question. But, again, no answer.Also maybe have an option on analysis extend, sections to see, and perhaps prompt to lessen the redundant information. E.g. in previous report, the "CLAUDE_NOTES.md massive content reduction" appears in Impact Map, Risk Assessment, Review Questions. Plus the entire sentence "Massive reduction in file size (212 lines removed, 16 added) suggests project documentation/status was significantly refactored or cleaned up" simply states what is obvious from the deleted lines in Files Changed. Some may like this, other (incl. me) won't. Personally will've preferred overall report be shorter.
The indirect impacts section seems interesting. There're cases that one may want to see modules impacted by a change, e.g. a function changing the result, making another function fail. But this is probably doable heuristically rather requiring an LLM to read the codebase.
That's cool. It also has a zsh hook, allowing you to switch to agent mode wherever you're.
Interestingly article (this and, more importantly, Kranc's) is posted late-16 but Scala's peak was early-17. So basically Kranc's article correctly asserted the then current state. Same cannot be said for HN. In discussion of the article (https://news.ycombinator.com/item?id=12662895), everyone was calling it clickbait.
>I hope it will be replaced by languages like TypeScript, but again, I doubt it.
Well, somehow it did happened. Most web dev is TS-first now.
Scala is an excellent language. At the same time, its competitors are good enough and already far more popular. Worse, its biggest one (Java) has adopted over last decade many features, dismissing Scala's strongest suit, being a better JVM language (and with Kotlin in the picture, backed by Android, that advantage is nearly gone). Scala.js/Native though may allow a nice new goal, one language everywhere.
* Discussion at the time: https://news.ycombinator.com/item?id=22830779. Article predates Scale 3 release (2021), a transition worse than Python v2->v3 (though not Perl/Raku level), as years later adoption remains low and some people actually have disdain towards it.
>manga-related project
No more info required to know it's good.
Beyond joking, there was/is indeed unexplored space in this niche. Quite amusing though how they went from an argument on a (yuri) manga discord to actually implementing & delivering a (technically competent and well presented) solution.
Also, got some comments. First will state two info points in regards to ZIP: (i) doesn't use solid compression (each file is compressed individually), (ii) can be used in archive-only (no compression) mode aka "stored" (compression method "0").
>Random Access
ZIP supports random access utilizing an (towards) EOF central directory and due to (i).
>If one file is corrupt, the whole thing won't open.
ZIP lacks corruption resistance but it isn't totally fragile. Due to (i) corruptions don't cascade across files; if one file is corrupted, others can be extracted; if no compression used (files "stored") is possible to recover files by headers.
>Metadata isn't native to CBZ,
CBZ (CBR,CB7,etc too) isn't really a well-defined format. It's just pictures within a zip file. (And due to this, project competes CBZ usage-wise but actual competitive tech is zip/rar/etc.) The ComicInfo file is conventional. This information can (and some readers support this) instead be saved in zip header as comment.
>BBF's content deduplication
Wonder how this works. Assume (due the comment '[...]the same "Credits.jpg", "ScanlationGroup.png"[...]') is done across files so maybe something like linked mkvs, that some anime mini-encode groups use? Then how zero-copy goal is achieved? In any case, no, ZIP cannot do this. But if files "stored", a deduplicating filesystem can handle it.
>Images inside are bit-exact copies. No re-encoding.
ZIP can do this due to (ii).
TL;DR BBF competes vs "stored" ZIP plus (conventional) header-saved metadata plus external tooling if my de-duplication assumption is correct. Issue though, and perhaps why an entirely new format is needed, CBZ is conventional and many things BBF targets to do won't hold if not design-bound.
Interesting seeing L4 be used for general programming. Others worth mentioning are:
1. Idris. General-purpose language but also proof assistant (~L4). It has few back-ends incl. C, JS, and JVM, so quite a large span of usable domains.
2. Glean. Rust-like syntax/UX, runs on Erlang VM, simple tooling (all-in-one compiler, build tool, fmt, pkg manager). Very modern-looking overall.
*If comment wasn't auto-posted, maybe a bug due to this? No thread for text to be attached so was dropped as comment to the next/previous live submission?