skysight-inc/HackerNews huggingface dataset:
Exactly. A year or so ago I thought, hey, maybe I should redo my personal infrastructure using Kubernetes. Long story short, it was way too much of a pain in the ass.

As background, I've done time as a professional sysadmin. My current infrastructure is all Chef-based, with maybe a dozen custom cookbooks. But Chef felt kinda heavy and clunky, and the many VMs I had definitely seemed heavy compared with containerization. I thought switching to Kubernetes would be pretty straightforward.

Surprise! It was not. I moved the least complex thing I run, my home lighting daemon to it; it's stateless and nothing connects to it, but it was still a struggle to get it up and running. Then I tried adding more stateful services and got bogged down in bugs, mysteries, and Kubernetes complexity. I set it aside, thinking I'd come back to it later when I had more time. That time never quite arrived, and a month or so ago my home lights stopped working. Why? I couldn't tell. A bunch of internal Kubernetes certificates expired, so none of the commands worked. Eventually, I just copy-pasted stuff out of Stack Overflow and randomly rebooted things, and eventually it started working again.

I'll happily look at it again when I have to do serious volume and can afford somebody to focus full-time on Kubernetes. But for anything small or casual, I'll be looking elsewhere.
> I know exactly what directories each of my apps can write to, and that they can't step on each others' toes

You can do this with docker commands too. Ultimately, that's all that Kubernetes is doing, just with a YAML based DSL instead of command line flags.

> Even if the whole node caught on fire, I can restore it

So, what's different from init/unit files? Just rebuild the box and put in the unit files, and you get the same thing you had running before. Again, for a single node there's nothing that Kubernetes does that init/unit files can't do.
Everyday Memory Palaces
Sublime text isn't as featured as Talend tools but it does what it does well and quickly and stays out of my way. Great for loading up a text file, scrolling around, and doing quick find/replaces.

Shell scripts using mostly sed and awk go a very, very long way when I want something repeatable or I'm dealing with a lot of data. And, when that starts getting heavy or long and I need more structure, python.

GUIs just get in the way in this space. By necessity, they need to be opinionated because there's only so much screen to get around in. They also tend to create artifacts that aren't quick to understand later and are locked into some particular product or way of doing things.
I'm usually fairly buzzword-adverse, and I didn't follow the NoSQL/Spark/Big-Data phase when it was hip. I was also hostile to kubernetes until I had to work with it against will for a project.

Since then, I completely changed my mind about kubernetes. This is a very good technology for only one reason -and it's NOT about container orchestration-. Portability. K8s is the missing piece that allows you to create a network of cooperating computers independently of hardware, OS, and even architecture.

If I have an home-made k8s cluster on my raspberry pies at home, it's not because it's lightweight and easy to manage -k8s adds a significant overhead-, it's because it gives me the ability to unplug one of them, take the sdcard, format it and plug another board without any interruption or configuration. I could plug my intel laptop to that network and have some pods running on it without having to change a single line in my configuration. Finally, I can zip a folder and email a bunch of yaml files to my friends (or have them git clone the repo), and they will be able to replicate an exact copy of my home cluster with all -or some- of the services. This is truly amazing.
Software is able to reason about software? Do you notice something in that sentence? If it would work - it would make the programers useless. But it doesent.

Once a pointer points at something in your parallel task, software is unable to reason about it, erring on the side of caution and thus, parallelism wont happen there.

Also these parallelisms, usually work for trivial parallel structures like for loops.
Easy to unroll into multiple cores, but also with little gain, as communication times eats the gained advantages.
By my reckoning, as long as the modem has no public- or customer-facing IP address, it's probably not going to be a vector for easy attacks. It might be accessible from within the ISP network, but if someone has access there then they can probably just tap your line directly, no need for additional exploits.
Cool idea, it is impressive that it is still around - alas it is flawed the same way all scientific data is flawed.

There is no metadata - all you have is an awkward imprecise textual search of the abstract that comes with the data. Good luck hosting the world's data that way.
Texas school district falls for email scam, hands over $2.3M
Is it really so hard to believe that this could be an organizational issue where no single individual is culpable enough to deserve a custodial sentence?

It really feels like many commenters here are just after some weird revenge porn.
Yeah. I like it from the point of view of "think new thoughts". It's an interesting thought. Let me highlight that with a few more words here to indicate that I don't just mean that as a polite sidebar; it really is an interesting thought. There may be something there.

But as presented, the code complexity scales like a nightmare; it makes the worst Ruby monkeypatching look sane. Something would have to be done about that before even a toy implementation could be done, because this will fall apart very quickly.

When you give away structured programming, you give away its benefits too. One of its benefits is that in a structured program, you can freeze a thread at any point and you have a clean mechanism for determining from there what its stack trace is, and all the relevant scopes it has access to and could be affecting it. In real code, this process may produce a very large number of variables and stack levels, but it'll still be a fraction of the program's possibilities. This is how structured programming helps us approach programs as structured slices of the code base, instead of a holistic view of the entire code base at once (this is the true reason goto-based code was so evil in the day; you could never do this analysis). This approach throws this away. That is not intrinsically wrong. But I'm not convinced at this time that the compensating features we get make up for losing that clarity, especially because the benefits are going to have terrible scaling problems as presented.

If someone was going to pursue this, this is the angle I'd take; how do I freeze my program and determine what is affecting the behavior of the current execution trace? Assume an arbitrarily powerful debugger attached to your running process, as long as it doesn't "magic" anything into existence. I can see sketches of ideas in my head, I am by no means saying this is unsolvable. But I think it's something I'd need to see laid out a bit more before I got too excited. To anyone thinking about this, I'd advise you to also not forget scale. Anything works for 100 lines of code. I need you to present me with something that can make sense of when I'm running, let's say, thousands of these advisory functions at a time on a single question. Structured programming has an answer to that; being a thousand layers deep in a stack trace may be a lot for a human to take in, but nevertheless, the procedures that structured programming provides will still give you answers. (And I'm not asking for the solution to work any better than structure programming does in that case. Thousands of anything is irreducibly complicated. But it needs to at least give me understanding in the ballpark of what I have in a thousand-deep stack trace.)
NflxMultiSubs is still working. I wrote a patch to fix it, and took over maintence on Chrome.

https://chrome.google.com/webstore/detail/nflxmultisubs-netf...
Interesting project and I like the name. It seems that the underlying relationship in each data source has to be relational though (even for JSON files) - is that a fundamental limitation of using SQL as the glue language, or are there plans to integrate hierarchical models of data in some form as well?
> But what happens if after "/p/" you put A, B, C and so on? It appears that you can find the first 28 posts of the social network.

Maybe I misunderstood the phrase, but how can you get 28 posts from 26 letters? the article doesn't mention lowercase letters
Federally funded Unimax smartphone pre-loaded with malware
Reaping the Rewards Of Risk-Taking (2011)
> The diagram shows each core has icache and dcache; what they've ditched is cache coherency.

This is not quite true: the local data memories are not caches, i.e., they do not implicitly move memory in from a more distant tier in the memory hierarchy. They are just plain explicitly managed local memories (sometimes called "scratchpads" to distinguish them from caches).
Containers are a mild improvement over existing technology. Nobody cares whether your cloud provider uses containers, older tech, or newer tech.
TrickBot hackers create new stealthy backdoor for high-value targets
The connection would prevent it from starting up for me because it verifies the license each time you start the program.

Neither vectorisation, nor batch macros (nor iterative macros) allow you to run the same set of commands until a condition is met in Alteryx.
13 investments in a year is incredible. Plus they'll create more value in $2M than Vision Fund will in $108B.
> I know it's an unpopular opinion but I don't see the point of kubernetes. It's a complexity monster which is not providing any real advantage over way simpler solutions.

The main selling point of k8s over any other tool is that it provides a single, unified, secured, multi-tenant API endpoint for managing all of production. Your developers updating their production app use the same API as a CI system that wants to spawn some worker containers, and the same API as an operator service maintaining a Redis cluster. All of this results in a single view into production. If things go well, the end result is that you swap daily interaction with a handful of different tools with disparate states (Terraform, Ansible/Chef/Salt/Puppet, shell scripts and proprietary tools) into just managing payloads on k8s.

> Even pod to pod communication, which would be trivial to do using any sane solution is a huge pain in kubernetes.

How is it a pain? A pod behind a service provides a DNS name that allows running requests to it - this handles the bulk of production traffic. If you want to contact a particular pod that is not behind a service just use the k8s API to retrieve details about it (like Prometheus does via k8s pod service discovery).
but swarm mode is now part of "regular docker"
This is simply untrue. The great thing about being bald is you can never have a bad haircut. Bald men, like men with long hair, or women with really short hair, appeal more to some people and less to others. But there's definitely no need to conclude you're screwed.

Physical attractiveness also matters way less for men in general. Personality and lifestyle are much more important.
Actually, Hossenfelders great fight has been with the concept of "naturalness", a fight that has now been won by the LHC killing off all the theories based on that concept.

And it wasn't ever so simple as "chasing mathematical elegance instead of trying to explain observations", the problem has been that there was a theory that could explain almost perfectly everything within a certain region of physics, but can't easily be extended.

Thus you work on crazy schemes to extend the existing theory (all the sensible ones already having failed), or you are forced to make an entirely new framework, and that takes a lot of work before it's finished enough to even reproduce the results of the limited theory.

If you take the second route, you are very vulnerable to the "chasing mathematical elegance" slander, but it's not like the other guys are doing any better: there aren't actually any unexpected observations that need explaining within the reach of the existing theory.
1. no garbage collector

2. No tail recursion

3. There is no cons, cdr or car stuff. Lists are just vector objects and you use push, cat, slice etc to manipulate elements.

Only this much is radical enough to say that it isn't a Lisp but disguised in Lisp syntax. Lisp is as much about semantics as the syntax. The power of Lisp to do amazing things comes from the language capabilities. If you cannot reasonably translate powerful programs from Lisp textbooks, then is it a Lisp?

Some languages (example: JavaScript, Python) make it easy to create an inefficient Lisp interpreter that could execute common textbook programs. Minimax, A-star search, unification matching, etc.
> The ability to have multiple applications running simultaneously on a host without having to know about or step around each other is nice.

If you're running containers, you get that for free. You can run containers without running Kubernetes.

And unit/init files are no harder (for simple cases like this, it's probably significantly easier) than learning the Kubernetes YAML DSL. The unit files in particular will definitely be simpler, since systemd is container aware.
Glutamate Built the Brain–Can It Treat It Too?
Where are you living where modems die every 2 years? My cable modem/wifi router from ISP is about 5 years old. Can't use your own cable modem in UK. They don't list providing of the modem as a line item on the bill either
Ah, so it’s all about some twisted sense of fairness? If things suck for some, they should suck for everyone?
Business services generally need high availability goals, so often that doesn't cut it. And your single server doesn't autoscale to load.

AWS gives you availability zones, which are usually physically distinct datacenters in a region, and multiple regions. Well designed cloud apps failover between them. Very very rarely have we seen an outage across regions in AWS, if ever.
Tesla Surges Above $500, Leaving Analyst Targets in the Dust
Not everywhere I assume, my grandfather worked 20 years as a miner in Belgium and his employer left the housing to the city only if they will let the miners stay there for a symbolic some (+-50€). Once the owner died the city immediately tried to change the rent to 500€, but the local miners union fought it and kept the old rent until the union chief died also of old age. There were no one capable of Fighting the legal battle. Basically the city ignored the owner's will to profit from coal miners.
Unfortunately, I do need to go to work if I'm interested in continuing to live.
Did Astronomers Just Discover Black Holes from the Big Bang?
I believe I said that. You might be confusing the reason for various sciences to get stuck with the mechanism of how they actually get stuck. The reason is that groups of people have common characteristics over time. As for the mechanism, I'm with you. Always assume the simplest explanation unless there's some evidence otherwise. Missing the "mental tools required to do the work" can be as simple as not being popular in your field of study, or a character unable to get funding or provide the oversight of funding that is necessary for your science to advance. I believe if you understand the reason, you realize that you could very well end up playing whack-a-mole simply by trying to fix the various mechanisms. That would be a tragedy.
I like that only permitting writes to other cores' memory simplifies the design. If you want to read, you have to write a request to that core by storing the request in a place it will look, and tell it where to put the answer. And, all the cores heve to check for such requests.

It is kind of surprising that that is acceptable. I suppose the usual case is that each core already knows what its neigbors will want to see, and sends those values before each neighbor needs them.
Chafa: Pictures to Text
The Next DARPA X-Plane Won’t Maneuver Like Any Plane Before It
Sometimes std::lock [1] is a solution: "Locks the given Lockable objects lock1, lock2, ..., lockn using a deadlock avoidance algorithm to avoid deadlock."

Of course this only work if all locks you need to take are exposed and not hidden behind some abstraction. Then again, when they are it is hard to make sure you only take one lock at a time anyway...

[1] https://en.cppreference.com/w/cpp/thread/lock
Amsterdam works because it's a very flat and very dense city. I bet there are potential candidates in the States, but not as common as you would find in Europe.

About the density, everything is just closer together over here. Public transportation is well-built and trains work great for anything further than that. Cars are mandatory by design in the US.
Usually involves talking with someone on the architectural level (Chief Architect, maybe CTO, VP or head of engineering if knowledgeable enough). Then involves onsite visits, questioning about where the data is hosted and factual verification of these claims.

Depending on company size/challenge, you might do some tests on their claims from the outside over the period of 24 months. For example, registering an account and then verifying if that one-time email got leaked into some other service.

Or, on cases of higher-criticality you will have monitoring of what data is coming out from the datacenter where the apps are running.

Direct access to source code reviews is rare. Albeit depending on the level of cooperation it could be a possibibility.
If you mean hierarchical data querying (like nested json, or json in sql rows), then that's very high on our radar.
Agreed. I was referring to breaking into sell-side from outside Wall Street. Apologies for the confusion.
A couple of things:

- the 'noon' photo is taken at night

- the '10:26am' photo shows shadows on the windowsill from the south and west - Pier 38 runs almost west->east from shore. (something on the shore reflecting light? I'm assuming the stronger shadow is from the sun). Popping the date and time into a shadow calculator shows the sun would have been positioned above the south east corner of Pier 40 from that window - which couldn't have cast either shadow. I used http://shadowcalculator.eu/#/lat/37.78196555892351/lng/-122.... to check. The 10:26 photo does look more like it was taken around noon.

So, as others have said, these are upload times not when the photos were taken.
Show HN: Renderproxy – Make your app crawlable without a line of code
Did it? It was pretty damned obvious what had happened.
Point taken.
However, the part about "why not kubernetes" reads:

[...] we started adding ever-more complex layers of logic to operate our services.

As an example, Kubernetes allows [...] this can get quite confusing [...].

[...] this can lead to tight, implicit coupling between your project and Kubernetes.

[...] it’s tempting to go down that path and build unnecessary abstractions that can later bite you.

[...] It takes a fair amount of time and energy to stay up-to-date with the best practices and latest tooling. [...] the learning curve is quite steep.

So in short "it is complex so this and that may happen if you don't learn it properly".

Ok, this reasoning applies a-priori to any tool.
Continues Its Reign as the Smallest Known Prime Number
Supreme Court Declines to Consider Medical Diagnostic Patents
That's an extremely watered down definition of "right connection." My brother is at JPM/MS/GS. We're immigrants, we grew up outside of New York entirely outside of the finance orbit, we went to public K-12, etc. He got into an Ivy-league school because he's a nerd who always turned in his homework early since age 6 and prepped hard for the SAT. I was the one who gave him advice on "which fields to study" and "which companies to apply to"--based on nothing more than doing some research on internet forums. (He was originally planning to go into a PhD program in STEM, something we had exposure to from our upbringing.) The interviewing process didn't require "know[ing] someone at a firm." The companies came on campus and interviewed the STEM nerds with the highest GPAs. The process isn't easy, but it's highly structured, and meritocratic for some definition of meritocratic.[1]

[1] I think its more accurate to say that the field requires lack of significant adversity more so than "connections." The median family income at Harvard is $168,000, the 80th percentile. These kids aren't working all summer to help their parents make ends meet. At the same time, their neighbors are engineers, doctors, government employees, etc., not hedge fund managers.
A good sentiment which doesnt work when bad faith actors take advantage of openness to capitalize on the race to profitable product by standing on (and not sharing with) the folks who struggle with and funded the enabling R&D. Free and Open Research is Knowledge as a Commons, and is just as vulnerable to bad faith actors as any other Tragedy of thr Commons.
This is amazing!

So somewhere pi is a computer program that when run would set up a server with an entry for every person that has ever lived or ever will live with complete information on that person. You could theoretically see a real-time movie of anybody from life until death. Crazy!

Do you know if k has to be finite?
.... Didn't expect a random data dump
> But you do see how the industry is struggling with certain problems: We are now with kubernetes moving into a cloud native area.

We were were moving into a cloud native era way before Kubernetes.
yup lots of love for visidata, a nice quick way to eyeball data and then munge: https://visidata.org/docs/join/ before proper carpentry with pandas.
Sure. But typically a to do list app is going to take a lot less time to MVP than an Airtable clone, for instance.
>To acquire hundreds of acres of prime land suitable for an urban environment

Land isn't really the issue. You do need access to water and you probably don't want to be too far from an existing road network. The bigger problem is bootstrapping an environment where people would both want to live and where their would be employment opportunities.
The "No Code" movement is not a delusion. Most of us in tech are very ego driven and don't think this will happen, the majority is not in tech and want this to happen. It will happen.
Ask HN: How to build a Facebook-like newsfeed?
I was just discussing with a friend how to build a newsfeed like Facebook, Twitter et al that (seems to) take into account what you are interested in but also what is popular among users you are connected to.

Do you know any pointers on where to start may it be books, articles, tech talks, research papers or insights (e.g. related to user experience, weighing, …).

Any pointers more than welcome.
Well ackshually... :)

Shout out for the deepest hand dug well: https://www.mybrightonandhove.org.uk/places/utilities/woodin...
Pathways that extend lifespan by 500 percent identified
It doesn't matter if it's a manager or your peers, you shouldn't have to justify your work every single day.

It's childish and immature and if you for some reason need to do it to be able to communicate, learn how to communicate properly, don't foist your miserable way of working on others.