Should you not rather train yourself not to be distracted by the noise like you train yourself not to be distracted by notifications?
202 karma · joined August 23, 2016
Should you not rather train yourself not to be distracted by the noise like you train yourself not to be distracted by notifications?
Daisywheels were common, IIRC.
They have a long history of refusing to pay bug bounties.
They did Apple a solid, but not in accordance with the precise terms as laid out by Apple, so it's perfectly justified for Apple to take the researcher's work for nothing?
Did they start out with German table names and decide to give new tables English names at some point?
If it isn't WindowServer losing its mind, it's some other buggy system daemon. Apple simply does not do stable versions of macOS any more.
https://en.m.wikipedia.org/wiki/Antitrust_cases_against_Goog...
Anchor your explanation in something with actual practical use.
It's why so many mathematicians are so shit at explaining maths to laypeople. They don't understand that regular people don't give a shit about numbers. They're just a means to an end.
Explaining how to turn numbers into more numbers doesn't land with people who dgaf about numbers.
You need to show how something is useful.
It strikes me as the mother of all spaghetti code. Is it even possible to meaningfully look at parts of the human body in isolation?
Maybe it's just because I'm old and remember the clusterfuck when the EU decided one TV company couldn't hold the rights to all the football matches.
(They divvy the rights up in such a way that you can't see a single competition on just one service, let alone just one team's matches.)
These ISPs absolutely should be forced to open their infrastructure to other providers, like in Europe, and for the same reasons.
That's the heart of it, isn't it? It's challenging.
At the core of modern web development is the attitude that developer convenience trumps all.
The software is free after all. (The thousands you pay in bandwidth and hardware upgrade costs to keep running their bloatware doesn't count because none of that goes to the web developer, and is therefore irrelevant in their it's-all-about-me worldview.)
WTFing at shell scripts is normal.
From what I've read, the payload isn't stored in the archive, but rather the test file itself is a sandwich of xz data and payload: There are 1024 bytes of xz archive, N bytes of payload, another 1024 of xz, etc.
Like what? As you note, mixing tabs and spaces is now an error.
I've never understood the objection to semantic whitespace. Complaining about having to indent code correctly strikes me as being akin to complaining about having to pee in the toilet instead of the bathtub.
You left out a very important qualifier: in the middle of a code line
The chances of someone accidentally fat-fingering a keyboard layout switch, typing one character, then switching back again without noticing while typing a line of code are very slight indeed.
Plus the fact that you'd need to speak a language written in that alphabet to have a plausible reason for having the keyboard layout enabled in the first place.
It's an online service, isn't it? Not a local application.
There's nothing curl can do about it.
The reason for wanting such notifications in the first place is because new owners often do dodgy things, and a company that specialises in buying up popular extensions and cramming them full of spyware typically doesn't want you to know about the change of ownership.
So extension authors can't be relied upon to provide this feature. The ones you particularly want to know about go out of their way to hide their involvement.
Definitely. Americans are very quick to prioritise the needs of businesses over those of people.
In Europe, the people come first.
Who can't afford to travel 100km?
Maybe for you, international travel means hopping on a plane.
Most Europeans live closer to another country than to most of their own.
How is that "insane"?
It's pretty clear that Apple Music hadn't gone rogue.
I use FF, too, but I can see why someone wouldn't want to: It's just not a very good Mac app. Weird windowing and focus bugs in fullscreen mode. Keyboard shortcuts that randomly stop working. Zero scripting capabilities (it used to have the bare minimum, but Mozilla bizarrely ripped it out), and just poor integration in general. My system-wide shortcuts — the ones that are so important I've added them to every context menu on the system? That's a big nope because FF devs apparently think showing poxy extension icons is more important.
Google had the good sense to copy Safari's keyboard shortcuts in Chrome. Mozilla didn't.
The bookmark manager is straight out of Windows 95. Awful UX.
I do like Firefox, but it's just not up to snuff on macOS.
Stagnated? It's going rapidly backwards.
Modern software development is such dogshit, my 2008 Mac Pro that can encode MP3s at 80x can't even run a damn music player anymore.
The player doesn't do anything new, of course. It was just built in a ridiculous fashion by developers who prioritise their own convenience over everything else.
As a basic example, `lstrip()` and `rstrip()` trim whitespace by default, but can also remove any characters you'd like from the end(s) of your string.
You'd need to code that up yourself in JS. Happens quite a lot.
APIs (for SPAs), OpenGraph/LD+JSON data in <head>, and data- attributes with proper data in them (e.g. a timestamp vs "just now" in the text for the human).
Scraping is a lot easier than it used to be.