skysight-inc/HackerNews huggingface dataset:
Not in a corporate environment with KMS though.
That's all fine and good, but you didn't understand my argument.

I was objecting to your assertion that a "deadlock" would necessarily cause the autonomous nervous system to fail.

Since computers don't do that, why do you think that evolved systems - which have billions of years to build up robustness - must do that?

Your objection to the "homunculus problem" is not relevant. A watchdog does not need to be a "brain" in any but the most poetic sense. It can be switch on a timer, where the timer is reset by the system.

Computer can have deadlocks on many levels. I could write a multi-threaded program which deadlocks. Even though that's frozen, the rest of the computer could act like normal.

Since you didn't specify which sort of deadlock you were looking for, I pointed to ones which occur at the most recently evolved parts of the brain.
Yup. The author does have some OK points in places, but some of them are either (a) facts of Life or (b) organizational/management issues.
I didn't consider small static sites. I agree with that and have done some landing pages that way that stand in front of SPAs. I guess I was commenting on OP wanting to use Rails or Spring MVC for views instead of only using them for APIs.

I'm not sure what the term for it is, monolith maybe.
You can't set a price tag on your time, it's way to valuable in the sense of you can't buy it back.

Spent your time wisely. You are going to die, and if you spent most of your prime time speculating in making more money, you never understood life.
I was writing a program similar to the 4-coloring problem. I represented colors as 2-bits (color 0, 1, 2, and 3).

I also created a bitmask representation of relations, which would represent 1-variable in 4-bits, 2-variables in 16-bits, 3-variables in 64-bits, and 4-variables in 256 bits.

Ex: Texas / Oklahoma / Arizona relation would be a 64-bit number ("true" means a color-set is in the relation. "False" means the color-set is not in the relation), and extracting or packing the data into these three variables would be a pdep or pext operation.

Extracting data (pext) would be a "select" operation. While PDEP + OR would be a "update" operation over the relation. I've written a join for fun, but I haven't gotten much further than that. First, because pdep / pext were slow on my machine. Second, because I figured out an alternative solution to my particular problem.

---------

I think the pext / pdep instructions have HUGE implications to 4-coloring problem, 3-SAT, Constraint Solvers, etc. etc. More researchers probably should look into those two instructions.

Just look at Binary Decision Diagrams, and other such combinatorial data structures, and you can definitely see the potential uses of PEXT / PDEP all over the place.

https://en.wikipedia.org/wiki/Binary_decision_diagram
The article didn’t even use them. They hacked a single voip ata with two ports and connected those together. That’s a pretty elegant (albeit impractical) solution to that rather unique problem.
The Global Object Pattern
It’s culture transfer when a company makes something and then another company makes a poor copy that sells for cheap? The only reason it’s cross-cultural in our modern world is that Chinese firms tend to not follow American IP law.
The difference is imperative vs reactive UI. The impact of this is hard to overstate.
What if there isn't any?
If you look carefully at their videos, you'll notice that each one of their vehicles is followed by a dark Prius with two people in it, and some videos (others are shot in angles that one cannot be sure) show another dark Prius driving in front of their vehicle.

They've launched a PR stunt, not an unmanned delivery service.
I've been running a ThreadRipper 1950X in my main box for the past 15 months or so and am generally extremely pleased with the results. However, my biggest takeaway from the experience of having 32 cores has been that an embarrassingly large amount of the software I use on a daily basis for productivity runs in a single thread. My expectation was that UI blocking would be rare- it isn't, particularly with Chrome, Firefox, and Slack. Jira in the browser is terrible- even with insane resources and 1Gbps bandwidth I regularly have to wait 10-15 seconds to be able to enter text.
And isn't available on many networks these days.
> there is a belief that it's easier to become a principal by leaving than by going through the rigorous promotion process

That's because in most places it is. The whole construct of "work above your pay level for years on end, and MAYBE one day you will be paid accordingly" is fundamentally flawed and will always foster an environment of low morale. That's a sucker bet, and is why people job-hop for meaningful career advancement. Promotions are little more than popularity contests, not unlike a beauty pageant. And much like a beauty pageant, they don't reward those who answer the judge's questions the most elegantly, they reward the ones who attract the most attention. If you want to know what a company values, pay attention to what it rewards/incentivizes, then ask yourself if you share those same values. If not, bounce. You'll likely make more money doing so anyway.
Yes, because all design issues are solved by gating everything behind an interface.
How do you bring up the topic & structure rates? EG, if you get 80% of the way towards that 5% goal, What about 120%? etc.

How do you price based on results like this without a clear internal view of the company's numbers. Feels like it would be throwing darts somewhat.
That is actually an enterprise feature that gets very little recognition. There are many challenges with keeping it all in sync, especially if you have multiple contributors. But may I ask more specifics on your case? For me and my team is about getting forecats and kpis from humans into a central database from which we can then do further analysis and plotting, reports, etc
Okay, my suggestion was nowhere NEAR the hyperbolic suggestion you are making.
You can get spray like bandages now. Which feels like a combination of glue and some sterilization stuff added in. Stings a little bit and then dries out and sticks like glue.
Direct link: https://developers.google.com/docs/api/
Why the Brain Is So Noisy
Large swathes of C code can't have an RCE by definition.

Any C code which is not available on the network (e.g. C code running on your refrigerator) by definition cannot have a remote code execution vulnerability.

Lots of software, such as the 'top' utility, makes no networking related calls in the codebase, so any instances of bugs would be buffer overflows or crashes, but not remotely exploitable by the usual meaning.

I think that you vastly under-estimate how difficult it is to accidentally write a remotely exploitable bug.

Sure, buffer overflows and undefined behavior happen all the time in C code. Those bugs might be 1 per 100 lines even in the average C code.

of those, hardly any will be network exploitable. Relatively little code will be handling data sourced from the network.
I think that the problem is, while you have near-total control over the information you collect, and can carefully consider its interactions, you have no control over the interaction of your information with other publicly available information. For example, the famous AOL de-anonymisation (https://techcrunch.com/2006/08/06/aol-proudly-releases-massi...) did not (I think it is accurate to say) rely on any metadata attached to the queries, only to the queries themselves.
Lack of intelligence? I simply can’t do math on a higher level.
What would you think of a multiplayer RTS, but where there is a vast ongoing struggle between various kingdoms and empires of the 4 races? (Persistent, vast MMO shared world.) The player doesn't command any side or any kingdom in its entirely, but can act as a hero unit and can command forces in his/her vicinity. (Basically, they're all like a kind of King Arthur who can reappear in a time of need.) The empires and kingdoms are entirely managed by AI and follow a cycle, where they reach a peak of their power (a morale stat follows a peaking curve) then decline and die.

The player works to increase his/her own legend by winning battles. The purpose of this design is to create an extremely complex and immersive world with depth of gameplay, but still enable players to "dip in" for a half hour session every once in awhile.
>exists only once and is needed in many parts.

I think many people could argue that this concept itself is a bit misguided. There are plenty of application patterns and architectures that help you move stateful data around your app and translate it for the components who need to consume it or change it, while hiding it from components in the tree which do not interact with or care about the state.

If you have many different components in your app that all need access to the same state data, and they exist at different levels in the hierarchy, maybe you need to re-think your component structure rather than figure out a way to inject mutable global state everywhere?
shitty name for a great idea.
Is it still very desktop centric as all MS Office products? Because if it is you will struggle to keep up with the amount of data, report and automation that need to run on top of various cloud applications.
A rough estimate of the escape velocity for Ultima Thule, assuming it was a sphere of uniform mass (it isn’t) of mostly ice comes out to ~7m/s (https://news.ycombinator.com/item?id=18811511)

Even better Jake-Low made a rough estimate of the forces between the two lobes:
(https://news.ycombinator.com/item?id=18811366)

And just for fun, I also worked out a best guess for the force between the two "lobes": 1.5 x 10^13 N (assuming Ultima Thule is the same density as our Moon)

Even ignoring that the two lobes are probably vacuum-welded together, it’s quite a large explosion you’d need to permanently separate the two lobes. Granted combinging two rough estimates to get a sense of the escape velocity of one lobe from the other is super messy, but it’s probably informative as a yardstick.

Simply breaking them apart wouldn’t free them, they’d mostly fall back together, you’d need to impart quite a bit of acceleration to one or both lobes to keep them apart. I’m not sure to what extent that would be feasible, but if it was it would take an array of carefully orchestrated nuclear detonations, or huuuuuge rockets along with the nukes.

I think.
I don't think it's fair to use the label "pre-existing political barriers" when talking about being able to convince people that your ideas and vision are worth the cost it takes to implement.
That they 'sell for cheap' in the original market is a thing that historically would have been a lot harder to accomplish than today. Transport used to be very expensive so local manufacture was the norm. Or did you miss the 'before' bit?
I obviously don't have access to their term sheets or whatever information their investment companies are providing them, but the model of trying to (over)fund the segment is not how VC succeeds. Granted, people are saying Softbank is reinventing VC. But everything I've seen leads me to believe they're going to lose money in spectacular fashion, just like how Masayoshi Son lost the most money in history back when the dot com bubble burst.

FWIW I used to work at a Softbank funded company. It was a fucking shitshow where the solution to every problem was to throw money at it, rather than actually try to fix the underlying problem. People are still writing articles about how this company is the future.

Lucky for me I have nothing invested and can just enjoy the show from the sidelines!
Dividing two pieces of work before you figure out what the right 'two pieces of work' are makes it very, very difficult for someone to refactor it later. As feature sets expand and expand, we frequently discover that two things are really three, or three things should be two with a bit of configuration. If they are in separate modules this is challenging. If they are in separate deployments people will just hack and get away from the code as fast as they can.

This sort of thing is a much overlooked aspect of YAGNI, and the related but lesser known concept of Reversible Decisions, which in a nutshell is: Any decision that can be changed easily, make it as cheaply as possible (time, emotional investment, etc. Chosing at random can work here, or quick show of hands without commentary - grandstanding is expensive). Any decision that will be difficult to unmake later? Play for time to allow more data points to come in before making the decision.

I kind of alternate between toolsmith and team lead, depending on the political landscape of the company. My philosophy is basically this. I say 'tool' below but it also usually works for processes (tools work better in times of high stress):

- Give people tools so they can do better (ie, make higher quality code changes)

- Make the tools foolproof, so they are more help than hindrance

- Apply social pressure (encouragement first, shaming for stragglers) to get people on board for using the tools

- repeat step 2 as new users find new problems

- Change development process to include the tool

So my first question is, is your plan to use microservices going to emulate this pattern, or are you just continuing a war of words by adding friction to the system? If you see people are writing bad code now, how much bad code that you don't see is going to be in microservices you don't care much about?

Are those microservices going to have an effect on your quality of life, the esteem of your team among other divisions of the company? Then you probably care what's in them and "out of sight out of mind" is a terrible strategy.
Datashader's approach is a bit different from an accumulation buffer, though similar in principle. It's not 3D rendering, and has no need for a z ordering; instead it's essentially 2D histogramming. For points, it simply takes each point, calculates which pixel it would land in, and aggregates per pixel, without ever storing all the data points per pixel. The key benefit over something like SciPy's histogram2d functions are in how it is implemented and used -- highly optimized, and highly integrated with viz tools so that it can let you just interact with your data naturally as if you had infinite resolution. Try it and see!
Other people are using words like "arrogance", "fanboyism", but there's a fun, short, free book on the question, "Under what circumstances are you justified in choosing to avoid epistemic modesty and assert that you know better than experts?"

It's Inadequate Equilibria by Eliezer Yudkowsky: https://equilibriabook.com/inadequacy-and-modesty/

Yudkowsky agreed with a small group of economists, and disagreed with the Japanese equivalent of the Federal Reserve. You might think, "The Japanese Federal Reserve has every incentive and resource to be correct about growth policies, and this small group of economists has no insight they don't have," but the story is more complicated than that.
Moving into JS development from Windows development was a shock.

APIs have breaking changes?! I get it, open source devs don't have huge corporate resources to ensure back compat forever, but wow, it moves so much burden onto product developers.
Testing is easy in Angular. (Thanks to the everything is an object approach.)

https://angular.io/guide/testing#component-class-testing

https://angular.io/guide/testing#service-tests
100% correct, and I'm guilty as charged. If leadership likes the sound of SPAs, and my next job wants me to have experience with SPAs, I'm using SPAs.
The honeycomb lattice mentioned in the article resonated with me.

I’ll go out on a limb and share a personal anecdote: In high school I took magic mushrooms with my friends, and at one point in the experience the world disappeared and I saw an undulating fabric in a honeycomb pattern. In the center of each “hole” in the fabric was a link to a memory, a time and a place.

It was one of those images that was hard to forget - I can still recall it many, many years later.

In “Dragons of Eden” Carl Sagan muses that drugs might work in an analogous way to how night time brings out the stars. The stars are always there, but daylight masks them.

In a similar way I’ve often wondered if there was something to that geometry I saw.

Or perhaps it’s just my brain trying too hard to be poetic :P
The cool thing about HN is that, by its very nature, any post that gets voted to the front page is warranted.
> an embarrassingly large amount of the software I use on a daily basis for productivity runs in a single thread. My expectation was that UI blocking would be rare- it isn't, particularly with Chrome, Firefox, and Slack. Jira in the browser is terrible- even with insane resources and 1Gbps bandwidth I regularly have to wait 10-15 seconds to be able to enter text.

Why would you expect anything different when JS _does_ run in a single thread? We'll have to wait for WebAssembly to have anything like real multithreading, with good-enough performance, on the Web.
It's similar to people gravitating to NoSQL when they probably actually needed a relational database because they don't really think about their data model and how it will be accessed.

That being said, as someone who has done a lot of infrastructure work, I do like web technologies that can fit into something like serverless and Ruby/Rails really isn't there. Speed, file size, and boot time all become much more important. Or if you can make it work, fully static pages that can live on S3/Cloudfront and any dynamic needs are abstracted away to API gateway/Lambda and pulled in.

I would much rather have an app running inside of Lambda instead of having to manage a load balancer and AWS auto-scaling, or even elastic beanstalk.

So many problems can be dissolved down into people picking the wrong tool for the job.
This is nothing new and hardly unique to the tech industry. Back in the 90s I worked summers at a factory that made door latches for Honda, Chrysler, and Nummi. About 1/3 were "temporary employees" employees of Manpower even though some people were there for over a year. Same job lower pay and no benefits.
> TypeScript doesn’t absolve you from learning JavaScript. When things go awry, you’ve still got to be able to spelunk the JavaScript code it produces.

TypeScript code is still 90% regular ES6 JavaScript, of course. That said I very rarely need to go grepping through the transpiled code.
How come every report on their "unmanned" delivery service fails to mention that there is a chase car following their vehicle and (visible in some some videos) a car driving in front of their vehicle?
You're missing the point of this project. It's not about the feasibility of throwing a billion points at a pile of software, to get an image. I can do that with a simple Python script. It's about doing so to create a meaningful and accurate data visualization, and not just a picture of, say, shiny spheres or a scene from Avatar.

I actually have a background in 3D computer graphics, and it's precisely because of my detailed knowledge of raytracing, rasterization, OpenGL, BMRT, photon maps, computational radiometry, BDRFs, computational geometry, and statistical sampling, etc... that when I came to the field of data science & specifically the problem of visualizing large datasets, I realized the total lack of tooling in this space.

The field of information visualization lags behind general "computer-generated imagery" by decades. When I first presented my ideas around Abstract Rendering (which became Datashader) to my DARPA collaborators, even to famous visualization people like Bill Cleveland or Jeff Heer, it was clear that I was thinking about the problem in an entirely different way. I recall our DARPA PM asking Hanspeter Pfister how he would visualize a million points, and he said, "I wouldn't. I'd subsample, or aggregate the data."

Datashader eats a million points for breakfast.

Since you're clearly a computer graphics guy, the way to think about this problem is not one of naive rendering, but rather one of dynamically generating correct primitives & aesthetics at every image scale, so that the viewer has the most accurate understanding of what's actually in the dataset. So it's not just a particle cloud, nor is it nurbs with a normal & texture map; rather, it's a bunch of abstract values from which a data scientist may want to synthesize any combination of geometry and textures.

I chose the name "datashader" for a very specific and intentional reason: we are dynamically invoking a shader - usually a bunch of Python code for mathematical transformation - at every point, within a sampling volume (typically a square, but it doesn't have to be). One can imagine drawing a map of the rivers of the US, with the shading based on some function of all industrial plants in its watershed. Both the domain of integration and the function to evaluate are dynamic for each point in the view frustum.
In the USA we don't do that.

Our sardines and anchovies have the head and guts removed, and probably the tail. We do sometimes eat skin and bones. The same goes for canned salmon and herring.

We also peel, decapitate, and gut our shrimp. This is probably a better comparison because the exoskeleton is similar.
On the other hand, calling someone out for un-credentialed analysis often amounts to an argument from authority. The GP's point about overhead would have been made just as well without the ad-hominem.
Not yet, like many effects of ecological collapse there is a lag time. As much as 50-90% of our calories come from angiosperms which are dependent on insects: https://www.livescience.com/52752-what-if-all-insects-died.h... and insects help us produce new top soil, of which we have lost half in the last 150 years: https://www.worldwildlife.org/threats/soil-erosion-and-degra...

The combination of soil loss, pollinator loss, and decomposer loss helping us produce new soil will be a double-whammy for our agriculture. Thus far I would assume the reason why we have gotten away with growing plenty of (increasingly less nutritious) food is because of the wasteful practices that are killing the insects and depleting our soil, so we are on borrowed time.
You're right, that sentence captures it entirely, the rest is additional words but not additional meaning.
Genuine question, What's the use case for this? If you already have to do some programming how is it different from generating html documents (like invoices) (that can be converted to PDF) and some web forms for filling out the templates?
And when the state has relevance to two components? Now it's okay to make it a global, because we can't be bothered to type "prop = value"?

I'm just not buying this argument. People add Redux to projects because they intend to use it, and there's almost never a case where a piece of data is actually needed in enough places that it should be global. It's certainly not common enough to justify importing a whole framework for managing global state.
It'll be interesting to see if there's an upswing in PyPy usage over the next few months, for the explicit reason that they're not slated to drop 2.7 compatibility. I would imagine a noticeable percentage of 2.7 codebases without the available resources for a rewrite (that has by definition, no business value) would welcome anything close to a drop-in replacement. I'll be very interested to see if I'm wrong though!
I don't believe we will be able to develop a sustainable colony on Mars, at least not with present technology. Every attempt we have made to build a self-sustaining ecosystem, such as Biosphere 2, has failed.

Eerily when Biosphere 2 collapsed the insects died first, which is exactly what we are observing now globally.
If you want one word, Datashader is a rasterizer. It takes data of many types (points, lines, grids, meshes) and creates a regular grid where each grid cell's value is a well defined function of the incoming data. Not sure anyone would be any happier with "rasterizer" than "renderer" or "shader" or any other single word...