I converted it to celsius and just realized it means you can't sleep if the temperature is above 22C. IMO, that's a reaching the level of a physical handicap: it's a very mild temp.
That is in no way a physical handicap. Sleep quality (in terms of actual rest and recovery) is highly dependent on temperature. The optimal temperature is about 18 °C for most people. This article has an extensive list of references if you want to dig into the research.
The entire world didn't have AC just a few decades ago and most people slept fine.
If in less than a century of introducing a tech your body becomes so dependant to it it impairs a critical body function if you don't have it, yes, it's a handicap.
Actually people often didn't sleep fine at all. Or let's see some evidence that they did because I don't believe you. I know my own grandparents complained about being unable to sleep soundly during the summer when they lived in New York without AC.
Complaining about not sleeping well in the middle of a hot summer is very different from not being able to sleep at all in the middle of spring without an AC.
It's pretty rare for our nighttime lows to be above 72, even in the Summer, and I live in a fairly hot part of the US (though not the South proper). Even when it's in the high 90s or low 100s during the day, which is typically only a few weeks a year, usually it still gets down to 75-78 at night. We're in the high-80s this week and nighttime lows will be as low as 58F.
Spring nighttime temps are more like 35-55.
The main trouble's the damn humidity. A very-humid 72 still feels gross. And maybe I could sleep like a baby on a night when it gets down to 60, but if that's a spring or summer night I'll wake up nasty and covered in sweat unless I've got some serious dehumidification going (that's what happens when I go camping—might be cold enough to sleep well, but unless it's Winter or late Fall the high humidity still has unpleasant effects). Plus you get mildew and mold problems if you let a modern, very-sealed-up (so, efficient for AC) house get very humid too often, so it's better to just dehumidify with the AC even if the outdoor temp matches what I'd like it to be indoors.
Well, another way I can sleep OK in most any condition (short of becoming badly sleep-deprived) is to get a ton of physical activity during the day. Wear myself right the hell out, so I'm dead-tired by sundown. I bet physical activity levels were way, way higher pre-AC, too.
Not sure about this, I'm 110 kg (242 pounds), and I sleep fine with temps up to 30C (86F). Higher than that is less comfortable, but not to the point of not sleeping. It starts to suck above 35.
I think it's more a about if you have lived with AC most of your life or not.
While being fat does mean I get more heat, I have witnessed drastic differences in body temperature adaptation that are independant of the weight of the person. Your ability to change your blood vessels dilatation, produce sweat, and work out your mitochondrias probably plays a big role, and I would imagine they are worse when you are overweight, and better if you lived in Africa or Canada.
But it does point out one critical point: if you start using the whole ecosystem because of convenience, you may end up reliying on MS Codespace, and therefore lock yourself in.
The solution seems simple to me: don't put your entire stack in codespace. Make sure you can easily use your whole stack on your own computer, and migrate easily.
Autokey is "good enough" but unmaintained and really rough around the edges. I really wish someone picked it up because it's 85% of the way to being a great automation tool.
I've lived there and in the US (and other countries.)
I would say it is best to be poor in Canada, best to be rich in the US. So if you are middle class in Canada, there is a good chance you are living hand to mouth and if you are poor in Canada, you have the luxury of time. From first (well technically second) hand experience, a family of 6 can be on the dole in Canada until the children are grown up after which the parents can go on disability until retirement kicks in.
It's not necessarily a bad way to go, the children of the aforementioned family utilized the free education and healthcare to get a leg up and most of them became middle class. At which point they will see the other side of the coin.
Most of their "advantages" (in "progressive" policy, "free" healthcare etc.) come from the fact that they have us paying for their defence, coupled with having plenty of natural resources and good geography. It is not a country that seeks or bothers to innovate much beyond riding the coattails of the US like a typical large anglosphere nation. In other words, the Australia of North America. Their primary tech sector functions as a cheap outsourcing service for US companies. The national industries are natural resources, real estate, and immigration. Canadians are tremendously proud of their "recent" innovations that are decades if not centuries old. If you look at the typical Canadian cultural propaganda, the country appears to have nothing to show beyond insulin (invented a century ago) and the Canadarm (a gimmick that allows them to pretend to be an aerospace player). They have no launch vehicle to speak of and their leaders happily destroyed their aerospace industry (see Avro Arrow and the whole Bombardier forced sale incident during the Trump era). The primary reason for their high quality of life is easy access and integration with the US market, without which they would be much poorer. They claim to be a middle power but are more like a middling power. By every metric of innovation and technological achievement, they are an embarrassment.
Given where Canada is and what we have, this is our perfect place. We have never needed to be a superpower, and we don't have the population base nor the geography. Our economy is resource based, and most everything centres around that, so more efficiency rather than innovation is needed.
We have a reasonably high quality standard of living and output. Not every nation needs to be a testosterone driven "we're #1".
As a Canadian, I agree. Canada has plenty of natural resources, good geography, powerful military allies, huge trading partners and high quality of life. It sure is tough here!
(But seriously though, you are more or less correct except for the part about us all being "tremendously proud" of our recent innovations. Nobody gives a shit.)
>the Canadarm (a gimmick that allows them to pretend to be an aerospace player)
That name "Canadarm" is related to how Canadians are far more flag-obsessed than Americans. The maple leaf appears in the logo/signage of every single company in Canada, including Canadian subsidiaries of US companies.
If Canada had a full space program of its own, we'd see red-and-white Canashuttles (named Anne Murray, Rush, Gordon Lightfoot, and Margaret Atwood) launching from Cape Canadaveral in Labrador.
Canada used to innovate, a lot- and was a decently recognized power during the world wars. Now.. not so much. I blame it on companies gaining more power, the conservatives privatization national assets leading to higher col and lower standards of living. More and more companies extracting wealth to provide the bare minimum.
Canada of today is not the Canada of last century.for both better and worse.
But that’s just what I think, and what I’ve seen over my life, could be wrong
None of these are counter-examples to what the OP said
> Not all, but the ones that aren't have clear product management of some sort.
That's effectively all of these except maybe ublock.
If you don't have someone trying to sell some portion of your code base, true community efforts not a commercial effort that happens to be OSS, you're probably an infrastructure project.
Interesting. So all of the examples have salaried design and product folks?
Meanwhile there's thousands of volunteering FOSS projects that are engineers only. Do product & design people not have passion projects? Or they do but are for some reason unable to collaborate with engineers (or vice versa)?
It's a complex problem. Design agencies and individual designers are blighted by the spectre of "spec work" [https://www.nospec.com] [https://creativemornings.com/talks/mike-monteiro--2/1]. The tl;dr of it is that business will approach agencies and demand they work on a product for free, of a a cost lower than the wok is worth in an act of good faith for the promise of fully paid work in the future. Except the work rarely comes. The upshot is designers are taught the value of their worth at college/university.
The other problem is the FOSS community itself. See the concurrent post about GIMP [https://news.ycombinator.com/item?id=32624055]. Opinionated devs that either don't see the value of design or having a designer. I know that this isn't true for all projects, but there a bad apples amongst the bigger, more well known projects (GNOME for example) that will spoil it for everyone else. Again, GIMP is a great example of this. As a result, most 'passion projects' lead to designers working on small projects that inspire them, which are rarely software related, ore they look to create something that can provide an income, either as a small second income or as a new business.
Canonical basically supports Ubuntu. (Over and above the Linux kernel and other components many of which are supported by many different companies (and individuals).
I already use spamgourmet (a old great free service in the same features) and despite the fact it has several very different domains, it's rejected sometimes.
Something as high profile as ddg will be flagged very quickly.
The only one that can get away with it is gmail with the "+" aliases, because nobody can afford to reject it.
Incidently, there is a wave of popular python projects in dev python spheres that use types to define validation and serialization: fastapi, typer, etc.
Granted, the python typing system is very limited, and to get complete validation, you'll need more than types as python type hints can't express complex rules.
Also, as the articles mentions, the validation will occur at runtime, it can't in any way make sure the program is valid from mypy checks alone.
Still, it's really nice to define your input data types and contraints in one go.
The Python typing system is limited compared to what exactly? It already has union types, generics, bounded generics, union types, literal types and structural subtyping.
Compare it to Haskell, OCaml and Rust and it looks like a toddler tripping all over itself compared to an adult athlete running at a steady 20km/h.
There are libraries in these languages where you can get a compile error if you make a mistake in an SQL statement.
Also, Python technically has no typing system to speak of so your comment is kind of strange. Not to mention pattern matching, destructuring and other goodies that improve productivity.
> Compare it to Haskell, OCaml and Rust and it looks like a toddler tripping all over itself compared to an adult athlete running at a steady 20km/h.
Well that is a pretty tall order. Those languages probably have the most extensive type systems among the languages with significant use. But even so Python's type system has features that some of them don't have: for example Rust doesn't have structural subtyping.
> Also, Python technically has no typing system to speak of so your comment is kind of strange.
Python PEPs define the typing annotations and the typing rules for each annotation. That for me counts as a type system, despite the fact that there is not built in typechecker and you can run programs that you didn't type check.
> Not to mention pattern matching, destructuring and other goodies that improve productivity.