For folks looking for a GUI tool, SourceGit is quite nice.
Written in C#, cross-platform (I have only used it on linux) and a cleanly-designed conventional ui that doesn't aspire to radically alter your workflow.
I dunno, to me that seems like all YAML's mistakes all over again. I quite like the conciseness, and significant whitespace seems like a good match here, but the double hyphen thing really seems odd to me. And the syntax is so hard to parse, apparently, that their own example is syntax highlighted incorrect, coloring content as if it's tags.
If I may ask, what made you settle on the double dash to disambiguate content from tags? Like is it some sort of nod to SGML from way back when? It seems like an odd choice to me at first glance, but I bet it was thought about long and hard so I’d love to hear some background about what alternatives you considered.
I was looking at Marko a few years ago because of the concise syntax. I have always thought highly of Pug and would have loved a framework that integrated that sort of elegant, minimal syntax. Unfortunately, Marko doesn’t even get the syntax highlighting right in its own docs for this style.
The example on that page with leading commas to separate tag attributes, and a number of other choices across the framework are also a turn off for me personally.
I’ve mostly been using Svelte for the past half-decade instead but still hope for something more elegant to come along.
There is a difference between a product that a company pushes out as part of its business roadmap with a commercial strategy around it vs. an experimental research project that a single developer takes up on their own initiative.
It is great that they were allowed to open source it.
This looks fantastic. Thanks for open-sourcing this. For a passion project this looks really polished and well done.
I know a lot of people have crazy expectations from open-source projects these days - and many of the comments here echo those, but you can gradually evolve it at your own pace. You don't owe folks anything.
It is quite beneficial for people who aren't writing python. And for them managing jupyterlab installations is a bit of pain.
I would like to use this with xeus kernel for sql (which is also native) and if this reduces the resource consumption of that setup significantly, its a big plus for me.
The README says the savings is ~75 MB. In most notebook workflows you’re at most running a couple at once. Saving <1% of my system memory doesn’t let me do anything I couldn’t do before. This also isn’t going to add concurrency/parallelism to your SQL unless xeus has some special magic that this is somehow able to exploit.
