skysight-inc/HackerNews huggingface dataset:
Simply tell the city, you need to permit enough housing for all of the people working in this huge new office complex, or Apple will leave Cupertino. Apple is such a large company that they pay a major chunk of Cupertino's tax revenues, so they would have a lot of negotiating leverage.
Come on, what kind of utopia are you living in?

Apple's core business is not environment protection, it's development of technology and applications for that tech.

That they're using the vehicle that is Apple to push for green energy is remarkable, putting pressure on the other giants. But this kind of expectation, that they should move away from the Mecka of tech devs. in order to push the envelope further would only lessen the net impact on their environmental work..
> Replacing a state machine with callbacks... something something something you're gonna have a bad time

Having written quite a few networking systems, I fully agree. Especially if it's coupled in this text with "replacing a single-threaded state-machine" with "a multithreaded system, which uses callbacks". IMHO the latter is almost guaranteed a recipe for all kinds of multithreading issues, from race-conditions over deadlock to memory issues. And even if the author of the library gets it right, the issues are often at library user level (didn't expect where the callback is executed and accessed their data without necessary synchronization).

The described model of nanopb sounds very sane compared to that. Pure multithreaded systems without callbacks (like in Go) also work reasonably well. But even those do not work without state-machines in all situations. In all cases where state is manipulated by more than one code-path it's mostly the most reasonable thing to handle this in some kind of state-machine which runs on a single thread, instead of trying to fight it with dozens of fine-grained locks. And just as an example: The HTTP2 implementation in Go uses a state-machine which runs on a goroutine per connection. And user code, frame reader and frame writer code communicate via messaging with that state-machine.
Huh, have to say I'm a bit embarrassed I didn't look that up myself. Thanks for taking the time.
Second Mover Advantage is as valuable as First Mover Advantage.

> it's cheaper and easier to let somebody else prove the market and then just come in and crush everybody.

before there is a dominant player

WRT to your Apple and MP3 market, Microsoft tried the same thing with it's Zune, and failed miserably.
In transit? Unless you know why you need something else - just use TLS. If you get to choose (as in - do not need to support WinXP/IE6/Android versions < 4.4) - select TLS1.2 with "safe/modern" cyphers.

Read the "website security" and "client server application security" sections of this and choose the advice closest to your project needs:

http://latacora.singles/2018/04/03/cryptographic-right-answe...

and the discussion of that from last week:

https://news.ycombinator.com/item?id=16748400

The great advice there is "Let AWS AELB handle it for you".
They should have kept RAID behind yellow tape for years to come. There's just too many problems that can bite you once a physical disk fails and you really need that RAID to recover.
Isn't this the same problem with a VC? The funds might like you now, but watch those ride numbers drop a bit and suddenly folks want ridiculous terms and you don't have many options. I would bet that getting $10m a year in the budget for a few years is no sweat at Uber...they had gross revenue of $37B in 2017. I realize they are trying to cut that, but increasing engagement in already profitable cities might have a material impact in the other direction.
Cigarette companies would disagree. The goal, as always, is the maximum extraction of short to medium term extraction of revenue. So long as you're not immediately killing your customers off, profits often greatly exceed costs.

And actually that part about not even immediately killing them off is not entirely true. Check out the 'pinto memo.' [1] When Ford was manufacturing the Pinto they discovered a critical flaw with the vehicle that could cause the gas tank to explode in rear end impacts, resulting in grievous injury or death. It would have cost about $10/car to fix the problem, but in an analysis - the 'pinto memo' - they discovered that it would cost less just to settle the cases of injury and death. They chose to not spend that $10/car and hundreds of people did end up burning to death because of it.

Fords' latest revenue numbers were $157 billion. Phillip Morris' latest revenue figures were $78 billion. It's for these reasons that I think things like consumer choice and information are critical. Genetically engineered foodstuffs are not inherently good or bad. Any given invention can be good or bad. This decision by the FDA, paired with their adamant stance against any sort of labeling, means they're forcing customers to simply take it on faith that companies like Monsanto have the customers' best interests in mind, even when doing otherwise could potentially be more beneficial for Monsanto.

And now finally to top all of this we also have regulatory capture. Obama created a special position new head role at the FDA, which he half jokingly referred to as the 'Czar of Foods'. He then appointed one Michael R. Taylor [2] to it. Taylor is former vice president lawyer and lobbyist for Monsanto whose legal career was pinned by a case in which he argued that companies ought be allowed to add at least a small amount of carcinogenic chemicals to processed foods. This capture goes well beyond corruption. You, indirectly, had Monsanto regulating Monsanto.

[1] - https://www.motherjones.com/politics/1977/09/pinto-madness/

[2] - https://en.wikipedia.org/wiki/Michael_R._Taylor
Apple has free shuttles to pick people up. There are 4 large apartment buildings recently constructed near the new office. Most people don't work in Cupertino. Lastly, many people can telecommute if they want to.

Apple is not perfect, but the energy Tim puts in making this stuff happens is beyond marketing desire.
My experience..the older you get, the more willing you are to give up income for freedom.

Happy to trade my nice house and cars to get a lower monthly cost basis. That then allows me to take a lower stress, lower hours, but lower salary job.

I guess it's as simple as ageing makes your non-work time seem more valuable.

"Very few sit on their deathbed wishing they spent more time at work"
You want someone who is a native English speaker to go through and fix all your copy.

You don't want nonsense like:

"Shieldfy Monitor all requests and Monitor your code to see how it react. When spot attack ,"
An April Apology – LineageOS
Oman Air appoints Paul Starrs as new chief commercial officer – Aviation
I would call it : prepare for retirement.

Reduce cost. ( Change house / Appartement)

Reduce working hours ( don't need to be drastic)

Get a hobby! ( Make sure it is one with social interactions)

Look for a position you like. With even less working hours. For example 40.

Prepare for retirement with a nice hobby. New friends and stress free environment.
(deleting)
Yeah I'm with you on the helmet laws. I'm not ok with the selective enforcement. If they cause more harm than good we should repeal the law.

When I took the MSF class there was talk of repealing the motorcycle helmet law for similar reasons. Not sure how I feel about that. It apparently came with an automatic DNR provision if you crash without a helmet.
I've never once seen it help and I've moderated forums since the 90s.

People used to put up FAQs and just link those. Now it's like the direction of the conversation is supposed to be decided before even talking and there's no concept of dialog or discussion which is where all of the interactions that were interesting to me happened.
https://news.ycombinator.com/item?id=16795089
Yes, I'm experimenting with it. Basically, I work many hours on work that I love, but that leaves me few opportunities for my own adventures on the weekends since I also have a farm to tend to. I've currently committed a few thousand dollars to see how I feel about this as an expense. My junior adventurer is currently scouting three zoos to get a sense of which is best, and what animals are like, and also what times works for which animals.

Either I could go on all three, or I could pick one. Well, I could do a bunch of research, or I could delegate.

What I may end up doing is funding many of these expeditions that are all within two hours of me, and then put them in a community blog.

If this works out, then I would then do the same thing for local farms and steal ideas and do interviews to publish.
Original author of zmq/nanomsg here.

After all those years dealing with the problem of implementing network protocols I believe that this entire tangle of problems exists because we are dealing with something like 35 years of legacy in two different but subtly interconnected areas: concurrency/parallelism and network programming APIs.

The area of concurrency/parallelism started quite reasonably with the idea of processes. But then, at some point, people felt that processes are too heavy-weight and introduced threads (I'm still trying to find out who the culprit is, but it looks like they've covered their tracks well.) When even threads became too heavy-weight people turned to all kinds of callback-driven architectures, state-machine-driven architectures, coroutines, goroutines etc. Now we have all of those gand we are supposed to make them work together flawlessly, which is a doomed enterprise from the beginning.

At the side of network programming, BSD sockets (introduced in 1983) are the only common ground we have. They are long past their expiry date, they don't adapt to many use cases, but there's no alternative. There are more modern APIs there, but, AFAICS, none of them provides enough added value of top to become the new universal standard.

It should be also said that creation of new universal APIs is hindered by a host of weird network protocol designs out there in the wild. The API designer faces a dilemma: either they go for sane API and rule at least some weird protocols out or they try to support everything and end up with one mess of an API. Not a palatable choice to make.

Then there's the area where the two problems about interact. Originally, you were supposed to listen for incoming TCP connections, fork a new process for each one and access the socket using simple single-threaded program with no state machines, using only blocking calls. Today, you are supposed to have a pool of worker threads, listen on file descriptors using poll/epoll/kqueue, then schedule the work to the worker pool by hand. This raises the complexity of any network protocol implementation by couple of orders of magnitude. Also, you get a lot of corner cases, undefined behaviour, especially at shutdown, weird performance characteristics and I am not even speaking of the increased attack surface.

All in all, it's a miracle that with the tools we have we are able to write any network applications at all.

These days I am working on attacking the issue on both fronts. On the concurrency side it's http://libdill.org -- esentially not very interesting, just an reimplementation of goroutines for C, however, what's worth looking at is the idea of "structured concurrency", a system of managing the lifetimes of coroutines in a systemic manner: http://libdill.org/structured-concurrency.html

On the other front, the network programming, I am trying to put together a proposal for revamp of BSD socket API. The goal is to make it possible to layer many protocols on top of each other as well as one alongside the other. It's a work in progress, so take it with a grain of salt: https://raw.githubusercontent.com/sustrik/dsock/master/rfc/s...
I am thinking of turning it into a summer internship for people that work on my farm during the winter.
In 2009 I left my well-paying job at Google to start a startup. I wasn't terribly unhappy at Google - I just didn't want to spend my whole life there, so it seemed like a good time to do something else. Over the next year and a half or so, that startup fizzled.

Psychologically that point of failure felt pretty bad. But it seemed pretty clear that I would be able to come back on the job market in a fine situation. Employers seemed to consider a year working on a startup as either a neutral or a positive item on my resume. And I had certainly learned a lot more about many different things than I would have in a few more years at Google.

Anyway, I felt like I had more fun working at the startup, and since my fizzled startup was actually able to pay me a bit I still had decent savings, so I did another startup. Investors thought the experience at the previous failed startup was a positive, and the experience from the first failed one really seemed like it was helpful to me too.

For you, if you have a high paying job at a FANG company and had prestigious positions in other companies then you are a pretty competent person. You are going to be able to find a job that pays you well enough to live a good lifestyle, even if you take some time on a failed venture, and even if you move to a different part of the country. You don't need to be afraid of a negative outcome.

You only have one life to live. Are you going to spend the rest of it in a well-paying job that you hate? Knowing that it might have worked out better if you had been willing to take a little risk?

TLDR Do it!
To that point, all user submitted content has a new and unseen hash, and could become executable in the face of a zero day in otherwise trusted code that is processing it. This is equally true of web applications and Excel attachments to emails.

People who think the top level poster’s approach to security is sufficient are gravely mistaken.
Leap Motion's Project North Star could help solve the missing link in AR
ODNS: Oblivious DNS
The problem you face is pretty simple, your opportunity costs are just too high:

The probability that you create a company as a first-time founder that generates $500k/yr or $42k/month is...

- in 12 months ultra low

- in 24 months super low

- in 36 months low

And being a founder lacking success over a period of many months or years might be much worse than what you experience now. You would learn a lot though. But I doubt that your mental health would be better.
> My question is: has anyone here, in a similar situation, done something like this? And if your company failed, have you been able to come back to the market in a good situation?

Not first hand but I know two folks who were in senior positions in a high paying job (one product head and one VP of marketing) who quit their high paying jobs to start their own companies. One of them failed and the person is now the CEO of another well funded company. The other one is doing fine and got an investment from a good investor.

My personal opinion is that if you are able to get a gig that pays 500k at one of the FANG companies you should have no problem getting a job back if your company fails.
Apple has an entire department dedicated to incentivizing employees to use environmentally-friendly alternative commute methods: shuttles from the surrounding cities, shuttles within campus, bikes on campus, rental cars to lessen the need to own one, subsidies for public transportation, and for those who still drive, plentiful EV charging spots.
> I suppose the reason NSA was delaying was they had to develop a workaround for the encryption

No. Their primary purpose was never to protect anybody else but their own operations (the concept "Nobody but us" is older and broader than Wikipedia currently knows https://en.wikipedia.org/wiki/NOBUS ) especially not "common citizens". The NSA is mainly a military institution. Had they been able to get by with nobody being allowed to use crypto but they, they would have done that and continue doing.

Bonus: this is directly from the NSA:

https://www.nsa.gov/resources/everyone/digital-media-center/...

Covered here:

https://www.dailydot.com/layer8/cryptokids-nsa-foia/
If you live in IL, check out Han's System. They sort of have the same look and feel as wierdstuff warehouse.
The housing stock here is too low to not just hold on. There’s no guarantee you’ll get another desirable place if you sell, unless it’s for an upzone in which case you can move up from developer money.
I am considering it right now for exactly the same reason. I'm almost your age, but I don't have a family. I don't have anywhere near your savings but I've done this once before with almost nothing, and I didn't have any problem coming back to the job market after my multi-year "hiatus" when I ran my own company. I even took a multi-month "sabbatical" before returning to the job market to travel and party and be a slob and pursue my own interests (with basically no money), so there's a big hole in my work history. But nobody seemed to care except for a couple of companies which I wouldn't have enjoyed working at anyway. But I'll tell you the one thing: yolo.
Monday, April 9, 2018 the perils of letting your computer dial the phone
That one is a much better source to start with, IMO.
What you are saying is correct, with a few nuances:

- as other commenters have pointed out, many employees who live more than a short drive from the office use shuttles. Not as good as public transit civically, but comparable ecologically.

- the vast majority of Apple’s 140k or so employees work in Apple Stores. Your post remains correct, but it is a fairly small number of employees who are operating in the dysfunctional urban quagmire that is the Bay Area.
Serious question: What's the business value case for not using Elm?
Perhaps Americans are just confident that if these things start happening there will be ample opportunity to implement legislative fixes.

I mean c'mon...."Refused entry into establishments"? Unless the Civil Rights Act of 1964 somehow gets repealed I don't see this as very likely.
The problem is, radar returns decline with the 4th power of distance - so if you can detect a 1m square at 100km, you can detect a 1cm square at 10km and a 0.1mm square at 1km. Yeah, a marble is fantastic in comparison to a barn door - but that 4th power cuts both ways.
It certainly did, but after all it was just a fun spare time project.
I guess there would be a lot of interesting software to reverse engineer; I am always open to suggestions that are able to extend my knowledge. And well, if you mean it in context of a job... I don't have any experience regarding the job market yet, but that also sounds quite striking :)
Well they also chose not to put the headquarters in a pot third world country, so let’s blame them for world hunger.
Thank you for the response. Remote work not an option even though it's FANG (trust me I tried), college fund already established and enough money in it, not mentioned in post.
Ahh, I missed the "without degree" part of the question. It looks like it's strongly recommended, certainly the Australian Germany Embassy page suggests you need a degree:

http://www.australien.diplo.de/Vertretung/australien/en/03/V...

But it looks like there are also exemptions for "bottleneck" industries that urgently require specialists, and Software Development and Programming are currently listed. (Some of the commercial sites suggest 5 years of commercial experience will also qualify.) You'll note that IT also gets a discount on the minimum required salary to qualify.

Try the Make It In Germany website, which is an official government site and links out to some of the exemption documents:

http://www.make-it-in-germany.com/en

Oh, and also note that Canadians (like Australians & Americans) get a favored status. Note at the bottom of that first link that Canadians can apply for a Blue Card after arriving in Germany. So maybe you could try applying for the Working Holiday visa (easier to get), and once you're over there look into converting your visa to the Blue Card.
I have driven a few. For what I need my car for, I prefer my BMW 535. I don’t race. 99% of my driving is 65 mph or less. I also have a wife and a kid, so a de-facto 2-seater is out of the question even if I did love it.
The maid cafes aren't that interesting. Agree with everything else. Most of the shops now are manned by Immigrants from Nepal.
I live in a small town in New Mexico. My ~1200 sq. ft. house cost $95k. My wife and I lived comfortably here, the two of us, on essentially $70k/year for the first four years of our marriage. Since then, the money has gone up, we have two kids and raising two kids here has been fairly inexpensive too.

Across most of the country, you could take an 80% pay cut and still be considered rich by 90% of the people around you.

Life is different out here but I think you have enough money, and you know it, and it isn't making you happy or you wouldn't be contemplating your move. So fuck it, what have you got to lose? You'll probably find that the abundance of time and massive reduction in stress is adequate compensation.
Since a game typically doesn't have a first mover advantage nor suffer from a "time is of the essence" problem, and given your opportunity cost of income, you should consider outsourcing the development of your game to a cheaper labor market. With your technical know how, you can supervise your team to your liking, launch the game, and see how it goes. While you still might be unhappy at work, this will preserve more of your savings than quitting, and give you a more viable option to quit in the future.
That's great. Next, focus on making products that can be repaired and upgraded by end-users for an extended period of time. Electronics manufacturing is resource intensive (beyond just energy) and a significant source of pollution (beyond CO_2 emissions). Recycling electronics is also resource intensive and does produce waste. If Apple tried to extend the average useful life of its products by just a couple years it would make a big difference.
Have you been to Cupertino? I wouldn't want to live there. And if I worked there, I wouldn't want to live within 1 mile of my office. Even if there were housing, many people would prefer to live elsewhere.

Apple also cannot threaten to leave the city every time they want something. How dystopian it would be to have a multibillion dollar company extorting City Hall like that.
I'm not sure, but I'm not deeply familiar with this part of the code. In general, I think it's good to be able to induce all of the failure cases for all of the error handling code that's being added.

This can be time-consuming work, but I would argue that this is the file system -- anything less is an unacceptable risk. This quote from my boss comes to mind:

Remember: you are (or should be!) always empowered as an engineer to take more time to test your work. -- http://dtrace.org/blogs/bmc/2015/09/03/software-immaculate-f...
Apple threaten to leave their new spaceship? A comically obvious bluff?
Well, I don't know Erlang (yet) and AFAIK, Erlang is rather focused on fail tolerance, high availability etc., which wasn't really a concern when I started the project. Python and NodeJS are quite good for quickly trying out ideas though.
To support your point, e-bikes are fast. They go like 25km/h, and they often beat cars in speed as they do not get stuck in traffic.