skysight-inc/HackerNews huggingface dataset:
I think the choice to adopt an SPA or not should be driven primarily by the project requirements. Are you mostly going to be serving up long-form documents or presenting users with tradition forms, or are you building something that needs to feel more like an "app" that is highly responsive to user interaction. I would choose an SPA only if the latter were true.

You essentially have two problems: 1) how to make common code available for reuse across what is essentially two separate websites/apps and 2) how to make it so that front-end focused developers and backend focused developers can work effectively together.

I don't think that either problem is best solved by adopting an SPA if you would not otherwise be driven to do so. Problem 1 can be solved in a lot of ways. You can build a set of common services into a library used by both apps, for example. This allows you to isolate and reuse common functionality without the overhead of an HTTP service layer if you don't really need it.

Problem 2 I would say winds up being more about both teams getting things "the way they want to do it" rather than strictly about difficulty learning. I've yet to see a server template system that would present much of a problem to a front-end focused person. The real problem is how can their toolchain, which may include things like transpilation, sass compilation, and a separate test runner, be integrated into the backend build process and framework. A lot of backend frameworks are somewhat opinionated about how these things happen, but there are ways to integrate just about anything with anything else.

Anyway, it really just boils down to understanding how your app would be best served based on how it needs to work, and doing it that way. There is a good bit on the trade-offs between the two linked below [1], although its author is biased towards "shared" front-end/back-end frameworks like meteor, and I don't agree with some of the conclusions.

[1] https://www.quora.com/What-are-the-tradeoffs-of-client-side-...
Just to play devil's advocate - as a founder, I've both made money and lost money. Some of my ventures were self-funded to failure and I had to write off hundreds of thousands of dollars. I repeatedly remind my family that my worst case is not a year of unemployment with zero income but rather a year of business failure with a painful amount of red ink. One or two experiences like that and you become very aware of the line between people willing to risk their time and money vs. people only willing to risk their time. If you really want to make the leap from employee to co-founder, you can probably do it - but need to bring money to the table or at least offer to work for much less than market (or even zero) in salary, which good founders will typically respect and overvalue since it reflects extreme personal commitment to them and/or the business.
The book did not feature parthenogenesis. It featured protogyny. Some individual females became male and bred with the individuals that remained female.

This has been observed in West African common reed frogs (Hyperolius viridiflavus), as a result of population pressure. If the pond is a taco fest, some of the frogs bring sausage.

This is actually more common in fish than in amphibians, but the book used amphibian DNA.
Heh... The irony of using Tim Berners-Lee's biggest regret - the :// - as the main logo element is quite amusing. https://bits.blogs.nytimes.com/2009/10/12/the-webs-inventor-...
If you were actually in a state of ketosis for 3 weeks your body would have mostly adapted to it. It takes a couple days of carb refeeding for insulin sensitivity to return to normal.

http://high-fat-nutrition.blogspot.com/2007/10/physiological... < blog on the topic (sorry to link this blog again, he really has some good posts on topics like this with research linked in)
Yes the tea recommendation is flat out wrong.
Meteor should be on the list of Node.js frameworks (absent a more appropriate category).
Twitter used to be the biggest SMS sender in United States. Much larger than Twilio, even bigger than operators like Verizon and AT&T. Infrastructure that came from Cloudhopper acquisition with continuous care and improvement gave Twitter a reliable and super cost effective _world-wide_ SMS delivery platform.

(I was an employee 2012–2016)
Hangry is a deliberate portmanteau of hungry and angry
> If the law requires a driver travelling at the legal speed limit to stay out of the "passing lane" so that other drivers can pass, this would imply that the law condones speeding, since only a driver moving faster than the legal speed limit can make use of that lane.

That's not how it works. The law is "stay right except to pass". This is true regardless of speed. Speeding is still illegal in any lane. The "stay right" rule is about not obstructing the flow of traffic, it has nothing to do with the posted speed limit.

e: To clarify many people drive below the speed limit, in this case it is possible to pass them in a lane to the left without exceeding the speed limit.
I agree that many places work that way, particularly if they have no idea how much value a dev creates. I don't know if it's 99% or not; that seems high to me, and even at such places, if I go in with proof/truth that I made $500K at my last job, I'm not getting an offer for $510K as a dev...
A lot of genetic algorithms already seed the next generation with copies of the top X fittest individuals, so it's essentially already done.
New Fingerprinting Techniques Identify Users Across Different Browsers, Same PC
A local adversary (in your network) can know that you're establishing a connection to a certain IP in another country, but they cannot know what that particular machine is accessing in turn. [This is my threat model, I use this in public WiFi].

And a remote adversary (who sees your VPS IP) cannot know who is, in turn, connected to that VPS, unless they can extract that information from the VPS provider via court order or hacking. [This is of more concern if you plan to do illegal things or are a dissident].

As always, you must model your threat scenario and proceed accordingly.
Careful - I know that guy (I am that guy). He hardly knows what he's talking about half the time, and for the other half he makes it up as he goes along.

Seriously though, glad you liked it.
That's a lot.
Using threading to handle user requests with Python seems very wrong to me. They might see solid improvement by ditching WSGI and employing a non-blocking solution (like Tornado, aiohttp or Sanic), running on PyPy as multiple instances behind a load balancer.
Untethered – Voice-Driven VR Serial Drama
Easter egg coming soon, maybe?

https://bugzilla.mozilla.org/show_bug.cgi?id=moz%3A%2F%2Fa
And as I keep saying: I don't value those assurances and in fact find them to be a net loss when accounting for breaking changes changes to clients.
"I understand you're only relating your previous misunderstanding but to others reading this, they need to realize that it's unrealistic for employees not to be diluted."

It's only unrealistic because of greed. There's absolutely no valid reason this has to happen.
Ukraine?
It will have to vote on the final agreement at the end of the 2 year negotiation, but May is refusing to have it vote on triggering Article 50, i.e. actual Brexit.
Im reading his book right now (The Case Against Sugar). He has a lot of citations. He's not saying he has no evidence, he's calling out the science being produced as corrupt/bad.
Eich stepped down. There was so much pressure on him from the community that he had no choice. Mozilla isn't beholden to shareholders or profit there goal is more social in nature and they've built their entire marketing and strategy around being the open and democratised internet, Eich had no choice.

Companies like Google shut down projects every day, one of the differences is that Mozilla works in the open and isn't so secretive.

But, I do know former employees and the company overall is a mess, with some teams better than others. People say the same thing about Apple though.
Underneath they're still divisible. AoT is always native machine code. JIT/VM/Bytecode is VM, basically machine code on demand.

Then there's interpreted code which has worked the same way for forever
I think you vastly underestimate the amount of money that was spent on Linux by various vendors. All the major companies in that wanted to sell servers or server related software essentially converged on linux as their platform of choice, since then IBM, RedHat, Google, Intel,... probably poured many billions more into Linux than Microsoft spend on the NT kernel.
The author was most likely talking about a FIDE rating. I think you'll find pretty much every on-line site has people rated well above their FIDE ratings. This is partly because people who pay money to join FIDE and pay money to play in tournaments take it much more seriously.
From the article

> [...] we expect that Crashlytics will become the main crash reporting offering for Firebase [...]

They will be integrating Crashlytics into their core developer offering, Firebase. Looks like if you are just using Fabric's Crashlytics service you will be ok. But there is more room to worry if you are using some of Fabric's other tools.
This kind of looks like a mashup of Reddit with G+'s circles. Which isn't necessarily a bad thing, although if that graphical tree view in "how-lyra-works" is the real UI it looks painful to navigate once it grows past a half-dozen comments.

> As a result, subreddits need to be moderated, which mitigates - but does not always prevent - unpleasant behaviour.

Many subreddits aren't moderated, and many of those work fine regardless. Downvoting is the first line of defence against unpleasantness. (Or the second, with the first being "stay well away from the default subs".) Moderation tends to be more about enforcing house rules over and above basic civility.

> On Reddit, you have no privacy. Your entire post history is visible to anyone.

Is that true of private subreddits too? (Genuine question, I've never had anything to do with them.)
Pretty sure that by inside lane they mean the main traffic lane.

http://dictionary.cambridge.org/us/dictionary/english/inside...

(I made that assumption before noting the .uks in their profile...)
Great color picker for mac os
"Process," is the answer to the question, "how do we get a team of talented engineers to design and implement software together?"

The answer to what should that process be? I'd look to the SWEBOK[0] for an introduction to the state of the art.

As for the question at stake here... let me use the words of someone much smarter than myself:

> Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it. And to make matters worse: complexity sells better.

> Dijkstra (1984) On the nature of Computing Science (EWD896)

If you don't appreciate the true difficulty of programming you're bound to create problems and spend most of the rest of your time debugging them later on. If your chief motivation is to sell a software product or service powered by software then it behooves you to create complexity. It seems more impressive when you can't explain why some component or feature doesn't work in a single sentence. You just want to control that complexity enough so that you can maintain the illusion of order.

If you want to achieve simplicity you have to work at it. It's hard and doesn't come for free. You really have to think. There's no way around that.

[0] https://www.computer.org/web/swebok/index;jsessionid=306e197...
Twitter just lost one of their crown jewels; Fabric is probably the biggest mobile analytics platform out there.
I don't think you understood my point. Lemme put it this way, if govt in France made it a law that you must pay 10% tip to the waiters at the restaurant, do you really think that the waiters would really be 10% richer?

If this were the law, would you not simply consider the cost of dining at a Restaurant to have gone up by 10%? And if that were the case then your eating out behavior would change the same way if restaurants DID raise their prices by 10%.

Since waiters are getting 10% more from the customers, this means restaurant owners will reduce the wages of the waiters by 10% and reduce the prices of the food by 10% (so at the end the waiters end up getting the same amount of salary, it costs the same amount to you to eat at a restaurant and the profit margin of the restaurant owner remains the same).

The fact is, that a company does not (and cannot, even if they wanted to) differentiate between "vacation" part and "salary" part of the employee compensation package. At the end of the day, the vacation costs them money and paying employee salary also costs them money. So when a company decides what compensation package to offer to a candidate.

For instance, if an employee would bring a marginal productivity of $100K in a year, then either they can offer 10% time off (26.1 days off, assuming 261 working days) + 90% in cash, or they can offer 0% in time off and 100% of the salary it would be the same to them.

Technically as the number of vacation time goes up, the cost to the company goes up too (if you took 6 months off, then this means the company might have to get new employees to fill for the remaining six years, which could be expensive).

In your example, you're just valued that much more by your company than your friends are by their companies.
NoSQL's only selling point is you don't need to learn SQL? Hardly true.

Major Oracle shops aren't dumping them for Mongo/Couchbase/... because they're trying to avoid SQL. They do it for scalability, availability, performance, flexibility and more.

I don't see that the facts in the real world back you up here.

Not claiming NoSQL is a panacea. You're definitely making some trade-offs, and in many cases it's just the wrong tech. But it's absurd to say it's happening to avoid a learning curve.
I do not have a single 'this' pointer in my programs. Not a single class/prototype. Imo, that leaves: Bad/no pattern matching support, many operators create statements and not expressions (e.g if/else) but they can be extracted to functions.
Also, relative path imports. This is nuts. But you can use root imports with webpack+TS and the problem is solved.
mutable objects/arrays is annoying. But we have the convention of never doing it, and it's been working for a long time. (https://github.com/AlexGalays/immupdate)
Granted, I would prefer immutable by default for sure.

Do you have other insane JS semantics in mind?

And yeah, F# looks brillant. Just wished it was not a .NET thing. Fable could interest me but it's just like bucklescript/reasonml: there is no momentum, no community, no libs. It would be a big leap of faith to heavily invest in it as an individual.

I generally like the FP approach with imperative escape hatches. Need more performance? Some code is actually more elegant in imperative form? Go for it.
F# can do it, scala can do it too (unfortunately with some crappy java compatibility concerns to deal with)
Hi Austin! We are in beta, and not ocean-boiling. Our plan does not require publishers to agree before they start getting revenue shares in escrow.

That's part of the plan, because it turns out to be hard to get agreements inked and signed. Even at larger scale (we're growing), getting pubs to agree is not easy or quick. As always when bringing up a new protocol, Metcalfe's Law is a pain. So we decouple and start sending money first. Money always helps.

We are talking to publishers from big to small, and we have verified ~120 publishers as domain owners, with 70 already having filed the W-9 or W-8BEN (if overseas) form.
>All this study shows is that the brains are pretty much the same physically. //

Apart from the cutely glossed over 11-12% size difference, which seems like a major physical difference (remember we're ignoring function/structure here and only concerning ourselves with macroscopic physical aspects).

Even when normalised though they found a 2.5% difference. Not huge, but still seems of note.

The set-up is this:

>“Despite the common impression that men and women are profoundly different, large analyses of brain measures are finding far more similarity than difference,” said Lise Eliot, PhD, principal investigator and associate professor of neuroscience at RFU’s Chicago Medical School. (http://www.sciencedirect.com/science/article/pii/S1053811916...) //

Professor Eliot is said to work closely with the study's writers. So, at least in Science Bulletin, and for the department performing the study the macroscopic brain morphology is being used to argue against the idea that men and women are different.

This gets to newspapers as "neuroscientists find mens' and womens' brains identical" and Eliot seems, with her comment, to be encouraging that viewpoint.

The final part of the study abstract:

> it is not accurate to refer to the human amygdala as “sexually dimorphic.” (ibid) //

Presumably they mean except for the 11-12% (+2.5% of that) volume difference which for some reason doesn't count. I guess it's like "men aren't bigger if their trousers are proportionally bigger than women's trousers"??

Your idea has a lot going for it, but you have to remember then that the hardware is not fixed at the point at which hormonal activity starts to have effect. Perhaps the brain hardware is more like a software programmable array that can affect its own continued construction rather than a fixed silicon die. [Probably a terrible analogy].
without an algorithm that determines the order of presentation of content, the service risks putting too much strain on the user to filter content. (which basically undermines the whole point of such a service)

alternatively, a thought provoking youtube video doesn't guarantee meaningful comments; and a meaningful comment doesn't guarantee a meaningful discussion
I mean, you _can_ if you organize your code such that you can. For example, Google's monorepo lets maintainers of a library find all internal usages and fix them. This is one of the benefits Dan Luu notes in http://danluu.com/monorepo/.
Right - the control flow is explicit, and works the same as regular control flow.
I really feel like you're ignoring the substance of most of my comments. Friction is often a factor for people who have the means to do this, but do you understand that many people don't have the means? At the absolute minimum, your friend needed several hundred dollars in the bank, and a resume that included more than high school and minimum wage jobs. I think you're taking this for granted, but it's nearly insurmountable for, again, millions of people in America.
Keep in mind that for many of us, including sciency types like me, just beliving something causes side effects can cause real measurable symptoms.

I had really annoying side effects from medication until at one point I realized I got the same side effects almost like clockwork even when I had forgotten to take it. At that point the side effects just disappeared completely I haven't seen them since.

(That said, the effect you felt might be real or not but I still agree with you that cutting back on sugar is smart.)
Nutrition's become a bit of a religious/political issue.

It just makes sense if you believe that studies are biased. It seems like trust in authorities (in this case to determine dietetic recommendations) would be a common factor with religious/political differences between persons.

Edit: or you could say that some people seems to trust facts more, other ones trust persons more.
Thanks for this. I'm annoyed, though - it looked less ridiculous in the thicker font they used in the competition. The new serif looks like crap.
Indeed. That's been the traditional wisdom, which I was also on board with for a long time.

What I'm concerned about is 'weather weirding'. On average, everything gets warmer, but because there's a lot more overall energy, the highs get higher, and the lows get lower, along with more extreme rain/flooding, along with more extreme drought. And, of course, a lot more intense storms.

I hope I am wrong, and it seems like the analysis of this line of thought is just starting to ramp up.

Anecdotally, it's why, for example, we got something like 10 or 12 '100 year' and '500 year' weather events in the US in 2016.
Economy without money
Thanks for posting this! I've found MobileOrg to be unusable.
Agreed. Reminds me of this scary page I found the other day when googling "certbot setup":

https://certbot.eff.org/all-instructions/
I used it in my all iOS development. Will it be 2nd class?
Navigating the container ecosystem with Kubernetes 1.5
Where are you living where entry level software engineer salaries are north of 200k? I'm in the bay area and base salaries for software engineering with a bachelor's degree range from 90-115k from what I've seen (generally with some stock options and bonus potential added on top but I've never met anyone who's come even close to 200k starting out)
The Eurostar is in St Pancras, not Paddington.
Writing Element Queries Today Using EQCSS
Right. That is the kind of data people like Mark Z need which was the point of the original comment.

You are disagreeing with people who may not actually disagree with you (I know I think open concept offices are terrible for most purposes).
You realize that most of Europe is in NATO with the US, right?
I feel like all of this just comes back to judgement calls. You can't pick technologies in a vacuum, and you can't generalize technology choices.

It's not very fair to make these claims without knowing all of the details around the situation. Microservices CAN be a pain, but it might offset a greater pain of trying to coordinate a monolithic deployment. It depends on things like team size, budget, and technology available to you.

This is where I see the disconnect between employers and most developers. "Programming" isn't a job. Your employer doesn't pay you to write code. They pay you to solve problems. The good employers don't care what tools you use to solve the problem, just that you solved it. The bad employers will force you to use technologies and buzzwords that probably don't apply to your situation. You should be able to defend all of your decisions and have good reasons for them.

On the flip side, not everything you try will work - that doesn't mean that it's a bad option, just that it didn't work for your situation. You don't need to have a redundant low-priority memo system because you don't get enough value out of it to justify the overhead of maintaining it.
Of course that's why it's a negotiation.
Humanity causing its own end is a heavy topic. And it is a hopeless topic considering the new leadership in america.
"... parthenogenetic offspring may have anywhere between all and half of the mother's alleles. The offspring having all of the mother's genetic material are called full clones and those having only half are called half clones. Full clones are usually formed without meiosis. If meiosis occurs, the offspring will get only a fraction of the mother's alleles."[1]

[1] https://en.wikipedia.org/wiki/Parthenogenesis
I disagree with the Xcode sentiment. While it's horrible in its current state, it has consistently gotten better with every release, although honestly the progress is so slow that it feels like the only thing that can salvage it is perhaps architecture redesign and rewrite from scratch.
The article didn't read that way to me.

The GC is a fallback mechanism to catch any refcounting loops, but the reference counting is still in force, so non-looped objects still do get collected.

When the GC runs, everything gets touched. Without it, the refcounting still hits some shared objects, but this is reduced enough to be worth it, and the heap doesn't grow without bounds.
I have used RethinkDB and must say this is one of the most polished pieces of software I have ever used. The only think I am wondering is, whether the project could have moved faster if it had not been implemented in C++.