skysight-inc/HackerNews huggingface dataset:
If Google treated all poiltical discourse within it's walls like it did Damore, there probably wouldn't be an issue. The whole problem is with favoring one type of speech/thought in a militant fashion that violates federal law.

And regardless of the law, it's UNETHICAL to discriminate in the name of diversity. In 2018, companies are expected to do the right thing. This article paints a very damaging picture of Google discriminating against white males (Disclaimer: I'm NOT a white male)
I always thought anti-aging tech should come with a mandatory course of ayahuasca to shake the belief system up a little.
> It’s astounding when people think that advertising doesn’t affect them.

I know that advertising affects me. That's one of the reasons why I block ads at every opportunity.
It took 200,000 years for our human population to reach 1 billion—and only 200 years to reach 7 billion...

6 minute American Museum of Natural History animation

https://youtu.be/PUwmA3Q0_OE

The fundamental problem is over population IMO
A simple idea: strip CO2 from the air and use it to produce fuel
You know, I understand a certain amount of PHP bashing. It's far from the most sane language that I have ever used and parts of the syntax are flat out painful.

That said though, the version of PHP you are talking about was written 23 years ago. The language has changed a tremendous amount over 23 years. The state of the tool 23 years ago would be a very poor reason to choose or avoid it today.

Hell, Java is roughly the same age as PHP. Nobody in their right mind would dream of using that first version of Java today. It isn't that the tool itself is bad. Rather, the tool has improved dramatically over the last two decades.
JavaScript is a worse language than PHP in some ways, for example no native type hinting, no native filter map reduce on hash tables, no explicit variable import into scope

I'm not saying PHP is a better asynchronous language than NodeJS but I'd definitely be wary of JavaScript unless you're interested in compiling

If you're interested in compiling then there are some very good languages in that space that are not JavaScript, Go, #F, etc
The headline suffers because it's a lot less nuanced than the article. Amazon exploits the lack of any better opportunities, but does not create that situation. Better than nothing, less than ideal, is the theme, but we can't expect the benevolence of corporations if we want to get the world closer to "ideal." They focus a lot on one nicer alternative - Stater Brothers - but acknowledge that they aren't of the same size and aren't in a position to replace all the Amazon jobs. Any debate over "will people vote with their wallet to punish ruthless businesses," that might've been started long ago with Walmart or foreign manufacturing or anything else, is long since settled. Someone is going to offer people shitty jobs as long as there is no better alternative, so direct the focus to fixing the system, not the single company.
IMHO, the biggest reason to use a language like Node when you want to do async programming is that for any random library you choose there's a 98% chance that it properly supports async as well and won't block on you. For better or worse async is pervasive in the ecosystem. Even in good languages like Python that have (allegedly; I've not used them) good async frameworks, most libraries will block as it's the normal I/O mode for the language, which really limits what you can use. I can't imagine the situation will be any better in PHP.
I work in ecommerce and I feel it’s somewhere in between. We need to build for seo optimizations for the category/product experiences yet there is a lot of application like intersections, especially on the category filtering and the product sku selections. Quickshops, In store pickup modals, user specific recommendations trays, add and edit reviews et all. Different caching for server render at the edge vs personalized components adds another layer. Being able to serve with a shared routing scheme both client side (for improved performance) and server side for faster initial page load and seo on non-Google crawlers is a tough problem. Especially when you add in client hydration of the redux store. That parse time is a real killer on mobile. You add in service workers and prefetching and the complexity ratchets up further. The other issue we deal with is marketing pixels and trackers. But that’s another story. There is a ton of complexity in building a highly functioning ecommerce site.
> For fast payments nothing beats a server with credit accounts.

For scalability and robustness, one server won't cut it. You need a whole infrastructure to handle lots of payments securely.

I see various exchanges having trouble with scaling to support all their (new) customers, and basically they are doing the "single server" that you are talking about. Only at deposit/redraw they need to go over the requested blockchain.

So in that sense, what is your view on the latest generation of cryptocurrencies which have instant transactions and 0 fees (such as Nano)? Since I consider them the BitTorrent of currencies, I don't see how any institution could beat that.
Immoral laws should be broken.

The law mostly works because people follow it, voluntarily, most of the time.

And if enough people break the law (and take steps to prevent themselves from being caught and avoid all consequences, obviously), then eventually the immoral law may as well not be the law because it becomes effectively unenforceable.

"The rules are the rules" is never a good excuse. What matters is the underlying intent and reason for the law.

In this situation, the intent of the law is to prevent employees from being exploited. So a judge should look at it and say "obviously, this person wasn't being exploited, and it is not the intent of the law to deport them in this case".
Microsoft’s cloud continues to grow as it chases Amazon
Nonsense, but you may have been brainwashed into believing it.

An enormous disservice to American school kids for the past forty years has been the ad nauseum repetition that you either graduate college or you’re a failure who’s a complete drain on society. This is bollocks. After training a few years, work in some skilled trades pays six figures. Others are easily making upwards of $70k. If you can’t survive on that, tighten your belt or move to a lower cost-of-living area.

Just like everyone you went to college with wasn’t a fit for med school, not everyone you went to high school is cut out for college. Learning a trade in vocational training may be exactly what they’re looking for and is definitely a path to good jobs. Earning a decent, respectable living is fine and in no way a comment on the person’s character or value or intelligence, but by painting it as “alternative school” with the connotation of a one-way track to Loserville, axe grinders have made the situation far worse.

Now, it’s true that being a fry jockey — or any other job where anyone can walk in off the street and do the same task with little training — is not economically survivable, but a career that peaks at unskilled labor is far worse than ordinary.
Defeating aging or extending human life to some extent say 150 years, gives us time to extend life to 300 and so on. It solves for true deep space travel and colonization of habitable planets.
I guess if you use standardized hardware protocols, you cut free of many drivers, you don't get flashy graphics but you get some GUI. For me it's often enough. I have zero love (no hate, just no love) for html5 levels of flexibility.
The unofficial existence of "no-go zones" in immigrant areas, the increase in grenade attacks, including against two police stations in the last few months (Helsingborg and Malmö), the increase in rape the last few years (particularly the recent gang rapes in Malmö) - these are all just racist fever dreams I take it?
"Asynchronous PHP; Why? Because it's there." I was expecting some actual reason.
This Robot Will Brew Your Coffee and Serve You for $3
I am an experienced PHP developer - and I also ask the question "why asynchronous PHP" all the time - except in a different context.

Every time I start thinking about doing some strange magic "asynchronous" function - I realise I can just use the standard queue systems built into most frameworks today. i.e. get the task - push it onto a queue - then do something else without waiting for the queue itself.

The thought of dealing with "forked" processes, memory leaks, strange race conditions etc and all the stuff that comes with async PHP does not seem worth it. It is very easy to "reason" logic behind a queue system. I can test it extremely well, and essentially break the process up into sub sections and not have to worry.

Note - I'm not saying there is no place for true asynchronous functions - but I think people reach for them in PHP when other easier solutions might suffice in the first place.
> No one wants to fail in hunting, farming, business or anything else.

The supporters of the football (soccer, for the Americans in here) club that I used to root for ever since I was 9 (I'm now in my late-30s) used to have this wonderful saying: "It's better to hit the post with a beautiful shot than to score an ugly goal". That saying was one of the many reasons why I loved that club, which didn't have that many trophies under its belt. For what is worth, the club has now been dead for 2 years (it was founded in 1923) for financial reasons, so there's also that (it sucks to be a football club nowadays in Eastern Europe). I'm also a Mets supporter, so I guess there's just a cohort of sports fans like me who get attracted to clubs for reasons other than the "obsession to win".
Except really its correct pronunciation is “demon”, just like how archæology and æon aren’t pronounced any differently because of the ash (which British English still uses). It drives me up the wall to hear “day-mon”.
China and India share the same water problem. When the time comes, yes, China will drain all the water it needs from Tibet. And probably sell access to India.

You don't need to redirect it though. You can, but you could also pipe it, pump it, bottle it, whatever.

The thing is, when you have no water, cost is no issue, because the stuff is way more valuable than gold.

The only real issue is India getting mad about it. But now that Tibet is China's territory, it has a legitimacy that will be impossible to contest peacefully.
Article states their entire operation uses 400,000 acre-feet of water a year. That’s 645,332,372 cubic-yards. Israel today produces 785 million cubic yards of water per year, using it for agriculture, among other things. [1]

From the same article:
“Desalination used to be an expensive energy hog, but the kind of advanced technologies being employed at Sorek have been a game changer. Water produced by desalination costs just a third of what it did in the 1990s. Sorek can produce a thousand liters of drinking water for 58 cents. Israeli households pay about US$30 a month for their water — similar to households in most U.S. cities, and far less than Las Vegas (US$47) or Los Angeles (US$58).”

At the $0.58 per 1000 liters, that farming operation would require $286 million to pay for the water needed. The article quoted profitability scratching a billion, so it seems that it is both within technological means and economically viable. For sure not as profitable as free water, but still viable.

No magic required either.

[1]https://www.scientificamerican.com/article/israel-proves-the...
There's no harm in asking.
Elixir has gotten this down perfectly.

I always wished js was sync by default and only async when you tell it to. Now you have the words async/await (and not too long ago promises, bluebird, waterfall), spread out all over your code for that since you only need async perhaps less than a quarter of your code base. but i dont see js ever becoming procedural first anytime soon.

then I discovered Elixir, i was curious to see how they tout their highly concurrent functional language solved this issue. and surprisingly its as simple as wrapping a block of code inside an async block. its such a pleasant experience finally having best of both worlds, especially coming from years of callback hells and trying to debug what becomes a set of spaghetti code for performing simple things.
You assume crash avoidance is the only reason a car would give up.

Self driving cars however have two goals, not hit anything AND got somewhere specific. It seems likely a car would disengage if it encountered a blocked road even if it did not hit anything. In that context we may see many cases where a car stops and 'gives up' which are in no way safety related and have no real safty risks.

While we don't nessisarily know the specifics, people have been testing these self driving cars for a while and yet crashing seems very rare even with unexpected handoffs.
I know a decent amount of php, but I'm primarily a Python developer who writes most code with asyncio and twisted.

I tried doing a relatively trivial async php script(basically a script that was supposed to make an outbound redis pubsub connection and outbound websocket connection and relay messages) using reactphp and found it to be nearly impossible due to language/framework constructs.

It was easy enough to make the outbound connections but there was no obvious way to actually pass messages between the two connections.

Async style really just does not seem to work well with php at all.
> with the most radical life extension scenario (assuming no aging at all after age 60)

That does not sound like the most radical life extension one can imagine.

IMHO the most radical one is : no more aging after the age of say 30. In that case, one crucial question is : would women remain fertile? If so, what would be their reproductive behavior?
Like Facebook or Uber? Both started with PHP.
Intel-SA-00088 for Intel NUC, Intel Compute Stick, and Intel Compute Card
I remember when node was new and everyone was trying those real-time chat tutorials. After following the cliché tutorial i realized in order to share the session between node and the rest of the php app I had to basically hack it.

I ended up having to read the source code of ReactPHP and add the functionality to my framework. Sure it is not one line of code like with node, but it's not rocket science either. I would definitely recommend trying ReactPHP to see the benefits.
You joke but this is exactly what should be done. Python also has an async story that leaves a bit to be desired. Async/await etc is getting more and more use, but with async coroutine mocks and everything it seems easier to start over sometimes.
https://www.heise.de/security/meldung/Meltdown-Spectre-Intel...
I’d be very cautious about buying anything big or lousy. Keep buying a series of small and easily integratable technology companies - like Powerbyproxi, purchased late last year.
Have 3-5 internal investments on technology and products that nobody has thought of yet. Don’t be afraid to spend too much, but also make sure you can deliver to Apple standards.

If this sounds like business as usual the good. Apple has done very well so far.
It's not a rule. It's 100% subjective and what's good enough for you is completely different than someone else. Being good at something though usually is built on some kind of goals and purpose which tends to lead to more satisfaction and fulfillment.
Not the most compelling list of pros/cons that I have ever seen.

In terms of raw performance for content sites, I found hybrid implementations like Gatsby.js to beat most things. Most of the cons of SPAs can be significantly diminished with SSR, proper chunking, and a variety of other modern techniques -- it just gets complicated in a hurry.
It seems like a bet on the perpetually declining cost of solar. The cheaper solar gets the less efficient the conversion rate for storage needs to be to still be viable.
That's pretty misleading. All systems I am aware of essentially try to compile query-specific code and avoid re-compiling runtime code that doesn't vary between queries (e.g. if you look at the HyPeR paper, that's exactly what they describe).

Compiling everything is questionable. There's not much point re-compiling runtime code or code outside of the hot path, it's expensive and doesn't bring any benefit.

E.g. things that aren't beneficial to compile per query include:
* Loops over a column of the same datatype, with no query specific branches (e.g. decoding a column of integers)
* Other static code, e.g. some hash table operations
* Outer loops that don't execute frequently
* Rarely executed code, e.g. error handling.

There are two general designs that let you compile only the necessary things. 1) the runtime calls into compiled code for hot loops vs 2) the compiled code drives the query and calls into the runtime. A lot of the systems you mentioned do the second, but Impala does the first, which seems to be the source of some misunderstanding. Also there were some cases where hot loops in earlier versions of Impala weren't compiled, but that's changed - generally we try to ensure that all hot loops are compiled.

I think generally the optimal design wouldn't be complete query compilation, but rather something more like a traditional JIT that selectively compiles parts of the query.

Source: work on Impala's query compilation
"...when they were deeply asleep and therefore unconscious."

Advanced meditators are able to be vividly conscious in deep sleep. Though it's probably impossible to describe, the closest might be "consciousness without content." It's subtle enough that most of us overlook it.

Even something as common as lucid dreaming took centuries to be taken seriously. The community at large insisted that it was a delusion. We are probably years away from being able to make sense of the claim that we can be profoundly conscious in deep sleep. Perhaps that can only happen when more of us are trained well enough to experience it for ourselves.

I'll be eager to see how society integrates these kinds of understandings into end-of-life issues, if I'm still around.
I'm considering it too. Also occasionally get a sub to Viz and Private Eye but let them go when the quality dips, as it does occasionally.
Starbucks overstretched and overpriced, say Wall Street analysts
> but I would assume it's not trivial to "just pretend to be one of the permitted devices."

Your assumption is incorrect. Even for devices that are designed with the express purpose of being hard to emulate (auth tokens, DRM chips, iPhone cables), it’s at most a simple matter of a grad student or Shenzhen resident with access to a fume hood and an electron microscope finding some burned-in private keys. For devices that aren’t designed to resist emulation, which thunderbolt devices generally aren’t, it’s trivial. This is essentially one of the core messages you should take away from the field of hardware security.

> IOMMU is not supported on any of the CPUs used by Thunderbolt-capable MacBooks.

They all do. Intel calls it VT-d.
>Rather than build a full SPA I can sprinkle a few components here and there on pages that are highly interactive

In practice, I've found "hybrid" apps hard to pull-off. In my experience, the question becomes, where do you draw the line?

Take the simple/common case of presenting a list view. From the list, you want to allow the user to click to view details, which you then present dynamically--maybe in an overlay. It's a great user-experience. Everything pops, the user can easily return to the list view without a full page-load, etc.

But, you now have a details view that is not reachable directly via its own URL. So, you use the framework's routing capability to assign one. Now, things are getting weird, because you're routing a dynamic view on top of a server-rendered one. You'll likely end up finding that you'll have to route the server-view as well for general navigability. And, you also have to account for people hitting the details URL directly (i.e. render the proper underlying server view, then let the client route to the dynamic URL).

Not to mention the back-button.

All manageable, of course. But, it gets messy to maintain such a hybrid approach. By the time you've integrated the routing, etc. the question becomes why hybrid? Why not full SPA?

If your app is super-simple wherein you're just doing the tiniest bits of dynamic stuff and you don't need things like first class URLs, navigability among dynamic content, etc. then, yeah, maybe. But, that's not really a hybrid-SPA solution because there's no SPA there.

In fact, I'm not sure there is a such thing as "hybrid-SPA". By definition, seems it's either a SPA or it's not.
Here's a list you might find useful: https://github.com/elazar/asynchronous-php
To save time in the future, bear in mind any time you think you are the only person that does or notices something: you aren't. This is due to the fact that people are all running on the same physical architecture, with very similar cultural and social ecosystems, plus the law of large numbers. Note that this does not apply to edge cases such as people engaged in activities or domains with a very small number of participants...
Have a look at Idris, ATS, Liquid Haskell, F* or Cyclone, then maybe you will appreciate Rust from another angle.
Just out of curiosity, did you create a throaway account just for this comment?
Early Facebook and Google Employees Form a Center for Humane Technology
I got the impression from the article that the water is almost never too low to use the waterways for transport. If it happens regularly then it's of course a wholly different matter.
'King of Kong' star Billy Mitchell lied claims Donkey Kong world-record analysis
Of course, when PHP was created its goal was not to be a programming language that can be used to build large complicated applications. When it happened there was no JavaScript and no asynchronous stuff in mind.

I just came here to say that ... neither was Javascript :)
What you are referring to is buried a third of the way or so into the article. I’m talking about the editorial headline. I expect many more people will stop at that than continue to read through until this quote is given context.
The compiler will see that you calculated capacity * 2. Since overflow is UB, the compiler may under that any code path that does this calculation does not cause signed overflow and can deduce that capacity * 2 does not overflow. Therefore, for example, the condition that capacity * 2 > capacity is equivalent to capacity > 0, and there goes your assertion. A modern compiler will likely also deduce that capacity > 0 and remove the assertion entirely. You can read up on "value range propagation" if you're interested.

But all this is beside the point. In C, you may not invoke undefined behavior and then expect anything at all about the result. With malicious input, UB can and will result in RCE.
Yes, but how do you handle the result? You will need a closure to store the context you had when you made the function call. That is async.
In a modern office there are no specialist typists; we all need to be able to pick our way around a keyboard. PowerPoint has made amateur slide designers of everyone. Once a slide would be produced by a professional, because no one else had the necessary equipment or training. Now anyone can have a go — and they do.

I'm struggling to follow. Putting your thoughts down on a piece of paper is something we all need to be able to do. Do people waste time doing it? Sure, some people will waste some time. A myriad of reasons to it. Boredom, clumsiness, a strong need to let out your creative sides, just to name a few.

Perhaps this entire piece comes down to being more aware of the things that distract you. The side quests that often start small, but end up consuming large portions of your time.

In a modern office there are no specialist typists

Sure, in a modern office you won't come across many such people (amongst other esoteric examples). But there's a counter argument here - forcefully introducing additional bureaucracy by proxies is just as hurtful, if not more.