skysight-inc/HackerNews huggingface dataset:
Likewise, you make it seem like ISPs are competent enough to recognize an attacked modem, and repair or replace it on demand, and promptly. My experience is that when your internet connection goes down or becomes unusable, and you call and complain, it can be literally several weeks before they even respond to you.

They may technically own the modem but you’re in your own to keep it running.
First off, this borehole isn't that deep. Over the continents, you'd need to drill to 40-70km to reach the mantle (sometimes even 100km). However, oceanic crust is much thinner. It is technically feasible to drill into the mantle in ocean basins, where the mantle can be only a few km below the seafloor.

Regardless, the mantle isn't molten. It's different types of rocks, but they're still rocks.

In fact, the mantle is exposed at the surface in a handful of locations (and a good chunk of the ocean floor). We have learned a lot from what's exposed at the surface, but these rocks have been significantly chemically alerted. Many of the minerals we expect to be there are unstable at near surface conditions. We'd learn a _lot_ from "fresh" mantle rocks

If you were to maintain the same temperature but drop the pressure to surface conditions, yes, deep mantle rock would melt. A hole with nothing in it going deep enough would cause a volcano (even if it didn't hit the mantle). However, not all of the mantle is hot enough for that to occur. (Again, the mantle is quite shallow beneath the oceans) We also have to keep the pressure at the bottom of the hole the same as the rock around it, so a well doesn't usually release pressure.

At any rate, in any case where you'd try to drill into the mantle, it would be impossible for a volcano to form.

All that having been said, geothermal drilling in Iceland has hit magma chambers by accident and caused a "mini volcano".
Most of them are. Quant jobs are often highly academic. Basically the same project structure as FAANG but never any deadlines.

Banks are where the arbitrary high stress jobs reside, and then certain specific companies that choose to enforce stress culture, like GSAM and Citadel.

But most have normal 9-5 hours, few deadlines, autonomy, project self-selection.
Hey, it sounds like you're still programming. Glad to hear it's going well!
Tesla tried to warn them that exact science is not always an exact science.
Why 'Autos Plus Tech' Is the Best Path for Automated Vehicles
“Significant mistakes”: MIT releases details of Epstein funding scandal
You nailed it in the first sentence. The blog post pretty much boils down to "k8s looks good but we were too lazy to learn how to use the thing, so we opted into something else".

Fair enough, legit argument, but trying to make a "counter-k8s" case based on that is not very convincing.
This. If we assume we're talking about the order of 10,000,000 tons, of which 10% didn't detonate (this is roughly accurate for bombs & shells, mines are much harder to quantify), then that left 1,000,000 tons of UXO.

If we assume (somehow!) half of that was dealt with quickly, that leaves 500,000 tons of UXO. If we assume 1000 tons are found per year, that's still 500 years to tidy up.

Across both wars the total may well be closer to 100M than 10M, so then that makes it 5000 years.
Car manufacturer's vision of the future seems likely to be something less than wholesome given what people need. My guess is this will be a city where everything is made to measure the environment, and the consequence will be that everything, including its occupants, will be managed in a way few other cities ever have been.
> What actually is the foundation of physics?

See Naturalism:

> 1. that there is an objective reality shared by all rational observers.[20][21]

> 2. that this objective reality is governed by natural laws;[20][21]

> 3. that reality can be discovered by means of systematic observation and experimentation.[20][21]

> 4. that Nature has uniformity of laws and most if not all things in nature must have at least a natural cause.[21]

> 5. that experimental procedures will be done satisfactorily without any deliberate or unintentional mistakes that will influence the results.[21]

> 6. that experimenters won't be significantly biased by their presumptions.[21]

> 7. that random sampling is representative of the entire population.[21]

* https://en.wikipedia.org/wiki/Naturalism_(philosophy)

Some other approaches:

* https://en.wikipedia.org/wiki/Philosophy_of_science#Current_...

Basically you have to make some metaphysical assumptions before doing science can even get off the ground. If you believe that reality is an illusion (Buddhism? Hinduism?) then you're less likely to be interested in understanding the world's workings. If you think that things occur for capricious reasons (e.g., pagan gods being the cause of things), then there is no reason to ask "why?". If things happen not because of inherit properties but because of God's Will (Occasionalism), then who can understand the mind of God?

I've heard it argued that science mostly developed in (Western) Christendom because it brought together all of the above assumptions under its Aristotelian world view. If you look at the invention of the telescope in ~1600: it spread over the world with-in a couple of decades, but most cultures weren't really interested in it.
13 Minutes was incredibly well done. A limited series best listened to from start to finish, so fair to recommend it in its entirety. For those in this audience looking for a gem: Episode 5 is about the Apollo Guidance Computer.
Well, there's a theory the earth is hollow and inhabited by dinosaurs and aliens, too. ;)

I think the best argument against abiogenic petroleum in the mantle is that if the theory had any merit Exxon would have figured out a way to bore into the mantle decades ago.
My team's code hasn't been able to run locally for at least 7 years. All development consists of committing changes to SVN trunk and running a Hudson build to update a shared dev server. We have hundreds of commits per day, mostly with unhelpful messages like "up".

halp
There are declarative general purpose programing languages.

That data you are talking about does need to be debugged, like Helm charts and pipeline definitions. Sure data is better, but config is code, not data.
Three simple emotional and pleasure things to give your wife the maximum orgasms
There already were a few of these in C++, most notably the tensor contraction engine. Mine was written in mathematica.

https://github.com/jparkhill/Symbolic-Many-Fermion-Codes

I would love to see one in rust there'd be real advantages for asynchronous parallelism in some of the most sophisticated models.
Drawing an elephant with four complex parameters
In my experience, "Low Code" is almost always weasel-wording. It's used to describe products that try to be "No Code", but fall short. It's a way of making excuses for everything you can't do, because you can get a "real programmer" to come in and paper over the cracks. Actually writing this code is rarely a pleasant experience, and the learning curve is a cliff that goes straight from "flowchart" to "writing React" (or worse).

As other replies have pointed out, the really successful tools are like Excel: They have a real programming language at the heart of them, and they don't try to hide it away.

Disclaimer: I founded and run something you could call a "Low-Code web environment" (https://anvil.works) - but I prefer "Visual Basic for the Web" (or "Web Apps With Nothing but Python"). We built it around the idea that writing code is inevitable - indeed, it's the best way to tell a computer what to do. So don't try to hide it - make it a first-class experience!
I wonder if by the time it gets through 3KM of the relatively thin diameter borehole if it cools and hardens enough to just plug the hole with rock?
> Disregarding of Swarm's merits why would anyone care what Mirantis has to say? As any other vendor Mirantis has its own agenda and promotes their vision of cloud stack. Does not mean it is the best solution for any particular user.

Because Mirantis now owns almost all of Docker's IP. https://news.ycombinator.com/item?id=22035084
cool, good job. psoriasis is a bad disease.

I hope they use their genetic data to develop more drugs.
NoSQL is definitely not obsolete. When you go to Amazon its not looking in PostgreSQL for your shopping cart, its looking in Dynamo. As someone who previously worked in Fortune 10 company, I can tell you that most production APIs were being driven off of NoSQL or were being migrated to NoSQL (specifically Cassandra and ElasicSearch).
It is a type of wealth. There are different kinds of wealth. Having a good, supportive family is a type of wealth. Being born in a country with plentiful drinking water and other natural resources is a type of wealth. Being able to sell your services is a type of wealth. Having a network of contacts in many places around the world is a type of wealth. Learning how to do something is also a type of wealth.

Some wealth you’re born with, or you come by from circumstance (many times relating to who you’re born to). Some wealth you can work on obtaining yourself.
Some miscommunication here. TFA doesn't distinguish between Oracle's ZFS and the Solaris fork, OpenZFS. Linus seems to be making comments about the former and is likely mixing up a few details about ZFSonLinux. His non-maintenance comments also appear to be about about the fork and probably mean "not keeping pace of feature parity with ZFS proper", which it doesn't.

I think he's just baffled by why anyone would expect the Linux kernel to make a special exception to support ZoL when there are already great native tools and the BSDs exist. And if you really need production ZFS, why not just buy into the officially maintained version from Oracle because you're not getting on-call support, paid or otherwise, from the open projects or Linux.

Largely, the article contains no impact or petition and reads like a click-trap set with Linus bait by someone with a real interest in defending (Open)ZFS's cult status as the pinnacle of all filesystems. I use ZoL at home, but it's not something I'd expect to see above SMB.
Protective IP on medical research probably means more investment is done in medical research.

The recognition of private property in intellectual endeavors necesarily means that more capital is invested in intellectual endeavors.

Personally I think that creating an artificial wall to make more people devote time to entertainment, or certain research, etc is pretty dumb and would be better not to exist at all.
Most frequently checked-out books in the history of the New York Public Library
"BTW, learning Kubernetes can be done in a few days. " - Learn something in a few days and the ability to run it in production are completely 2 different things. Security, upgrades and troubleshooting cannot be learned in couple of days.
> its apps don't waste CPU time or memory while not active
The 20% of my battery used by Google Play Services, despite the fact that the only Google service I use on my phone is YouTube, disagrees
Consume Any HTTP Service from Laravel
> Kubernetes is really really cheap

In terms of infra costs, I can believe it. But what about engineer resources to setup and maintain your infra in k8s clusters?

Where I work, we have a full time DevOps team that's almost the same size as the main product teams. That's really not cheap.
> you will be shocked how poorly they look and how far we have come in terms of the quality of Instagram content.

pics of photoshopped faces and body is quality content of instagram
http://archive.md/Iu1lO
His point is a bit deflective of the issue. They intentionally disabled api to my understanding for non GPL modules that zfs on linux relied on. No one asked for ZFS to be integrated in linux.
I hope someone with better understanding than me can confirm or infirm.
Apple’s repeated engineering failures (2018)
It's funny we use GKE and coudn't be more happy, once your CI/CD is setup you don't have to think about it and makes your developper life much much easier.

I don't even think for one second to go back to uploading tar.gz or DEB / RPM using scripts / puppets ect ...
For Fluid Equations, a Steady Flow of Progress
I've been using Docker Swarm in production for about 2 years now... processing about 1TB of data / month across 30+ containers. The networking and routing has been rock solid except for that one day that the Docker dev team, in one release, accidentally added random hashes to the internal DNS names of services. Ever since that day I've used the docker-compose network alias for internal routing https://docs.docker.com/compose/compose-file/#aliases

Discovering bugs in a technology you just started "looking into" actually sounds like the learning curve.
It gives you good abstractions for your apps. I know exactly what directories each of my apps can write to, and that they can't step on each others' toes. Backing up all of their data is easy because I know the persistent data for all of them is stored in the same parent directory.

Even if the whole node caught on fire, I can restore it by just creating a new Kubernetes box from scratch, re-applying the YAML, and restoring the persistent volume contents from backup. To me there's a lot of value over init scripts or unit files.
I doubt it was as cheap here in Mexico.

Currently the cheapest iPhone here is the iPhone 8 4.7'' and it costs about $550 USD.
Have you noticed a noticeable difference between Trikafta and the drug(s) that you were taking prior to this?
A project I'm using, which I'm also one of the authors of, is OctoSQL[1].

It allows you to transform and join data from different data sources (including databases like mysql, postgres, redis, and CSV or JSON files, more to come) using a familiar interface - plain SQL.

Other than that, I like Exploratory[2].

And for nested JSON data I use another project of mine, jql[3] - an easier to use (in my opinion) lispy alternative to jq. (originally inspired by a hackernews comment actually)

[1]:https://github.com/cube2222/octosql

[2]:https://exploratory.io

[3]:https://github.com/cube2222/jql
You might find this helpful: http://languagelearningwithnetflix.com/catalogue.html

"Netflix usually has good subtitles for the original language of a title, that match the audio track. Subtitles often don't match the audio for dubbed audio.

The catalogue lists titles by their original language. It allows you to find French films, to study French, and German films to study German etc. By using one of the listed titles, you should have good subtitles that match the audio."
All of this glosses over the biggest issue with Kubernetes: it's still ridiculously complex, and troubleshooting issues that arise (and they will arise), can leave you struggling for days pouring over docs, code, GitHub issues, stackoverflow... All of the positives you listed rely on super complex abstractions that can easily blow up without a clear answer as to "why".

Compared to something like scp and restarting services, I would personally not pay the Kubernetes tax unless I absolutely had to.
Based on my experiences, in the very beginning of your day at the office, I'd recommend to tackle the work item which has the most odds of being completed in a certain time frame.

Let me elaborate - If you have a TODO list of N work items that could belong to one or more of -
Set A - require more thinking
Set B - require larger communication overhead
Set C - have a clear go-to strategy and can be broken into multiple items

Then, picking up the items more inclined to Set C right after you reach the office might be a good strategy.
The obvious reasons are a. you know what to do and b. you know how much time its going to take
They are not good at updates, though.
Could be, generally speaking is difficult to get the right subtext from just a couple of sentences.
Yes, this was my problem.

OSX ish solves it, you still have to split the machine memory between docker and OSX manually. For example, if you want to run for example a big integration test that needs lots of ram you have to tweak it and then put it back. With Linux it's automatically managed.
I can't find any pricing page for Profitwell
Ok, if two processors read/write the same address what happens? Could I assume the reads are coherent but writes are not?

If this is the case then I assume I'd just need to design-wise restrict one processor from writing to another's area, yes?

I've worked on worse. Quite promising set of ideas from my limited reading.
> but we were too lazy

This is unnecessarily dismissive and contributes to what makes HN a toxic place for discussions. They've already addressed the reasons.
Mental Health in Remote Teams
It seems counter-intuitive to use a large amount of water on top of the borehole filling material. If some radiactive waste gets past the filling material, particles may rise up in the water all the way to the surface.
What about sequential locking/unlocking with consistent locking order for all resources? I was under the impression that this solved the deadlock problem but I haven't yet tried it in practice.
Because under the law, it didn't produce the work.

Look at all the AI-driven visual art we're seeing happen. Copyright goes to the artist who set up the system and then selected the work, because that's the actual creative activity.

Creators have always used tools. The tool isn't what gets copyright, no matter how elaborate the tools. Once the tools have consciousness, drive, and self-determination, we might think otherwise. But that's not where we are today.
> Mandating that all phones must have a headphone jack would make sense if manufacturers omitted it for anticompetetive or other nefarious reasons, knowingly acting against the interests of their customers.

I guess that's a matter of opinion, because I am convinced that this is exactly what happened. Apple sells dongles for money and also makes money on Lightning licensing.
Its just docker, your containers remain exactly the same only the orchestration changes!
I'm not sure what you're talking about, here. Used to live in Nagoya and have been to Toyotashi many a time. It's a pretty average small Japanese city.
Not nearly as scary as https://en.wikipedia.org/wiki/Ocean_disposal_of_radioactive_...
FWIW subtitles for the original language will also sometimes vary from the original audio as well. I tend to re-watch shows on low volume with subtitles on so I've caught this a number of times, but it's fairly rare.

Usually I've seen the subtitles shorten the words in the audio. "You must come with me now" -> "Come now" or similar. I've been assuming it's to help the reader keep up with some quick exchanges.
I really like R / Tidyverse, but that requires that you have more memory than your datasize (especially if you are using narrow and long dataframes, such as recommended by tidyverse) and it also requires you to code, instead of using a UI
You are honestly the first person who has been able to articulate this issue to me. Thank you.
Agreed. At this point HN could have a post about the merits of plain old dedicated servers and it would seem novel.
Most likely they themselves adopted a previous "cool" technology that later bit them after dying off, or being realized as just another fad. I think that apprehension of a new technology is a healthy, pragmatic response in most cases.
Wow. Can you take a byte for byte copy of the shared dev server and make a VM image or something?
This post should probably have (2019) in the title.

I'm the Nomad Team Lead and can try to answer any questions. Since this post was made the team has expanded, and the task/job restarting issue they link has been (mostly) addressed. Also new since this post is our Consul Connect integration which can accomplish similar goals to k8s network policies, albeit opt in and with the actual discovery/networking code living in Consul/Envoy respectively.
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.

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

I would actually be frightened by running kubernetes in production. The simplest things are so hard to do that I don't even want to think about how to fix a weird issue when something goes wrong...
Yes the database is on the same instance. The biggest downside to that is my droplet gets low on space as the database grows but so far it hasn’t been too much of an issue. The growing need for SSD space has pretty much matched the growing need for RAM as I increase the droplet size.

For backups: I have a bash script set up every night to run a pg_backup and send it to an S3 bucket where I store the last 7 days of backups. All static files (images mostly) are hosted on S3 with no real backup but that works fine for my particular use case.
Be warned that one of the worst ways to learn a language is through translations. Most translations leave out a bunch of information because between connotation, denotation, and grammatical correctness you can really choose one or two of the above. That's in addition to the fact that most translations are either produced by machines with no understanding of the content or even of the complete grammar of the target/source languages, or mechanical turk style low wage laborers with tight deadlines and questionable knowledge of either languagr.
Queues are my advice. The locking is all in the queue operations. Everybody else just takes and posts work items to the queue. Can even use lockless queues.
If you don't need container orchestration, you don't need kubernetes. If you need reliability and instead of using k8s, orchestrate your container manually you have issues.
Storing in salt domes is easier. Salt domes are completely impermeable because any incipient cracks creep close.
Think it really depends on where you land. I think everyone agrees that Google is easy-mode; beyond that, it depends on which group you're in.

Two friends at Apple illustrate: one says he does basically nothing but surf the web, the other last I heard is is nearly sleeping under his desk in a crunch.
> Thank god trends like Pulumi and the new AWS sdk is emerging.

The more things change, the more they stay the same.

The pendulum is swinging back towards scripting languages. But give it a few years, and we'll be railing against scripting languages for not being idempotent enough, and moving back to the latest version of YAML and XML (perhaps we'll go with TOML this time) with custom interpreters.

We have seen this half a dozen times already, between turing complete DSLs in ruby, to plain bash, perl, and python scripts. The other side are the DSLs written using YAML, JSON, and XML (and every other config language written in history).
You give yourself far too much credit. Quoting your own words back to you isn't stalking. You're the one who claims to make a point of wrecking havoc with users on purpose. If you didn't want what you said coming back to you, you should have deleted that posting, or not written it in the first place.

You were wrong and weren't able to support your views seven months ago, and you're still wrong and still can't explain yourself now. In the intervening months have you made any progress in changing even one person's mind not to use spaces in their file names? It would have been a much better use of your time to learn Python or JavaScript in those seven months, since it's bash that's actually causing you problems, not the people who use spaces in file names who you're so compelled to punish.

Back to your argument -- go ahead and state your views: what is your evidence that "Filenames are the variable names of shell scripting"?

Have you submitted pull requests to the Linux kernel and bash and any other affected libraries and applications to eliminate spaces from file names, and have they been accepted yet?