bla2

(it's "crescendo", an Italian word I believe)

When I was 19, I did use this option a few times. Success rate was about 50%, not awesome.

Or older parents == better circumstances for kid, and better chances for kid with autism to be successful.

I get what you're saying, but I'm not sure if planning trips to the other side of the globe qualifies as "daily use" either :-)

I think it's neat to see that the route is along a great circle -- that wasn't clear at all before this change.

Remember the link recently that predicted Tesla shorts are about to unleash lots of negative press to make money? That's part of that.

Edit: https://news.ycombinator.com/item?id=17521946

How is Android funded by advertising? The google services running on it are funded by advertising, but you don't have to use those.

It's so weird to me that Google gets all this flack when they made Android open source, while Apple gets none of it and kept iOS closed source and super locked down.

Given that, it's somewhat understandable that they're moving to a more closed model, sad as it is.

Sure, electron apps get this very wrong. App makers are free to write software that prioritizes something else than being a good Mac app. But Apple's own apps should be good Mac apps.

Consistent UI, simple and fast built-in apps for common tasks, good unix subsystem, fast file system, pretty text rendering, system libraries that make it fairly easy to write good native apps, etc.

macOS has all this, but it had all this for a while. There are so many good things in it. Preview.app is great -- it even lets you do simple PDF editing, while being fast, reliable, and easy to use. CoreGraphics does beautiful drawing, reasonably fast, leading e.g. to gnuplot having pretty antiailased graphs on macOS but not elsewhere (via Aquaterm -- this might be outdated information though, haven't used it in a while). The find pasteboard is clever and convenient, as are document icons -- and dragging them into Terminal even inserts the path to the document. There are so many well-thought-out details on macOS.

I don't care about iCloud integration, sync with iOS, Springboard, tabs in Finder or Maps, Siri, iMessage integration (I don't use an iPhone). The new Photos app doesn't honor mac system conventions. The Mac App Store is repulsive to me in its philosophy, and its implementation has been inept. I miss the HIG. Airpods are cool, but connecting them with my MBP works only haphazardly as you'd expect of regular old Bluetooth headphones, not as you'd expect of Apple hardware talking to Apple hardware.

I could go on for much longer, but I'll stop now :-)

For Macs, in my opinion they used to build high quality products, but they're losing their lead. macOS hasn't improved in ways that matter to me in years and some things got worse. The hardware used to be untouchably good, but the new MacBook Pros are worse for me than the original retina MacBook Pro I still use -- performance hasn't improved much (the latest upgrade might have changed that) and keyboard, ports, power connector all got worse.

https://security.googleblog.com/2018/07/mitigating-spectre-w... says that they've been working on site isolation (one process per domain, so potentially several per tab) for many years. chrome has been multiprocess (process per tab) since day one and it took other browsers years to catch up with being multiprocess. So if other browsers decide to pursue this approach, it'll likely take them years as well. So 3 doesn't seem super unlikely to me :-/

The nytimes publishes an article like this every few months. It's not like they're impartial in this area -- tech took news's audience. Don't give this attention it doesn't deserve.

> I don't ever want to have to fight so hard for a PEP and find that so many people despise my decisions.

Leading a large open source project must be terrible in this age of constant outrage :-(

Blink (the HTML engine) is still going to push the same drawing commands to all the backends. Winding rule order stuff might be different if a backend is buggy, but things like this shouldn't be different.

Meh, to look outside your filter bubble you can just open google in an incognito window. I do that from time to time, and for web search, filter bubbles don't have much of an impact imho. I mostly search for technical things though.

I don't get why people recommend DDG. It's mostly a different skin on bing search results. Why is relying on bing better than relying on google? If DDG had its own engine, I could see the "they're the small underdog focused solely on this" angle, but as-is, you have the choice of Microsoft or Google.

BEAM (the Erlang VM) + Erlang, Elixir, hipe-llvm seems like a good addition to the graph.

Almost all compilers producing machine code can instead also produce assembly. In fact, many compilers internally produce assembly and then run an assembler to produce machine code. So the Assembly node is missing many in arrows.

Thanks for sharing!

> it wasn’t until I was 30 that my wife and I had enough for a downpayment for a house.

Not sure if that's meant to evoke sympathy, but to me that sounds extremely entitled. I'd be grateful if I had a house at 30.

Is it common for people around you to feel they deserve to own a house?

The "What problems do Bitcode introduce?" section is a bit silly too: Production binaries you ship don't contain bitcode. For store apps, the app store will strip it, for non-store apps you strip it yourself. It's like shipping your app with debug info, that also makes reversing easier.

Finally, the bitcode_retriever code is fine, but you could get the same functionality with 3 lines of shell (`otool -l mybinary | grep -A 4 __bitcode` to get the part of the file containing bitcode and then use `dd` to extract that).

I only skimmed, but I found several mistakes. With bitcode, you still get one bitcode slice per arch since LLVM bitcode isn't platform-independent. Pointers are for example sized differently, which causes the same C file to compile to different bitcode; preprocessor macros are different, which also causes the same C file to compile to different bitcode; and so on. App thinning can be implemented without bitcode, so that whole "What problems Apple’s Bitcode aims to solve?" section is bogus.

Weird it lists Firefox but not Chromium. Firefox on Windows is great, but on Mac it's just ok.

A simple build system fits the tools listed here and covers graphs. An NFA regex matcher would cover it too.

The usual play is "when behind, join up with others and promote openness". That's what Google and Microsoft are doing vs AWS in cloud, its what browsers did during IE 6.0's reign, it's what Apple did with it's OS kernel, and so on.

It admittedly doesn't seem like a great fit for current Apple.

This surprised me at first:

> having difficult conversations with individuals is never fun

But apparently "difficult conversations" is a Valley euphemism for "firing people" and doesn't mean "discussing difficult engineering problems".

I am pretty disillusioned with them too, and they do push an agenda in many areas (pro-military, anti-tech, etc). I loathe their opinion pages, they're a weird mix of bland and constantly pseudo-outraged. But I still like lots of stuff they create and a subscription isn't super expensive, so paying seems like the right thing to me personally. I'm just reading a newspaper, not looking for someone to marry. (I wouldn't want to marry someone who always agrees with me either, come to think of it.)

A bit easier but also more expensive than the other options mentioned: Pay for a NY times subscription.

> GTK+ 3 stopped changing in drastic ways, which was well-received, and we are finally seeing applications moving from GTK+ 2.

It's almost as if devs care more about stable APIs than about endless churn for minor features!

I don't think that's true. You can have a profile per window, the windows live in the same process.