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.
The door refused to open. It said, "Five cents, please."
He searched his pockets. No more coins; nothing. "I’ll pay you tomorrow," he told the door. Again he tried the knob. Again it remained locked tight. "What I pay you," he informed it, "is in the nature of a gratuity; I don’t have to pay you."
"I think otherwise," the door said. "Look in the purchase contract you signed when you bought this conapt."
> Dan would eventually find out about the free kernels, even entire free operating systems, that had existed around the turn of the century. But not only were they illegal, like debuggers—you could not install one if you had one, without knowing your computer's root password. And neither the FBI nor Microsoft Support would tell you that.
It is, not so much so that the concept is not without precedent ("book burnings" are quite famous throughout history), but that the book burnings will be conducted by corporations that also have all the data on those who ever read them, and not to mention they are the ones who initially made money selling them in the first place.
In fact [blank] is a fantastic writing prompt for a dystopian novel, seems like a fun little game to play with friends.
You know it is not book burnings that concern me (they do a bit). It is more re-editing that will start to happen once they get the tech just right. They will edit problematic people in and out of old movies. At first it will be used for advertising. Such as switching one cola for another in scenes or a billboard in the background. It will be something like 'restaurant X has given us money to change billboards for a year'. Next year 'car company Y has given us money to change billboards for a year'. Then they will go bonkers with it. Do not like the dialog, because they said something you no longer agree with? Well run it through a couple of programs and they are now saying something else, or new and upcoming actor someone wants to promote. So you will see something then a few months later it will be edited and you will never see what you saw before.
Oh and it is already happening with adverts in some streaming movies.
And will we even notice when the books are “burned”? I have so many digital titles I think it would take quite a while for me to catch on if they were removed slowly enough.
Weird to think a book burning could happen right under our noses (literally!) without us even realizing.
I have been looking for a book title to express my discontent at the state of freedom and privacy in our rapidly all digital society today and what we can do about it.
There are several more cases of books being remotely disabled and I see this being used for censorship before long.
Which could happen system-wide because they turned off the DRM servers (a la Microsoft books) or maybe you've been deemed "unacceptable" on the platform.
> I was shooting heroin and reading “The Fountainhead” in the front seat of my privately owned police cruiser when a call came in. I put a quarter in the radio to activate it. It was the chief.
I'd like to have a serverless bug tracker, like Fossil, but for git.
Basically a bug tracker that stores the whole DB in the git repo but separately from the main tree. The tickets get synced when I push/pull, I can interact with them locally without needing an internet connection, without having to filter out projects, authenticate, etc. An open ticket would have my current branch/tag/commit as a default value for tracking, although it could be change.
And I really, really don't want notifications. Just a dashboard where the last things that are important to me are listed as long as I haven't marked them as read, and an access history.
Edit: consider having a look at the development version. While the core feature hasn't changed much, the webUI definitely improved. Also, the core became more robust and ready to accept more features easily.
Not very promising, it is written in a language which:
- is controlled by Google.
- doesn't support generics. Do we really want people to constantly rewrite basic data structure classes in 2021 and thereby reinvent bugs constantly (and waste time which could be spent on more meaningful purposes)?
Damn, these are some stupid arguments. Go is open source. Even if Google went rogue, there's nothing they could do. Go would just get forked by the community and that's it. As for generics, they're just nothing more than a developer convenience, they don't matter at all regarding what a product can do. Also they're planned in Go for next year.
> Go is open source. Even if Google went rogue, there's nothing they could do.
Have you ever used a library where the company who paid the development went "whoops, not our product anymore! poof goes the paid team, website, the community forums, the knowledgebase" ?
Usually nobody continues to maintain these after 90% of the workforce behind them gets fired and the surrounding infrastructure disappears.
Software is almost worthless without the brains behind it.
> As for generics, they're just nothing more than a developer convenience,
So you propose people write the 100,000th implementation of linked lists, maps, etc. because what they want to stick into it is not class A but class B?
> Also they're planned in Go for next year.
The fact it took years to plan them instead of including them right away is a nice proof of how ill-conceived Go is as a language.
It might have been nice as a toy to teach aspiring programmers. It shouldn't have ended up in production software.
> Damn, these are some stupid arguments.
Thanks. I consider yours as stupid too. How much progress exactly have we achieved with this wording now?
> Do you use the same argument when purchasing consumer products from shady countries which abuse workers?
This analogy makes no sense. You are comparing a product made through coercion and abuse of workers to a product willingly made with tools that you happen to have differing preferences on.
My point is NOT that Go would be made primarily through forced labor (although usage of money earned through the yield of the forced labor from ReCaptcha is rather likely).
My point is that Google is an evil company, and we shouldn't support evil entities by using their stuff.
And to make that point apparent, I mentioned other instances where people would think it is pretty obvious that "producer is evil = don't use their stuff", hoping that you would see there is no reason to act any different on Google just because they produce products which are of a type different from those that evil entities normal produce.
Because it really doesn't matter whether it is software or clothes or diamonds, if you use something publicly of someone you support them, and Google should not be supported.
Very valid points about recaptchas. Now, what does that have to do with the Go programming language that is FOSS?
Or are you calling for developers to essentially put restrictive sanctions on any and all Google products/projects?
And if so, are you actually holding yourself to the same standard? Never using a recaptcha? Never visiting a site that uses Google Analytics? Never watching a YouTube video? Never using a device which runs the Android operating system? etc., etc.?
Because you seem to be demanding such a standard from the rest of us.
> Or are you calling for developers to essentially put restrictive sanctions on any and all Google products/projects?
Yes.
> And if so, are you actually holding yourself to the same standard? Never using a recaptcha? Never visiting a site that uses Google Analytics? Never watching a YouTube video? Never using a device which runs the Android operating system? etc., etc.?
I intentionally enter a large percentage of invalid data into recaptchas to spoil their dataset.
Google Analytics is blocked by my ad blocker.
Same goes for ads on youtube.
With regards to using their stuff, I don't demand anyone should stop privately using it if they need it. You just shouldn't encourage any further people to use Google stuff by filling their ecosystem with more new software.
> I intentionally enter a large percentage of invalid data into recaptchas to spoil their dataset.
So do a few others. You are easily selected out as anomalous data, just fyi.
> Google Analytics is blocked by my ad blocker.
Great. Are you also blocking Google Fonts? Are you sure that Google is not hosting anything you are touching on a website?
> Same goes for ads on youtube.
But advertisers pay YouTube based on the viewership reputation of YouTube. You are merely providing a reduced amount of value to Google in this way.
> You just shouldn't encourage any further people to use Google stuff by filling their ecosystem with more new software.
Very honest question: Do you think you would have actually said this same thing about the C programming language in the 70s, 80s? Maybe you would have.
All in all, I am not sure that your stance justifies writing no code in Go which provides less value to Google's bottomline than even Google Fonts.
Perhaps some advertiser somewhere in the tech industry benefits from Google's public-facing Go packages proxy data for reaching a developer audience to sell to? Who knows? But, developers can turn that off and/or use self-hosted proxies.
Also, lone wolf retaliation is fine but not nearly as effective as just running for political office and being anti-Google.
This is such an oversimplification. Microsoft, Apple, Amazon, etc. are all guilty of ecosystem lock-in. Google in many ways is the most generous when it comes to open source and most of the hardware utilizing Google is by other manufacturers.
You are absolutely right! And this is why I avoid any and all software written in C due to AT&Ts prior evil monopolistic practices of the mid-20th century. /s
Yes but all those tools share one common problem: they leak their implementation or want to do too much.
The ruby one ask to gem install, the python one to pip install, the one in bash assumes Unix, the one in perl tells you to "make install" (!), radicle wants to replace my entire stack.
As a Python dev, I don't want to ask my front end experts or worse, my testing team, to setup an entire python env just so they can fill tickets. I just want to donwload an executable, and then fill in my tickets.
gitbug gives us binaries. You just execute it, and you are good to go.
Maybe one day, Python devs will take the time to use nuitka to produce binaries for their users.
Because as a dev, my attention is precious. To be productive, I prefer to pull information, than to be pushed information to.
E.G: HN doesn't push information on me. I can answer to you now because I know that at this very moment, I don't need to focus on something hard. But this afternoon, I will, and so I don't want to be disturbed and will just close this tab. Voilà, no distraction.
I don't need to be notified bugs: I don't work on them in real time. In the morning, I select the ones I will work on. New ones have little relevance to me until the next morning, which a dashboard will show me.
I need notifications on things like my clients calling me or my server failing. Those are the stuff that I need in real time.
The very first thing I do when registering with a new service, especially corporate/social ones is to go to the notification settings and disable everything but the direct message stuff.
I leave them enabled but email only, then I set up filters for each service to move it to */automated/jira directories automatically.
That way my inbox stays clear but I can speed run through first thing to make sure I’ve not missed anything, I also ruthless cull anything unrelated to my work, so any notification a project I don’t work on gets deleted.
This reduces several thousand emails a month to about 6 I actually need to see in my inbox.
https://caniuse.com/?search=grid