cbdumas

That line would be drawn through elections, legislation, and court decisions. Decisions like the one OP was referring to [0] where the Supreme Court found that compulsory vaccination is within the state's power, and further that "[r]eal liberty for all could not exist under the operation of a principle which recognizes the right of each individual person to use his own [liberty], whether in respect of his person or his property, regardless of the injury that may be done to others."

0. https://en.wikipedia.org/wiki/Jacobson_v._Massachusetts

With that scheme an attacker who gets access to a code (no matter how old) can then generate their own going forward. The hash function here means that even if someone obtains a code they can't generate other codes.

I guess that's possible, but it's hard for me to imagine that with billions of dollars at stake they didn't even consider it. I think they made the calculation that forcing their customers and creators to use crypto would lose them even more business than banning their core product.

The fact that OnlyFans isn't even trying to move to crypto to keep their business alive is a stunning indictment of the state of crypto as a viable payment method.

A few comments here are drawing a parallel between tech companies shutting down Gab (temporarily) and payment processing companies forcing this move from OnlyFans (which from the outside looking in appears tantamount to shutting them down). Regardless of how you perceive the two specific cases, I think they make people uncomfortable because in both cases they demonstrate the power that large tech platforms have over law-abiding companies.

It seems to me that the government needs to take some of that power back from tech companies by clearly delineating which services can and cannot be refused and in what circumstances. For instance, I think it is perfectly right for Google to remove Gab from their app store if they wish, but I think it would be wrong if Gab was refused internet service by their ISP, for example. Similarly, as we transition to a cashless world I think there need to be limits on the authority that payment processors can exercise over which businesses are allowed to receive payments and which are not.

I think it's hard to find because those two preferences are in direct, irresolvable conflict.

Perhaps the "paperclip maximizer" doomsday scenario was right in was right in its broad strokes but just wrong about the agents involved? They were worried about a super-competent AI that burns resources producing low-utility widgets. In fact we have created an system (a combination of societal incentive structures and technological tools) that burns resources producing low-utility pseudo-random numbers.

Anyone listening to the sample audio linked to in the article should read this note from the last time this was discussed on HN: https://news.ycombinator.com/item?id=26309787

Summary: the Lyra audio samples are louder which muddies the comparison

I couldn't agree more. Cloudformation is a nightmare in my opinion and never should have seen public release. CDK is what Cloudformation always should have been.

I don't think the author needed to bring "false accusation" into the picture here, and in fact it weakens the point. I think male investor saying to a female CEO that her male colleague is better suited to the CEO role would be taken, ipso facto, as sexism. No falsehoods need enter the picture.

I agree completely, I've listened to the reference sample probably ten times now and I can only hear /wɪ/

All these replies telling you this isn't possible are amazing. Perhaps they are forgetting that when you hold coins at Coinbase that's no different from a bank giving you a bank note saying you "own" x amount of gold in their vault.

EDIT: I was obviously not the first to say this but it is really interesting to watch the crypo space re-invent all of modern finance, one piece at a time.

What do you see as the killer use case for crypto currency/blockchain/smart contracts, etc.? I mined a few Eth in the very early days, and hung onto it until selling recently. I sold because I couldn't convince myself they had any value not based on the "greater fool theory". Was I wrong?

The stability and ubiquity of C are probably it's biggest upside characteristics and, as you say, there is a lot to like there. But you have to admit the language is showing it's age and has some huge flaws.

To call manual memory management a foot-gun would be a ridiculous understatement. Once you've used a language with modules and namespaces, going back to C is so painful. The C standard library is super minimal and has lots of... lets call them... quirks. Basically lots of things that are easy and safe in any of the languages you mentioned are difficult and dangerous in C.

Also this bullet point under "Lawful Purposes Only":

> Acting in any manner that might subject us to unfavorable regulatory action, subject us to any liability for any reason, or adversely affect our public image, reputation or goodwill, as determined by us in our sole and exclusive discretion.

My reply was at least partially facetious as this wasn't my first exposure to Go. If you like the simplicity of Go's type system I can't argue with that, but I do think your article demonstrates the way that simplicity at the language level pushes complexity into the users code. Pick any modern statically typed language and this whole post will boil down to something like:

  data Genre = Adventure
             | Comic
             | Crime
             | ...
             deriving (Show)

I had heard that the Go type system was just annoying and too simple to be useful, and this blog post has convinced me that that is 100% true.

Exactly, and from a features standpoint Postgres can do everything Dynamo can do and so much more. I think a lot of software devs don't really know SQL or how RDBMS work so they don't know what they are giving up.

I can't speak to your specific use case, but I can tell you that a relatively small RDS instance is probably a lot more performant than you think. There is also "Aurora Serverless" now which I've just started to play with but might suit your needs.

As far as what makes Dynamo a good fit, I almost take the other approach and try to ask myself, what makes Postgres a bad fit? Postgres is so flexible and powerful that IMO you need a really good reason to walk away from that as the default.

> Designing scalable systems when you don't need to makes you a bad engineer.

> In general, RDBMS > NoSql

These two bullet points resonate with me so much right now. I'm a consultant and a lot of my client absolutely insist on using DynamoDB for everything. I'm building an internal facing app that will have users numbering in the hundreds, maybe. The hoops we are jumping through to break this app up into "microservices" are absolutely astounding. Who needs joins? Who needs relational integrity? Who needs flexible query patterns? "It just has to scale"!

Something I rarely see brought up in these articles is the difficulty of defining "data" and who would own it. If I buy something on Amazon to be shipped to me from a third party seller, which part of that transaction is data that belongs to me? To Amazon? The the third party?

The article ventures a short list: "websites visited, credit card purchases, workout routines, music streamed", but I don't see how that could ever be turned into a coherent definition. A "credit card purchase" likely involves a dozen distinct parties with their own individual role and view of the event.

SQL proficiency is something I've seen developers of all sorts neglect, which I think is a huge mistake. And relegating SQL to something that just an "analyst" does is an even bigger mistake.

Several times over my career I've been brought in on a project where the team was considering replacing their RDBMS entirely with a no-SQL data store (a huge undertaking!) because they were having "performance problems". In many cases the solution is as simple as adding an index or modifying a query to use an index, but the devs regard it as some kind of wizardry to read a query plan.

This is awesome, thanks to all contributors to this incredible tool!

This is cool, however there is an implicit assertion here that better lit = safer. As far as I can tell this is questionable at best, a decent roundup of studies can be found here https://www.washingtonpost.com/news/wonk/wp/2017/11/02/what-...

I haven't seen anyone here mention DataGrip, so here goes:

If you work with a database you should try DataGrip. It is the best client I've ever used, for every single database I've tried it with (mostly Postgres, some SQLite and Redshift as well). Autocomplete just works, it will create schema diagrams for you that are accurate and useful, it's data export tools are obvious and fast. I pay for a license personally for use on side projects, and use it at work on a daily basis.

I'm not the person you asked but I have my frontend hosted separately from the Heroku backend. CORS was a bit of a pain at first, mostly because I had never had to deal with it before, but after initial setup I never think about it.

I too was really sad to see WSL 1 be replaced by what seems to be just a built-in VM. One of the great things about WSL 1 is that I can run Linux tools on my laptop without the memory overhead of a VM. My laptop only has 8GB of ram which is not enough for Windows and a Linux VM to comfortably share, but plenty to run the Linux tooling I want under WSL 1.

On my desktop with 16GB of ram I can just run Virtualbox. WSL 2 solves nothing for me. Like the author I am very skeptical that WSL 1 will be maintained going forward but I hope it is.

IMO your assertion is validated by the excellent overview of Stack Overflow's infrastructure given here:

https://nickcraver.com/blog/2016/02/17/stack-overflow-the-ar...

Very few web apps will ever serve as much traffic as SO.

> [T]here are others who ... don’t have the need for human connection (because they get that from their family and friends) from their job, only a paycheck.

I don't have a problem with people who feel that way, but for myself I would find that very bleak given the substantial fraction of my life I am expected to spend working. Different strokes for different folks I guess.

I can't wait to go back to the office. Everything about my job is harder from home. Harder for me to focus on work, harder for me to separate work and life, so so so much harder to forge the actual human connections that make tech work feel at all worth doing.

ETA: Interesting that the above has resulted in high controversy in both up/down votes and replies. I can tell this is a very emotional issue for people. To be clear I'm not interested in forcing people to do anything, just trying to share my experiences. I would be disappointed if my job went permanently remote, and would probably start looking for a new one.