skysight-inc/HackerNews huggingface dataset:
I disagree. As a gamedev writing game logic you are right.

But as an engine programmer, I agree with the linked author. I'll take your points one at a time.

Most engines are multi-core, but we do different things on each core (and this is where Intel's hyper-threading, where portions are shared between the virtual cores, for cheaper than entire new cores, is a solid win). Typically a game will have at least a game logic thread (what you are used to programming on) and a "system" thread which is responsible for getting input out of the OS and pushing the rendering commands to the card along with some other things. Then we typically have a pool of threads (n - 1; n is the number logical core of the machine; -2 for the two main threads, +1 to saturate) which pull work off of an asynchronous task list: load files from disk, wait for servers to get back to us, render UI, path-finding, AI decisions, physics and rendering optimization/pre-processing, etc.

AAA game studios will use up to 4 core threads by carefully orchestrating data between physics, networking, game logic, systems, and rendering tasks (e.g. thread A may do some networking (33%), and then do rendering (66%), thread B might do scene traversal (66%), and then input (33%), see the 33% overlap?), they also do this to better optimize for consoles. But then they have better control of their game devs and can break game logic into different sections to be better parallelized, where as consumer game engines have to maintain the single thread perception.

SIMD is used everywhere, physics uses it, rendering uses it, UI drawing can use it, AI algorithms can use it. Many engines (your physics or rendering library included) will compile the same function 3 or 4 different ways so that we can use the latest available on load. It's not great for game logic because it's expensive to load into and out of, but for some key stuff it's amazing for performance.

That stuff the GPU is doing eats up a whole core or more of CPU time. So what if we are generally running serial algorithms, we need to run 6 different serial algorithms at once, that's what the general purpose CPUs were built for.

This is all the stuff you don't often have to deal with coddled by your game engine. The same way that webdevs don't have to worry about how the web browser is optimizing their web pages.
> That is reality, but calling it "unhealthy" implies that the current state of things is somehow wrong.

The current state of things is wrong, and unhealthy. We may one day achieve a healthier reality after recognizing this is so.
Spreadsheet with SaaS Benchmarks data
For flex: "While in Beta, based on Compute Engine Pricing for each VM. Pricing will change in the future." [1].

I'm guessing the flex price will go up when it leaves Beta?

[1] https://cloud.google.com/appengine/docs/the-appengine-enviro...
People really don't communicate as well when they aren't collocated.
I Just Drove Eight Hours on Tesla Autopilot
That's about what you would make in Ukraine given the info you listed. So for US this seems really low.
The form-factor for laptop screens are built for media consumption, even though the square form-factor is superior for productivity (I found an old Sony Vaio and the screen form-factor felt very pleasant). Seems the general consumption of media has dominated CPU design in addition to everything else in our computers.
Even more off-topic, here's something I don't understand:

- Cheapest home for sale in Atherton on Zillow is listed for $3.2 million

- The public schools shown to be in the same area as this house have unbelievably low scores (as measured by GreatSchools.org):

-- Selby Lane Elementary (assigned) .... 4/10

-- Garfield Elementary ..................2/10

What gives?
That's because the video game engines doesn't have to be hardened against malicious asset files. All the code in a video game runs at the same permissions level, which you definitely can't say about a random page on cnn.com.
Idealistically and for the fun of philosophically considering the matter, by creating a world composed of societies in which the inhabitants are free from want.
Or the web was ready to explode anyway, and requiring a bit more strictness would not have significantly hampered its adoption.
The CPU has a limited amount of silicon to spend on instruction decoding. That silicon is also part of every single instructions issue latency. Machines like the Cray with complex internal operations paid the cost in issue delays, and most workloads won't earn them back.
And yet we evolved a rather handy set of features for altering and shaping our behaviors.
Oh man, I didn't know you guys released your tools. I'm a big fan of your stuff -- awesome to see such polished prods on the web. Happy to have helped enable some amazing work!
At least with food, we have the option to shop from local farmers markets (wherever possible). But it is nearly impossible to do it with electronics, clothing etc
From 2008: http://www.vldb.org/pvldb/1/1454171.pdf

Also: http://researcher.watson.ibm.com/researcher/files/jp-INOUEHR... and https://github.com/NumScale/boost.simd
I imagine it'd be more like changing human behaviors, and the societal conditions in which they are shaped.
Show HN: SunSed CMS
What would this gain us, other than visual clutter and compatibility issues between IDEs?
> I didn't think it was possible to come up with an idea worse than leap seconds but we did it guys!

Leap seconds aren't the problem, its the fact that we're stuck on a Babylonian style of timekeeping. Measuring time with completely uncorrelated rotations of objects is a ... fun idea. Or maybe the problem is that time is very hard to determine "naturally".
With all due respect, What argument do you think I'm trying to make?

I ask this because I'm still rather unclear about the argument that the original article is trying to make. I'm even more confused about what conclusions slipstream would have us draw from his web-post. Some comments here say that it's not an exploit, that instead its a lesson about why you shouldn't, as a matter of policy, include backdoors. Others say that it is a backdoor/security hole, and are appropriately up in arms over it. The only thing I'm confessing is confusion.

I understand that you think I'm being disingenuous, and the nice thing is that we really don't need to continue this conversation. If it is as bad as some are suggesting, than wouldn't an exploit be out in the near future? I'd expect such an exploit, or even evidence of a backdoor, to make further news, and if I see it then I'll obviously have my answer.
CareSkore gets $4.3M to bring machine learning to preventive care
Exhibit A. A human selfishly ignoring the thesis of a statement in order to sound wise and try to win the disagreement by subterfuge.
True, but in cases like that it seems like the CPU is hardly the problem in the big picture. ;)

Sounds like you and I mostly agree. Just that when you do a root cause analysis, "more efficient CPU usage" seems to rarely be the best place to optimize, compared to "do less I/O" or "stop putting 25,000 widgets on one page", or "smaller RAM footprint", and so on.
SolarCity is designing a roof made of solar panels
AES uses the vector unit on Intel chips.
it's only a matter of time before Amazon has a recruitment problem that it can't fix.

That is to be seen. There are lots of horrible employers who are still around (EA for example). Supply of workers is much greater than demand (even software industry is not immune to it as more and more youngsters enter the profession)
Doesn't the compiler at least need to use the platform-standard argument convention when calling OS functions?
Exhibit B: A human expending energy to protect an idea from a self-important prat too busy playing word games and Tea with Philosophers to listen.
A long, long time ago, I read a blog post in which a developer chided people for making expensive-to-develop games that could only run on 5% of PCs, then complaining about low sales. His point was, "Why would you drive up your development costs just to drive down your potential sales?"

edit: found it http://draginol.joeuser.com/article/303512/Piracy_PC_Gaming
Is the ABS Census online yet?
It would be cool if you could use a GAN to generate images merely by providing an object name. You could train the GAN on images obtained by searching for that object name in an image search engine.
My experience is that it's extremely uncommon, including on physics systems. While I no longer work in games, I did for several years, I probably can count the times that I used double precision on one hand (if you exclude the JavaScript work that plagued the end of my game development career).

The reason for this is simple -- it's twice as slow. The vector width is half the size, and so you can do half as many operations at a time.
A pretty solid rule of thumb is that 32 bits has enough precision for rendering, physics needs doubles if it's going to use a lot of iterations. Simplified models like Super Mario jumps or the tractor beam in "Thrust" (single rigid joint) can get away with 16-bit fixed point precision.

OTOH rendering of geometry only needs about as much precision as the display offers, which often means 8 bits on older hardware.
> If you are defining honest as some midpoint between a white lie and an asshole, then what is being honest?

Honesty is an endpoint, with the other side being dishonesty (including lies). On a separate axis, you would have maybe "gentleness of communication". On a third axis, orthogonal to the first two, you might have "intent", ranging from benevolent to malevolent.

So, complete honesty would be a plane. Some parts of the plane are difficult to reach (completely honest, completely gentle, completely benevolent), and may be impossible depending on the situation (timing, your relationship with the person, etc), and your own skills of communication.

"Asshole" would be a cloud within that volume, mostly floating around where "malevolence" and "harshness" have high values. None of these things are binary values, though. The soft edges fade into each other; we're working with shades of grey.
> We have all this office automation, but too many people in offices.

I can't speak to the general case, but to my experience with big corporations/enterprises.

Automation is rarely implemented, and when it is it's half-assed. And then a year or two later they try again, but the old system remains, and now your workers have to connect two systems manually. And then a year or two later...

Not my domain, I'm busy enough, but in one area of my org there are a ton of people whose job is, at its core, to manually synchronize about six databases. They also interface with customers, so that part can't or shouldn't go away. But they spend 80% of their time (estimate based on friends who worked there) doing that manual sync. Every time someone had the same thoughts as me but the power to do something tried to automate it, they ended up with an extra database that was only partially connected to the rest.

Too many stakeholders, not enough leadership.
Our data is primarily stored in postgres. We've looked into using Mongo to store FHIR-compliant documents, which is the newest standard (and best standard, IMO) proposed by HL7.

Haven't looked at that many immutable databases, but they seem interesting. Most of the time medical data does not require many writes (rarely are two doctors editing your record simultaneously), but the audit trail that datomic provides could be very useful as a built-in feature.
I fail to see how a majority of people can generate money via capital. Investment income only works when there are people willing to take the investment money and produce goods or services. In a world where the majority have an over abundance of capital, and little to nobody to actually work to produce, where would the value be created?
The system works right now because most people are poor and have to work to live rather than invest to live.
Is that a "why is there so much office work" question, or "why are there so many people travelling to offices"?

On the former: perhaps the Jevons Paradox at work, or something alligned with it, Baumol's Cost Disease and Amdahl's Law both come to mind.

The Jevons Paradox notes that as a thing becomes cheaper, the total amount of it demanded can increase. A particularly noteable case of this is the cotton gin ("cotton-engine"), which roughly halved or more the cost of removing seeds and chaff from cotton, or alternately, doubled the labour productivity associated with it. A result was a tremendous increase in labour demand, which in Antebellum Dixie meant an increased demand for slaves. The US imported 80,000 slaves from 1790-1809, when imports were banned, then proceeded to increase the number through breeding through the Civil War.

In the case of office jobs -- decreased costs mean an increased demand.

Baumol's Cost Disease has a few elements to it, one is noting that some labour cannot be markedly improved in efficiency. Where physical production and manufacture becomes increasingly efficient, you'll relatively increase the amount of labour elsewhere within the economy, by definition in less-productive roles.

Amdahl's Law similarly notes that in any computer process, parallelisation will serve to increase the significance of the nonparallelisable portion of processing -- if a task is 90% parallelisable and 10% not (by time), then with a tenfold increase in parallelisation will result in roughly 50% of the task being nonparallelisable. The 10% of time is not fungible through parellelisation.

Another factor is being pushed to limits through competition. If other firms are extracting all possible value through increased office-and-administrative tasks -- marketing, HR, and other efficiencies, then companies which don't pursue these ends are at a disadvantage. It's not that there are more gains to be had, but there are the only gains to be had, and you'll lose by not pursuing them.

It's somewhat related (though I'm explaining it poorly) to the tendencies of those under extreme duress to take actions which seem otherwise irrational. Investors will buy high and sell low because they have an increased liquidity need when market prices are low. Dust bowl farmers would increase their farming intensity in the presence of both drought and low market prices because they had fixed debt obligations they had to meet to remain solvent.

(Gordon mentions the investor case in Rise and Fall.)
Even though the JVM probably gets in the way of the kind of low-level optimizations we are talking about here, Java is not the main factor for the CPU usage.

All those voxels take up a good chunk (heh) of processing time. They are not all static, you know. Not sure how much of that could be shifted to the GPU.
Generally very positive. I posted about it elsewhere in this thread.
I feel like you've not seriously used each of them. Ghcjs is very interesting, but also very, very early. The ecosystem is tiny, the compiler produces huge and slow builds, the interop is tricky, the semantics imperfect. It may be a very long time before any of those are resolved, too! Compiling a lazy language to Javascript is no simple trick. Luite deserves all the praise in the world for getting it this far... but there's just a long way to go.

So, in the terms of this article, Ghcjs might be around the same place Scala.js was 2 years ago. In the mean time, Scala.js has taken off in a lot of ways. It's yet to be seen what will happen with Ghcjs.
Can I upload such image for instance to facebook and intent to run it as html (with some JS inside)?
The problem with podcasts
Except for: types. That's a big deal about what the author liked about Scala.js.
Yeah, I heard that things are much better than they were back then. I guess I'll reconsider once my lease is finished. The good thing is that MARTA is pretty good and on-time usually from what I saw.

What did you study btw?
No no - it's most likely a "good thing"(tm)

It's not like I trust my browser and https any less than I trust my phone's baseband processor and it's NSL-able telco-end backdoorability...
The income I was getting felt luxurious even without the RSUs. I viewed them as "promises of extra income next year" rather than "money I get this year but forfeit if I leave", which seems much healthier for many reasons. You're always on a revolving set of RSUs anyway; it's not like there's a point where they've all vested. In no sense is that 'handcuffs'. It's more of a guaranteed raise.
DEA regularly mines Americans' travel records to seize millions in cash
Put aside the silly title and the inconsistency between the subtitle and content ("the only real problem was the driver behind the wheel" vs "The sensors failed to register a rapidly accelerating gold-colored SUV beside me and would have driven directly into its path had I not quickly taken over") and this article has a really good point to make:

As we get closer but not entirely to autonomous vehicles, figuring out how to communicate to users (at what point do we stop calling them drivers?) the necessary level of engagement (and notifying them when that level changes) is going to be increasingly critical.
It's open source and runs on a raspberry pi, so I'm sure you could 3D print a better form factor if you want :)
Now I have to apologize for playing both sides of this conversation, but we've been working on this tribalism for a few hundred years, maybe if you were a better student of human history than I am you could make a case for a few thousand.

We have a way to go, but we have made at least some progress. Maybe in another few hundred years humans won't be so 'Us and Them'. Maybe materialism will be the next thing we work on. Who knows, maybe by the time we reach the next galaxy we'll have it sorted out.
when you call it Autopilot and not SuperiorCruiseControl you've set expectations. It's no use trying to re-define the term more accurately after the fact. They'll survive but the halo got dented.
I was full in for Dart but Scala.js has been one of those alternatives that seemed more viable. Thanks!
Show HN: Constructing Methamphetamine in VR
#mountTrump?
Glad somebody wrote this. I agree 100% (well... probably more like 90% -- but mostly nits that aren't worth getting into).
So what's Amazon actually doing about those bad departments?
An abusive work environment is akin to an abusive home environment. Given that at work you don't even have the option of standing your ground, it's at least as bad.
that's an uninteresting opinion.
I've been communicating solely with people for years, from home, using chat and sometimes video, but usually just text.

I don't forget what someone just told me.

I have a trail of requests and ideas from clients and coworkers.

if necessary I will jump on a phone call for faster data transfer.

the office is great for talking to coworkers, which is almost always about non work stuff, vs when I'm at home working and all my conversations are about work.

I rarely get interrupted when I'm in the zone unless it's an actual emergency.

I could go on.
I don't think the people who stay for a long time are "starry-eyed". I think they're people who jive better with the culture. That perfectly explains why they like it there, too.

I did well with the culture, and therefore had a positive experience. I'm definitely aware of people who didn't. I'm also aware of people who weren't unhappy, but left for unrelated reasons (several because the weather in the Bay Area trumps Seattle for them. I don't know if I feel that way, having not lived down there, but I think Seattle's weather is vastly underrated.)

(I feel compelled to defend Amazon since I feel like the lone naysayer in this comment thread.)
They usually set the content type to that of an image so the browser won't execute the JS.

They've messed this up in the past, see this legendary bug bounty report [1]

1. https://whitton.io/articles/xss-on-facebook-via-png-content-...
How Let's Encrypt was built
Well the wider screen format allows for a keyboard with a numpad now, without getting a massive "lip" below the keyboard.
Am I wrong in thinking that the problems complained about here are precisely because it uses sensors and a camera and not lidar?

(I did a bit of research, and reading around says "probably", but i trust HN's opinion a bit more :P)
mewo2, I am immensely grateful to you for devoting the time and energy to a task I've been meaning to undertake (and thus value), but have yet to find the time.

Your success is inspiring, and I've forked your repo(s) to try and continue your work. Thank you so much!
I wonder if there is similar article/insights about cam models.
I got the opposite impression - that it's an exploitative industry that preys on the needy. Anton is someone to want to help, not somebody who's situation is enviable, at least to my mind.
Check these out for specific benefits:

http://libre.adacore.com/developers/technical-papers-single/...

http://www.adacore.com/press/spark-skein/
That argument has in fact been made for why, e.g., the Romans didn't exploit coal, which they had (from England) rather than human and muscle power.

Slaves were far too cheap.

A developing thought: the industrial revolution, writ large -- starting with the Medieval industrial revolution of increased use of wind and water power, was in many was a continuously ramping-up circumstance of living close to (but not immediately at) the thresholds of subsistence, having available opportunities for improvement, and having a gradually increasing degree of technical complexity in tapping into those opportunities, which developed as the challenges and opportunities increased.

If you're not testing your limits, you've got no incentive to improve.

If you've pursued some improvement, but are then contented with the results, you'll continue in a "fat and happy" existence. This has occurred in several places and times through human history.

If you're pushing at limits, and are aware of the concept of technological advance, but the resources aren't available, you'll tend to slide into decline. Arguably this happened to the UK following WWI. England had steamed into modernity on the basis of its coal reserves, but switching to oil, without (then-known) reserves, she stumbled and the United States picked up the slack.

(Why the Middle East didn't exploit its own oil reserves earlier is a tremendously interesting question -- whether for want of technology, industrial capacity, or other reasons. I'm planning on looking into this.)

Another possibility is that the technological leaps are simply too great. The Middle East question may have been a case of this, and the West (and world at large) may face that conundrum in switching to renewable or sustainable energy options.
If Apple can take the phone and unlock it with the tools and knowledge at their disposal, then they have a backdoor for it. The distinction that you're drawing is meaningless.
Similarly, in my office too many people try to communicate tasks and plans to me verbally. I've had to tell them to send me emails (or put in a JIRA entry or whatever).

I cannot incorporate something into my task list that's undocumented, and text (email or JIRA preferred, chat is sufficient for small things but can't be a priority item) is a fantastic way to ensure that it makes it into the queue.