Zato
scroll
Our great sponsors
Zato | scroll | |
---|---|---|
3 | 34 | |
1,070 | 329 | |
- | 1.2% | |
9.9 | 6.5 | |
about 1 month ago | 9 days ago | |
Python | JavaScript | |
GNU Affero General Public License v3.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Zato
-
We Should Have Markdown Rendered Websites
Yes, the article is correct, there is a market for Markdown sites and related products.
Our Zato website is in Markdown: https://zato.io
We have a purpose-built static site generator, which makes sense in our case because:
* The resulting site is very fast, seeing as there is no need for runtime generation of any assets / HTML / any kind of resources
* It is easier for developers to work on documentation because they already know Markdown
* It is easy to statically apply filters such as spell checkers for multiple languages during the build
* Various optimizations can be applied, e.g. incremental builds or on-demand builds
The drawbacks are:
* Non-technical translators may have a difficult time working with anything but either their own specialized tools or MS Word and they consider Markdown to be "advanced"
* Sometimes you work with writers who are not technical at all and who will not understand what a build system is even if they are open to the idea of learning Markdown itself
Thus, there is a market for a lightweight CMS that would enable non-technical people to author Markdown in their browsers, without a need for any command line usage.
- Open-Source ESB, API, AI and Cloud Integrations in Python
- Service-Oriented Architecture (SOA)
scroll
- [OC] Cancer in the United States: Heatmap Visualizations
-
Ask HN: What are you building that is taking multiple years to make usable?
It took me many years to get Scroll (https://scroll.pub/) to the point where I love it and am confident it will be the dominant language for writing going forward (replacing markdown).
I first had to invent Tree Notation (2017), which I got wrong on my first two tries (2012's Note and 2013's Space). Then I needed to invent Grammar (2017), and then I made the predecessor to Scroll called Dumbdown (2019). 2 years after that I shipped the first version of Scroll (2021).
Now we are on Scroll version 58 and it's blazing fast, very simple, extremely extendible, and scales very well.
It was 90% me for a while, but recently been very much a team effort.
It took a while to get right because it's a whole new kind of language, so there were a lot of mistakes that I made and had to undo, and it took a while to figure out exactly what was special about it and how to double down on that.
- Ask HN: With recent layoffs, how would you advise new grads entering the market?
-
Anyone interested in starting a local newspaper using new tech?
I recently started 2 new newspapers: https://longbeach.pub/ and http://hawaii.pub/. Very different from traditional newspapers in that they are: public domain, open source (view source on every page), and built using a new language (https://scroll.pub/).
-
Argdown: A simple syntax for complex argumentation
Another cool site I found recently (via the replit guy) is https://www.rootclaim.com/
Very cool way to present arguments.
I'm thinking of taking that, as well as argdown, and building some easy to use keywords in scroll https://scroll.pub/
-
We Need to Know LR and Recursive Descent Parsing Techniques
> Context-free grammars, and their associated parsing techniques, don't align well with real-world compilers, and thus we should deemphasise CFGs (Context-Free Grammars) and their associated parsing algorithms.
I think CFG are highly overrated. Top down recursive descent parsers are simple and allow you to craft more human languages. I think building top down parsers is something every dev should do. It's a simple technique with tremendous power.
I think the source code for Scroll (https://github.com/breck7/scroll/tree/main/grammar) demonstrates how liberating moving away from CFGs can be. Easy to extend, compose, build new backends, debug, et cetera. Parser, compiler, and interpreter for each node all in one place. Swap nodes around between languages. Great evolutionary characteristics.
I'll stop there (realizing I need to improve the docs and write a blog post).
-
I am building a new kind of newspaper and so have been collecting and studying old newspapers. Here is one from my collection, an issue of the Columbian Centinel (Boston), from 1795, when George Washington was president. The classifieds make me laugh. Lots of Schooners for sale.
- Uses a new language called Scroll: https://scroll.pub/
-
Start a Fucking Blog
Also, put down Markdown and give our Scroll a try: https://scroll.pub
It now powers sites like my own blog (https://breckyunits.com/), knowledge bases like PLDB.com, and our first new public domain daily newspaper called the Long Beach Pub (https://longbeach.pub/1-3-2023.html).
-
Programming languages in 25 days, Part 2: Reflections on language design
> Java, Go, Javascript, Rust, etc are all regularly written with whitespace, and have tools to enforce such formatting, but they don't derive information from it.
Ah you reminded me. A curious phenomenon I've observed with Prettier in JS and fmt in Go is languages are moving to standardized whitespace, but as you said, not yet deriving information from it. I don't know enough about Java or Rust but I suspect they probably both have adopted a Prettier/fmt like convention where all code is formatted on save. So it seems like we are moving to a world where it will be a simple flip of a switch to then start having popular languages extract meaning from the whitespace.
> Also, Python has existed for decades and still there is little further adoption of indentation-sensitivity. It doesn't seem like a wave of indentation-sensitive languages will be coming any time soon.
I think it's coming big time this year. I think our Scroll (https://scroll.pub/) will catch fire and be the go to language instead of Markdown by the end of the year. Then with the increasing success of TreeBase (powering PLDB and others) we will start to see JSON fall for config formats and document storage databases. A lot more will happen to, data vis will be a big one, but those 2 I'm reasonably certain of happening in 2023.
-
Ask HN: Programs that saved you 100 hours? (2022 edition)
GoAccess: https://goaccess.io/. I don't miss Google Analytics at all.
Loom. It's not open source I don't think but I'm digging it and excited when a public domain competitor comes out.
Our https://scroll.pub/. It's far beyond markdown at this point. I am able to not only write better but also maintain thousands of pages of content by hand (well, most of the credit for that belongs to Apple M1s, Sublime Text, git, MacOS, and Github). The stuff we are doing with it now would just not be possible with anything else, and what we're coming out with next year is super exciting. It's all public domain.
What are some alternatives?
pycon
breckyunits.com - Breck Yunits' Blog
python-fints - Pure-python FinTS (formerly known as HBCI) implementation
CameraTraps - PyTorch Wildlife: a Collaborative Deep Learning Framework for Conservation.
okuna-api - 🤖 The Okuna Social Network API
ppg.report - Weather report tailored for paramotor pilots, available worldwide. 🌏 Combines winds aloft, nearby Terminal Aerodrome Forecasts, hourly forecast, NWS active alerts, FAA TFRs, SIGMETs, G-AIRMETs and CWAs
Alerta - Alerta monitoring system
djot - A light markup language
python-n26 - 💵 Unofficial Python client for n26 (Number 26) - https://n26.com/
sumatrapdf - SumatraPDF reader
abna - Python library to automatically retrieve mutations from ABN Amro
true-zen.nvim - 🦝 Clean and elegant distraction-free writing for NeoVim