387 karma · joined February 5, 2020
- 2 USB-C (1 of which is used for charging, I'll probably have reason to use the other at some point with increasing USB-C adoption)
- 2 USB-A (1 for a wireless mouse, 1 frequently used for flash drives and whatnot)
- SD (used occasionally - cameras and with an adapter for micro SD in phones)
- RJ-45 (used occasionally, probably more often soon)
- HDMI (used somewhat regularly)
- Headphone jack (also built into the Framework)
So with the Framework I'd be missing out on 3 ports. I could survive with that, but it'd be pretty sub-optimal. Thankfully I shouldn't be in the market for a new laptop for 5+ years, so hopefully Framework will have more options by then.
I'm (very gradually) switching from a 2014 Android phone to a 2017 Android phone, both secondhand. I'd like something that can run Lineage OS (and wasn't entry-level several years ago), but both still manage most of what I need.
Most people I know with Android phones keep them at least 3-4 years. (Off the top of my head: one switched from his Windows phone a couple years ago, another has an old Samsung one with a physical home button.)
Similar with Apple: I know one person who will not give up his 6s until Apple stops supporting it (and only begrudgingly then); I know a number of other people with the 6s, and one with the new SE.
That said, I'm pretty sure all of that comes more from the perspective of money than saving the earth.
Edit: somewhat unrelated, but I hear a lot of people mention how Apple is much better with OS updates. That's true (although Lineage helps, and manufacturers are getting slightly better), but app support for old versions of iOS is horrendous. I almost never see support for more than 2 old versions of iOS, if that. Meanwhile, ~85% of apps run fine on Android 4.4 and half or so get updates, and just about all do on Android 6.
I'm finding two relevant Firefox bug about being more strict than Chrome[1][2], but neither of them seemed to cover this case specifically. I'm considering filing a bug about it, but doing so would link my bugzilla account (full name and whatnot) with my HN account.
[0] https://gpac.github.io/ComplianceWarden-wasm/avif.html [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1689806 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=avif-compliance
I'm not sure if this is an image error or a Firefox issue, I have heard about Chrome being more lenient than spec when loading avif images. I might look into that a little more and maybe file a Firefox bug to see what they think, I'll update here if so.
[0] https://www.mozilla.org/en-US/security/advisories/mfsa2021-3...
And now I'm down the rabbit hole of reading about tuning systems again.
Can you?
That is to say: you can try, but I don't think most people are very good at consciously choosing not to think or worry about something that they know, if that's even possible.
Edit: Actually B♭ minor is the enharmonic equivalent of A♯ minor. IE another case of things in music that are the same but aren't.
Article 6:162 Definition of a ‘tortious act’
- 1. A person who commits a tortious act (unlawful act) against another person that can be attributed to him, must repair the damage that this other person has suffered as a result thereof.
- 2. As a tortious act is regarded a violation of someone else’s right (entitlement) and an act or omission in violation of a duty imposed by law or of what according to unwritten law has to be regarded as proper social conduct, always as far as there was no justification for this behaviour.
- 3. A tortious act can be attributed to the tortfeasor [the person committing the tortious act] if it results from his fault or from a cause for which he is accountable by virtue of law or generally accepted principles (common opinion).
https://github.com/gorhill/uBlock/commit/8cd2a1d263a96421487...
[0] https://github.com/slymax/tablist (links to Chrome and Firefox extensions there)
That said, at least for tracking consistency is more important than accuracy.
Correction: upon further research, this is where 440hz originated. However, it was not the original standard (or where musical notes come from), and I find the history interesting, so I'm going to post it anyway.
Tuning used to be based off of whatever instrument was not easily tunable (the piano or organ), or some other instrument (oboe?) if there was none. For much of musical history tuning was significantly lower than A=440, albeit with a lot more variation; however, it tended to rise[0][1] in order to create a more brilliant-sounding timbre (particularly in larger venues), especially among instrumental pieces. This led to some contention, especially with vocalists who found the increasingly-high notes more and more difficult to sing. There were several efforts to readjust tuning to something more reasonable, but ultimately none of them worked for long. Frequency was actually orignically standardized in Article 282, section 22 of the Treaty of Versailles.[2] This may not make a lot of sense at initial glance, but when thinking about it as how good orchestras sound, it does make some sense as an economic policy
This is where I originally messed up, though. The Treaty of Versailles references something else (which I don't have a link for), but which, per [1], standardizes to... 435hz. But again this crept up, and apparently the US and UK did some shenanigans with interpreting it (the UK changed the temperature to get it to 439hz, I haven't found out precisely what the US did), and there was again some debate. Some people gave up and standardized with the UK to 440hz, some stayed at 435, and eventually the ISO did step in and standardized again on 440.
So we may all be breaking international law by tuning to 440hz.
[0] https://en.wikipedia.org/wiki/Concert_pitch#Pitch_inflation
[1] https://www.youtube.com/watch?v=BzznBt8tVnI
[2] https://en.wikisource.org/wiki/Treaty_of_Versailles/Part_X#A...
He doesn't have a pacemaker, but it may not be as unreasonable of a thing as you might assume.
I do think it would be interesting to see it, though.
> Nitpick: it is difficult to take a shower with water in solid form (ice).
Nitpick: having a temperature below zero does not necessarily mean that it is in a solid form; for example, it could be at a high pressure or not have a nucleus to freeze around (supercooling).
[0] https://gitlab.com/The_Quantum_Alpha/the-quantum-ad-list/-/i...
I doubt much work is being done on it, but presumably they at least make sure it works; I mentioned it because a few posts up (edit: you) mention testing (rather than initial design) as the reason why having multiple designs is so difficult.
> The mobile vs desktop versions you posted are likely the same codebase with minimal (if any) differences....
It's entirely possible that they're derived from a similar codebase at some point, but what reaches the browser is significantly different - it's barely responsive, based on user-agent, and appears to be significantly different obfuscated blobs of HTML, CSS, and JS.
Desktop (plain HTML): https://mail.google.com/mail/u/0/h/