FreeCAD Version 1.0 Released
After more than twenty years of intense and sustained development, the FreeCAD community is proud to announce the release of version 1.0. FreeCAD 1.0 is now available for download on all platforms.
https://blog.freecad.org/2024/11/19/freecad-version-1-0-released/
@mitch I assume that's just the display software not honouring EXIF rotation or equivalent? Or did they actually decide penguin butt was what your slide needed?
> As a fun aside, i threw Arab numbers into something recently for subsection markers (1.A.۱, 1.B.۲, …) just to play with this notion.
I hope it worked well! One caveat - if the audience was unfamiliar with the symbols, those ones may not have been particularly useful, because someone who doesn't know the order can't use them to navigate (for example, if you see 1.A.۶ and you want to find 1.A.۵, should you scan up the page or down it?). And if the list isn't ordered, you may as well just use bullet points.
> Depending on fonts those glyphs can be very similar looking. I'm thinking of the story of how "patient O" became as "patient 0" (https://radiolab.org/podcast/patient-zero-updated). There are other real world examples of glyphs becoming confused, causing confusion in underlying concepts.
This is true, but I don't think it affects Greek letters particularly badly. I used to do peer tutoring as an undergrad, and I can't recall anyone mixing up Greek and Latin letters, but I can recall plenty of occasions where someone would mistake variable x for multiplication ×, or even variable t for addition +, *in his own handwriting*. It really awakened me to the importance of penmanship, and now I always use cursive, even in equations.
> Consider a student in a lecture. How is a student who uses a digital device for note taking going to capture these as a lecture flies by? You might say, use pen and paper, but what if there are dexterity issues or other constraints that prevent this? Even if they have pen and paper, what if they hear the instructor say a glyphs name, but they didn't recognize it.
Absolutely. Math notation was handwritten for most of its history and so it evolved under very different pressures from programming notation - suppose you want to distinguish multiple kinds of "x". If you were handwriting them, it'd be much faster to just add some kind of distinguishing mark (x₀, ẋ, x⃗, x̅, x̂, ...) than it would be to use programming variable names `x_initial`, `x_vector`, etc. Moreover, the math forms (and the initial choice of "x", for that matter) take up much less space on physical media, which is costly relative to disk space. On the other hand, to create those symbols at a keyboard requires either a very good memory for Unicode codepoints or extra time to go look them up. To me it's a case where machine must serve man, not the other way around - if you're going to use a computer as a substitute for taking notes by hand, whatever assistive technology you use has to be capable of handling the notation; if it's not, or if it makes things more difficult, the fault is with the technology, not the notation.
> Or consider the learner reading a text. When you read a math text do you think of the symbols as visual symbols, or do you translate them in your mind into utterances in a natural language?
Utterances for sure. Lots of people say they're visual learners, but I've never thought of myself as such - even if I'm reading quickly, a mistake like "well" instead of "we'll" sticks out like a sore thumb, but I can skim right past a homophone like "wheel" without noticing. In a math context, reading fast means I might confuse A and a, because I read them both as "eh" if I don't take the time to read the first one as "capital eh". But I'll never confuse α for either because it sounds completely different.
@sunflowerinrain I used Pale Moon for a time. It's a fork of Firefox from way back when (wouldn't be surprised if over a decade at this point) but actively developed since then. It has the usual issues of a niche product: harder to find troubleshooting info, fewer extensions available, some websites complain it's out of date, etc. That said, it worked well for me and if you want something like Firefox was historically, I think it's reasonable to try.
> It's not even the Greek letters Greek people use.
> the math was actually fine in Arabic
I guess it evens out because we don't use the same numbers Arab people use (1, 2, 3, ... vs ۱, ۲, ۳, ...).
I like the Greek letters because they indicate information about what the symbol represents - in the same way you might use x for a scalar but X for a matrix, or typeset ***x*** in bold to show it's a vector, seeing φ and θ and π floating around tells you that you're likely dealing with angles. In another context I might have x, y in physical space and χ, η in Joukowsky coordinates, so when I see z and ζ I have a good idea which system each belongs to right away, and thus I'm unlikely to get them mixed up as I manipulate my equations.
On the other hand, despite their distinctness, they're close enough to Latin letters that they're often intuitive (α looks like "a", β like "B", etc.), so between that and the limited number you use at any one time, it's never felt particularly onerous to learn them. That's an advantage I think you'd lose with wingdings.
> The "menus" are on the left and right-hand side of QGIS.
Ah, okay.
- Top left, browser: View > Panels > Browser
- Bottom left, layers: View > Panels > Layers
- Top right, processing toolbox: Processing > Toolbox
- Bottom right, identify results: "Attributes" toolbar > Identify Features (you can see this icon selected near the top centre of my screenshot)
> i wonder if i can get the polygons to show in different, pretty colors, like yours
In the processing toolbox:
- Cartography > Topological coloring
- Advanced > Algorithm Settings > Invalid Feature Filtering > Do Not Filter
- Run
Then in the layers pane:
- Right-click the new layer > Properties > Symbology
- Top dropdown (probably reading "Single Symbol" by default) > Categorized
- Value > "color_id"
- Classify
> What did you use to open it with
I opened it with QGIS. That's the screenshot you see. The version in our repository is 3.38.2 "Grenoble".
> you said you found a bunch of menus as well
I don't think I said that - can you point me to the quote you're referencing?
I got the initial file from [this link](https://www.inegi.org.mx/app/biblioteca/ficha.html?upc=702825296827) - it's a zip file containing more zip files, and the one you'd want for Mexicali is 020020001. That'll have a bunch of shapefiles called `020020001<SUFFIX>.shp`, and the "asentamiento" ones have a suffix of `as`.
@Bahais_Mexicali are you looking for something like this? This is based on the "asentamiento" category from the National Institute of Statistics and Geography. I don't think Google lets you scrape their data like you're describing - their general model is to sell products based on data, not the data itself.
@bibliolater Former QOTO user @peterdrake made [a game](https://redslash12.itch.io/gerrymander) on this theme a while back. Not much replay value but a neat puzzle to solve once.
@sunflowerinrain Culinary Cargo Cult! I like it.
@mitch kam kam, rúz be rúz
@sunflowerinrain my best guess is than the man/men distinction is easier to remember because changing the vowel changes its pronunciation. For some reason, in the woman/women distinction, the orthographic change is on the second vowel but the pronunciation change is on the first.
@mitch ah man it's there if I zoom in or read the mouseover text.
@mitch took me a minute, but I think I got it: "no'úmah"? I was trying to make the thin lines be diacritics at first.
@AnnemarieBridy [obligatory xkcd](https://xkcd.com/984/)
@mitch here's an alias for your `.bashrc`:
`alias resudo="(export \$(compgen -v); fc -ln -- | grep -Pv '^\s*resudo(?![^\s])' | tail -n 1 | envsubst | sudo su)"`
This handles one-liners with pipes, semicolons, ampersands, etc., which the double-bang version can't. It's slightly different from your request in that it executes the whole one-liner with a single privilege escalation rather than one for each constituent command, which no doubt will prove important in some edge case.
Briefly explained, the core idea is to pipe `fc` to `su`. The `export`, `compgen`, and `envsubst` parts are there to ensure that any environment variables get expanded. The `grep` and `tail` are there to exclude itself from the definition of "last-used one-liner", in case you should want to repeatedly invoke it. The whole thing is in a subshell to insulate you from the side effects of `export`.
@sabbatical that works way better than I expected. I'm impressed!
@selzero as an undecided voter in a swing state who's getting really tired of political ads, please spend less time on us too ;-)
@mitch I'd love to learn how the video driver breaks the swapfile; that sounds like a story with a twist ending.