6 ms·
Gliimly is a programming language for web services
- not_your_vase 2y agoI really love the commit messages. This style adds a lot of value.
- Alupis 2y agoThis has the appearance of "developed in private, cleansed, thrown over the wall" sort of thing. The commit messages probably mean something to whoever is behind Gliim LLC. Some people get it in their heads that their commit history needs to be "clean". It doesn't...
- IshKebab 2y agoCommit history has to be clean just as much as code has to be clean. That is to say, it doesn't - but it's far nicer working with clean code than tangled uncommented messes.
- derefr 2y ago> Some people get it in their heads that their commit history needs to be "clean". It doesn't... If by "clean" you mean "readable" (in the literate-programming sense), then I'd be a strong advocate of that. I would like to one day see a repo that is maintained in such a way that, if you just dump out the commits in chronological order (e.g. `git log --patch --reverse --pretty=format:"%s"`), the result is essentially a jupyter notebook that explains the system being built as it builds it. Such a thing would require a lot of rebasing, of course. --- But of course, actually looking at giimly's commit history (https://github.com/gliimly/gliimly/commits/main/ https://github.com/gliimly/gliimly/commits/main/), you don't mean "readable." You mean "says nothing." I think this repo is clearly the result of "development in private", but I don't think the commit messages here were "cleaned up." I think this is just this person's way of using git in a single-user context — they just want to incrementally save WIPs, so they number them. (Maybe they even use an editor plugin that does this for them on save, or through a keyboard-shortcut.) That being said, I do sometimes also see this in the cases of private repos that were so messy and fraught, with long-lived now unmergeable feature branches, that the best way to integrate everything was to just convert each long-lived branch into a set of .patch files; manually prune and edit those .patch files in a text editor; and then `git am` each patchset into a synthetic commit. Those commits don't really have coherent purposes — they're just incremental steps of a single long integration — so you may as well just number them. (Usually, though, people rebase-squash these all once they're done.)
- Alupis 2y ago> If by "clean" you mean "readable" (in the literate-programming sense), then I'd be a strong advocate of that I don't disagree. However the commit messages should have some meaning. Looking at the repo closer, it appears the commit messages are release numbers: Commit 91: https://github.com/gliimly/gliimly/commit/956f8001890d85a4d39dda932ea95c01f220c531 https://github.com/gliimly/gliimly/commit/956f8001890d85a4d3... Release 91: https://gliimly.blogspot.com/2024/11/gliimly-91-released.html https://gliimly.blogspot.com/2024/11/gliimly-91-released.htm... Which, if the case, is even more awful. Now to understand the change history, I need to consult/cross-reference some documentation page that might 404 in the future. Additionally, the releases have many un-related changes grouped together (as one would expect for a release, not a commit). Lately I've become fond of the squash-merge. All development is in a branch, and to merge you open a Pull Request (or equivalent on whatever platform you use). The PR gets squashed into one commit that references the original PR, which retains all of the commit history and discussion/review comments. Best of all worlds in my opinion, and frees developers to commit freely without consequence or care.
- aeontech 2y agoJust to comment on your last paragraph - I don't really understand people's obsession with having squashed commits on main. I may not have a local copy of the branch that was merged months ago, so I can't get the un-squashed history without jumping through hoops. It also makes tools like git-bisect much less useful. With my team, once you are done with your PR, you do a quick rebase pass over your branch and squash any remaining partial/in progress/fixup commits into a final set of meaningful logical commits - this set gets merged into mainline wholesale, without any further squashing. Each commit has the ticket id in the commit message, so you can find all related changes easily if ever needed. This gives us history that's both granular enough to be useful, and meaningful. (Granted, if your team is disciplined enough to only have very small and granular PRs that only deliver a small logical unit of change at a time, the distinction between approaches becomes moot... but in my experience most PRs tend to be a little bigger that that, and contain at least a couple of related but distinct sets of changes) And yeah, the commit history in this project is just hilarious.
- kaycebasques 2y ago> The commit messages probably mean something to whoever is behind Gliim LLC To me it just looks like they increment by one with each commit. Some numbers might be skipped simply because of fixup rebases. https://github.com/gliimly/gliimly/commits/main/ https://github.com/gliimly/gliimly/commits/main/
- leptons 2y ago>Some people get it in their heads that their commit history needs to be "clean". It doesn't... I do not care about git commit history at all. Do not squash. Don't do anything other than commit, push, and merge PRs. I don't delete old branches, I don't do anything beyond the basics. I don't even use rebase. It has never bit me in the ass at all in all the years I've been running this team. The less I have to do with git, the better.
- kgeist 2y agoAt our organization, no one squashes or rebases either. We never delete branches. It's been like this for around 15 years. Not a single problem.
- leptons 2y agoI guess it depends on the developers and how they choose to commit. On my team we don't commit unless we're ready to push, so we aren't creating 100s of commits for every feature or bug fix. Some developers seem to think they need to commit every 2 seconds for every tiny little change. That's just seems like a waste of time to me, and it also creates the need to squash and do more stuff with git. Anything that distracts me from writing software and putting work into the code is a distraction, and git is a distraction. I don't really want to deal with git as often or as much as some developers seem to use it constantly to commit everything... git commit -m "added a blank line"
- kgeist 2y agoDunno for me it's great to commit if I just made substantial work but it's not ready yet. It's assuring that my work won't be accidentally lost if I mess up. Especially it's great to commit at the end of the day or if I just wrote tests which all pass. Stuff works, I can move on, and forget about it. Next day when I write more code, and something breaks (but worked yesterday) I can easily see the diff between yesterday and today and see what changed and where I'm currently at. Commit messages remind me of what I did, step by step. Then I push to the dev environment and if QA finds bugs, I commit new changes which fix the bugs. It's also great for the reviewer - they only have to look at the single bugfix commit, the rest of the code is fine (already reviewed). I don't find a use for squashing, modern tools allow to see several commits as one diff.
- johnisgood 2y ago> This has the appearance of "developed in private, cleansed, thrown over the wall" sort of thing. To be honest, I do this with personal projects, and by "this" I mean I finish the project, try to polish it and "cleanse" it as much as possible, and then git commit add with message "Initial commit", and after that of course I have proper commits for bug fixes, feature additions, etc.
- agumonkey 2y agomystery driven development
- rapnie 2y agomagic number driven design
- wruza 2y agoMost of the commit messages in my personal projects say “Temp” and yet to see any issues with that. I have some repos where I maintain commit messages (by inertia) and it always bugs me as an utterly useless routine. In the rare case when I have to investigate history, there are actual code changes and all the tools to navigate them. There’s no “read through the log to find a change” in my workflow, just like there’s no “read through code to find an identifier”. It doesn’t mean that this works for all projects and workflows. People report their day saved by a commit message. But that blanket belief in sacred commit messages is just that. It’s not unusual to see a 1-person repo to contain synthetic messages cause under no peer pressure people act like it’s natural to them.
- deleted 2y ago[deleted]
- benatkin 2y agoMy first impression is that like with HTMX, it's for a style of web apps that has few uses nowadays. The benefit of the HTML syntax quickly goes away if it has a JavaScript frontend. The routing doesn't make sense in a non-trivial app. For a non-trivial app, something more flexible like Django's routing system makes sense. It says it's service-oriented. It doesn't have what I expect from something service-oriented in its big example, though. For instance the entry point to the app is /session/start and it doesn't route based on HTTP methods. https://gliimly.blogspot.com/2024/11/multi-tenant-saas-notes-web-application.html https://gliimly.blogspot.com/2024/11/multi-tenant-saas-notes...
- kgeist 2y ago>My first impression is that like with HTMX, it's for a style of web apps that has few uses nowadays. What do you mean? I see nothing common with HTMX. It feels more like old PHP5 projects, where they mixed business logic with controllers, database access and template rendering all in one big soup.
- duskwuff 2y agoEven PHP had a composable expression syntax (e.g. nested arithmetic/string/array expressions, function calls, etc). I don't think this does; every statement seems to be a unique, standalone thing.
- think970 2y agoThat may be a good thing. I think it's more natural to have it that way. I always wondered why a keyword in a programming language must have this rigid meaning. In English, that's not the case, there's a context. Gliimly seems much simpler than PHP or other "classic" programming languages out there (C++, Java, Go, whatever). I think there's something to the idea of expressing programming closer to English, in a declarative way. I'll give it a try, I'd love to type (much) less and just sort of "talk" programming, because that's what this looks like.
- 2y ago
- OutOfHere 2y agoI see it is implemented in C. Doesn't this add a substantial attack surface, especially relevant for web services? How is the "memory-safe" claim justified?
- burnt-resistor 2y agoThere is a pervasive, cultural lack of formal verification in software, and it's risky, terrible, and should be stopped. Formal verification can takes multiple forms and operates at different spans across the layers of the stack. We need more of it to prove the correctness of compilers, libraries, and programs. It is a lot of work, but it's critical to proving things are as good, as say, seL4.
- johnisgood 2y agoWe need more Ada / SPARK!
- tlarkworthy 2y agothere is a culture of type safety which is a very watered down machine checked proof that the thing entering a function has affordances X,Y and Z. Its not the end to end functional verification you are talking about but its not nothing either.
- up2isomorphism 2y agoYes, it opens a large attack surface for a group of people who thinks “memory-safe” is only possible when that word appears on the top of a language’s features list.
- flockonus 2y agoTL;DR for people coming from developer friendly web servers like Rails, Go, Node, Python -- this is not it. https://gliimly.blogspot.com/2024/09/web-service-hello-world.html https://gliimly.blogspot.com/2024/09/web-service-hello-world...
- antihero 2y agoWhy on earth would you want to use a developer unfriendly language to build anything in? This example URL: http://127.0.0.1/hello/hello-world/name=Mike http://127.0.0.1/hello/hello-world/name=Mike What? Is the project some sort of joke?
- peterh76 2y agoLooking at the comments, I am puzzled. Do any of you have real jobs, where you need to do things fast and easy without the mess? This seems like a good fit. Most comments are kind of snooty here, don't ya think? When I look at the examples, like the top one (currently) on the web page, which is a "SaaS example in 200 lines" (or something to that effect), it looks good to me. Simple, quick to grasp. I actually ran it, and it worked. I was able to quickly make something useful (especially since PostgreSQL is my bread and butter), and there's an application server that runs just fine. I even tested performance with ab, and got some 3900 requests per second through Nginx. Of course that's meaningless given we all have different hardware, but I can tell you it's pretty zippy. And what's wrong with the URL above? How's that a joke? In what universe? Someone below mentioned this is like an assembler. What? It's the opposite you guys. If I look at the example, and I look at the code I'd have to do in just above any language (and I've done it twice so far in different languages), Gliimly looks like a step forward to me. Say when I did this in Go, I'd say that looked like an assembler, and Gliimly looks like a high level language. I wonder where are these comments coming from. Folks from other projects who don't like competition? Geeks who love their ancient tech to the point of exhaustion? Come on folks, give the rest of us regular people a break.
- marcosdumay 2y agoThose are as short instructions as you can get for deploying something on the web. It only seems to be missing a development server.
- ks2048 2y agoTip for anyone presenting a new programming language, IMHO: include a 10-to-20 line program on the front page to give people a quick idea of what it looks like. After a few clicks, I think I found the "Hello World" example, begin-handler /hello-world public get-param name @This is Hello World from <<p-out name>> end-handler
- duskwuff 2y agoThere's a more extensive worked example at: https://gliimly.blogspot.com/2024/11/multi-tenant-saas-notes-web-application.html https://gliimly.blogspot.com/2024/11/multi-tenant-saas-notes... And, at a glance, I see: - HTML output being constructed by string concatenation. - SQL queries being constructed by what looks like sprintf. - No functions, just HTTP handlers, some of them marked as "private". - No expression system, just non-composable commands like "hash-string" or "match-regex". - No evidence of an object or class system. - Some evidence of filenames with 'magical' behavior like "before-handler.gliim". None of this fills me with confidence. This is a toy at best.
- benatkin 2y agoIt's a lot like https://hurl.dev/ https://hurl.dev/ or https://jqlang.github.io/jq/ https://jqlang.github.io/jq/ - it's an intentionally limited DSL. I think if it were more like https://hurl.dev/ https://hurl.dev/ I might find it slightly more interesting.
- thephyber 2y agoThe criticism wasn’t only about how limited the DSL was — it was about how some of the design choices are repeating patterns which are very common sources of security defects. HTML and SQL are DSLs themselves and have non-trivial security contexts.
- deleted 2y ago[deleted]
- 2y ago
- hathawsh 2y agoThe only owner of this project is "Gliim LLC" and it's written in C with cryptic commit messages. This looks dangerous. If this is an honest project and not an attempt to inject malware into other people's projects, you should: - Say who you are. - Commit as individuals, not as the company. - Explain how this is memory safe. The C language makes that seem very unlikely.
- koito17 2y agoTip: use the patch format feature of GitHub to view people's e-mail addresses. Looking at the commit log, the initial commit caught my attention. The author of the initial commit does not link to any particular account on GitHub. See https://github.com/gliimly/gliimly/commit/23e44479d675d3124ecc4653ece4107bafd2e1fc.patch https://github.com/gliimly/gliimly/commit/23e44479d675d3124e... From here, we can see some identity. From: gliimly <sergemij@yahoo.com> Pasting the e-mail address into a search engine reveals another work by the same person. In particular, https://vixra.org/pdf/1208.0044v2.pdf https://vixra.org/pdf/1208.0044v2.pdf . The fact the person publishes under Vixra likely means they are not someone malicious, just what some in the mathematics community call a "crank".
- j_bum 2y agoThanks for the sleuthing work. And by “crank” do you mean a recluse? Or someone off of the grid?
- koito17 2y agoThe first definition in [0], that is: a person who has strange or unusual ideas and beliefs [0] https://dictionary.cambridge.org/dictionary/english/crank https://dictionary.cambridge.org/dictionary/english/crank
- duskwuff 2y agoAnother term for it would be "fringe science". The paper is an amusing thought experiment based on some baseless assumptions; it would be foolish to assume that it describes any kind of physical reality.
- triyambakam 2y agoInstead of .gliim I would have gone with .glm
- rfl890 2y agoMost of the offered cryptographic primitives (encrypt-data[1], decrypt-data[2], derive-key[3]) are not easy to use correctly. The encrypt/decrypt data interface uses AES-256-CBC with (seemingly) no authentication, and the key derivation uses PBKDF2 with default iterations of 1000 and vague instructions on which value to choose. No interface to a memory-hard KDF is available. This, along with the notion of memory safety from untested C code doesn't really instill a sense of confidence in me... I would suggest throwing away all the cryptographic primitives you currently have and instead interface with libsodium, which is a library designed for the rest of us non-cryptographers. [1]: https://gliimly.github.io/encrypt-data.html https://gliimly.github.io/encrypt-data.html [2]: https://gliimly.github.io/decrypt-data.html https://gliimly.github.io/decrypt-data.html [3]: https://gliimly.github.io/derive-key.html https://gliimly.github.io/derive-key.html
- slmjkdbtl 2y agoI'm still not getting it, this looks like a standard language + swapped keywords + web service libraries, what does the new language accomplish?
- ahoka 2y agoDoes this run on Temple OS? Would be a good fit.
- anonzzzies 2y agoDoesn't seem compatible with Holy C.
- anacrolix 2y ago[flagged]
- sakesun 2y agoThe phrase "programming language for web services" remind me of Borland Charlotte language introduced 20 years ago. Those days the term web services means SOAP, however. :)
- proxyf150 2y agoI tried Gliimly. I just had to after some really weird comments below that start like a gossip club and then degenerate into preferences for git commiting (like anyone cares about either). Anyway, Gliimly's simple to write code with, and without being too pedantic about what some people think "web service" or "service-oriented" means, it did what I needed it to do. That is to say, I was able to build a web application for work (insurance) pretty darn quickly, all in a REST-like structure of service calls. I am not a fan of an object oriented paradigm, though the company I work for (still) uses C++. I used to be all over it. But it's gotten so complicated that I am looking to make a 180 and find something so simple it stinks. Gliimly could be it, or not, but I like simpler. Is it safe? I did try some nasty stuff that would overwrite memory, and the program stopped with the appropriate message. I tried SQL injection and couldn't do it. So the fact it's written in C doesn't mean anything, I mean lots and lots of critical software are written in it. I haven't run into any bugs, and compiler error message were pretty descent. The performance was better than C++ for the same legacy app we have, and that's about 12x larger in terms of source code. Overall, Gliimly is something I could work with, assuming it stays, which is a big if. Most projects like this eventually lose steam unless they get some kind of sponsorship from a "consortium" of companies, but hey, some work out without that kind of backing just on their merit. Time will tell.
- velcrovan 2y agoRight click → Inspect element, find `body { letter-spacing: 2px }` and uncheck. AHHHHHHHH much better
- antihero 2y agoThe website is hurting my eyes to read, is it mono/overspacing Times? Also the language looks...really difficult to mentally process and doesn't seem particularly as expressive as anything that currently exists and is used regularly. It seems to be doing everything unpleasantly/wrong to the point I'm not sure if it's some sort of elaborate joke.
- kriket8ho 2y agoOn the contrary. The web site is clean and easy to navigate. The language is much less jarring than most commonly used languages today, which unless you're using them day in day out, often look undecipherable. Gllimly looks like I could pick it up in a day. Very expressive. I guess for people who worked with complicated languages much of their career, their stuff is easy. Realistically though, this language would be my choice if I were to learn something new. And that's no joke.
- slater 2y ago> The website is hurting my eyes to read, is it mono/overspacing Times? Yeah, they're fucking with the letter-spacing, adding 2px. Note to devs that want to play web designer: Don't. And especially don't mess with letter-spacing.
- gbickford 2y ago> Create Hello World application: > sudo mgrg -i -u $(whoami) helloworld Why does it need sudo to compile?
- whalesalad 2y ago2px letter spacing on `body` is atrocious
- pmontra 2y agoThe language has a 60s flavor. This snippet reminded me of COBOL like verbosity with kebab cased keywords. set-number max_loop = 300 start-loop repeat 1000 use i start-with 1 etc.