The concept rocks, so I really hope it will work and become popular.
A few remarks:
- the go get install is broken in the readme. I opened a ticket.
- since go cross compile, maybe you could provide binaries for Linux/Windows/Mac ? No need to go get, no need to install docker. That would open the door to include the tool in web frameworks.
Yes, being able to compile my VueJS component from inside my Python VM would be a huge plus: I would finally have one single template language on the frontend and the backend, and just one endpoint for rendered pages and API.
Quote from that SO post: "This is not a Safari bug. It's just a different interpretation of the spec.
When dealing with percentage heights, some browsers (like Safari) adhere to the traditional interpretation of the spec, which requires a defined height on the parent.
In other words, a percentage height on an in-flow element will be recognized only when the parent has a defined height.
Some browsers, such as Chrome and Firefox, have moved past this interpretation and now accept flex and grid heights as an adequate parent reference for a child with a percentage height.
But Safari is stuck in the past. This doesn't mean it's wrong, invalid or a bug."
Just worth noting, as I had a lot of fun with that one.
- it's unix only, which, when using a multi-plateform language like python, is limitating
- can't be used programmatically without subprocess hacks
If you use Python, watchdog is an interesting alternative:
- it works were Python works: pretty much everywhere
- it uses the best API for the job (e.g: inotify on linux), but will fallback on manual scanning in a thread if the underlying OS has no special file system watcher API
- it's a lib that can be use programmatically
- it features the command "watchmedo", which is basically what entr does, but with an optional rich file format and plugin system
- for simple use cases, all that stuff stays super simple
But the markdown is not the final product, it still needs to be converted to html using a "static site generator" or some other thing that breaks every couple of years. I had my static site break due to jekyll shenanigans four times in the last few years, and then I decided to move the whole thing to plain html, and replace jekyll and its myriad of unused and fragile dependencies with a three-line shell script that calls "cat". Moreover, markdown is confusing to use for basic stuff like links, images (see the sibling comment), and even enumerated lists [0].
every dialect of markdown has an infuriatingly different way of doing basic things that totally breaks your soul if you use a handful of them at the same time.
EDIT:the example you wrote is not exactly the same thing as mine, is it? It seems like it would convert to H1 and H2 headings and both would be displayed in the body.
> Moreover, markdown is confusing to use for basic stuff like [...] enumerated lists
This is a huge plus for me. Any list with more a dozen of entries and it would be tiresome to have to fix that. Also I can move the lines around freely without weird formatting issues.
Links are okay in my opinion, images are just a bunch of crap. To make an image clickable you'd have to do an image within a link, something like:
[](url)
> every dialect of markdown has an infuriatingly different way of doing basic things that totally breaks your soul if you use a handful of them at the same time.
Completely agree there. Extensions of Markdown are really annoying, but I guess that's what happens when "true" Markdown wasn't updated since 2004.
I agree, and went the html road as well for a time, but I hit roadblocks:
- When I'm in the flow, I really don't want to think about the structure of my text. The ms required for the tag insertion breaks that.
- Unless you very disciplined with your HTML use, it's hard to get back structure from you HTML doc. You have to limit yourself to the subset you would get from markdown.
I'm experimenting with asciidoc now, let's see if it's working.
You can use style="white-space: pre-wrap" on a div, and
deal with the structure later. You'll still be able to use links and images, and the text will not look like a turd, before you get to finishing up the structure. At that point you can remove the pre-wrap style.
> is it mainly about letters and whitespace in sequence like text/plain?
The main inconvenience of writing plain html is the need for <p> tags. They really do break the flow! It would be so much better if a blank line inserted them implicitly. This is indeed the killer feature of markdown and TeX.
I don’t understand these complaints about breakages. Download Hugo. Generate your site. Now use that Hugo binary till the end of eternity. The Hugo project might add, deprecate or remove features but that won’t affect you in any way. Your binary will continue to work till the end of time. (Assuming we still have x86 or ARM computers available)
Never tried hugo, but it surely must be cleaner than jekyll. As a matter of policy I prefer to install tools packaged by my distribution. For debian, the jekyll package went through several "engines" and whatnot along the years, and each change broke the build. For some reason it even needed particular python versions, even if it is written in ruby. A complete nightmare. I honestly lost faith in static site generators after the experience with jekyll. Even if hugo is saner, it is still amenable to breaking as its debian package evolves, and I don't want to deal with that.
If you care about breakage, don't rely on a package manager that will constantly change the package version. Grab the binary from the Github releases page and use it in perpetuity.
> If you care about breakage, don't rely on a package manager that will constantly change the package version.
I do care about breakage of my C, C++ and Fortran programs, and I would be very surprised if updating gcc broke their build (unless using -Werror). Why can't static site generators, which are arguably much simpler than compilers, have the basic property of not breaking sites?
Hugo has no dependency (or rather they'd baked into the single binary), it's just a binary and even runs on my shared hosting. It's the only reason I switched from Jekyll. I had so much trouble with Jekyll breaking it was unbearable. Zola is another option.
That’s quite different: # is <h1>, ## is <h2>. What you were responding to used <title> and <h1>. Markdown is for units of content smaller than a page. It doesn’t provide any means of specifying document metadata or similar.
Jython exists, and is in the same performance ballpark as CPython.
Python does so much highly dynamic stuff that even writing a good JIT compiler for it is hard, OTOH these exist. On top of all, it has GIL. I suppose the plain bytecode interpreters are as fast as possible.
WASM alredy got a killer app: being able to run any snippet of any language in a browser. For teaching programming, it's use, because projects like pyiodine can load a full python vm in a the browser and let the student experiment with the snippet without taking the risk of ruining my server.
On the other hand, there's strcmp()/strncmp(). I can never wrap my head around the fact that strcmp(s1, s2) == 0 (or even better, !strcmp(s1, s2)) means s1 is equal to s2.
If you look at strcmp like "the difference when you compare the strings for sorting", it makes complete sense. If the first mismatch of strcmp(a, b) is smaller than 0, you put the a before b, otherwise you put b before a.
The fact that an equality check can be made by running a comparison function is useful, but that's not all the method does.
For other methods in much C code, a common mindset is that a method returning a value will return the error code, with error code details in errno. The error code for success is 0, which is fitting of course.
Had C implemented booleans, this problem would never have been a problem, because if(int) wouldn't have been a legal expression, but sadly booleans are implemented as integers in the language instead. I strongly dislike languages that do allow implicit casting from integers and such to a boolean, if(var!=0) is much more readable because of the explicit boolean expression.
And the worst thing is: malaria is easily curable, as malaron is not only preventive, but fully kill the plasmodium in the liver cells. Despite that, we don't provide the drug to them.
It would cost a fraction of what we spend on research for a vaccine, but no cigar.
Of course, there is the argument that we risk developing resistant bugs. But the truth is, if suddenly all mosquitoes were moved magically to the US, you would see the drug massively used for everybody without a second though.
Not sure why you were downvoted down much but here’s my 2 cents.
I first started taking anti-malarial medicine as a child. My entire life I’ve been hearing of resistance to one drug and then another drug, and then another. Also, whenever we took chloroquine or any other drugs on a regular basis, we were well aware that having the medicine in our body would not prevent malaria—-we took it just to help reduce the severity of malaria when we’d become infected. Looks like there are already strains resistant to your drug of choice:
May be worth mentioning that the article documenting malarone-resistant malaria is virtually 20 years old already. As far as I'm aware, the problem of drug-resistant malaria hasn't been getting better...
Thats a weird argument. "Lets not give the medicine that might help as that might also encourage mutations." --> basically you are saying let's deny it to the many dying today in order to ensure the few (that can afford it) can still use it in the future. A deeply immoral and selfish perspective if spelled out this way.
The only solution then is rapid and large-scale intervention. Massive use of the most effective/least side-effect variety of drug for all at risk populations for 3(?) months, then bring in the alternatives and quickly and widely ensure their use in those areas where resistant strains still spread.
I am not saying don’t treat people. The anti-malarial medicines we used growing up were very affordable, so access was not the problem. I’m saying the vaccine is more encouraging because the medicines have not been able to put much of a dent into the problem of malaria.
A few remarks:
- the go get install is broken in the readme. I opened a ticket.
- since go cross compile, maybe you could provide binaries for Linux/Windows/Mac ? No need to go get, no need to install docker. That would open the door to include the tool in web frameworks.
Good luck, and thanks for sharing.