On pretty much a daily basis I’m torn on whether to enforce real tabs everywhere even in shared code or give up and use spaces. Tabs as spaces are so much worse, it’s still surprising that most of the JavaScript and Ruby world has settled on them. Trying to fight it creates new problems.
@manton Everything is double posting for me again! Microblog is just too buggy for me to rely on it!!!!!
@manton I didn't install any app, AFAIK. I just hit reply, type some text and hit POST in top right. Very buggy, verrry frustrating after all these years. It should be easy, but apparently it is not. Urgggh!
@Ron Hi Ron! Can you list these details for what you're using:
Machine: Computer/Phone/Tablet/Other
System: Windows/Mac/Android/iOS/Other
Client: Browser/App/Other
Exact client: Chrome/Edge/Safari/Official Micro.blog app/Other
With that information it might be easier to hunt down the bug.
@SimonWoods Hi Simon, I am now using LG Android phone. Manton told me to stop using the Android app and to use web app instead. How do I tell? I think I'm in some generic micro.com now.
I did install a current update to microblog app with the gold and orange star. I did that thru Google app store, I think.
What I'm in now has a cancel button and a Post button below the edit window. Maybe that is web interface? I found it with Google search.
@SimonWoods That reply didn't double post. This one is from clicking on the gold/yellow icon on my phone. Maybe that is the Android app? I click on POST in top right corner of phone on this one.
@Simonwoods Now back on web version. The app did not double post this time. Maybe it is fixed now. I don't know what breaks it and how to delete duplicates when I get them. It's embarrassing, so I rarely post. 😥
@manton I think my JSON data templates and CSS probably have an unholy mess/mixture of tabs and spaces. I started out using tabs, then (I think) read somewhere that Hugo and Go prefer spaces, so tried to remember to use them instead. Is there an official preference?
@manton Yeah, Go has settled on tabs over spaces as well. I think the saving grace is that everyone in the Go community more-or-less expect code to be formatted using go fmt, which converts spaces to tabs, and any Go text editor pretty much expect tabs in the source. You can adjust how large the indentation appears, but at least you're less likely to encounter a file using spaces.
@manton I mean isn't the solution to just use spaces then? I kinda don't get the big deal of having to use spaces anyways... (not trolling, I just never have had the chance to interrogate this with anyone)
@matti Don't want to start a big debate about this, but the main advantage to real tabs is that everyone can have a different preference for indentation (2 spaces, 4 spaces, 8 spaces!) and it all just works seamlessly.
@manton things we don't talk about in polite company: religion, politics, Mac vs PC, and tabs vs spaces.
