skysight-inc/HackerNews huggingface dataset:
For all of that theory crafting you forget the person holding you at gunpoint is emotional as well and would just shoot you for having ruined their chance to get money. What use are you to them at all now?
> Any benefits to the build-in-container approach that are compelling?

The build in container approach makes it so that in theory you have reproducible builds too from any Docker supported machine. I personally like this approach because it makes it so that you don't run into the case where "It works on my machine" when testing locally.
I remember in those days there was a lot of "demo scene" music that was traded electronically. Not usually by floppy disc, but, well, it could have been.

(Surprising no vaporwave artists has gone this route: release a vaporwave "album" on floppy disc, done entirely in ScreamTracker, and recommended to be played ideally on your Gravis Ultrasound...)
We considered it, but at the time we just felt implementing map/reduce over Lambda would just introduce a more complex architecture for such a simple problem.

Maybe the recently introduced SQS->Lambda support might make it a bit cleaner, but in the end we opted for EC2.
The estate is liable but the lender may not pursue it. When my Dad died with a couple of similar credit card debts they were immediately written off. Maybe because chasing elderly widows isn't a good look.

Though comments elsewhere in the thread suggest that American lenders don't have these scruples.
I don't think it is at all clear that an engineering solution here is a priori a bad idea. It is possible that an organization that can land rockets standing up has better than average engineers.
Yes, this awful engineering team built an incredibly successful company/product. I wish I was as awful as them.
To be blunt, its news to a lot of people, but it also isn't wrong. Microservices really shouldn't share a database, and if they do then they aren't "microservices".
Things are going to get a lot worse before they get better, if ever.
‘We’re going after Tesla’, says Fiat-Chrysler with their new EV plan – Electrek
It depends how much you want to spend.

WholesaleInternet.com I have used for their dedicated servers, but they also have inexpensive colo. The guys at HandyNetworks.com currently have some colo of mine, they have good quality hands-on help (their office is right beside their colo); they are more expensive however.

Check with WebHostingTalk.com and look for good reviews. Warning: always deal with either the owner/tenant of the colo or no more than 1 step removed; you don't want to be renting space from a reseller of a reseller: if someone in the chain goes under and hasn't paid for a few months, it will be a nightmare for billing and you may have trouble getting your hardware either turned on, or returned.
Vaporwave is a huge genre which covers a wide range of styles. Here are two favourites which show different styles. From down tempo electro: https://www.youtube.com/watch?v=8GW6sLrK40k to new reworking of 80s pop songs: https://www.youtube.com/watch?v=jynPLTeBaFc

The main thing that ties in the different styles is the slight feeling of nostalgia and the internet subculture central to it. The playfulness with the subculture is a core element of the subculture. "Vaporwave is dead" is an example of such. It's post-hipster in a way as hipsters are too serious, always searching for the authenticity, where vaporwave will copy and rework stuff. It's kind of close to the way Discordianism worked - is it a music genre thats disguised as a joke or a joke thats disguised as a music genre?
If you're going to go microservices, you want service A to use service B's public API (MQ or RPC or whatever), not to quietly depend on the schema B happened to choose. And sharing a database server instance turns overloads into cascading failures, unless the stack is very good at enforcing resource limits on noisy neighbors.
Fair, I concede that. I still maintain that OP's statement contributed nothing of value to the discussion.
I mean you can just walk up to it - you don't need to hike anywhere. It's in the middle of urban environment. It's not somewhere in the wilds.
A Landmark Legal Shift Opens Pandora's Box for DIY Guns
A number of comments touched on this, that microservices are also an organizational strategy: you have a team that manages that particular service.

My company is probably typical in that we implicitly use microservices because we have consume dozens of microservices provided by other companies.

We only have a handful of services we maintain, each with dedicated engineers.

And what becomes a service? You want to answer two questions:

1. Does it have a concrete business justification?
2. Does it have clear functional requirements?

If it has a business justification, it will get people assigned to keeping it running. If it has clear functional requirements, it will make sense to the people working on it which service does what.

That's still pretty vague, so you want to look at who has done it well, and why it worked for them.

Companies like AWS have been extremely successful in using microservices because every last one service has a business rationale, it's either directly making money (EC2, S3, SQS) or it supports the needs of customers who are using a service that makes money (VPC, Cloudformation, all their internal auth, billing, provisioning, security and such).

The caveat there is that the big B2B service providers are not a great model for companies that have a lot of business logic.
For starters, the sudden loss of all modern computing would cripple oil extraction, transportation, and refining for years on end.
Uh, the only way to test this scenario is to make someone die.
Which is why keeping your keyboards wiped down (I use baby wipes) isn't just for compulsives.

It's a hygiene and security best practice.
I'm not sure you understand how the GIL works in Python. If you're using multiprocessing, there's no locking across the code executing on each core. Also, if you're writing to the same file from four processes, you're going to need locking.
> Nobody gets a pass to buy free stuff with their credit cards before they die.

While they don't "get a pass", this is something that happens - credit-givers know this and the risk is baked into the price and amortized over the entire card-holding population. A lot of people have delinquent debt and some choose to declare bankruptcy.

How do you repossess an expensive luxury cruise, or a stay in Vegas? Some debt is just written off.
Absolutely. The feeling of building things from scratch that people actually use - it never gets old.
Do you realize that this is actually an anti-pattern, that adds unnecessary complexity and potential security problems to your app? Test code must be separated from production code - something, that should know every developer.
Surely this is "no true scotsman"? They've tried microservices and it didn't work for them, you're saying that if only they'd "fixed" their micro-services architecture it would have worked?
Sometimes, I've seen a lack of regard for data consistency within a monolith.

That is not completely on the developer, either. Pre 4.0 Mongodb, for example, does not do transactions. On the other hand, I've seen some pretty flagrant disregard for it just because there are not atomicity guarantees.

Microservices makes reasoning on that harder.
Is the balance of your bank account recorded publicly? So it seem there is no need for a public record.

And GDPR does not prohibit voluntary owner entries into a central whois directory, it just prohibits transferring personal data without consent.
>The first item on the list was to consolidate the now over 140 services into a single service.

software engineering walks in circles. NoSQL people seem to be growing up and learning about consistency and transactionality. I'm waiting for somebody to discover threads and shared variables back as a revolutionary way to improve performance and greatly simplify the implementation of a system of "actors".

Joking aside, i think greatest reason for Segment's microservices failure was that they didn't use Kubernetes.
It's not giving that's the problem. The problem is in misuse of the donations. Your link does classify it as a myth but I live in a developing country and I can attest to the fact that most aid money donated by Western society either gets misused or swindled unless it's through proper channels. Finding proper channels is not as easy as you think. Even reputed organizations have been caught misusing funds:

(1) https://timesofindia.indiatimes.com/india/foreign-funding-of...

(2) https://www.oneindia.com/india/crackdown-on-fcra-violation-n...

(3) https://www.socialpost.news/national/modi-govt-cancels-licen...

If you truly are a "noble charitable cause" then there is no reason to hide your source of funding. Majority of these NGOs (Charities are classified as Non-Governmental Organizations in India) haven't filed their annual returns since their inception. So basically it's unaccounted dollars free-flowing into the country with no mention of source or the purpose for the donations. It could very well be money-laundering or for other ulterior motives. That can only be dispelled if the NGOs filed their annual returns just like every other organization. But the fact that they refused to do it, inspite of it being clearly laid down in law, shows ill-intent. You can't eat your cake and have it too.
You might want to either increase the quality of your JPEG encoding or switch to a different format (GIF might work well at the sizes you're rendering). The compression artifacts from JPEG are very visible on solid-coloured areas: https://i.imgur.com/CcS7gL6.png
I'd guess for that page the technical details get fed to marketing who boil it down to whatever they think will impress people with limited (if any) technical knowledge.
I said above I didn't think this was a situation where anybody should do anything. It's 12 people in a cave. In the global context, that's noise. this is just classic news turning minor events into global news.
Interviewing expert marketers
Hi everyone, thanks for checking this out. I've been working remotely for a while, and am now trying coliving out.

I had this idea knocking about for a while to book appartments with other makers, developers etc. One of the most important parts I wanted to solve with this is to create safe community where we can meet people to colive with that are more trustworthy. Let me know if you have any thoughts about the concept, thanks!
Look at the package dependency tree of an average linux program. They are absolutely examples of "microservices" talking to each other.
Although it's insensitive, it makes sense from a legal perspective. IANAL, but I imagine it's something like:

1. paypal receives notice she's deceased, so they have to collect the remaining balance

2. the creditor must notify the client (hence the letter being addressed to her) of their account being closed, and that the full amount is due

3. the creditor must specify a reason for terminating the account, hence the "see section X of the agreement that says you have to be alive to hold an account", "...you are deceased"
Just look at the dead husks left by Apple, BMW, and Cisco!
It depends but in general I'd disagree. If the small balls of mud have all kinds of implicit dependencies, but you have to find them by searching across codebases (and languages) -- does that sound easier than finding them all in the same codebase and language? Overall, its comparing bad design to bad design. I think the main argument I'd make here is, micro-services doesn't actually solve the big ball of mud problem, it solves a completely different problem.
I'd wager that microservices, a lot of the time, are basically used as a management structure rather than for their benefits as pure tech, so less mature teams can silo themselves off and avoid communication (e.g. "I can work just on my backend image processing bit without dealing with the React guys now", "now the CTO won't be on my back so much," or whatever).

The irony being that anything approaching SOA (or microservices) requires exactly the same amount of communication. More likely they require more since it's almost certain that such a decision introduced chaos.
I tend to agree with you and I think you are being downvoted unfairly. The man was a hero for doing what he did and there should be more attention given to what he did and its impact on the outcome.
I, too, want to know the implementaion details. That said I’ve watched hundred of eyes gloss over as I emphatically implored lay-persons about password policies and tools like password managers and Frankly their definition of ‘secure’ can be encapsulated in ‘256-bit encryption’.

An oversight on Mozilla’s part for security-types and engineers, but maybe they have the masses in mind with this tool & it’s marketing site.
It’s basically a feature flag. I don’t like feature flags but it is a thing.

But if you are testing an artifact, why isn’t the artifact testing part of your CI process? What you want to do is no more or less an anti pattern than swapping out mock services to test a microservice.

I’m assuming the use of a service discovery tool to determine what gets run. Either way, you could screw it up by it being misconfigured.
I cooked in fine dining for 5 years. Then did 5 years in the military. Now I'm coding.

If I had to do it all over, I'd probably still do se/dev, just earlier. Sucks being behind my friends when it comes to money/homeownership/etc.

After having two careers where money wasn't great, I'm all about the money now.
Have Square or Stripe addressed letters of demand to dead people?
Amen to that. Just by curiosity, what is the barrier of entry for adding a new language in your ecosystem?
I just got a dell precision at work and had to reinstall for full disk encryption. Ended up ditching the dell distro and installing an Ubuntu 16 derived distro. Everything works fine 2 months in.
Discover how Machine Learning can be in charge of your insurance claim
Nobody fines ICANN.

A German registrar doesn't fulfill its contract with ICANN anymore. ICANN sues them at a German court to fulfill it. The court rules that the contract clause is illegal according to German law, so the registrar is not obliged to fulfill it.
One of the things that I like about the Erlang/OTP ecosystem is that it encourages you to design systems that are very modular, but does not force you to run every service as an independent entity. By designing around supervision trees of dependent services, one gains the advantages of a monolithic environment without losing the ability to split services out onto discrete nodes.

But that's an "all in" environment. You are Elixir/Erlang/OTP, or you are out. That is, understandably, not an option for many use cases.
> If you're opening the letter of the deceased person, aren't you likely the the executor of the estate anyway?

That's not a reasonable assumption in my view. Why should a widow(er) be prevented from opening their late spouse's mail, even if the executor is another person (say, their lawyer)? Should all mail be passed unopened?
Ah, I read this wrong. I thought it was look someone up and figure out who you follow whom they also follow. Would rather you call this 'reciprocals'.
Way back in the pre-Internet days, magazines often had little classified ads sections in the back. There was nearly always a couple of businesses that almost said they would send you pornography, usually for scientific and educational purposes; an offer to sell you a weather balloon or information on ham radio clubs or telescope kits; and at least one ad like this:

Make money at home stuffing envelopes! Send SASE and enclose $2.50 for our guide on how you can make money in your spare time!

And if you were foolish enough to send them the money and a SASE -- a self-addressed stamped envelope, the equivalent of an HTTP GET -- you would get a sheet of instructions, which began: "Take out an ad in a magazine telling people to send you a SASE and money. Make copies of this sheet and stuff them in the SASEs..."
It's crazy to me that there are so many moving parts to businesses like this - how do you keep it all in your head? Or are there strategies to reduce the complexity of the business problem so you don't have to keep everything in your head?
Between “database servers” and “database tables” there is another level of granularity: “database users”.
> So many times during technical discussions, I had to keep my mouth shut in the name of self-preservation.

This sounds like an issue with being able to articulate why something is or isn't going to net the expected benefits or being able to foresee unexpected risks. Keeping silent is better than throwing out silly hyperbole risks, but not bring up real risks because "they don't want to hear it" is completely bogus. Any solid engineer will bite at another potential risk to ensure they don't find themselves engineered into a corner 65% through a project. Your comment also makes it out like the notion the article is making, monolith over microserves, is gospel for every situation; that in no condition would it ever make sense to use microserves and that only naive zealots would espouse the wisdom (dogma) to use them. You can use any piece of technology poorly, that doesn't mean the core concept is flawed, just that your problem space is different than what that software is trying to solve. Consider using HDFS as a primary data store in place of MySQL where it doesn't make sense and you might cry the wisdom of wishing someone had told you HDFS is terrible and to just use the tried and true MySQL of olden days.
Yes, this. It matters if there is something tangible to be repossessed or not.
>It's worse than that; it's my observation that most microservice architectures just ignore consistency altogether ("we don't need no stinking transactions!") and blindly follow the happy path.

If two microservices have to share databases, they shouldn't be microservices.

One microservice should have write access to one database and preferably, all read requests run through that microservice for exactly the reason you mentioned.

>I've never quite understood why people think that taking software modules and separating them by a slow, unreliable network connection with tedious hand-wired REST processing should somehow make an architecture better.

If you're running microservices between regions and communicating with each other outside of the network it is living in, you're probably doing it wrong.

Microservices shouldn't have to incur the cost of going from SF to China and back. If one lives in SF, all should and you can co-locate the entire ecosystem (+1 for "only huge companies with big requirements should do microservices")

>ustomers couldn't care less, except that it now takes far longer to implement features that cross multiple services - which, if you've decomposed your services zealously enough, is pretty much all of them.

Again, that is an example of microservices gone wrong. You'll have the same amount of changes even in a monolith and I'd argue adding new features is safer in microservices (No worries of causing side effects, etc).

I will give you +1 on that anyway because I designed a "microservice" that ended up being 3 microservices because of dumb requirements. It probably could've been a monolith quite happily.
Inside and Beyond Ticketmaster: The Many Breaches of Magecart
Is the firefox lockbox for hot stocks?
$100M buys a lot of cop hours. And the cops will probably recoup their salary by writing tickets to people attempting to visit the sign. An act that is currently illegal. No special interests would be served by that. And it would not feed our city council members’ obsession with literally printing their names on everything they can.
Yes. Can these be used in cases where traditional radio systems can't be used? Like deeply submerged submarines?
This one really trips us up too. We were just talking about it yesterday actually.

I tend to:

fooA:
- bar1
- bar2
baz:
buzz

I think this is technically more correct but I just find it unintuitive to read:

fooB:
- bar1
- bar2
baz:
buzz
I venture there all the time via hiking or biking as I live near-by.

1. It gives access to an area a lot of people wouldn't / couldn't adventure to due to location and/or heat during the summer.
2. It's the journey not the destination. The view along the way would be pretty cool.
3. The observatory has very limited parking.
Reading through the code and these commits is absolutely hilarious. Beautiful piece of functional comedy.
East Germany, West Germany? North Korea, South Korea? Case studies in extremely similar starting points which both tried to industrialize from nearly the same starting point, only differing in how the markets were regulated, with wildly differing outcomes.

I imagine if someone could accurately answer your question they'd win a Nobel Prize. But there is little doubt free market economies vastly outperform centralized economies. Plus free markets are about exercising freedom over how your labor and assets are used. So yay freedom.
> 2) Patents enable business models that separate design from production. ARM and MIPS, for example, design chips incorporated into designs from myriad manufacturers.

Their designs are already protected by copyright, though.
Same way they attack SSL and other cryptographic security systems, I'd suppose.
Apple combines machine learning and Siri teams under Giannandrea
Ask HN: What 'smartphone' should I get my mother?
Some background: My mom is 78, lives alone, and is very bad at technology. She has difficulty using a mouse, lost the password to her chromebook, and cannot remember where she puts the wi-fi password for the home, so currently is disconnected from the internet.

She says she wants a smartphone so that she can stay in touch with the world. I'd like to get her one so that she can keep up with news, write emails, but I want information egress to be as limited as possible (to prevent identity fraud or asset theft). Even if I tell her to never input her email address, I don't want her to click on a link that will download an app, for example.

Are there any non-obvious solutions to this? Otherwise, would IOS or Android be better? (I use Android, but consistency with me is a secondary factor)
I scored 20 (zero percent authoritarian), but I mean those were some pretty extreme and silly questions. I can't see anyone really scoring too high on a test like this who isn't completely crazy!
It's not all clipboard based - Keepass has an RPC plugin that can be used with browser extensions for Firefox and Chrome. I also use Keepass2android for (duh) Android, and while you can use copy/paste it also has a custom keyboard you can use instead.
I see more and more stirrings of similar sentiments here in America every day, too.
I love this excerpt from your link:

> the need Toyota had to start building cars in the United States, a requirement due to the possibility of import restrictions by the U.S. Congress.

So much irony.
This is nearly what I'm talking about but it requires the terminal emulator to understand the image format. I guess that makes sense for transfer efficiency, and if you want a pixel-level API you could just transfer BMPs.
Apple may acquire AgileBits (1Password)