skysight-inc/HackerNews huggingface dataset:
(have we come to some max nesting level here, cant reply to the child comment)

One db can be a problem, or a strenght depending on the domain; And I really dislike religious design, esp microservices.

I have less problems by avoiding ORMs (and religios microservice arch, or fundamentalist interpretations of rest)

Database handles the shared state in a heterogenous environment.
We need it to be centralized to keep track of money, the apps can't do that, two independent databases cant do that either. It must be one system that guarantees concistency.

It works great, there is no downtime. The interfaces are defined, the database stands alone, updates are deployed separately.
You and sol_remmy are talking about two different things. You are talking about overall expenditures in the health care system. He is talking about insurance prices charged to individual purchasers, in particular ones that are relatively young and healthy.
30 Books Recommended by Brad Feld
>This kind of reminds me how in one of the Wikileak emails, Clinton removed a country from a list of human rights violators for a mere donation.

This is just flat out wrong. There was a rumor going around that a donation got Algeria taken off of a list of state sponsors of terror.

The problem is that it was never on that list in the first place.
The Ultimate Motivation Boost for Entrepreneurs
you can always get back to what you had before unless you try really, really hard to destroy data

git reflog is your friend
HTML with great default styles and better built-in form and interactive elements (date picker, sortable tables) would be ideal. Screw CSS, it slows everything down, just have good defaults and don't let pages mess with them much. If we must have CSS at least jettison the complex parts with animation and such. Make it very, very simple and weak. No Javascript. Can't be trusted if it has the ability to initiate connections or modify form data, isn't useful enough without that to justify the added bloat to the client.

God, it'd feel lightning fast compared to what we have now. And it wouldn't be able to spy on you. A document-centric (once again) web that's somewhat less crippled than Gopher would be amazing, but we absolutely must cut out things like scripting in order to make the client trustworthy (and fast).
The odd part to me is that people forget how much you get for the measly 2% or so in fees you pay to a bank annually. You get FDIC insurance, protection against fraud, someone you can call for assistance, relative stability, ability to pay for things anywhere. With btc you get none of that, plus risk of losing your assets due to a user negligence, ignorance, hacks, sophisticated scams, or other culprits.
I've had a few cases where I accidentally removed a local change before committing it; using Time Machine you can still recover some files then. I wish more editors had built-in support for it, if you're trying to restore a local file, macOS's TextEdit has support for Time Machine.
Degraded Service, Upgrade Next Week[Kraken.com]
If you asked about the GitHub alternative, it's this: https://git.scuttlebot.io/%25RPKzL382v2fAia5HuDNHD5kkFdlP7bG...
"In all areas with phone lines there are multiple providers giving around 20Mb/s."

I don't know about the rest of the UK but I don't think that is the case in Scotland - once you are any distance from a city or town the speeds can drop dramatically and that's not even in the Highlands or Islands. Certainly when we were looking at houses about a year ago there were quite upmarket new houses in Perthshire that had no broadband at all.
They can certainly provide much better porcelain out of the box. Mercurial is at least as powerful as git, but I always joked that the learning curve between the two is something like, you read the docs for 5 mins and you'll know what the next 50 commands to type into hg. Whereas git, you spend 50 minutes reading the Pro Git book, just so you know what the next 5 commands should be.
> 2. data is erased for good because someone makes a mistake while using rebase

No. Just no. Please stop spreading FUD like it's candy. Git only deletes commits after a GC, which won't erase commits from reflog and will keep unreferenced commits for at least a month before deleting them. And rebasing generates new commits, leaving the old ones exactly how they were. If somebody lost a commit after a rebase, and nobody nearby could help them recover it, they should consider spending a few hours learning about git.

I've been using git for 4 years both at work (with a team of 40+ people) and at home, without ever having any of the problems listed here (except 3 which has nothing to do with git). It takes a few hours, maybe a few days to understand how git works and how to use it. Instead of blaming the tools, you (and your team) should probably learn how to use them.
Stop seeing countries as single coherent actors. The best thing to do is for as many governments as possible to stay out of as many people's affairs as possible.

Just because the Chinese government is stopping Alice from mapping Chinese roads doesn't mean your government should stop Bob from buying Chinese maps. Why should your government punish Bob just because the Chinese government punished Alice? Alice and Bob don't even know each other.
What GUI do you recommend? My experience has been that GUIs are the easiest and fastest way to make a mess that can't be corrected without dropping to CLI or re-cloning. (I'm looking at you SourceTree). I've long recommended that everyone who uses git know how to use the CLI even if they don't use it regularly.
Well, anything with a GPS in. The value of those devices in the West largely derives from there already being map data for them to use.
As an occasional attendant of the meetup, and a member of the related Slack, I'm pretty sure this will be an awesome event!
> I'm planning on making a hard push for git on the team I just joined

You mean a force push. `git push --force` is one of my favorite commands. I've aliased `git yolo` to `git push --force --no-verify`.
Make's concurrency is pretty good, as long as your dependency graph is correct.

Problems arise when one of your build steps creates temporary files for each invocation and they end up overwritting each other (race condition).

This would have the same issue
>I don't think it provides the most consistent UI or helpful help, though.

Understatement! Git is one of the most user-hostile tools I've ever seen. And I've used Sendmail.
> Object-oriented programming 101 assumes that all your objects are in memory, in a graph,

Yes. We insist on using this OOP style where your objects are Person, Order, Invoice, etc. Ignoring that the data is stored in tables.

But, it may not be the only way. What if your objects really are things like Tables, Records and Relationships. (e.g PersonTable, OrderTable, OrderDetailTable, etc) and your operations are whatever you can do with these tables. We are trying to abstract away something that is very real. What if we embrace it instead ?
Even Chinese prefer foreign brands to domestic ones (if they can afford it) even though almost all of those are made in china under 51-49 JVs. I’ve personally never been impressed by a chinese car that wasn’t an outright clone, well maybe those new BYD electric taxis running Beijing.

A friend of mine worked a contract with JAC once to help them...design the info-tainment system for their upbrand Audi A5 compete, which involved copying Audi’s system as much as possible then parring it back because they weren’t willing to use high end hardware in it.
F# should be best is Excel macros language. You may provide option to run Python from F#.
I presume buttermilk works as well?
> I used git in the terminal and the diffs/patches/merges/pull requests don't turn out right

Your answer there is just doing git pull --rebase by hand. I don't like that style at all, but if you must do it surely use the command that's designed for doing it.

> I pushed stupid things onto the remote server

Worth saying you can branch before fixing - that might be a little less intimidating than "access by commit ID"

> I already made my changes in multiple commits, but the repo owner wants me to rebase it to a single commit

Disagree with "you should do it", though that's probably a political question.
The sleeping giant Toyota is finally waking up. Vehicle batteries have one critical advantage over fuel cells: vehicle owners can generate their own power at home and recharge the batteries in a convenient setting. Musk came to the same conclusion, but his company Tesla may get stepped on as the giant begins to walk and then run in the same direction.
When I started working for the government (2010) it was .backup, .bak, .new, .newNEW, new-JIM, .20100910... all on one guy's workstation. Luckily Gitorious landed within months. (better than nothing)
I'm interested in collecting strategies for destroying bitcoin. Would anyone like to brainstorm?

If the resources of all governments combined were brought to bear on the problem of demolishing BTC, what would be a way to accomplish that?

Making it illegal won't work. Neither will buying it – that will just raise the price. 51% attacks aren't effective because all they can do is double-spend coins, not arbitrarily reassign wealth.
There are roughly 2000 existing companies with over a billion in sales.

That should mean, within an order of magnitude, there are thousands of billion dollar ideas/potential businesses.

Are there more than a thousand teams capable of executing on a billion dollar idea? Is this the wrong way to evaluate the space of ideas?
Ask HN: How to stop watching porn?
I am unable to focus on work. It's become a serious issue as I waste many hours watching porn.
Need some serious advice.
I don't trust GUI clients; it's easy to not be able to discern the current status, easy to just commit all changes, some of the clients don't respect the pre-push hook, and I've seen other colleagues who have no clue what they're actually doing end up mixing pull and pull --rebase, somehow managing to make duplicate commits with slightly different contents and not having a clue what's going on.

Don't use clients if you don't even understand the basic git workflows. And those usually don't support the advanced oh shit situations this article is about.
Maybe I ought to also insist I build git from source and scrub any reference to --force from it.
Are We Finally Going to Help Puerto Rico Power Up?
Like it or not, countries do exist and are the framework on which commerce is built. Bob will need to shop elsewhere and Alice will need to confront her government over their policies costing her lost sales (if she is Chinese)
I use https://github.com/kasper/phoenix It's mostly just a javascript driven utility for managing windows, but it's really easy to bash together some nice tiling. I've got it set up for os-alt-ctl-numpad (5 is fullscreen, the ordinals are half screen, and 7,9,1,3 are quarters.) and os-alt-ctl-shift-
numpad for a 3x3 grid... along with a bunch of other things i've defined.
> If that is true - which it appears to be - are the Koch brothers the only ones?

Nope. There are e.g. Tom Steyer [0], Sheldon Adelson [1] and many others, both left & right (and the Kochs aren't really 'right' anyway — they're much more libertarian than they are conservative, supporting homosexual marriage &c.). Billionaires have the same right to free speech that paupers have, but they've got rather a lot more money to spend speaking than others do. Personally, I suspect that a lot of the anti-Citizens-United animus comes from billionaires (or employees of billionaires) annoyed at the competition: they don't want poorer citizens to band together to fund political speech.

[0] https://en.wikipedia.org/wiki/Tom_Steyer

[1] https://en.wikipedia.org/wiki/Sheldon_Adelson
The curse of the 500 mile email and the car that won't start because it's allergic to vanilla icecream. ;)

- https://www.ibiblio.org/harris/500milemail.html

- http://www.cgl.uwaterloo.ca/smann/IceCream/humor.html
Have you tried this:

https://rtyley.github.io/bfg-repo-cleaner/

I've used it in the past, and it's pretty straightforward and does the job well :)
Most of these have nothing to do with git, but are true of any distributed repository. At that point, your argument becomes: distributed repositories are bad for business.

Then there's this:

> Graphic designers, writers, HTML/CSS frontenders, managers, data analysts and QA staff can’t use Git, even though they all used Subversion.

What rubbish. The features of subversion are a subset of git, and the git equivalents are easy to learn. For a svn user, there's literally only a single additional command they need to know: git push.
"I have found that when I speak, I rarely command attention and captivate as some others do. "

Be careful with that assessment. You may captivate people like others do but you may not notice. I learned that in toastmasters. I thought that everybody had checked out of my speeches after the first minute but actually people listened and liked the speech.
Upton Sinclair's "It is difficult to get a man to understand something, when his salary depends on his not understanding it." still holds true here.
That's because people write shitty makefiles. Most makefiles I see are full of improperly used double colon rules, phony targets not marked .PHONY and implicit ordering assumptions.

If `-j' was enabled by default, then it would be much harder for writers to develop these issues. But I suspect most of these authors, who are already unwilling to learn make properly would simply give up and use a different tool.
If you use Vagrant you might wind up doing all the heavy lifting in shell scripts anyway.
This seemed a great comment until the very last sentence. Are you really claiming that Congress wanted to fund the advancement of medicine globally, and they did so by banning imports of pharmaceuticals?

Surely there's simpler explanations for this that fit the facts better?
Early in the history of a repository, I committed some files with sensitive information. The only way to fix this (and similar problems) is to reconstruct the repos starting from the commit just before you committed the unwanted file(s).

I'm a bit of a git naif, there are doubtless better ways to do this. This was mine:

0. Back up my repo.
1. Save the entire commit history as patch files.
2. Use BFG (amazing tool) to scrub all references to the unwanted files [0]
3. Create new repo from the commit just before unwanted files.
4. Apply the patches.
5. Use a custom Perl script to apply the dates in the patch files to the new history. [1]

Technically, your repo will be fully reconstructed at step 4. Also, be advised the patch files themselves may have to be massaged to remove references to the file(s) in question. If the filenames themselves are not unwanted, you can add them to .gitignore for good measure.

Step 5 merely preserves the dates of the original commits. Keep in mind that for this last step, your script will have to work in reverse chronological order as the history will be altered from that point forward.

[0] https://rtyley.github.io/bfg-repo-cleaner/
[1] http://eddmann.com/posts/changing-the-timestamp-of-a-previous-git-commit/

EDIT: Swap steps 1 and 2. Add advisement that patch files may require manual alteration. Add hint regarding .gitignore. Title case "Perl".
Legal corruption is still corruption. But to fix it you have to change the system, not just enforce existing rules. And in order to change the system, you have to have a better system ready and widespread support for it. That's hard.
Researchers 3D-print WiFi-connected objects that don't need power
Yeah, filter-branch is the way to go for this. Also to for example extract a folder into a new repository. I've used it in a few cases.
The problem is that if you count monetary base and frqctional reserve inflation as well, that 2% can go up to 20% very easily.
For the most part using git is like five commands and it is definitely fast to use them from the command line if you have some sort of git understanding
In general, nothing.

For example, Chrome eats pretty much all free memory keeping tabs loaded, but surrenders it gracefully when needed. That's a great use of memory.

But for an OS, and specifically for a feature that doesn't devolve unless the user goes and manually changes it, it's obnoxious. The OS is inherently a support layer for the things the user opens by choice; I'd argue any expansion of its resource footprint ought to have a clear justification.
Writing Testable GPU Code
Assuming 2% inflation (and 0 fees and interest), you also get 81 ct purchasing power back on the dollar after 10 years.

For some people that amounts to fraud.
The reason the Web needs rescuing is because it's not a particularly well-designed system that has been patched over and over again for the last quarter century. And now it has been degraded to a delivery layer for JavaScript apps, a poor RPC protocol and an overly complex UI rendering toolkit.

It should have had protocol-level technologies for preserving historic data, for search, for offline use, for authoring and publishing. If you look closely, cloud services created tools to easily do all those things and that's how they got in control.

"The Internet was done so well that most people think of it as a natural resource like the Pacific Ocean, rather than something that was man-made. When was the last time a technology with a scale like that was so error-free? The Web, in comparison, is a joke. The Web was done by amateurs."
-- Alan Kay.

A lot of web devs were enraged by his comment without listening to the context. He was talking about the lack of protocol-level solutions for resilience of the Web.
If you're on a mac, I can't recommend Tower enough. It's a paid app but well worth the money. Otherwise Git Kraken is a foss offering that is also excellent.
I think this thread [1] along with unstable modules were convincing enough for people not to trust their production applications with an open source project that has a shaky future.

Most people who were interested in the approach moved their efforts to TrailsJS [2]

[1] - https://github.com/balderdashy/sails/issues/3429

[2] - https://trailsjs.io
Wow what a joke of a link.

You know what gets you a defined jawline?

Getting down to a legit 7% body fat. Your jaw will have no fat to hide behind.
You should just about always add at least some swap.

Anyone who thinks otherwise hasn't read much or seen very many systems.

start here:

- https://www.kernel.org/doc/gorman/html/understand/understand...

- https://www.kernel.org/doc/gorman/html/understand/understand...

- https://www.linuxquestions.org/questions/linux-kernel-70/why...

- https://kerneltalks.com/disk-management/swap-addition-in-lin...

- https://linuxaria.com/howto/linux-memory-management

- https://kernelnewbies.org/Linux_4.8#head-a0b674ff33af7e3e7b8...

- https://kernelnewbies.org/Linux_4.11#head-680ed3eee137456d6a...

- https://kernelnewbies.org/Linux_4.14#head-5327850512ba28763d...

- https://help.ubuntu.com/community/SwapFaq#How_much_swap_do_I...

- https://access.redhat.com/solutions/15244

- https://serverfault.com/a/684800/2321

- https://serverfault.com/q/329928/2321

- https://serverfault.com/q/25653/2321

- https://serverfault.com/a/825915/2321

- https://askubuntu.com/q/184217/3544

- https://antipaucity.com/2011/08/08/why-technical-intricacies...

I've been in environments ranging from a few dozen individual servers to 100s of 1000s. In companies ranging from mom-and-pop shops to international investment banks. Every last one is configured with swap. Because unless you have done all the profiling to truly know you don't need it, you should be running it.
A more positive spin is that you'll have an "ORM" that's exactly adapted to your application. Many apps (1) don't need to work with multiple DBMS types and (2) don't use even close to the full panoply of SQL features.

In a language like Java that has a generic DBMS API you can get along just fine with a few classes that handle CRUD operations and transaction management. Somebody familiar with JDBC and SQL can write the bridge classes in about a day, while keeping the overall application vastly simpler.

Either way somebody needs to make an informed choice about ORM vs. direct SQL. It seems as some people get in trouble because they skip that part of the design process.
neither AT&T nor Samsung were able to do it against MCI or Vizio. But, sure, lets pretend it is different this time.
I guess thats like the difference between money and power. Money can make things happen but true power is about getting things that can't be bought.
I don't think git will lose features, and even if they do, git's core and data model is really, really good - if you look closely, most commands are relatively simple operations on the relatively simple data model and tree structure. I'd say they'll continue the current direction, mostly adding missing features and changing the defaults to be more sane (like default push mechanics).
Is the slow tube the one that takes an hour?
Maybe it's not worth being in there because of how simple it is, but I guess it would be useful for newcomers:

# Oh shit, I've changed 200 files and want to revert to the state of this morning
$ git add . && git commit # often. Very often.
$ git reset --hard commit_id
> you only had to lift it a foot if you wanted to steal it.

Which is exactly what happens.
> I don't think the answer is nothing.

Seriously? Think about it. If you could pay, say, $100k to own all the bitcoin in the world, would that be smart or would that be stupid?

Why would anybody buy bitcoin from you if you owned all of it? Everyone will prefer to use a cryptocurrency that either: a) they already own some of; or b) a merchant is requesting; or c) they expect to go up in value more than an alternative. Now, in calculating c), everyone knows that everyone else is looking at a) and b) as well. The expectation of Bitcoin if you're the only holder is really bad.

If you like your chances at 100k, take the experiment out further. How about 1 million? 10 million? The ceiling here is super low relative to the "market cap" people are talking about.

So it's not just the buy/sell dynamics. Bitcoin doesn't have intrinsic value, and that's actually weird --- most other securities do. The most similar security is gold, which is like, 1% intrinsic value and 99% this type of speculative logic. The difference is that gold is unique --- bitcoin isn't.
> I don't think it provides the most consistent UI

That reminded a video where Linus Torvals is been interviewed and he says that if he ever have to make good UI to get out of a desert island, he would die there.
Lessons from starting and shuttering a retail tech company.
i know that some shops do nightly tape backups of the harddrive on the fileshare and consider that sufficient for version control. the theory is "developers don't have to learn a new tool and we will never lose more than one day's worth of work".

these shops don't understand the benefits version control offers when it comes to code review and maintenance patches on old versions of the software, or vendor-specific streams for your software.
Usual 'coding monkey' that is mostly copypasting 2-3 lines, thinks it is a 'programming' and thinks she is a programmer and tries to dwell on that topic -_-
About 10 seconds of searching w/ your favourite search engine would reveal the Bitcoin wiki, which has this nice document: https://en.bitcoin.it/wiki/Myths
Use Gitlab and you can at least prevent --force push with permissions.
2010. I've been following the industry since I left, and I promise you neither the physics of FN flash nor the manufacturing process has fundamentally changed since then. Nor have the true endurance numbers substantially improved. If anything the situation is worse now with smaller device dimensions. The only thing standing between your collection of cat gifs and oblivion is the flash controller making intelligent guesses about what it just read.
https://help.github.com/articles/removing-sensitive-data-fro...